- dovecot - dovecot.org

[Dovecot] critical X-UID reordering problem after upgrade from 1.1 to 1.2
by robh＠cs.indiana.edu 23 Aug '09

23 Aug '09

We upgraded our imap server hardware and went from dovecot 1.1.3 to 1.2.3 in the process and have been having a critical problem since. I believe I've tracked it down to X-UID reordering that dovecot seemed to do to the mbox format (I know, I know...) inboxes. The problem has manifest itself in several ways with different mail clients but the general problem is that the mail clients have gotten confused about which message is which. For example, thunderbird will display the wrong information about a message in the header listing but then show the correct data in the message display window when you actually open the message. As you can imagine, this is causing all kinds of user problems. Here is a very simplified explanation of what I'm seeing. Imagine that the inbox had 5 messages with X-UID values 1, 3, 5, 6, and 9 before the upgrade. After the upgrade the X-UIDs were reordered so these same 5 messages now might have X-UID values of 1, 2, 3, 4, and 5. Thunderbird then shows the summary information like this: Subject/Sender/Date for message 1 Subject/Sender/Date for message 2 Subject/Sender/Date for message 2 Subject/Sender/Date for message 4 Subject/Sender/Date for message 3 Now, if you actually open the 5th message it shows the right message body but the summary information is for the message that *used* to have X-UID 5 (which is now the 3rd message). So, the thunderbird cache is out of sync and I can fix it by removing the .msf file for that mailbox but, as you can imagine, the prospect of getting all the users to remove their .msf/.pst/?? cache files is daunting, to say the least. I've seen discussions about similar things happening with mbox format inboxes but they all seem to be in the context of some ancient 0.xx version of dovecot with known mbox processing bugs. But, I went from a reasonably current 1.1.3 version to 1.2.3. Right after seeing the problem, I upgraded to the just released 1.2.4 but either that didn't address the problem or, if it did, the reordering damage was already done by version 1.2.3. So, my 2 questions are: 1) Anyone know why this would have happened and whether it is a dovecot problem or something I botched? I folded all the local config changes I had made to the 1.1.3 conf file into the stock 1.2.3 conf file so they should have been identical modulo changes in the distro. And, our local config changes are really minimal. 2) Is there anything I can do now other than getting all the users to remove their .msf/.pst/etc files? It sure would be grand if there was something I could do on the server side that would magically cause all the client-side caches to be invalidated. I'm hesitant to strip the inboxes of all the X-IMAPbase and X-UID lines because I'm not sure what the ramifications of that might be. Here are some other random thoughts in case they might be related: - The old server was running 32bit RHEL4 and the new one 64bit RHEL5 - I'm using the pre-built dovecot rpms from atrpms.net - The dovecot index cache is kept in /var/cache/dovecot/indexes and I did not copy that over from the old server to the new assuming it would just be rebuilt. Any and all help is greatly appreciated! --Rob =============== dovecot -n output follows ================== # 1.2.4: /etc/dovecot.conf # OS: Linux 2.6.18-128.4.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.3 (Tikanga) protocols: imaps pop3s ssl: required ssl_cert_file: /etc/mail.pem ssl_key_file: /etc/mail.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_max_processes_count: 512 max_mail_processes: 2048 mail_max_userip_connections(default): 15 mail_max_userip_connections(imap): 15 mail_max_userip_connections(pop3): 10 first_valid_uid: 200 mail_location: mbox:~/mail/:INBOX=/var/spool/mail/%u:INDEX=/var/cache/dovecot/indexes/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %v.%u lda: postmaster_address: postmaster(a)example.com auth default: passdb: driver: pam userdb: driver: passwd

3 4

[Dovecot] valid-client-cert not implemented in postfix
by Alex 22 Aug '09

22 Aug '09

Hey. I noticed that postfix doesn't support valid-client-cert. I went ahead and implemented it, for those who are interested. See attached diff. Code base: ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/postfix-2.7-20… Feedback is welcome. -- Alex

1 1

[Dovecot] Help with building sieve
by Jonathan Siegle 21 Aug '09

21 Aug '09

Am building sieve plugin on AIX. This is revision 1095:8010f1eb66b3. I see the following error when doing the build: rm -fr .libs/lib90_sieve_plugin.lax^M mkdir .libs/lib90_sieve_plugin.lax^M rm -fr .libs/lib90_sieve_plugin.lax/libsieve.a^M mkdir .libs/lib90_sieve_plugin.lax/libsieve.a^M (cd .libs/lib90_sieve_plugin.lax/libsieve.a && ar x /usr/sadmin/src/ imapservers/dovecothg/dovecot-1.2-sievepsu/src/plugins/lda-si eve/../../../src/lib-sieve/.libs/libsieve.a)^M libtool: link: warning: object name conflicts; renaming object files^M libtool: link: warning: to ensure that they will not overwrite^M Usage: uniq [-c | -d | -u] [-f Fields] [-s Chars] [-Fields] [+Chars] [Input_file [Output_file]]^M I think this is the crux of my missing notify_operation token I reported the other day. I can solve the uniq -cd problem. I don't know what libtool is trying to do there.

2 3

[Dovecot] question Thunderbird acl shared namespace
by Robert Schetterer 21 Aug '09

21 Aug '09

Hi Timo, i have shared namespace namespace shared { separator = / prefix = "shared/%%d/%%u/" location = maildir:/usr/local/virtual/%d/%%u/:INDEX=~/shared/%%d/%%u/ subscriptions = no list = children inbox = no } acls are working as expected no problem here but if i look acl rights with thunderbird to another users shared folder it reports it as domain not as user like this "this folder is shared by domain ... you have bla bla rights" if i use prefix = "shared/%%u/" tb reports "this folder is shared by user ... you have bla bla rights" checked it via telnet looks right here with prefix = "shared/%%d/%%u/" list "" "*" * LIST (\HasNoChildren) "/" "Templates" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Drafts/kkkk" * LIST (\HasNoChildren) "/" "Test" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/pppp" * LIST (\HasNoChildren) "/" "Junk" * LIST (\HasNoChildren) "/" "Trash" * LIST (\Noselect \HasChildren) "/" "shared/schetterer.com/monika@schetterer.com" * LIST (\HasNoChildren) "/" "shared/schetterer.com/monika@schetterer.com/Trash" * LIST (\HasNoChildren) "/" "shared/schetterer.com/monika@schetterer.com/INBOX" 7 OK List completed. 8 getacl shared/schetterer.com/monika@schetterer.com/INBOX * ACL "shared/schetterer.com/monika@schetterer.com/INBOX" "r" "" "robert(a)schetterer.com" akxeilprwtscd 8 OK Getacl completed. is this a known thunderbird problem is there a workaround with dovecot known ? or did i wrong tests via telnet ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 1

[Dovecot] Released Sieve v0.1.12 and ManageSieve v0.11.9 for Dovecot v1.2.4
by Stephan Bosch 21 Aug '09

21 Aug '09

Hello Dovecot users, I finally managed to make new releases of Sieve and ManageSieve for the recent Dovecot v1.2.4 release. The ManageSieve release is important to match login proxy API changes in Dovecot; older versions will not compile against the new Dovecot release. The new Sieve release first includes the new date extension, which allows matching against date values in header fields and the current date-time at script execution. Changelog Sieve v0.1.12: + Testsuite: added support for testing binaries stored on disk. + Implemented the new date extension. This allows matching against date values in header fields and the current date at the time of script evaluation. Changelog ManageSieve v0.11.9: * Adjusted to changes in the Dovecot login proxy API. This release therefore depends on Dovecot v1.2.4. + Reintroduced ability to abort SASL with "*" response. Latest ManageSieve specification includes it. The releases are available as follows: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.12.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.12.tar.gz.sig ManageSieve (package + patch): http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.9.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.9.tar.gz.s… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.4-managesieve-0.11.9.diff.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.4-managesieve-0.11.9.diff.g… Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] SASL Dovecot, Active Directory, LDAP
by Gilles Albusac 20 Aug '09

20 Aug '09

My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I would like to use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I need to use SASL Dovecot fonctionnality and ldap request. How to configure Dovecot to enable SMTP/SASL and verify login/password who are declared on a second server in Windows 2003 (Active Directory). Regards

1 0

[Dovecot] dovecot auth is case insensitive, but fs is sensitive :)
by Benny Pedersen 20 Aug '09

20 Aug '09

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo(a)example.com with a password can login with fOO(a)example.com and fOo(a)example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had horde installed dovecot 1.1.7 -- xpoint

6 7

[Dovecot] script to report quota upon user's request
by Δημήτριος Καραπιπέ ρης 20 Aug '09

20 Aug '09

Hi there is there any binary/script to repot user's quota upon request? Dimitrios Karapiperis

4 3

[Dovecot] dovecot-1.2.4, sendmail,deliver,sieve
by Jonathan Siegle 20 Aug '09

20 Aug '09

I'm trying to setup deliver as an LDA for system users. I've read http://wiki.dovecot.org/LDA/Sendmail which handles virtual users. I don't see a README for what I need. I want sendmail to accept the mail and then hand off to deliver with sieve plugin. Deliver should look in the users home directory which is found in /etc/passwd for the sieve-script to see what to do with it. If the sieve-script DNE, then just deliver to INBOX(from dovecot.conf). Any help would be appreciated. Thanks, Jonathan protocols: imap disable_plaintext_auth: no login_dir: /usr/dovecot-1.2.4/var/run/dovecot/login login_executable: /usr/dovecot-1.2.4/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h:INBOX=/var/spool/mail/%Ju/%u mail_full_filesystem_access: yes mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf mail_plugin_dir: /usr/dovecot-1.2.4/lib/dovecot/imap/ imap_client_workarounds: tb-extra-mailbox-sep imap_id_log: * lda: postmaster_address: postmaster@localhost auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5/krb5.keytab gssapi_hostname: $ALL debug: yes worker_max_count: 2 passdb: driver: pam args: max_requests=1 userdb: driver: passwd plugin: mbox_snarf: /gpfs/inbox/%Ju/%u

2 3

[Dovecot] Oops!
by Daniel L. Miller 20 Aug '09

20 Aug '09

I was testing a new webmail client - like an idiot, against my own mailbox, instead of a test mailbox (or even a separate server) - and my Inbox got wiped. Fortunately I backup our mails nightly, so I only lost a couple from today. No idea how the wipe occured - I didn't INTENTIONALLY perform a delete + purge...but it happened. Is there a way of configuring Dovecot to ensure that any delete operation specified by a client results in a "move to Trash" as a precaution? Instead of relying on the client to perform it? -- Daniel

2 1