June 2010 - dovecot - dovecot.org

[Dovecot] Thunderbird namespace handling
by Thomas Hummel 10 Aug '10

10 Aug '10

Hello, I've noticed that Thunderbird (3.0.3) seems to wrongly "repeat" the namespace prefix when selecting the top level maildir of a namesapce. It doesn't occur if "list=yes" and TB has no clue about the namespace prefix. But it seems to happen only when TB is aware of the namespace prefix, either via the NAMESPACE command (so in "hidden=no" setups) or via hard setting it up in the "Account Settings". For instance, if location = maildir:/courriel/boites/test:CONTROL=/courriel/meta/test hidden = no list = yes Trying to select the mailbox which appears as "#test" in the UI gives 4 select "#test/#test" in rawlogs, giving for the user a "Mailbox doesn't exist" error, whereas, via telnet, I can : x select "#test" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 2 EXISTS * 0 RECENT * OK [UIDVALIDITY 1271768576] UIDs valid * OK [UIDNEXT 3] Predicted next UID * OK [HIGHESTMODSEQ 3] Highest x OK [READ-WRITE] Select completed. The same happens with any combination of (hidden=, list=, "Allow Server to override [the namesapce] settings") where TB knows about the namespace. Any ideas ? Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 24

[Dovecot] IMAP IDLE, Virtual mailboxes
by Patrick Nagel 05 Aug '10

05 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, K-9 Mail (on Android) has been mentioned on this list multiple times recently, I think it's definitely an IMAP client "on the rise". :) It supports IMAP IDLE, and so brings "push mail" to Android mobile phone users. To bring this into the context of this mailing list: I guess a lot of people on this list are making use of server-side filtering (using sieve), so that mails from certain persons or mailing lists end up in the right mailboxes, right on delivery. Now, this is all great, but there are issues when server-side filtering and IMAP IDLE come together: Only one mailbox can be "watched" with one IMAP IDLE connection. So, people who have set up elaborate server-side filtering with say, 50 different sieve "fileinto" calls, will constantly have a *lot* of IMAP IDLE connections open, if they really want to get informed of any mail arriving in any of their mailboxes. Keeping those 50 IMAP connections open wouldn't cost much bandwidth, and who cares about the Internet router's connection tables getting unnecessarily big, anyway? But then there is the "problem" of a mobile phone being carried around constantly, switching physical connections (from WLAN access point 1 to WLAN access point 2 to 3G to 2G to no connection at all and back), every time needing to terminate* those 50 IMAP connections, and then establish 50 new ones (with SSL handshake overhead and all). So, all in all, not an optimal solution. *) (which does not always happen the way it should, see http://code.google.com/p/k9mail/issues/detail?id=1255) I see two ways to improve the situation (one of them quite dovecot-centric): 1) A new extension of the IMAP protocol: IMAP MULTI-IDLE, which somehow allows a client to get notified of changes to more than one mailbox within one IMAP connection. This conflicts with the basic IMAP design though, AFAIK, and is thus not likely to be feasible. 2) Enhancing dovecot's Virtual plugin, so virtual mailboxes do not only get updated on select and expunge, but also when anything changes that affects the set of messages shown in the virtual mailbox. I guess that would have an impact on performance, and thus should be optional. Let me explain the second one: With the help of the Virtual plugin, it is possible to pull all those 50 mailboxes that receive incoming mail together again, just like the INBOX of the pre-server-side-filtering times - the user could configure a virtual mailbox to show all unread mails from those 50 mailboxes. Now the mobile IMAP IDLE users could just watch that one virtual mailbox, needing only one IMAP IDLE connection. After having read the mail (directly in the virtual mailbox), it would disappear, but of course still be in the "real" mailbox, determined by the sieve filter on delivery. Patrick. - -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAku+ydsACgkQ7yMg/OiDoAXV9ACdF+BEstnjfUeJlR/JQKFf6N7n yxYAnAnuD2popWYLfZNCCtlpkAP4SQww =L33A -----END PGP SIGNATURE-----

7 19

[Dovecot] Plugin Handle input messages
by Alex Baule 03 Aug '10

03 Aug '10

Hi Timo.... I try to change my plugin to read the input email to increase a header line and one \r\n. But i need help to get this input.... My plugin is based in zlib plugin. In "static int zlib_permail_get_stream" function, have it. if (imail->data.stream != NULL || (_mail->uid == 0 && zuser->save_handler == NULL)) { return zmail->super.get_stream(_mail, hdr_size, body_size, stream_r); } I think this is the line that return the stream that is the stream sent by client. I try to change this line and put inside this IF , a call to my function to handle with the input email from client. But i got some errors about the input part. In other email, Timo said, to get the S and W flags in the email name, i need to intercept the email input from client to dovecot, in this part is done the W and S calculation. Timo, where is the part that i can get the input from client ?

2 4

[Dovecot] Mbox corruption - Inbox beginning with 'FFrom' or 'FrFrom'
by Henri Khou 03 Aug '10

03 Aug '10

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or 'FrFrom' We can temporarily fix the issue by manually editing the mailbox so that it begins with a proper 'From'. For some users, the problem reoccurred after we apply this workaround. I have to mention that this server has been running fine since almost a year with the current hardware and software configuration. Does anybody has an idea regarding this issue? Many thanks Henri ============================= System : openSUSE 11.1 (x86_64) Local FS : ReiserFS dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27.37-0.1-default x86_64 openSUSE 11.1 (x86_64) log_path: /var/log/dovecot.log syslog_facility: local7 protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_cert_file: /etc/ssl/certs/cert_742088754.pem ssl_key_file: /etc/ssl/private/imap.ehess.fr.key disable_plaintext_auth: no verbose_ssl: yes 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 login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_greeting_capability(managesieve): no mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 mail_max_userip_connections(managesieve): 10 mail_uid: mail mail_gid: mail mail_location: mbox:~/:INBOX=/var/mail/%u:INDEX=/var/run/dovecot/indexes/%n mbox_lazy_writes: no 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_plugins(default): quota imap_quota trash expire mail_plugins(imap): quota imap_quota trash expire mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib64/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_reuse_xuidl(managesieve): no pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_lock_session(managesieve): no pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): dict_db_config: /etc/dovecot/dovecot-db.conf sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam args: dovecot userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs:User quota:user:mount=/var/spool/mail quota_rule: *:storage=40M quota_rule2: INB0X:storage=250M quota_rule3: Trash:storage=20M quota_rule4: Spam:ignore quota_rule4: Sent:storage=20M trash: /etc/dovecot/dovecot-trash.conf expire: Trash 7 Spam 1 expire_dict: proxy::expire dict: expire: db:/var/lib/dovecot/expire.db

4 14

[Dovecot] Go Away Message after the first successful login on proxy server
by Tomislav Mihalicek 23 Jul '10

23 Jul '10

hello i have a dovecot 1.2.11 and i have implementation of 2 dovecot machines, one proxy one storage part. everything is working fine, i only have one question regarding the message that should go away after the first successful login on proxy server. how to remove it on proxy server? May 7 16:04:19 proxy-server dovecot: pop3-login: proxy(tmihal(a)example.com): started proxying to 192.168.1.100:110: user=<tmihal(a)example.com>, method=PLAIN, rip=192.168.22.222, lip=192.168.1.100:109 [root@dougie:/usr/local/src/dovecot-1.2-managesieve]/etc/init.d/dovecot restart Restarting DovecotIf you have trouble with authentication failures, enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork This message goes away after the first successful login. -- View this message in context: http://old.nabble.com/Go-Away-Message-after-the-first-successful-login-on-p… Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] [dovecot] Dovecot Migration so far
by Mark Moseley 20 Jul '10

20 Jul '10

We've been doing our own beta testing of Dovecot 2.0-beta4 IMAP (both direct IMAP and webmail-fronted), and we've had nothing but glowing compliments from our beta users/victims. I've also been running a lone box with the latest mercurial build and that's been running just fine too. All mail data is on NFS, but I've put indexes on the local disk, which has worked just dandy so far. Everything's been great and all I've seen amiss are a few random problems -- all of which are are barely impacting us and I mention only for the sake of feedback. All boxes are Debian Lenny i386, running 2.6.33.1. One oddity is that I see lots of messages like this (I've obfuscated paths/IPs/usernames, so assume paths are all actually correct) for a variety of different mailboxes prior to their indexes directory getting initially created: Apr 02 13:25:24 imap(mail@box): Error: creat(/var/tmp/Indexes/14/75/mail(a)box/dovecot.mailbox.log) failed: No such file or directory Judging by the mtimes of the containing directories, the directory was created a couple of seconds after the error gets logged, so I'm guessing mailbox_log_alloc is just getting called too early. It obviously just happens that first time. Doesn't seem to actually be hurting anything, that I can tell. One other kind of weird thing I saw was that originally I had my indexes on a dedicated partition with ext4 (Debian Lenny, i386, 2.6.33.1), I was seeing scattered messages like this: Mar 29 18:02:38 imap(mail@box): Error: FETCH [] for mailbox INBOX UID 3244 got too little data: 1116 vs 1087383 Mar 29 18:02:38 imap(mail@box): Error: Corrupted index cache file /var/tmp/Indexes/12/dc/mail(a)box/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 3244 The message corresponding with UID 3244 was around 1116 bytes (+32 bytes, IIRC), so no clue where the 1087383. In all the cases of that error I saw, the lefthand number of bytes was very closer to correct and the righthand was way way off, and the S= flag in the filename was correct too. I'm guessing that the random righthand number was just due to corrupted cache. When I reformatted that partition as ext3, the error went almost completely away (just a few total over the past few days, as opposed to a few per hour when it was on ext4). I don't even have an educated guess as to why that'd happen. A wild guess would be that ext4's delayed allocation was causing problems. Even under ext4, it was still pretty rare and only, say, 1 out of 100 imap logins. And ext3 performance on the indexes partition so far has been just fine, so I don't plan on switching back to ext4 -- though if anyone has any experience with putting indexes on reiserfs and/or xfs versus ext3, I'd love to hear your thoughts. I've also seen a couple of these in the past few days (on beta4, not repo version -- haven't been running repo version long enough to say if it'd do the same): Mar 31 21:52:54 imap(mail@box): Error: fdatasync(/mail/username/mail@box/Maildir/dovecot-uidlist) failed: Input/output error Mar 31 21:52:54 imap(mail@box): Error: Raw backtrace: /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77c0b71] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77c0bef] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(i_error+0) [0xb77c0ea8] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x9a9) [0xb7837ca9] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x56) [0xb7837d56] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index_begin+0x51) [0xb78734d1] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb78716eb] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_force+0x4d) [0xb78719bd] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_uidlist_lookup+0x96) [0xb7877646] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb787215a] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x7f0) [0xb78729d0] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0 [0xb78715b6] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0x162) [0xb7871b92] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x39) [0xb7815759] -> dovecot/imap [mail@box 215.108.28.102 UID](imap_sync_init+0x54) [0x805efa4] -> dovecot/imap [mail@box 215.108.28.102 UID](cmd_sync_delayed+0x223) [0x805f2a3] -> dovecot/imap [mail@box 215.108.28.102 UID](client_output+0xb6) [0x8056de6] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0 [0xb77d5d4a] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xb77cd1d5] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0xb77cc220] -> /opt/dovecot-2.0.beta4/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xb77b9e1a] -> dovecot/imap [mail@box 215.108.28.102 UID](main+0x1c5) [0x805f8e5] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xb764d455] -> dovecot/imap [mail@box 215.108.28.102 UID] [0x804e621] Mar 31 21:52:54 master: Error: service(imap): child 4500 killed with signal 6 (core dumps disabled) In 4 days of beta testing with a fair number of users, I've seen maybe 4 of these backtraces total, so not exactly a big issue. These are all super minor things. Everything's been fantastic so far.

3 6

[Dovecot] dovecot 2.0.beta6 dies when I try to delete a folder with thunderbird
by Sven Kirmess 16 Jul '10

16 Jul '10

When I try to delete a folder with Thunderbird 3.1 I get the following log entry and the folder is not deleted. Filesystem is ZFS. Jun 27 15:32:36 azati dovecot: [ID 583609 mail.error] master: Error: service(imap): child 18215 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Jun 27 15:32:36 azati dovecot: [ID 583609 mail.error] master: Error: service(imap): child 18213 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) # 2.0.beta6: /etc/opt/dovecot/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc zfs first_valid_uid = 100 mail_location = mdbox:/l/dovecot/%u/dbox namespace { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } service imap { vsz_limit = 1073741824 } ssl = required ssl_cert = </etc/opt/dovecot/dovecot/certs/dovecot.pem ssl_key = </etc/opt/dovecot/dovecot/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes

2 11

[Dovecot] Ok, I've given up
by Chuck McManis 15 Jul '10

15 Jul '10

Sigh, In the interest of moving forward on this project I've given up trying to get Dovecot to support mailboxes, rather I've tweaked around in qmail and had it deliver into a mail directory on a disk, that isn't NFS mounted. That got me past the various locking complaints and "operation not supported" on home directories that were mounted from the NetApp filer. Going as vanilla as possible I've managed to both send an email that qmail delivered and fetch the email with my 3 test clients (Eudora, Thunderbird, and Evolution) (I know they are, in a sense, all variations on a theme but MUA monoculture seems to be inevitable these days). So a few questions for the other esteemed system operators here if you know the answer I'd love to hear it. Question 1) Are my user's passwords safe from prying eyes? First, part of this effort was to move off of an APOP infrastructure into something more secure against password eavesdropping. To that end I've configured Dovecot with simply: protocols = pop3 service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } Note that there is NO port = 110 listener and yet Dovecot seems to listen there anyway. My question, can I be sure that it is not accepting non-SSL based connections? Attempts to use plaintext on 110 were rebuffed so that seems to be the case. My intent is that if my user is using this in an airport they won't give away their email password to a bad guy who is sniffing all the packets. Question 2) Is there any way to run dovecot from tcpserver ? One of the things I like is the program tcpserver. I like it because I can simply "not allow" large chunks of the internet to connect at all to certain ports. (I use this for SSH in particular since all the kids love throwing dictionary attacks around). I'd like to give my POP3 ports equivalent protection. I also like the logging facilities of the supervise / multilog service. To use this I'd need Dovecot to accept the connection handed to it, and not do the whole setsid daemon thing since tcpserver will start another one if needed. I can send the logging out to stderr (thanks!) and get the logging stuff but still wondering about the 'hand you a connection.' --Chuck

11 22

[Dovecot] Thunderbird and shared mailboxes
by Keith Edmunds 08 Jul '10

08 Jul '10

I'm setting up shared mailboxes as in http://wiki.dovecot.org/SharedMailboxes/Shared, and have set ACLs as described on that page to share one folder of user A's mailbox with User B. However, I'm struggling to get Thunderbird for userb(a)example.com to read the shared folder of usera(a)example.com. Has anyone done this? Thunderbird 3.0, Dovecot 1.2.11 Thanks, Keith

2 10

[Dovecot] Thunderbird problem
by Frank Bonnet 08 Jul '10

08 Jul '10

Hello Some users had occasionally a problem with Thunderbird , some random emails with attachement(s) cannot be read anymore the email appears empty and TB seems to enter in an infinite loop saying it is downloading the message The only solution I found was : 1 - stop thunderbird on the client machine 2 - remove the .imap user's directory 3 - restart thunderbird on the client machine After doing that all emails re-appear normally and attachements are readable/downloadable again. ALL our clients use the IMAP(S) protocol. Anyone had the same problem ? Thanks F

19 61