- dovecot - dovecot.org

[Dovecot] No 'from' in messages
by Remy Zandwijk 06 Mar '05

06 Mar '05

Hi all, Over the weekend, we've migrated our old mail environment to Sendmail and Dovecot: - Dovecot 1.0 stable - Sendmail 8.13.3 - Procmail 3.22 Procmail is MDA for Sendmail and it delivers mail to Maildir boxes. Email clients like Eudora, Thunderbird, Outlook and mutt are working OK. When using Outlook Express and Pine however, in the message list the 'from' or 'sender' field is empty. This means users of these programs cannot see who did send the mail to them. When running Dovecot 0.99 in a early test period, this problem did not occur. Question: Did anyone see this behaviour before and how to fix it? Best regards, Remy Zandwijk

2 4

[Dovecot] Dovecot 1.0-stable .deb file?
by Ian R. Justman 06 Mar '05

06 Mar '05

Hi, all. I know that there's no official Dovecot 1.0-stable .deb, given Timo's recommendations. However, does anyone have even an "unofficial" deb of it for, say, Sarge? I want to use 1.0's ability to use both mbox and maildir; the latter is very helpful for dealing with mailing lists. Thanks in advance for any help. --Ian.

3 2

[Dovecot] Password scheme overides
by Andrew Hutchings 06 Mar '05

06 Mar '05

I notice in the wiki you can have password sceme overides (such as {PLAIN}password). Would this work with the password fields in SQL databases (as it isn't clear in the wiki or conf file)? Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 06 Mar '05

06 Mar '05

In my original email I noted that the directory /usr/local/etc was in the dovecot.conf variable valid_chroot_dirs : valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib Is that not sufficient? Under the /var/run/dovecot directory the directories ./usr/local/etc exist with dovecot-pgsql.conf in. Is there some big RTFM item I'm missing here? -Matthew P.S. - email address changed due to problems with upstream, will jump back as soon as this is fixed so I can finish my migration :) On Sat, 2005-03-05 at 09:06 +0100, Gunter Ohrner wrote: > Am Samstag, 5. März 2005 05:27 schrieb Matthew J. Harmon: > > I have dovecot (+ssl) configured on debian in a chroot with > ^^^^^^ > > I've never run dovecot chrooted, but... > > > The file exists, and permissions look good: > > root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf > > ...let me guess, you're not in the chroot here? > > So, how should dovecot be able to find this file while it runs chrooted? > You need to put all needed files into the chroot. > Yep, that's how it's with 0.99.x. With 1.0-tests however Dovecot opens > the dovecot-pgsql.conf before chrooting. --- Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root at alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root at alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root at alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

1 0

[Dovecot] Still having problems deleting messages through IMAP
by Doug Eubanks 05 Mar '05

05 Mar '05

Hello, I am using SquirrelMail with the 1.0 releases, and I have even backed up to the latest stable release based on 1.0. I am using MailDirs. When I delete a message, the message still shows up in the message list until either I log out and back in or a new message arrives in that folder. Any ideas? Thanks Doug Eubanks doug(a)simflex.com The speed of time is one-second per second.

2 1

[Dovecot] fd_send broken pipe
by Mike Foley 05 Mar '05

05 Mar '05

Hi, I'm trying to move from UW-IMAP to Dovecot. This is on a RedHat 7.3 system and I'm using the Dovecot RPM from Dag Weirs site. dovecot-0.99.13-1.0.rh7.rf.i386.rpm http://rpmfind.net/linux/RPM/dag/redhat/7.3/i386/dovecot-0.99.13-1.0.rh7.rf… When I start up Dovecot, I get the following: dovecot: Dovecot starting up Feb 28 01:41:54 yelofsrv dovecot: Auth process died too early - shutting down Feb 28 01:41:54 yelofsrv dovecot: child 13724 (auth) returned error 127 Feb 28 01:41:54 yelofsrv imap-login: fd_send(-1) failed: Broken pipe I'm just trying to do a simple PAM/passwd type login. No MySQL/LDAP/PGSQL stuff. I've Googled till the cows came home (almost literally. I was up till 2am last night searching) and can't seem to find a straight answer. Any help/pointers? thanks, mike

2 1

[Dovecot] compile dovecot with mysql support
by Jefferson Campos 05 Mar '05

05 Mar '05

Hello! Is not possible to compile dovecot 0.99.14 version with mysql4, the dovecot configure scripts not detect the mysql4 libs. I already installed the mysql libs and devel packages... --with-mysql doesn't work! Any help or suggestion? Thanks, Jefferson

2 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 05 Mar '05

05 Mar '05

Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root@alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root@alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root@alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root@alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

3 2

[Dovecot] mbox or maildir?
by Brian Read 04 Mar '05

04 Mar '05

I am using dovecot in an SMEServer (aka e-smith), and recently backed-up on one system and restored on another system the imap email directories. The trouble was that dovecot "guessed" the mail type wrongly, and I ended up with "empty" ~/Mail directories (did it create or populate these?), and full, but ignored ~/Maildir directories for every user. Could someone point me to the chapter and verse of how (and when) dovecot decides which type of mail is in use, and how you can change the decision. I tried editing /etc/dovecot.conf, but that didn't seem to make any difference. Using dovecot 0.99-10 under a Redhat 7.3 base on kernel 2.4.20-18.7 -- Cheers Brian http://www.abandonmicrosoft.co.uk

3 3

[Dovecot] Dovecot response to "FETCH" command
by Alex Tang 04 Mar '05

04 Mar '05

Hi folks. I just converted my site from UW+mbox to dovecot+maildir (stable-test59, 2005/02/25). For the most part, everything is great. The server seems faster and less memory intense than the UW server (this part has made me very happy). And it's definitely more user friendly to me than Courier. There is one thing however... A few of my users are using the web based mail reader (Squirrelmail-1.2.11) that i provide for them. Once i converted to dovecot, the squirrelmail users were reporting that when viewing the folder list page, 2 things were happening: * The date for all of the messages was being displayed as "Sun 4:00 pm" * all messages were shown as being "new". they never would be transferred into the "Seen" state. After doing some IMAP protocol sniffing, i found this difference in the way that the UW server and the dovecot server handles the "FETCH" command... Squirrelmail issues a FETCH command to get message header information like this (lines broken with backslashes for readability): A009 FETCH 1:1 (FLAGS RFC822.SIZE INTERNALDATE BODY.PEEK \ [HEADER.FIELDS (Date To From Cc Subject X-Priority \ Content-Type)]) The UW server returns: * 1 FETCH (FLAGS () RFC822.SIZE 710 \ INTERNALDATE "27-Feb-2005 23:50:42 -0800" \ BODY[HEADER.FIELDS ("DATE" "TO" "FROM" "CC" "SUBJECT" \ "X-PRIORITY" "CONTENT-TYPE")] {153} Date: Sun, 27 Feb 2005 23:50:42 -0800 From: root <root(a)scorchedearth.us.proofpoint.com> To: altitude(a)scorchedearth.us.proofpoint.com Subject: asdf When the same FETCH response is returned by dovecot, the response looks like this: FLAGS () RFC822.SIZE 3358 INTERNALDATE "27-Feb-2005 07:55:27 -0800") * 1 FETCH (BODY[HEADER.FIELDS (DATE TO FROM CC SUBJECT X-PRIORITY CONTENT-TYPE)] {205} Date: Mon, 28 Feb 2005 00:04:22 +0800 From: xxx xxx <xxx(a)xxx.com> To: dovecot(a)dovecot.org Content-Type: text/plain; charset=UTF-8; format=flowed Subject: [Dovecot] "not listening" notification I noticed that in the UW response, the "* 1 FETCH ..." is the first line, and contains all of the data except for the message header info. However, in the dovecot response, the data is split into 2 lines, and the first line is not the "* 1 FETCH" line. In reading through the squirrelmail source, squirrelmail is not recognizing this as a valid response, and thus the date, size, and flags are not being properly set in the internal squirrelmail message objects. This explains why both the date as well as the "seen" status of the message is never properly set. OK, after all this blabbing on...here's my question. Is the data being sent back by dovecot a valid response? My knowledge of the IMAP protocol is weak to say the least. I tried reading the IMAP RFC (3501), in particular section 6.4.5 which defines the FETCH command), and the RFC seems to specify that the response should have the "* # FETCH" lines come first. However, the RFC seems vague, and i didn't wade through any of the other RFCs out there. I figure it is legal, since the two other clients i've used seem to understand it just fine (thunderbird/mozilla, mutt). However, could this be the reason why mozilla/thunderbird sometimes gets the message size wrong (and hence why the "tb-negative-fetch" workaround is needed). For now, i'll bang on squirrelmail to support the response sent by dovecot. Thanks. ...alex...

3 4

[Dovecot] hanging imap... and users getting other users' emails!
by Josh Burley 03 Mar '05

03 Mar '05

Hi All, We recently upgraded from UW (boy, starting to sound like a broken record, eh?)... Two problems: 1. Every two or three days users are unable to access their email via IMAP. It seems that it's because dovecot-auth has hung. Has anyone seen anything like this? 2. (the really serious one)... one of our users, "angie" has twice had her Outlook download other users' email! Once as another user, "helene", and just now as "mkarlin". The first time she got 800 of helene's email, and just now, about 30 of mkarlin's.... from our log, I noticed: Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core pop3-login: Login: angie [::ffff:68.231.223.128] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Our server setup: Fedora Core 3. dovecot-0.99.13. OpenLDAP, and dovecot auth'ing off PAM (mostly default setup, using Mailbox, and mail/ as a subdir). Any ideas? Any more debug info I can supply? .josh

4 10

[Dovecot] Is Dovecot SMP and thread-safe?
by Peter Franck 03 Mar '05

03 Mar '05

Josh´s problem report reminds me of other multi-CPU issues. Just a guess, Peter

5 5

[Dovecot] selective POP3 user
by Barry Kwok 03 Mar '05

03 Mar '05

I want to know if it is possible to limit some users to use POP3 service only in a server running BOTH IMAP and POP3 service. In other words, some users can choose IMAP or POP3 and some users can only use POP3. Barry

3 2

[Dovecot] Several issues with 1.0-stable
by Remy Zandwijk 03 Mar '05

03 Mar '05

All, We have Dovecot 1.0-stable deployed in our 3000 users environment as of last weekend. Up untill now, I have 3 issues: - When stopping Dovecot with: kill -TERM `cat /var/run/dovecot/master.pid`, the 'dovecot' process itself dies, the 'imap-login' processes die, but the 'imap' processes (there are a lot of them) don't die, but become a zombie. I think the way I stop Dovecot is the way to do it. The zombies can be killed by doing a 'pkill -9 imap', but that's not quite elegant. - Dovecot is running in a Solaris 9 environment. It turned out that Dovecot crashes when more then 256 filedescriptors are being used. This is rather normal, since Solaris only support 256 descriptors per 32-bit process. After starting Dovecot, I do a 'plimit -n 8192, 8192 `cat /var/run/dovecot/master.pid`, which allows Dovecot to have 8192 filedescriptors. Timo, is it possible to introduce a config file option to configure the number of descriptors? - Pine and Outlook users don't see the adresses or names of the people who sent them email. In my email yesterday, I said I remembered that tests with Dovecot 0.99 showed no problems. Today, I installed both Dovecot 0.99 and 1.0-stable on my test box. It turned out that 0.99 indeed works OK and that 1.0-stable is the problem. The user mailboxes are 'Maildir'; we do not use mbox format. I like to see this problem being fixed..... We have 2 namespaces in our setup: the default namespace and a namespace which location is set to ~/.Mailstorage. When not using a prefix in the email client setup, users can make new email folders in the default namespace and the 'Mailstorage' namespace. We want users only to create mail folders in the Mailstorage namespace, not in the default namespace. Questions: - Is it possible to force a prefix to clients? - If not, is it usefull to have an option in the namespace configuration that allows or disallows the creation of mail folder? If so: consider this as a feature request. Thank you for reading, best regards, Remy Zandwijk Free University of Amsterdam The Netherlands

2 1

[Dovecot] Newby Question
by Troy Bull 03 Mar '05

03 Mar '05

Hello I just setup my IMAP server and everything works great, except for 1 small detail. I am upgrading from uwashington's imap server, and in theirs I had to put a directory "mail" in for the imap folder (this is on the client). The problem I have is with dovecot this makes an extra level (I think). So on my server ~/mail is where the mail folder is located, but when the client puts in the "mail" for the imap server directory dovecot looks in and creates folders in ~/.mail/mail. This is a problem for me because I have many clients and I would have to go reconfigure each one. My question is this, is there a way to make dovecot look in ~/ so that when combined with the imap folder from the client it ends up in ~/mail? I hope that is clear enough, I was thinking maybe I need to set default_mail_env, but i have no idea to what? Thanks in advance Troy

2 1

[Dovecot] Trigger getmail via mail-client action?
by Gert Brinkmann 03 Mar '05

03 Mar '05

Hello, I want to use dovecot on my private debian/unstable-system to have the advantages of an IMAP-Server (Access to mails from different computers, Simply changing the mail client). I decided to use dovecot, because I very often have read (in the web) that it should be more simple to configure than other servers. Now I have the following question: I want to use getmail to retrieve mails from my provider's pop3-server. I do have a dial-up-connection that is not online permanently (I do not have a flat rate). I could start a script on ppp's ip-up that periodically invokes getmail and on ip-down to kill it again. But I would prefer to invoke getmail only when I really want it to be run. The ideal solution for me was to invoke getmail when the "Get Mail"-Button of the mail client is pressed. Is this possible? Perhaps there is something like a connection- or refresh-trigger in dovecot? Thank you, Gert

4 5

[Dovecot] Dovecot started by inetd
by Peter Franck 03 Mar '05

03 Mar '05

Is anyone else starting dovecot by inetd on the list? I'm unable to get it running, stupid me. I need help by someone more experienced. Peter

2 1

Re: [Dovecot] Too many open files, etc.
by Remy Zandwijk 28 Feb '05

28 Feb '05

> a few days ago I switched out UW-server installation to > dovecot 0.99.14 (Solaris 9). There were a few client issues, > but mostly the migration was ok. > > But I have still some questions/problems: > > +) dovecot-auth: ... PAM: pipe() failed: Too many open files > I increased the max. number of open files. Is this normal > behaviour, that more than 512 open files are needed ? Martin, we're dealing with the same problem right now. We are using dovecot 1.0 stable and we migrated last weekend. 32-bit processes in Solaris 9 have 256 filedescriptors avail- able. This seems a bit to small. Using this command to get the number of file descriptors used by dovecot: ls -1 /proc/`cat /var/run/dovecot/master.pid`/fd | wc In our enviroment this is currently around 390. You can limit the number of file descriptors per process in Solaris 9. After starting Dovecot, we issued the command: plimit -n 8192,8192 `cat /var/run/dovecot/master.pid` This gives Dovecot 8192 filedescriptors. HTH, Remy

1 0

[Dovecot] UID inserted in the middle of mailbox
by Nicolas STRANSKY 28 Feb '05

28 Feb '05

I'm seeing these with latest 1.0-stable : Feb 27 16:48:12 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (176 > 150) Feb 27 16:49:58 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (4409 > 4237) Feb 27 16:50:04 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (7122 > 5116) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (15571 > 14535) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (16578 > 14535) Feb 27 16:50:19 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (23318 > 13713) -- Nico L'étude approfondie de la nature est la source la plus féconde des découvertes mathématiques. -+- Joseph Fourier -+-

2 1

[Dovecot] Protect some mailbox to remove
by FireFly 25 Feb '05

25 Feb '05

I've installed dovecot 0.99.14 (maildir, postfix, RHEL3) and I would like to create , for every user, 4 mailbox (in skel): mail-sent, spam, virus-alert and sysadm. Procmail, parsing header mail, will move mails into a specific mailbox. Every users could move, delete, read these mails but they must not delete mailbox folder (such as INBOX mail). Thanks in advance, Francesco __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Dovecot] APOP
by Steven Stern 25 Feb '05

25 Feb '05

I want to turn off POP3 and use POP3S in its place. So far, it's working well for Outlook and Thunderbird. But I'm running into problems with Agent: It supports APOP but not POP3S. Is there a way to have Dovecot support APOP authentication on a normal POP3 connection? I'm running 0.99.13 on Fedora Core 3. -- Steve

2 1

[Dovecot] A few words about NFS please?
by Jeff A. Earickson 25 Feb '05

25 Feb '05

Hi, Could you say a few words about Dovecot and POP/IMAP to an NFS mounted filesystem? I thought I saw on the dovecot webpage that NFS is "no way" with 0.99 and "maybe" with 1.x. I was looking for the FAQ and couldn't find it. My setup is like so: My mail server is a Solaris 9 system, running sendmail/procmail, and qpopper POP. Mail is stored in mbox format. The /var/mail filesystem is NFS exported to another Solaris 9 system that runs UW-IMAP. The user community also has login access to this second system, so there are also local email clients like Pine and emacs using the NFS /var/mail. So, POP and sendmail/procmail accesses /var/mail locally, while UW-IMAP accesses it via NFS. The user community has been warned to do either POP or IMAP, but not both. There are very few problems with this setup. I would like to use Dovecot for both POP and IMAP on the two machines. I know NFS is frowned upon, but this has worked for me. Comments and suggestions, please? Jeff Earickson Colby College

4 3

[Dovecot] Inotify
by Nicolas STRANSKY 25 Feb '05

25 Feb '05

Hi, Is there any plans to use the Linux inotify, which is a major improvement over dnotify ? (Linux mechanism for communicating filesystem events to user space) Regards, -- Nico Écrivez dans l'ivresse, mais relisez-vous à jeun. -+- André Gide (1869-1951) -+-

2 1

[Dovecot] Authentication woes
by woollettg 25 Feb '05

25 Feb '05

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability completed. Authentication failed. no mechanism available Security strength factor: 0 mercury:/etc/dovecot# Below is my configuration file for version 0.99-14.1 on a Debian Sarge box I'm quite happy with plaintext auth for now. Any help or suggestions much appreciated. Graeme ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc/dovecot # --localstatedir=/var --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. login_executable = /usr/lib/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location imap_executable = /usr/lib/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_passdb = passwd #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by auth_userdb above. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5"

3 2

[Dovecot] Re: Problems with MySQL/PAM authentication
by KATOH Yasufumi 25 Feb '05

25 Feb '05

> I'm using (or trying to at least) a combination of PAM/passwd and MySQL > authentication: : (snip) > MySQL authentication works without problems but authentication real > (system) users dosn't: : I have similar problem using Multiple Auth Database: auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } I tested: | % telnet localhost 143 | Trying 127.0.0.1... | Connected to localhost. | Escape character is '^]'. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 NO Authentication failed. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | Connection closed by foreign host. "kato(a)harp.gr.jp" is registered in /etc/dovecot/passwd. First time it failed, but success at second time. "auth local" works without problem. | Feb 24 11:19:24 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(virtual): userdb(kato(a)harp.gr.jp,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:19:33 tara dovecot: IMAP(kato(a)harp.gr.jp): mkdir(/home/kato(a)harp.gr.jp/Maildir/cur) failed: Permission denied | Feb 24 11:19:33 tara dovecot: imap-login: Login: kato(a)harp.gr.jp [127.0.0.1] | Feb 24 11:19:35 tara dovecot: auth(local): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:19:35 tara dovecot: child 14884 (auth) killed with signal 6 I rewritten dovecot.conf and tested. The result is different. auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } At this time, "auth virtual" work, and "auth local" doesn't work. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | * OK Dovecot ready. | 1 login kato password | 1 NO Authentication failed. | 1 login kato password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. (kato is system user) | Feb 24 11:28:52 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(local): userdb(kato,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:28:59 tara dovecot: imap-login: Login: kato [127.0.0.1] | Feb 24 11:28:59 tara dovecot: auth(virtual): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:28:59 tara dovecot: child 14924 (auth) killed with signal 6 It is not worked well to write configuration previously, but worked well to write after. I tested with ldap auth instead of paswd-file auth. I got same result. Env: Plamo Linux 4.01 (kernel 2.6.10, glibc 2.3.2) dovcot-1.0-test62, dovecot-stable-20050222 -- karma @ jazz.email.ne.jp / Y.KATOH Sorry for my poor English.

2 2