- dovecot - dovecot.org

[Dovecot] Problem with 1.2 and sieve: failed with unsuccessful implicit keep
by Julien Danjou 09 Jul '09

09 Jul '09

Hi, First, thanks for this awesome piece of software. I've just upgraded to latest dovecot, aka 1.2. I've a problem. I've started using Sieve, and everything works fine, I already received a thousand of mails without any problem. However, there's one mail which is stuck in the postfix queue because of that: Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): mkdir_parents_chown(danjou.info/jd/) failed: Permission denied (euid=8(mail) egid=8(mail)) Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): copy: i_stream_read() failed: No such file or directory Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): sieve: msgid=? <1186f9b5-0529-4622-8f4a-58462f9a4bcb(a)svr-exchange.siege.ldlc.com>: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2009-07-08 18:47:51] Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): read(mail, uid=1) failed: Permission denied Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): sieve: msgid=? <1186f9b5-0529-4622-8f4a-58462f9a4bcb(a)svr-exchange.siege.ldlc.com>: failed to store into mailbox 'INBOX': BUG: Unknown internal error Jul 8 18:47:51 prometheus dovecot: deliver(jd(a)danjou.info): sieve: script /var/mail/sieve/jd(a)danjou.info.dovecot.sieve failed with unsuccessful implicit keep IMHO, the bug is around the uid stuff. the read(mail, uid=1) seems very wrong. since this uid is not used at all in the configuration file. I can provide more information if needed, just ask. dovecot 1.2 Debian GNU/Linux 5.0 (lenny) CPU amd64 FS is ext3 # dovecot -n # 2007 pts/0 19:27:38 # 1.2.0: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-1-amd64 x86_64 Debian 5.0.2 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s managesieve ssl_cert_file: /etc/ssl/private/ssl.naquadah.org.crt ssl_key_file: /etc/ssl/private/ssl.naquadah.org.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login first_valid_uid: 8 last_valid_uid: 8 mail_privileged_group: mail mail_location: maildir:/var/mail/vmail/%h mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: user: mail passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: mail group: mail plugin: sieve: /var/mail/sieve/%u.dovecot.sieve Anonymized mail attached. The From line was manually added, mainly because I extracted the content from the Postfix queue. (I'm not subscribed.) Cheers, -- Julien Danjou // ᐰ <julien(a)danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // Life is life. Lalalalala.

2 9

[Dovecot] System users, mbox format and global ACLs
by Axel Luttgens 08 Jul '09

08 Jul '09

I need some help here... ;-) I'm experimenting with global ACLs, but just fail to understand very basic behaviors. So, before digging into the source code, I would really be delighted if someone could immediately point a mistake I'm making and miserably overlooking. The output of dovecot -n is provided at the end of this email. Just in case, conforming to the suggestion made in http://wiki.dovecot.org/ACL , I've specified a CONTROL directory; but I get a similar behavior without it. As far as the acl plugin is concerned, I've just specified a directory for global ACLs; whether that directory is populated or not doesn't seem to have an impact on the observed behavior. Here's the structure of the test user's home directory: total 0 drwx------ 4 testuser people 136 26 jui 13:52 . drwxr-xr-x 3 root admin 102 19 mai 16:56 .. drwxr-xr-x 4 testuser people 136 28 jui 17:09 _mailboxes drwxr-xr-x 2 testuser people 68 28 jui 17:07 _mboxesctrl ./_mailboxes: total 96 drwxr-xr-x 4 testuser people 136 28 jui 17:09 . drwx------ 4 testuser people 136 26 jui 13:52 .. drwx------ 3 testuser people 102 19 mai 17:02 .imap -rw------- 1 testuser people 48685 25 jui 16:58 inbox ./_mailboxes/.imap: total 0 drwx------ 3 testuser people 102 19 mai 17:02 . drwxr-xr-x 4 testuser people 136 28 jui 17:09 .. drwx------ 5 testuser people 170 23 jui 18:02 INBOX ./_mailboxes/.imap/INBOX: total 88 drwx------ 5 testuser people 170 23 jui 18:02 . drwx------ 3 testuser people 102 19 mai 17:02 .. -rw------- 1 testuser people 1376 23 jui 18:02 dovecot.index -rw------- 1 testuser people 26624 28 jui 10:23 dovecot.index.cache -rw-rw-rw- 1 testuser people 10284 25 jui 17:57 dovecot.index.log ./_mboxesctrl: total 0 drwxr-xr-x 2 testuser people 68 28 jui 17:07 . drwx------ 4 testuser people 136 26 jui 13:52 .. I've tried various combinations of permissions and ownership, again without any obvious influence. The manual creation of directory ~/_mboxesctrl/.imap doesn't seem to be more helpful. So, let's go to the heart of my "problem": # telnet 127.0.0.1 imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. a1 login testuser ****** a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in a2 list "" * * LIST (\NoInferiors \UnMarked) "/" "dovecot-acl-list" * LIST (\HasNoChildren \UnMarked) "/" "INBOX" a2 OK List completed. a3 logout * BYE Logging out a3 OK Logout completed. Connection closed by foreign host. And indeed, a file named "dovecot-acl-list" has now been created under the _mailboxes directory: ./_mailboxes: total 96 drwxr-xr-x 5 testuser people 170 28 jui 17:11 . drwx------ 4 testuser people 136 26 jui 13:52 .. drwx------ 3 testuser people 102 19 mai 17:02 .imap -rw-r--r-- 1 testuser people 0 28 jui 17:11 dovecot-acl-list -rw------- 1 testuser people 48685 25 jui 16:58 inbox This is the only file to have been created consecutively to the telnet session. Is such a file supposed to be created there? If yes, why? I would have tended to believe that it is more a server internal matter than a name having to appear in the namespace. More generally, is such a file supposed to be created at all? After all, the configuration doesn't explicitely mention per-mailbox ACLs at all... Anyway, this is what gets written in mail.log for the whole telnet session: dovecot[82305]: auth(default): new auth connection: pid=82374 dovecot[82305]: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=49879 resp=<hidden> dovecot[82305]: auth-worker(default): pam(testuser,127.0.0.1): lookup service=imap dovecot[82305]: auth-worker(default): pam(testuser,127.0.0.1): #1/1 style=1 msg=Password: dovecot[82305]: auth(default): client out: OK 1 user=testuser dovecot[82305]: auth(default): master in: REQUEST 8 82327 1 dovecot[82305]: auth(default): passwd(testuser,127.0.0.1): lookup dovecot[82305]: auth(default): master out: USER 8 testuser system_groups_user=testuser uid=2001 gid=2001 home=/Volumes/ALMbpSpare/ People/a/testuser dovecot[82305]: imap-login: Login: user=<testuser>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot[82305]: IMAP(testuser): Loading modules from directory: /usr/ local/dovecot-1.2.rc7/lib/dovecot/imap dovecot[82305]: IMAP(testuser): Module loaded: /usr/local/ dovecot-1.2.rc7/lib/dovecot/imap/lib01_acl_plugin.so dovecot[82305]: IMAP(testuser): Effective uid=2001, gid=2001, home=/ Volumes/ALMbpSpare/People/a/testuser dovecot[82305]: IMAP(testuser): acl: No acl_shared_dict setting - shared mailbox listing is disabled dovecot[82305]: IMAP(testuser): mbox: data=~/_mailboxes:INBOX=~/ _mailboxes/inbox:CONTROL=~/_mboxesctrl dovecot[82305]: IMAP(testuser): fs: root=/Volumes/ALMbpSpare/People/a/ testuser/_mailboxes, index=, control=/Volumes/ALMbpSpare/People/a/ testuser/_mboxesctrl, inbox=/Volumes/ALMbpSpare/People/a/testuser/ _mailboxes/inbox dovecot[82305]: IMAP(testuser): acl: initializing backend with data: vfile:/usr/local/etc/dovecot-acls dovecot[82305]: IMAP(testuser): acl: acl username = testuser dovecot[82305]: IMAP(testuser): acl: owner = 1 dovecot[82305]: IMAP(testuser): acl vfile: Global ACL directory: /usr/ local/etc/dovecot-acls dovecot[82305]: IMAP(testuser): acl vfile: file /usr/local/etc/ dovecot-acls//.DEFAULT not found dovecot[82305]: IMAP(testuser): Namespace : Using permissions from / Volumes/ALMbpSpare/People/a/testuser/_mailboxes: mode=0755 gid=-1 dovecot[82305]: IMAP(testuser): acl vfile: file /usr/local/etc/ dovecot-acls/.temp.ALMbp.local.82375.f9efcb24711711fb not found dovecot[82305]: IMAP(testuser): acl vfile: file /Volumes/ALMbpSpare/ People/a/testuser/_mboxesctrl/.imap/.temp.ALMbp.local. 82375.f9efcb24711711fb/dovecot-acl not found dovecot[82305]: IMAP(testuser): acl vfile: file /usr/local/etc/ dovecot-acls/INBOX not found dovecot[82305]: IMAP(testuser): acl vfile: file /Volumes/ALMbpSpare/ People/a/testuser/_mboxesctrl/.imap/INBOX/dovecot-acl not found dovecot[82305]: IMAP(testuser): acl vfile: file /usr/local/etc/ dovecot-acls/dovecot-acl-list not found dovecot[82305]: IMAP(testuser): acl vfile: file /Volumes/ALMbpSpare/ People/a/testuser/_mboxesctrl/.imap/dovecot-acl-list/dovecot-acl not found dovecot[82305]: IMAP(testuser): Disconnected: Logged out bytes=23/431 Why does the server seem to expect to find a temp file under ~/ _mboxesctrl/.imap? As well as, more surprisingly, under /usr/local/etc/ dovecot-acls? In a word: Some bad configuration of mine? Or some bug somewhere? Or do I just don't understand ACLs as implemented by dovecot? TIA, Axel # 1.2.rc7: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 imap ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap-login login_executable(pop3): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ pop3-login first_valid_uid: 2001 mail_location: mbox:~/_mailboxes:INBOX=~/_mailboxes/inbox:CONTROL=~/ _mboxesctrl mail_debug: yes mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable(default): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap mail_executable(imap): /usr/local/dovecot-1.2.rc7/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.2.rc7/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /usr/local/dovecot-1.2.rc7/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.2.rc7/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.2.rc7/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: debug: yes passdb: driver: pam args: * userdb: driver: passwd plugin: acl: vfile:/usr/local/etc/dovecot-acls

2 5

[Dovecot] Problem with sieve and german umlauts
by M. Bobkiewicz 08 Jul '09

08 Jul '09

Dear list, I?m running a postfix (2.5.6) / Dovecot (1.1.11) on a Centos 5.2 box. I?ve written a small gui application to simply create Out of Office replys with sieve. The resulting code did work with maildrop without any problems. Now sieve fails when it meets any german umlauts like ä or ü. It just stops compiling the scripts and complains about the missing "};". A simple fix is to just replace the umlauts, but that doesn?t meet the expectations of my users. Is there any escape code I could use or any way to place the mail text outside the script? Best regards, Mike

3 2

[Dovecot] expire plugin with 1.2 cronjob undefined symbol: capability_string
by Robert Schetterer 08 Jul '09

08 Jul '09

Hi, sorry if this asked twice, i ve searched the list and found some equal posts, but couldnt get my problem fixed with it if running cronjob with expire ( using mysql ) i get dovecot -c /etc/dovecot/dovecot.conf --exec-mail ext /usr/lib/dovecot/expire-tool --test Info: Loading modules from directory: /usr/lib/dovecot/modules/imap Info: Module loaded: /usr/lib/dovecot/modules/imap/lib01_acl_plugin.so Error: dlopen(/usr/lib/dovecot/modules/imap/lib02_imap_acl_plugin.so) failed: /usr/lib/dovecot/modules/imap/lib02_imap_acl_plugin.so: undefined symbol: capability_string Fatal: Couldn't load required plugins someone tips how to fix it ? perhaps problems relate to mail_location settings? dovecot --version 1.2.rc8 -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] mbox format and UIDVALIDITY
by Axel Luttgens 08 Jul '09

08 Jul '09

My base concern may be illustrated with the help of that simple telnet session: # telnet 127.0.0.1 imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. a1 login testuser ****** a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in a2 list "" % * LIST (\NoInferiors \UnMarked) "/" "Sent" * LIST (\HasNoChildren \UnMarked) "/" "INBOX" a2 OK List completed. a3 create new1 a3 OK Create completed. a4 create new2 a4 OK Create completed. a5 select new1 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] a5 OK [READ-WRITE] Select completed. a6 select new2 * OK [CLOSED] * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] a6 OK [READ-WRITE] Select completed. a7 unselect a7 OK Unselect completed. a8 delete new1 a8 OK Delete completed. a9 delete new2 a9 OK Delete completed. a10 logout * BYE Logging out a10 OK Logout completed. Connection closed by foreign host. During the whole telnet session, both files "new1" and "new2" remained empty (i.e. no pseudo-message written to them), no uidvalidity-related helper file seems to have been created and no uidvalidity-related function seems to have been called. And clearly, both mailboxes "new1" and "new2" have received the same UIDVALIDITY. Those UIDVALIDITYs appear to be persistent; messages may be added to and deleted from those mailboxes, those mailboxes may be renamed... their UIDVALIDITY remain unchanged and equal to 1. In fact, any additional mailbox is created with that unique and persistent UIDVALIDITY of 1. Is this supposed to behave that way? (note that I quickly tried with dovecot 1.1.16 and could observe the same behavior) TIA, Axel # 1.2.rc7: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 imap ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap-login login_executable(pop3): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ pop3-login mail_max_userip_connections(default): 4 mail_max_userip_connections(imap): 4 mail_max_userip_connections(pop3): 10 first_valid_uid: 2001 mail_location: mbox:~/_mailboxes:INBOX=~/_mailboxes/inbox:CONTROL=~/ _mboxesctrl mail_debug: yes mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable(default): /usr/local/dovecot-1.2.rc7/libexec/dovecot/ imap mail_executable(imap): /usr/local/dovecot-1.2.rc7/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.2.rc7/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/dovecot-1.2.rc7/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.2.rc7/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.2.rc7/lib/dovecot/pop3 pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: debug: yes passdb: driver: pam args: * userdb: driver: passwd

2 5

[Dovecot] Wrong credential caching
by Ralf Hildebrandt 08 Jul '09

08 Jul '09

A user logged in with a captial "L" for his username: Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): lookup Jul 7 12:30:31 postamt dovecot: auth(default): shadow(Loser,10.47.64.227): unknown user Jul 7 12:30:31 postamt dovecot: auth(default): cache(Loser,10.47.64.227): miss Jul 7 12:30:31 postamt dovecot: auth-worker(default): pam(Loser,10.47.64.227): lookup service=dovecot Jul 7 12:30:31 postamt dovecot: auth-worker(default): pam(Loser,10.47.64.227): #1/1 style=1 msg=Password: Jul 7 12:30:33 postamt dovecot: auth-worker(default): pam(Loser,10.47.64.227): unknown user Then I told him that he's supposed to use an "l" instead of "L" but: Jul 7 12:42:01 postamt dovecot: imap-login: Login: user=<loser>, method=PLAIN, rip=10.47.64.227, lip=141.42.4.250, TLS Jul 7 12:42:02 postamt dovecot: auth(default): client in: ... Jul 7 12:42:02 postamt dovecot: auth(default): cache(Loser,10.47.64.227): hit: Jul 7 12:42:02 postamt dovecot: auth(default): cache(Loser,10.47.64.227): User unknown Jul 7 12:42:02 postamt dovecot: auth(default): cache(Loser,10.47.64.227): hit: Jul 7 12:42:02 postamt dovecot: auth(default): cache(Loser,10.47.64.227): User unknown Jul 7 12:43:50 postamt dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<Loser>, method=PLAIN, rip=10.47.64.227, lip=141.42.4.250, TLS: Disconnected I think the auth cache may work case-insensitive, thus making the "User invalid" response for "Loser" also valid for "loser" (which is the valid and correct username!) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 2

[Dovecot] Dovecot 1.2rc7 / Sieve Plugin problem / Namespaces
by reg9009 08 Jul '09

08 Jul '09

Hi, I've got a problem with Dovecot 1.2rc7 and a Sieve script which should store eMails in a subfolder. It always fails with Jun 28 14:56:43 deliver(): Error: sieve: msgid=<4A47687D.30903(a)some.domain>: failed to store into mailbox '': Invalid mailbox name Jun 28 14:56:43 deliver(): Error: sieve: script /home/dovecot/sieve/info/dovecot.sieve failed with unsuccessful implicit keep This is with dovecot-libsieve. Same happens with cmusieve, though the message is slightly different: Jun 28 14:55:39 deliver(): Info: cmusieve: Executing script /home/dovecot/sieve/info/dovecot.sievec Jun 28 14:55:39 deliver(): Info: sieve runtime error: Keep: Generic Error Sieve script: if header :comparator "i;ascii-casemap" :contains "X-Spam-Level" "*****" { fileinto "INBOX/Junk"; stop; } I tried "INBOX.Junk", "Junk", etc., but no success. Namespace section in dovecot.conf: namespace private { separator = / prefix = INBOX/ inbox = yes #hidden = yes #list=yes } Same configuration works with cmusieve and Dovecot 1.1.16. I assume some problems with the namespace separator. Anyone got any ideas or got sieve running with namespace separator "/" and prefix "INBOX"? Regards, Sebastian

2 4

[Dovecot] Bug in MEMORY INDEX ? [v 1.1.16]
by Joel A. Chornik 08 Jul '09

08 Jul '09

When setting a CONTROL directory that does not exists (has to be created by dovecot upon first login) AND INDEX=MEMORY Dovecot POP3 will fail upon first login with 'Couldn't init INBOX: Internal error occurred. Refer to server log for more information.' Temporary fix seems to work fine patching dovecot-1.1.16/src/lib-storage/index/maildir/maildir-util.c ---- 98a99 > unsigned int k = 0; 105c106,109 < dirs[i++] = mail_storage_get_mailbox_index_dir(box->storage, --- > > /* Only create index folders if index is not MEMORY */ > if(!mail_index_is_in_memory(mbox->ibox.index)) > dirs[i++] = mail_storage_get_mailbox_index_dir(box->storage, 107c111,113 < i_assert(i == N_ELEMENTS(dirs)); --- > else k++; > > i_assert(i == N_ELEMENTS(dirs)-k); ----- Tested only on dovecot 1.1.16 Regards, Joel A. Chornik ELSERVER.COM

2 1

[Dovecot] readdir and rename don't mix; patch included
by Mike Abbott 08 Jul '09

08 Jul '09

Enclosed please find a patch to dovecot-1.1.16 that fixes a common problem we see under load on Mac OS X and HFS+. The symptom is that sometimes readdir() returns EINVAL. The problem is that readdir() and rename() don't mix well, and maildir_scan_dir() renames messages from new/ to cur/. The solution I chose is just to retry scanning the directory, since code to rescan is already present. An alternative solution would be to read the entire directory first, then process the contents; that is, to do all the readdirs before any renames. The patch is like Apple's previous ones, all tagged with /*APPLE*/ and formatted to simplify our merges. Please reformat it as you desire. It should also apply easily to 1.2.0. --- dovecot-1.1.16/src/lib-storage/index/maildir/maildir-sync.c 2009-05-20 16:42:49.000000000 -0500 +++ dovecot/src/lib-storage/index/maildir/maildir-sync.c 2009-07-07 19:50:37.000000000 -0500 @@ -354,7 +354,8 @@ return -1; } -static int maildir_scan_dir(struct maildir_sync_context *ctx, bool new_dir) +static int maildir_scan_dir(struct maildir_sync_context *ctx, bool new_dir, + bool final) /* APPLE */ { struct mail_storage *storage = &ctx->mbox->storage->storage; const char *path; @@ -486,6 +487,11 @@ } } + /* APPLE - rename can cause readdir to fail with EINVAL; force + quiet rescan unless this is the final such rescan already */ + if (errno == EINVAL && move_count && !final) + move_count = MAILDIR_RENAME_RESCAN_COUNT + 1; + else /* APPLE reduce code deltas */ if (errno != 0) { mail_storage_set_critical(storage, "readdir(%s) failed: %m", path); @@ -772,7 +778,8 @@ that new/ dir is checked as well. it's a good idea anyway. */ unsigned int count = 0; - while ((ret = maildir_scan_dir(ctx, TRUE)) > 0) { + while ((ret = maildir_scan_dir(ctx, TRUE, + count == MAILDIR_SCAN_DIR_MAX_COUNT)) > 0) { /* APPLE */ /* rename()d at least some files, which might have caused some other files to be missed. check again (see MAILDIR_RENAME_RESCAN_COUNT). */ @@ -783,7 +790,8 @@ return -1; if (cur_changed) { - if (maildir_scan_dir(ctx, FALSE) < 0) + if (maildir_scan_dir(ctx, FALSE, + FALSE) < 0) /* APPLE */ return -1; }

2 1

[Dovecot] GSSAPI cross-realm fixed
by Bryan Jacobs 08 Jul '09

08 Jul '09

Attached is a patch which in my environment (Linux/Heimdal 1.2.1) fixes cross-realm GSSAPI authentication. Changes it makes: 1. When using krb5_kuserok, do not call gss_compare_name to check that authn_name and authz_name are the same. Instead, make TWO calls to krb5_kuserok, one for each ID. If both IDs are acceptable, allow the login. 2. Disable checking that the name is a GSS_KRB5_PRINCIPAL_NAME, as this doesn't appear to be always the case for the authz_name. If I create a .k5login listing both username@REALM1 and username@REALM2, and make that file follow the appropriate security restrictions (world read, user only write permissions), this lets me use GSSAPI logins with principals from either REALM1 or REALM2. This leaves untouched the behavior in the case where krb5_kuserok is not available. Bryan Jacobs

2 3