- dovecot - dovecot.org

[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