- dovecot - dovecot.org

[Dovecot] Warning, newbie!
by Pete 17 Mar '05

17 Mar '05

Greetings All, I am a Postfix/Courier-IMAP user and am interested in Dovecot. I have install Dovecot via FBSD ports. I have got to the part where I can telnet in to the server. -bash-2.05b$ telnet 192.168.1.61 143 Trying 192.168.1.61... Connected to 192.168.1.61. Escape character is '^]'. * OK dovecot ready. x login pete testing * BAD [ALERT] Plaintext authentication is disabled, but your client sent password in plaintext anyway.If anyone was listening, the password was exposed. x NO Plaintext authentication disabled. x logout * BYE Logging out x OK Logout completed. Connection closed by foreign host. -bash-2.05b$ I am afraid I dont know what to do from here. Anyone care to assist me? Thanks, -- Pete http://milneweb.com http://nomorevirus.com

2 1

[Dovecot] 1.0-test65
by Timo Sirainen 17 Mar '05

17 Mar '05

http://dovecot.org/test/ If dovecot-auth was crashing with you, this release should fix it. I don't know when it did though, I just applied a patch from Andrey Panin with that description :) Fixed also another dovecot-auth crash with Solaris and maybe some other systems. Contains the first attempt of a Dovecot LDA. It's still in pretty ugly shape, but it should work, more or less. I wouldn't recommend using it in production yet. There are two ways to use it: 1. As a normal user. The username is taken from passwd. 2. Giving -d <username> option. This connects to dovecot-auth and requests the uid, gid, home, etc. from it. dovecot-auth's master socket is expected to be in /var/run/dovecot/auth-master but you can override this with -a parameter. To actually create the auth-master socket you'll need to add this inside auth { .. } : socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 } } Dovecot LDA also currently needs dovecot-lda.conf file. Everything that is read from it is just dumped into environment variables internally. You should be able to set pretty much all the same settings in there as exists in dovecot.conf. The most important exception is that instead of default_mail_env there's just "mail". Example dovecot-lda.conf would be: # note that namespaces aren't supported yet.. mail = mbox:~/mail:INBOX=/var/mail/%u mbox_read_locks = flock mbox_write_locks = flock # EOF All this goes away once I get the config process implemented. The actual usage goes something like: /usr/local/libexec/dovecot/deliver -d username < mail_file ie. the mail is read from standard input. Any suggestions if the "deliver" name should be changed and maybe moved to /usr/bin/? Another large change is that I created dynamically growing array implementation with possibility to do compile time type checking. The old code was using buffer_t for arrays, but that got pretty ugly. I changed most of those in lib-index/ to the new array API. I'd be happy if someone changed the rest of them since it's pretty boring and time consuming job :) See lib/array.h for explanation how it works. And finally a small advertisement: http://mjr.iki.fi/texts/patentfund

2 1

[Dovecot] corruption and errors in dovecot-stable
by Nicholas Riley 17 Mar '05

17 Mar '05

Hi, We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10) a few days ago and have been seeing many errors and one corrupted mailbox so far. Almost everyone uses mbox format, and most users primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well as accessing the mailboxes locally with Mutt, and have not noted any visible problems. There have been several of these messages: dovecot: Feb 21 11:40:06 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (5308 > 1151) dovecot: Feb 21 22:57:13 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (6458 > 1151) dovecot: Feb 22 08:37:03 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/reportlab-users (5162 > 3812) Others: dovecot: Feb 22 11:44:17 Error: IMAP(njr): file mbox-sync-parse.c: line 221 (parse_x_uid): assertion failed: (!ctx->sync_ctx->sync_restart) dovecot: Feb 22 11:44:17 Error: child 19931 (imap) killed with signal 6 dovecot: Feb 25 06:26:09 Error: IMAP(kbode): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) dovecot: Feb 25 06:26:09 Error: child 83423 (imap) killed with signal 6 (I think this refers to the mailbox that was corrupted) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Corrupted transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: Extension record update update without intro prefix dovecot: Feb 25 12:30:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: marked corrupted dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Lost transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Feb 25 12:39:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1108933119 != 1109356120) I am currently reinstalling 0.99.14, but it would be nice to be able to switch to a 1.0-derived version again - we have to run two copies of 0.99.x to get what we want. If there is any additional testing I can do to help fix these problems, please let me know. Thanks, -- Nicholas Riley <njriley(a)uiuc.edu> | 4111 Siebel Center Department of Computer Science | 201 N. Goodwin Ave. and Medical Scholars Program | Urbana, IL 61801-2302 Univ. of Illinois at Urbana-Champaign | +1 217 244 2274

3 4

[Dovecot] Minor documentation bug with 0.99.14
by John Peacock 16 Mar '05

16 Mar '05

The sample dovecot-example.conf contains these lines: > # 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. Included doc/mkcert.sh can be used to easily generate self-signed > # certificate, just make sure to update the domains in dovecot-openssl.cnf > #ssl_cert_file = /etc/ssl/certs/dovecot.pem > #ssl_key_file = /etc/ssl/private/dovecot.pem but the aforementioned doc/mkcert.sh contains these lines: > CERTFILE=$SSLDIR/certs/imapd.pem > KEYFILE=$SSLDIR/private/imapd.pem either the script should be changed to reflect the sample config file or vice versa. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

2 1

[Dovecot] Problems with Outlook 2002 SP3 & Dovecot 0.99.13 Redux
by Md 16 Mar '05

16 Mar '05

Hi, I posted this question a while back and didn't get much response. Since then, I've done a bit more experimenting and wonder if someone can help me move forward towards resolution. The orignal question... > I'm running Dovecot0.99.13 on Fedora Core 3 and things work fine when using either > Thunderbird 1.0 or Outlook Express as IMAP clients. Outlook (2002 SP3) on the other hand > runs incredibly slowly, or just outright hangs. I've discovered that if I delete and recrete .../Maildir in the user account such that the directory exists but is empty, then outlook seems to behave. If on the other-hand, I try to create a folder, with outlook, outlook will hang and the folder won't be created. If I create the folder with another client and then go back to using outlook, outlook will hang. I've taken some network traces and have annotated them here... Starting with an empty "Maildir" Time Source Destination Protocol Info 8.515435 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 8.516056 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 8.516539 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 8.516733 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 8.594634 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 8.640521 192.168.73.3 192.168.73.1 IMAP Response: + idling 8.640709 192.168.73.1 192.168.73.3 IMAP Request: DONE 8.640983 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 8.641165 192.168.73.1 192.168.73.3 IMAP Request: 0003 LIST "" "" 8.641315 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\Noselect) "." "" 8.642387 192.168.73.1 192.168.73.3 IMAP Request: 0004 LIST "" "INBOX" 8.642956 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\HasNoChildren) "." INBOX 8.657424 192.168.73.1 192.168.73.3 IMAP Request: 0005 LSUB "" "*" 8.657925 192.168.73.3 192.168.73.1 IMAP Response: 0005 OK Lsub completed. 8.660627 192.168.73.1 192.168.73.3 IMAP Request: 0006 IDLE 8.660973 192.168.73.3 192.168.73.1 IMAP Response: + idling Now try to create a sub-folder using outlook: 0.000000 192.168.73.1 192.168.73.3 IMAP Request: DONE 0.000587 192.168.73.3 192.168.73.1 IMAP Response: 0006 OK Idle completed. 0.000910 192.168.73.1 192.168.73.3 IMAP Request: 0008 IDLE 0.001113 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs. Killing outlook and starting it again gives this trace: 5.110260 192.168.73.1 192.168.73.3 TCP 1953 > imap [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460 5.111826 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 5.112139 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 5.112600 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 5.112798 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 5.127237 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 5.135355 192.168.73.1 192.168.73.3 IMAP Request: 0002 IDLE 5.137334 192.168.73.3 192.168.73.1 IMAP Response: + idling 5.138060 192.168.73.1 192.168.73.3 IMAP Request: DONE 5.138273 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 5.138505 192.168.73.1 192.168.73.3 IMAP Request: 0004 IDLE 5.138646 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs again. Any ideas or help would be greatly appreciated. Thanks, Md

2 1

[Dovecot] imap-login zombies
by Robin Breathe 16 Mar '05

16 Mar '05

Running dovecot-0.99.13 on Solaris9/Sparc with ~25k users, we are having regularly recurring problems with large numbers imap-login/pop3-login drones, cycling on poll(). Over the course of 1-2 days, the number of such processes slowly rises to >1000, exhausts resources, and necessitates that dovecot be restarted (having killed all current active and zombie child processes). Nothing of interest seems to be logged with the possible exception of a reasonably high number of aborted logins (~10/hour). Can anyone offer any guidance as to how to track down this bug and help get it resolved? Any help would be much appreciated, as we would very much like to see this resolved in the 0.99 branch. Regards, Robin

2 1

[Dovecot] dovecot-auth hangs with IO leak
by Alan Tam 16 Mar '05

16 Mar '05

Hi dovecot, I am using the debian dovecot packages on a system running LDAP. My /etc/pam.d/common-* looks like this, which simply means try /etc/passwd first, and try LDAP using the same password if it is failed. account [success=1 default=ignore] pam_unix.so account required pam_ldap.so use_first_pass account required pam_permit.so auth [success=1 default=ignore] pam_unix.so auth required pam_ldap.so use_first_pass auth required pam_permit.so session [success=1 default=ignore] pam_unix.so session required pam_ldap.so use_first_pass session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_permit.so When many LDAP users login, /var/log/auth.log shows many (expected) error like: (note "pam_unix") Feb 3 18:16:15 eta dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=127.0.0.1 Feb 3 18:16:19 eta dovecot-auth: (pam_unix) check pass; user unknown After recent upgrades from probably 0.99.10 to 0.99.13, these lines begin to appear in /var/log/mail.log: Feb 3 16:31:00 eta dovecot-auth: Login process has too old (123s) requests, killing it. Feb 3 16:31:00 eta dovecot-auth: Login process has too old (124s) requests, killing it. And some more like this, which shows the problem: Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (13) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (14) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (15) The problem can be solved by changing /etc/pam.d/dovecot to: auth required pam_ldap.so account required pam_ldap.so session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_ldap.so This change means PAM not fail auth for /etc/passwd again. I think dovecot has some problem dealing with the pam_unix + pam_ldap configuration. Do you have any idea? I am Cc-ing this message to the corresponding bug in Debian BTS. -- Regards, Alan

2 2

[Dovecot] Bit of a Newbie Question
by Jud 16 Mar '05

16 Mar '05

Apologies in advance - I'm sure there's something quite obvious I'm not doing correctly, but since I'm unable to resolve the problem myself.... I've installed Dovecot 99.14 on FreeBSD-CURRENT using the Dovecot FreeBSD port. My "network" consists of a cable modem connected to a router which is in turn connected (only) to my computer. My ISP assigns a dynamic IP address. I have ddclient set up to sync the dynamic IP to my hostname and MX via dyndns.org. Local operations (local delivery via Postfix or copying/moving/deleting with Thunderbird) work fine. Mail delivery from remote machines does not seem to work via either IMAP or IMAP-SSL. (That is, test e-mails I send from this [Fastmail] account to my local IMAP server never reach their destination.) Enabling port forwarding on my router for ports 993 and 143 has made no difference. What should I be doing to make this work correctly? Jud

5 7

[Dovecot] Strange behaviour with moving mail
by Remy Zandwijk 15 Mar '05

15 Mar '05

Hi All, Sorry to bother you again. I am not too familiar with IMAP yet, so maybe I am asking stupid questions. Here goes anyway: In our (Dovecot 1.0-stable) setup, we have two namespaces: the default namespace, which location is '/var/mailstore/1%u/%u' and the "Mailstorage" namespace, which location is '~/.Mailstorage/'. Now we create a folder called 'Test' in the default namespace and the "Mailstorage" namespace. As far as I know this is possible and not a strange thing to do. When moving an email from the first 'Test' folder to the other 'Test' folder, it appears that everything works like expected, but when refreshing the mailbox, the message is still in the original folder. This happens with a number of different mailclients (which are configured with an empty namespace setting). I guess Dovecot doesn't look at the namespace in which the mail folder is. Is this a Dovecot bug or is this normal behaviour? Best regards, Remy B.T.W: When moving the mail, this is the IMAP conversation: 00029 UID COPY 4 TEST * 2 EXISTS * 2 RECENT 00029 OK Copy completed. 00030 UID STORE 4 +Flags.silent (\Deleted) 00030 OK Store completed.

2 3

[Dovecot] Is it possible to regenerate the index files?
by Joakim Verona 15 Mar '05

15 Mar '05

Is it possible to regenerate the index files, on other conditions than the mbox file being read? For instance, it would be nice if I could regenerate the index for a specific mbox whenever procmail delivers mail to it. If theres no existing solution, would it be possible to make a small script with something like "nc" that could send an imap command to dovecot, so that dovecot would rebuild its index for that mbox? If so, which imap command triggers an index rebuild? -- Joakim Verona www.verona.se

2 5