October 2005 - dovecot

[Dovecot] FreeBSD Ports Issues
by Barry Jeung 16 Oct '05

16 Oct '05

Installed dovecot for the first time, using the FreeBSD port. Found 2 issues with the port, and I've only been able to resolve one of them. First of all, the port, (or perhaps dovecot) does work with mysql 4.1 encryption. I had to create a user with access to the mysql table, then do 'set password = old_password('password');' in order to get dovecot to talk to the server. The second issue, is that dovecot seems to be ignoring my user_query settings. I have the following in dovecot-sql.conf: password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 125 as uid, 125 as gid FROM mailbox WHERE username = '%u' The password query works, however the user query seems to default to something else, and no matter how I change the user_query line in dovecot-sql.conf, it uses the same query. Here's an excerpt from my logs: dovecot: Oct 11 03:19:30 Info: Dovecot v1.0.alpha3 starting up dovecot: Oct 11 03:19:31 Info: auth-worker(default): mysql: Connected to (null) (postfix) dovecot: Oct 11 03:19:35 Info: auth-worker(default): sql(user(a)example.com,1.2.3.4): query: SELECT password FROM mailbox WHERE username = 'user(a)example.com' dovecot: Oct 11 03:19:35 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=5.6.7.8 rip=1.2.3.4 resp=AGJqZXVuZ0Bjb2JhbHQtaXQuY29tAHRlc3Q= dovecot: Oct 11 03:19:35 Info: auth(default): client out: OK 1 user=user(a)example.com dovecot: Oct 11 03:19:35 Info: auth(default): master in: REQUEST 1 13590 1 dovecot: Oct 11 03:19:35 Info: auth-worker(default): sql(user(a)example.com,1.2.3.4): SELECT home, uid, gid FROM users WHERE userid = 'user(a)example.com' dovecot: Oct 11 03:19:35 Error: auth-worker(default): sql(user(a)example.com,1.2.3.4): User query failed: Table 'postfix.users' doesn't exist dovecot: Oct 11 03:19:35 Info: imap-login: Internal login failure: user=<user(a)example.com>, method=PLAIN, rip=67.188.145.230, lip=209.25.157.150, TLS So obviously the query fails because that table doesn't exist. However that's not the query that I have in the configuration file. As a matter of fact, I have no idea where it's pulling that query from. Any pointers would be greatly appreciated.

4 3

[Dovecot] How to deny access from some ip or network
by Alisher Minarov 16 Oct '05

16 Oct '05

Version: dovecot-0.99.11-1.FC3.4 OS: Linux mail.server 2.6.9-1.667smp #1 SMP How I should call daemon in hosts.deny file to deny access from some ip or network? Or it can be do by dovecot itself?

5 5

[Dovecot] Dovecot on FC3 with Active Directory authentication
by Jeff Ramsey 16 Oct '05

16 Oct '05

I am building an IMAP server that uses Dovecot/Sendmail on FC3 to replace our POP server that uses Dovecot (via POP)/Sendmail on FC2. My new server is authenticating users via winbind/smb against my WIndows 2003 Active Directory. The authentication is working great. The problem come up when a user gets an email and has not ever logged into the IMAP server via SSH, local, or GDM, therefore that user has no home directory. /etc/pam.d/ssh, /etc/pam.d/login, and /etc/pam.d/gdm all have a line calling mkhomedir.so, which is using the /etc/skel home directory skeleton to create the user's home dir upon successful login, however, when I add that line to /etc/pam.d/dovecot, I get a permission denied error in /var/log/maillog. I'm assuming this is because dovecot is running as the user at this point, and therefore does not have the necessary permissions to create a folder under / home/DOMAIN/, which is where the home dir is supposed to be. If I manually create the folder, and set it's permissions, or if the user logs in via any of the before-mentioned methods, dovecot and sendmail work great. Does anyone else run a similar setup? If so, how did you overcome this problem? If not, can some Linux gurus recommend either altering the write permissions on the /home/DOMAIN directory, or should I try to call the mkhomdir app earlier in the process somehow? Any help would be appreciated. I'm trying to make this as seamless as possible. Basically, I can manually create all the home dirs well enough, but when I add a new user to the Active Directory, it would be nice if this part was automated as much as possible. Thanks, Jeff Ramsey MIS Administrator Tubafor Mill, Inc.

3 5

[Dovecot] Mapping username only for auth
by Andy Cravens 16 Oct '05

16 Oct '05

I am running Dovecot alpha 3 with authentication from the local shadow file. I'd like to change the authentication to use our radius server. I can probably do this through pam. The usernames on the mail server are set up as first initial + last name ( jdoe for John Doe ). The usernames on the radius server are the employee number. Is there a way to map the username to the employee number in dovecot before handing off the authentication to the radius server? I want the usernames on the mail server to remain first initial + last name. I don't mind maintaining a mapping file to go from username to employee number because I can automate this task. Has anybody done this?

2 1

[Dovecot] saslauthd/dovecot/root
by Andrew Instone-Cowie 16 Oct '05

16 Oct '05

Hi, I am using SMTP-AUTH over TLS with sendmail, to allow remote users to authenticate and send mail via my server, and this uses saslauthd to authenticate users. I have set up saslauthd with the "MECH=rimap" mechanism, so it uses the local IMAP server, Dovecot, for authentication. I want to do this because Dovecot is set up to use /etc/passwd for user credentials (so I don't have multiple password files to manage), and Dovecot handles restricting the range of valid UIDs (including blocking root). (Using the default MECH=shadow with saslauthd allows all users to authenticate, which I don't want) For real "normal" users, this all works fine - right password = user can relay mail, wrong password = relaying denied. So far so good. If I try to authenticate as root (which I want NEVER to work), with the wrong password, Dovecot correctly refuses to allow root IMAP access and saslauthd/sendmail denies the relay. But if I try to authenticate as root with the correct password (which I still want NOT to work!), Dovecot still refuses IMAP access, and puts this in the maillog: Oct 5 14:16:18 hadrian dovecot: Logins with UID 0 not permitted (user root) Oct 5 14:16:18 hadrian imap-login: Internal login failure: root [127.0.0.1] But saslauthd seems to treat this as a successful authentication and still allows root to relay email! So: Dovecot problem or saslauthd problem? Server is running CentOS 4.1, fully patched. Packages are dovecot-0.99.11-2.EL4.1, cyrus-sasl-2.1.19-5.EL4, sendmail-8.13.1-2. Thanks Andrew

2 1

[Dovecot] Confused
by Matt Juszczak 16 Oct '05

16 Oct '05

Hi all, I really don't know where to go from here. I've traced and pasted, but never heard responses.... I'm getting the following (see bottom of this email) in a single day of dmesg....most of the time the error message in the log file is something like: Oct 5 09:21:43 mail1 dovecot: imap(*****): file mbox-save.c: line 280 (mbox_save_init_file): assertion failed: (mbox->mbox_lock_type != F_RDLCK) Some of them also have something to do with storage space. Any ideas at all? Thanks :) Regards, Matt ---dmesg snip---- pid 20905 (imap), uid 34411: exited on signal 6 pid 42237 (imap), uid 33345: exited on signal 6 pid 42757 (imap), uid 33345: exited on signal 6 pid 43036 (imap), uid 33345: exited on signal 6 pid 41987 (imap), uid 32768: exited on signal 6 pid 99572 (imap), uid 35371: exited on signal 6 pid 99759 (imap), uid 35371: exited on signal 6 pid 49474 (imap), uid 33345: exited on signal 6 pid 82739 (imap), uid 33345: exited on signal 6 pid 67938 (imap), uid 33345: exited on signal 6 pid 68042 (imap), uid 33345: exited on signal 6 pid 68115 (imap), uid 33345: exited on signal 6 pid 68169 (imap), uid 33345: exited on signal 6 pid 68869 (imap), uid 33345: exited on signal 6 pid 72285 (imap), uid 31502: exited on signal 6 pid 98711 (imap), uid 32277: exited on signal 6 pid 99429 (imap), uid 32277: exited on signal 6 pid 36768 (imap), uid 33345: exited on signal 6 pid 38110 (imap), uid 33345: exited on signal 6 pid 38115 (imap), uid 34959: exited on signal 6 pid 53649 (imap), uid 34910: exited on signal 6 pid 53943 (imap), uid 34910: exited on signal 6 pid 70003 (imap), uid 33345: exited on signal 6 pid 23368 (imap), uid 31646: exited on signal 6 pid 59048 (imap), uid 34709: exited on signal 6 pid 59164 (imap), uid 34709: exited on signal 6 pid 59347 (imap), uid 34709: exited on signal 6 pid 13848 (imap), uid 33345: exited on signal 6

2 2

[Dovecot] Dovecot error: Unknown protocol 'imap\
by Paul E Virgo 16 Oct '05

16 Oct '05

First, thanks to Timo for the patch -- fixed missing protocol name error on my Solaris box. Now, I've moved the whole distro, part and parcel, to a Centos 4.0 Linux box, with the HOPE of getting it working there. But when I've set all of it up, I get the error message, mentioned in the 'Subject' line, in my /var/log/dovecot file. Any clues? PEV

2 1

[Dovecot] Dovecot pop3 locking up
by Neil Wilson 16 Oct '05

16 Oct '05

Hi guys and girls, I am having a problem with Dovecot. It seems like it's the dovecot auth daemon that is locking up(I'm guessing) I am running SuSe 9.3 Pro, and Dovecot 0.99.14 Everything works perfectly for a few days, and then eventually I end up with tons of what look to be "stale" processes.(I'm guessing roughly 300 like below.) 4204 ? S 0:00 dovecot-auth 24722 ? S 0:00 pop3-login 24723 ? S 0:00 pop3-login 24724 ? S 0:00 dovecot-auth 24921 ? S 0:00 dovecot-auth When I "telnet 127.0.0.1 110" I get a login, and I can type "User blabla" I get an "OK" then I type in "pass blabla" and then I don't get any response, and I have to kill my session with "Ctrl ]" and then "quit". I am using both POP3 and IMAP, but it seems to be only the POP3 daemon that dies. There are roughly 60 users on the network, and it dies after roughly 5 days of usage, and I then have to restart Dovecot by running /etc/init.d/dovecot stop and then start Any help would be appreciated. Thanks. -- Neil Wilson

2 2

[Dovecot] deliver: select destination folder
by Dominik Werder 16 Oct '05

16 Oct '05

Hello, I wanted a commandline switch within deliver to select the destination folder within an IMAP account, so I added the -f switch, heres the diff, the implementation is only "proof of concept" hehe, I didnt checked if theres any security riscs in doing this. Could we add something like this to dovecot? diff deliver.c.orig deliver.c 342c342 < const char *destination, *mail; --- > const char *destination, *mail, *folder; 355a356 > folder = NULL; 364a366,373 > } else if (strcmp(argv[i], "-f") == 0) { > /* destination folder */ > i++; > if (i == argc) { > i_fatal_status(EX_USAGE, > "Missing folder argument"); > } > folder = argv[i]; 378a388,391 > if (folder == NULL) { > folder = "INBOX"; > } > 449c462 < if (save_mail(storage, "INBOX", input) < 0) --- > if (save_mail(storage, folder, input) < 0) bye! Dominik

2 1

[Dovecot] Problem with pop3 and alpha3
by Alfonso Sparano 16 Oct '05

16 Oct '05

I don't know. I'm not tried with a real client but only with telnet. I would like to be sure that everything is correct before try with outlook/Eudora/thunderbird at all. -----Messaggio originale----- Da: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] Per conto di Andrew Hutchings Inviato: domenica 16 ottobre 2005 10.21 A: dovecot(a)dovecot.org Oggetto: Re: [Dovecot] Problem with pop3 and alpha3 On Sun, 2005-10-16 at 10:06 +0200, aspar(a)unisa.it wrote: > Hi all, I have a problem with dovecot-alpha3 and pop3 protocol (on a tru64 > 5.1a...) > > In my Maildir/cur there are 8144 mails and if I use pop3 protocol I receive in > the output 8146 line instead of 8144. The problem is that 2 mails are > duplicated . The output of "List" command is like: > > 1 51265 > 2 261783 > . > . > . > 2987 30291 > 2987 30291 (duplicated line) > 2988 16631 > .. > 4601 1231 > 4602 8921 > 4602 8921 (Another duplicated line) > 4603 1313 > . > > I've deleted dovecot.* and dovecot-uidlist in the Maildir path but the problem > remains. > > Suggest? Is a bug? > I've tried also to remove the first 1000 messages but the problem now is on the > mail number 2635 and not 1987 like I can think. > > Alfonso Is the client generating mail not found errors when this happens? If so it may be related to the problem I am seeing. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 37: "Now, with penguins, (cuddly such), "contented" means it has either just gotten laid, or it's stuffed on herring. Take it from me, I'm an expert on penguins, those are really the only two options." - Linus Torvalds

1 0