May 2010 - dovecot - dovecot.org

[Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Andrey Panin 14 Aug '17

14 Aug '17

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

[Dovecot] Sieve vacation not working
by Phill Edwards 24 Feb '15

24 Feb '15

I've been trying all night to get vacation working in my .dovecot.sieve file. The way our email works is we have one account on dovecot which serves my mail and my wife's and we use procmail and sieve to put the emails in different folders depending on who it's for. I'm trying to set up a vacation reply on my wife's email address (aaaaaaaa@optus* below) so people can update to her new address. Here's my file with the email addresses masked: require ["fileinto", "vacation"]; if address :is "to" "xxxxxxxxxxxxxxx(a)ozemail.com.au" { fileinto "Phill_OzEmail_Folder"; stop; } elsif address :is "to" "yyyyyyyyyyyyyyyyy(a)optusnet.com.au" { fileinto "Phill_Optus_Folder"; stop; } elsif address :matches "to" "aaaaaaaa@optus*" { vacation "Please update my email address to bbbbbbbbb(a)exemail.com.au"; fileinto "Sarah_Optus_Folder"; stop; } else { keep; stop; } The problem I'm having is that no auto-replies are sent. I removed .dovecot.lda-dupes and that didn't help; so then I touched it and now it's a 0 byte file and that didn't help. There is no dovecot.sieve.err file and I can't see anything in /var/log/dovecot.log which gives any message about why this wouldn't work. The emails to aaaaaaa@optus* get filed into the right folder so I know the matching is working. I've also tried a reject recipe and that worked fine, so I know that it can send an email if it chooses to. So it's a complete black box mystery as to why it just won't send a reply. Regards, Phill

5 9

[Dovecot] Auth worker max line size
by Emmanuel Dreyfus 09 Sep '12

09 Sep '12

Hello I have been playing with some exotic authentication scheme with Dovecot and PAM. That involves sending really large base64 encoded data as the IMAP password, and I have hit a line limit in Dovecot, with AUTH_WORKER_MAX_LINE_LENGTH set to 1024. This limit is especially frustrating since other parts of the software use much larger limits: MAX_INBUF_SIZE 4096 MAX_IMAP_LINE 8192 AUTH_CLIENT_MAX_LINE_LENGTH 8192 I had to make the patch attached below to get my authentication working. I can live with this local patch, but given the much more liberal limits of MAX_INBUF_SIZE at 4096 makes we wonder if this 1024 limit on AUTH_WORKER_MAX_LINE_LENGTH could not be a bug. Or is there a security concern at using more than 1kB? Opinions? (please Cc: me, I'm not subscribed ot the list) --- src/auth/auth-worker-client.h.orig 2009-06-23 18:32:15.000000000 +0200 +++ src/auth/auth-worker-client.h 2009-06-23 18:32:33.000000000 +0200 @@ -1,8 +1,8 @@ #ifndef AUTH_WORKER_CLIENT_H #define AUTH_WORKER_CLIENT_H -#define AUTH_WORKER_MAX_LINE_LENGTH 1024 +#define AUTH_WORKER_MAX_LINE_LENGTH 4096 struct auth_worker_client *auth_worker_client_create(struct auth *auth, int fd); void auth_worker_client_destroy(struct auth_worker_client **client); void auth_worker_client_unref(struct auth_worker_client **client); -- Emmanuel Dreyfus manu(a)netbsd.org

3 5

[Dovecot] dovecot 1.2.3: TB fails to unsubscribe folder after deletion
by Max Dittrich 07 Mar '11

07 Mar '11

Hi, I'm running dovecot 1.2.3 with "imap_client_workarounds = tb-extra-mailbox-sep" and noticed that after deleting a folder (moving to Trash and emptying it on exit) that folder in Trash still keeps subscribed. I think the reason for that behavior is that the call for mailbox_list_set_subscribed() in imap/cmd-subscribe.c (line 84) is fed with the original mailbox name and not the stripped version in verify_name. Assigning verify_name to mailbox in the workaround-conditional fixes this issue for me. I'm not very familiar with C programming but while tracing cmd_subscribe_full() I stumbled upon another thing. In mail_namespace_find_mask() (lib-storage/mail-namespace.c at line 413) mailbox is reassigned with a local string (not t_strduped). I think this might be a problem when mailbox is dereferenced after returning from that function?! .max

3 10

[Dovecot] Can't connect to auth server
by Phill Edwards 13 Feb '11

13 Feb '11

I'm trying to phase out procmail and move to dovecot-sieve instead. It ain't proving easy. I'll describe my setup: - Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms. - A single user account is used to store all our email (the account is called maildb). - Getmail is being used to fetch the email from various ISP mailboxes. I want to deliver mail to different folders in maildb's Maildir/ depending on who the email is addressed to (the procmail recipes currently do that). - Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb") allow_root_commands = true - When I run getmail I get this error in dovecot.log: deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a problem. I have no idea what that file should look like. As I installed from binary RPMs I would have thought one would have come with the install. Can anyone help? Regards, Phill

4 6

[Dovecot] Automatic Debian Dovecot repository now also includes amd64 binary packages.
by Stephan Bosch 04 Jan '11

04 Jan '11

Hi, I've recently significantly improved the automated Dovecot Debian package builder. At the beginning it only produced i386 binaries for Debian testing. A few weeks back I added a slave builder that builds packages for Debian stable. Today I have extended the slave builder with support for multiple architectures and I've added amd64 binaries to the repository. The master builder still builds packages for testing/i386 every hour. The slaves check for new source packages about 20 minutes later. Read the following wiki page for more information and read it carefully when you are considering to use these packages: http://wiki.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages Also, every day at four 'o clock in the morning, the latest source packages are uploaded to the openSUSE build service, which builds i386/amd64 binaries for several Ubuntu versions (experimental): http://download.opensuse.org/repositories/home:/sbosch:/ Regards, Stephan.

2 2

[Dovecot] Question about mbox_snarf and dovecot2.0
by Jonathan Siegle 18 Nov '10

18 Nov '10

Hello, I'm running revision 10622:de9d6dae7fe5 on AIX 5.3 with some local mods for our inbox hash function. I'm having a problem doing a "select inbox" when I use the mbox_snarf plugin. When I run truss on the process I see the following stat calls: 614528: kread(9, " 1 s e l e c t i n b".., 4096) = 15 614528: statx("/gpfs/inbox/14/tstem38", 0x0FFFFFFFFFFFF2F8, 176, 0) = 0 614528: statx("/gpfs/users/t/s/tstem38/IMAP//gpfs/inbox/14/.imap/tstem38", 0x0FFFFFFFFFFFED98, 176, 0) Err#2 ENOENT 614528: statx("/gpfs/users/t/s/tstem38/IMAP//gpfs/inbox/14/tstem38", 0x0FFFFFFFFFFFEDD8, 176, 0) Err#2 ENOENT 614528: statx("/gpfs/users/t/s/tstem38/IMAP", 0x0FFFFFFFFFFFEC88, 176, 0) = 0 614528: statx("/gpfs/users/t/s/tstem38/IMAP//gpfs/inbox/14/tstem38", 0x0FFFFFFFFFFFEDD8, 176, 0) Err#2 ENOENT 614528: statx("/gpfs/users/t/s/tstem38/IMAP", 0x0FFFFFFFFFFFEC88, 176, 0) = 0 and the client gets: 1 NO [CANNOT] Invalid mailbox name For pathing I have: plugin.conf: mbox_snarf = /gpfs/inbox/%Ju/%u and mail.conf:mail_location = mbox:%h:INBOX=/var/spool/mail/%Ju/%u I verified that not using the mbox_snarf works just fine. I have no namespaces enabled. Thanks, Jonathan

2 9

[Dovecot] mdbox: Cannot create subfolder called "dbox-Mails" (2.0beta5)
by William Blunn 06 Sep '10

06 Sep '10

I am trying out "mdbox" under Dovecot 2.0beta5. Looking in the "mailboxes" directory under the mdbox storage root ("~/dbox" in my case), I can see that the mail folders are mapped into filesystem directories. But Dovecot seems to put all the message list information ("dovecot.index.cache", "dovecot.index.log") for any given mail folder into a directory called "dbox-Mails"... But this directory name exists in the same namespace as that used for mail subfolders... So this means we cannot create a mail subfolder whose name is "dbox-Mails"! I concede that this eventuality may be unlikely, but when designing in a green field, surely we should avoid such obvious pitfalls? Surely we would want to make it so that these objects exist in different namespaces, so that mail folders can be created with any name? So perhaps the directory "dbox-Mails" should use a character in its name which could not be used in mail folder names. Or mail folder names could have a non-identity mapping into directory names such that the directory name can never be "dbox-Mails". Regards, Bill

4 14

[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] 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] dsync convert Maildir -> mdbox, separators in subscriptions file
by Frode Nordahl 06 Jul '10

06 Jul '10

Hello, I'm playing around with Dovecot 2.0 beta 4. If I use dsync to convert a users mail stored in Maildir format to mdbox format, the subscriptions file in the new mdbox is created using the wrong mailbox separator ('.') leading to folders within folders not being readable by clients using the subscription feature. Excerpt from IMAP: . LIST "" "*" * LIST (\HasChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Spam/Test" . LSUB "" "*" * LSUB () "/" "Spam" * LSUB () "/" "Spam.Test" I am not currently using Maildir, and have no plans to either, so I am very pleased with mdbox using '/' as seperator. I am considering to use Maildir as a transition format so that I can use allready available scripts to do the job (uw2dovecot.pl first, then dsync). So the question is, is this a bug in dsync? At the time of conversion mail_location = maildir:~/Maildir I used the following command to do the conversion: # dsync -u username convert mdbox:~/mdbox -- Frode Nordahl

3 3

[Dovecot] Dovecot 2.0 beta4 and Expire Plugin
by Burckhard Schmidt 06 Jul '10

06 Jul '10

Hello, there seems to be an error writing into the expire database defined by dict. dict { expire = sqlite:/usr/dovecot/etc/dovecotbeta-dict-expire.conf } ... plugin { ... expire = AutoCleanSpam 1d expire_dict = proxy::expire } with dovecotbeta-dict-expire.conf: connect = /test/addons/expire/expiresbeta.db map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } sqlite shows schema: CREATE TABLE expires ( username varchar(100) not null, mailbox varchar(255) not null, expire_stamp integer not null, primary key (username, mailbox) ); CREATE TRIGGER mergeexpires BEFORE INSERT ON expires FOR EACH ROW BEGIN UPDATE expires SET expire_stamp=NEW.expire_stamp WHERE username = NEW.username AND mailbox = NEW.mailbox; SELECT raise(ignore) WHERE (SELECT 1 FROM expires WHERE username = NEW.username AND mailbox = NEW.mailbox) IS NOT NULL; END; Delivering of an email into folder AutoCleanSpam via sieve script works fine. error-log: Apr 08 12:57:05 lda(account1): Debug: sieve: executing compiled script /addons/sieve/account1.sieve Apr 08 12:57:05 lda(account1): Debug: expire: Mails expire in 86400 secs in mailbox: AutoCleanSpam Apr 08 12:57:05 dict: Error: sqlite: exec(INSERT INTO expires (expire_stamp,username,mailbox) VALUES ('1270810625','account1','AutoCleanSpam')) failed: unable to open database file (14) Apr 08 12:57:05 master: Error: service(dict): child 10936 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Apr 08 12:57:05 master: Error: service(dict): command startup failed, throttling deliver-log: Apr 08 12:57:05 lda(account1): Error: read(/var/run/dovecot//dict) failed: Remote disconnected Apr 08 12:57:05 lda(account1): Info: sieve: msgid=<4BBDB681.10003(a)hu-berlin.de>: stored mail into mailbox 'AutoCleanSpam' If I use a non existing database filename in dovecotbeta-dict-expire.conf like connect = /test/addons/expire/expiresbeta.dbbbbb I see in the log dict: Error: sqlite: open(/test/addons/expire/expiresbeta.dbbbbb) failed: unable to open database file So I'm sure, having the rigth config file. Moreover how to start expire-tool now? dovecot --exec-mail ... is no more valid. Additional: /usr/dovecotbeta/sbin/dovecot --build-options Build options: ioloop=poll ipv6 openssl Mail storages: cydir dbox maildir mbox mdbox raw shared SQL drivers: sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap passwd prefetch passwd-file sql static /usr/dovecotbeta/sbin/dovecot -n # 2.0.beta4: /usr/dovecotbeta/etc/dovecot/dovecot.conf # OS: SunOS 5.9 sun4u auth_debug = yes auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ012345 67890 auth_verbose = yes base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot-error default_client_limit = 6144 dict { expire = sqlite:/usr/dovecot/etc/dovecotbeta-dict-expire.conf } first_valid_gid = 20 first_valid_uid = 20 info_log_path = /var/log/dovecot-error listen = 172.19.5.17 log_path = /var/log/dovecot-error mail_access_groups = sysdov mail_debug = yes mail_gid = sysdov mail_location = dbox:%h:INDEX=/addons/index/%u:CONTROL=~/Control:LAYOUT=fs mail_privileged_group = sysdov mail_uid = sysdov mbox_write_locks = fcntl passdb { args = dovecot driver = pam } plugin { autocreate = AutoCleanSpam autocreate1 = Junk autocreate2 = Trash autocreate3 = Sent autocreate4 = Drafts autosubscribe = AutoCleanSpam autosubscribe1 = Junk autosubscribe2 = Trash autosubscribe3 = Sent autosubscribe4 = Drafts expire = AutoCleanSpam 1d expire_dict = proxy::expire sieve = /addons/sieve/%u.sieve } service pop3 { process_limit = 0 } ssl_cert = </opt/csw/etc/ssl/certs/mail.pem ssl_key = </opt/csw/ssl/priv/mail.key syslog_facility = local2 userdb { args = /usr/dovecot/etc/sybldap.conf driver = ldap } verbose_proctitle = yes protocol imap { log_path = /var/log/imap.log mail_plugin_dir = /usr/dovecotbeta/lib/dovecot mail_plugins = autocreate expire } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = /var/log/deliver.log log_path = /var/log/deliver.log mail_plugin_dir = /usr/dovecotbeta/lib/dovecot mail_plugins = sieve autocreate expire postmaster_address = postmaster(a)hu-berlin.de sendmail_path = /opt/csw/sbin/sendmail } -- Burckhard Schmidt

2 6

[Dovecot] 2.0 beta4 latest hg: segfault with virtual plugin
by e-frog 21 Jun '10

21 Jun '10

Hello Timo, latest 2.0 hg version (changeset a6b050cc4a9a) segfaults when selecting a virtual mailbox. Backtrace and dovecot -n are attached. Please let me know if I can help with anything else to debug this. Regards, e-frog

2 4

[Dovecot] A new director service in v2.0 for NFS installations
by Timo Sirainen 16 Jun '10

16 Jun '10

As http://wiki.dovecot.org/NFS describes, the main problem with NFS has always been caching problems. One NFS client changes two files, but another NFS client sees only one of the changes, which Dovecot then assumes is caused by corruption. The recommended solution has always been to redirect the same user to only a single server at the same time. User doesn't have to be permanently assigned there, but as long as a server has some of user's files cached, it should be the only server accessing the user's mailbox. Recently I was thinking about a way to make this possible with an SQL database: http://dovecot.org/list/dovecot/2010-January/046112.html The company here in Italy didn't really like such idea, so I thought about making it more transparent and simpler to manage. The result is a new "director" service, which does basically the same thing, except without SQL database. The idea is that your load balancer can redirect connections to one or more Dovecot proxies, which internally then figure out where the user should go. So the proxies act kind of like a secondary load balancer layer. When a connection from a newly seen user arrives, it gets assigned to a mail server according to a function: host = vhosts[ md5(username) mod vhosts_count ] This way all of the proxies assign the same user to the same host without having to talk to each others. The vhosts[] is basically an array of hosts, except each host is initially listed there 100 times (vhost count=100). This vhost count can then be increased or decreased as necessary to change the host's load, probably automatically in future. The problem is then of course that if (v)hosts are added or removed, the above function will return a different host than was previously used for the same user. That's why there is also an in-memory database that keeps track of username -> (hostname, timestamp) mappings. Every new connection from user refreshes the timestamp. Also existing connections refresh the timestamp every n minutes. Once all connections are gone, the timestamp expires and the user is removed from database. The final problem then is how multiple proxies synchronize their state. The proxies connect to each others forming a connection ring. For example with 4 proxies the connections would go like A -> B -> C -> A. Each time a user is added/refreshed, a notification is sent to both directions in the ring (e.g. B sends to A and C), which in turn forward it until it reaches a server that has already seen it. This way if a proxy dies (or just hangs for a few seconds), the other proxies still get the changes without waiting for it to timeout. Host changes are replicated in the same way. It's possible that two connections from a user arrive to different proxies while (v)hosts are being added/removed. It's also possible that only one of the proxies has seen the host change. So the proxies could redirect users to different servers during that time. This can be prevented by doing a ring-wide sync, during which all proxies delay assigning hostnames to new users. This delay shouldn't be too bad because a) they should happen rarely, b) it should be over quickly, c) users already in database can still be redirected during the sync. The main complexity here comes from how to handle proxy server failures in different situations. Those are less interesting to describe and I haven't yet implemented all of it, so let's just assume that in future it all works perfectly. :) I was also thinking about writing a test program to simulate the director failures to make sure it all works. Finally, there are the doveadm commands that can be used to: 1) List the director status: # doveadm director status mail server ip vhosts users 11.22.3.44 100 1312 12.33.4.55 50 1424 1) Add a new mail server (defaults are in dovecot.conf): # doveadm director add 1.2.3.4 2) Change a mail server's vhost count to alter its connection count (also works during adding): # doveadm director add 1.2.3.4 50 3) Remove a mail server completely (because it's down): # doveadm director remove 1.2.3.4 If you want to slowly get users away from a specific server, you can assign its vhost count to 0 and wait for its user count to drop to zero. If the server is still working while "doveadm director remove" is called, new connections from the users in that server are going to other servers while the old ones are still being handled.

6 22

[Dovecot] question about rpc quota reporting 1.2.11
by Tom Lieuallen 11 Jun '10

11 Jun '10

Timo, thank you for the reply to my question about shared folders yesterday. I'm now trying to get quota reporting working consistently. This is with dovecot 1.2.11 in solaris 10 sparc. We have local quotas for the mail spool (/a1) and quotas for home directories. All are UFS and have rpc (rquota) working fine. With just this: protocol imap { mail_plugins = quota imap_quota } My mail client (thunderbird 3.0.4) reported the home directory quota. So then I added this: plugin { quota = fs:INBOX:mount=/a1 quota2 = fs:Home:mount=%h } First, I had to make /a1/quotas world readable, otherwise I'd get this error: open(/a1/quotas) failed: Permission denied I'm getting the same type of error with the quota2 line now: open(/nfs/rack/u4/quotas) failed: Permission denied Since the home directory quota worked without the plugin configuration, my guess is that the plugin config is not using rpc. I can't find any way to force it to use rpc. Again, if I make that 'quotas' file world readable (which I believe isn't good practice), dovecot stops complaining. Also, what should I expect to see on the client? Will dovecot report only one quota (the one that's closer to the limit), or will it report both? I've only seen the first quota in thunderbird, but that could easily be a client issue. thank you Tom Lieuallen Oregon State University

2 4

[Dovecot] dovecot 2.0b3 crash with lmtp and DNS based proxy
by Oliver Eales 09 Jun '10

09 Jun '10

Hello, i am trying to proxy a LMTP connection with version 2.0b3 Currently i have the problem when trying to use a named based proxy for LMTP the process doesn't resolve the hostname and crashes: Feb 26 16:53:26 auth: Debug: ldap(vodafonemail56@vodafone.de,::1): pass search: base=ou=mailboxes,ou=vfag,c=de,o=vodafone scope=subtree filter=(&(objectClass=uco)(mail=vodafonemail56(a)vodafone.de)) fields=userpassword,isactive,host Feb 26 16:53:26 auth: Debug: ldap(vodafonemail56@vodafone.de,::1): result: userpassword(password)=<hidden> proxy(proxy)=1 host(host)=kangaroo.arcor-so.net Feb 26 16:53:26 auth: Debug: master out: PASS 1 proxy host=kanagroo.arcor-so.net Feb 26 16:53:26 lmtp(17929): Debug: auth input: proxy host=kangaroo.arcor-so.net Feb 26 16:53:26 lmtp(17929): Error: lmtp client: kangaroo.arcor-so.net is not a valid IP Feb 26 16:53:30 lmtp(17929): Info: Disconnect from ::1: Client quit Feb 26 16:53:30 master: Error: service(lmtp): child 17929 killed with signal 11 (core dumped) Program terminated with signal 11, Segmentation fault. #0 0x00000000004081fe in lmtp_proxy_try_finish (proxy=0x633898) at lmtp-proxy.c:193 193 if (lmtp_proxy_send_data_replies(proxy) && (gdb) bt full #0 0x00000000004081fe in lmtp_proxy_try_finish (proxy=0x633898) at lmtp-proxy.c:193 No locals. #1 0x0000000000409bb3 in lmtp_client_deinit (_client=<value optimized out>) at lmtp-client.c:137 client = (struct lmtp_client *) 0x633db8 #2 0x00000000004089c8 in lmtp_proxy_deinit (_proxy=<value optimized out>) at lmtp-proxy.c:86 proxy = (struct lmtp_proxy *) 0x633898 #3 0x000000000040602e in client_destroy (client=0x6191c8, prefix=<value optimized out>, reason=<value optimized out>) at client.c:255 No locals. #4 0x00000000004067d3 in cmd_quit (client=0xb, args=<value optimized out>) at commands.c:407 No locals. #5 0x000000000040669b in client_input_handle (client=0x6191c8) at client.c:61 _data_stack_cur_id = 3 output = (struct ostream *) 0x619b80 line = 0x631461 "quit" ret = <value optimized out> #6 0x00007f3217c9b8db in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:208 ctx = (struct ioloop_handler_context *) 0x6177b0 event = (const struct epoll_event *) 0x617820 list = (struct io_list *) 0x619c60 io = (struct io_file *) 0x619c20 tv = {tv_sec = 59, tv_usec = 976185} t_id = 2 msecs = <value optimized out> ret = 1 call = <value optimized out> #7 0x00007f3217c9aa48 in io_loop_run (ioloop=0x6175a0) at ioloop.c:350 No locals. #8 0x00007f3217c8ae03 in master_service_run (service=0x617480, callback=0x6) at master-service.c:478 No locals. #9 0x0000000000405b92 in main (argc=1, argv=0x617370) at main.c:92 ---Type <return> to continue, or q <return> to quit--- set_roots = {0x40bd00, 0x40b980, 0x0} service_flags = <value optimized out> storage_service_flags = 675 c = <value optimized out> (gdb) Regards, Oliver Eales

2 4

[Dovecot] Dovecot 2.0 shared mailbox using ACLs problem
by p.quidacciolu＠libero.it 07 Jun '10

07 Jun '10

Hi, I'm trying to configure shared mailboxes using ACLs. On dovecot 1.2.10 it works fine, but the same configuration on dovecot 2.0. beta4 doesn't work. When I try to access to the shared mailbox I get the following message: Query: SELECT "users/user2/INBOX" Reason Given: Mailbox doesn't exist: users/user2/INBOX In the next the dovecot -n output and the dovecot-ldap.conf content: # 2.0.beta4: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.9-89.ELsmp i686 Red Hat Enterprise Linux AS release 4 (Nahant Update 8) ext3 auth_mechanisms = plain login mail_debug = yes mail_gid = mailusers mail_location = maildir:/mnt/mbox1/mailusers/%n/Maildir mail_uid = mailusers namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = no list = children location = maildir:/mnt/mbox1/mailusers/%%n/Maildir: INDEX=/mnt/mbox1/mailusers/%n/Maildir/users/%%n prefix = users/%%n/ separator = / subscriptions = no type = shared } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/tmp/shared-mailboxes.db } service auth { user = root } ssl = no userdb { driver = passwd } userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } protocol imap { mail_plugins = quota imap_quota acl imap_acl # /usr/local/etc/dovecot/dovecot-ldap.conf hosts = ldap-vip base = o=mailusers user_attrs = mailQuota=quota_rule=*:backend=%$ user_filter = (&(objectClass=person)(|(uid=%u)(uid=%n))) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=person)(|(uid=%u)(uid=%n))) Regards, Pier Luigi

2 1

[Dovecot] dovecot 2 beta4 errors & core dumps
by de Lafond Guillaume 07 Jun '10

07 Jun '10

Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user(a)domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user(a)domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed: (box->transaction_count > 0 || box->view->transactions == 0) Apr 03 10:23:47 imap(user(a)domain.com): Error: Raw backtrace: /usr/ local/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e9adc1] -> /usr/local/ dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e9ae3f] -> /usr/local/ dovecot2/lib/dovecot/libdovecot.so.0(i_error+0) [0xb7e9b0f8] -> /usr/ local/dovecot2/lib/dovecot/libdovecot-storage.so.0 [0xb7f3e9c2] -> / usr/local/dovecot2/lib/dovecot/lib10_quota_plugin.so [0xb7cdaaea] -> / usr/local/dovecot2/lib/dovecot/libdovecot-storage.so. 0(mailbox_transaction_rollback+0x20) [0xb7ef03f0] -> /usr/local/ dovecot2/lib/dovecot/lib10_quota_plugin.so [0xb7cda323] -> /usr/local/ dovecot2/lib/dovecot/lib10_quota_plugin.so [0xb7cda4df] -> /usr/local/ dovecot2/lib/dovecot/libdovecot-storage.so.0(maildir_sync_index+0x897) [0xb7f52bb7] -> /usr/local/dovecot2/lib/dovecot/libdovecot-storage.so. 0(maildir_transaction_save_commit_pre+0x710) [0xb7f50f70] -> /usr/ local/dovecot2/lib/dovecot/libdovecot-storage.so.0 [0xb7f3ee27] -> / usr/local/dovecot2/lib/dovecot/libdovecot-storage.so. 0(mail_index_transaction_commit_full+0x85) [0xb7f08ee5] -> /usr/local/ dovecot2/lib/dovecot/libdovecot-storage.so.0(index_transaction_commit +0x83) [0xb7f3ea53] -> /usr/local/dovecot2/lib/dovecot/ lib10_quota_plugin.so [0xb7cdab81] -> /usr/local/dovecot2/lib/dovecot/ libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x42) [0xb7ef0c72] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] [0x804eab2] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] [0x804e8cb] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] [0x804ed02] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] (cmd_append+0x1d9) [0x804f069] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] [0x80562dc] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] [0x8056379] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND] (client_handle_input+0x2d) [0x80564ed] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND](client_input+0x5f) [0x8056f0f] -> / usr/local/dovecot2/lib/dovecot/libdovecot.so.0(io_loop_handler_run +0xf5) [0xb7ea7425] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so. 0(io_loop_run+0x30) [0xb7ea6470] -> /usr/local/dovecot2/lib/dovecot/ libdovecot.so.0(master_service_run+0x2a) [0xb7e93eaa] -> dovecot/imap [user(a)domain.com 10.0.0.5 APPEND](main+0x2ad) [0x805f9ed] -> /lib/i686/cmov/libc.so. 6(__libc_start_main+0xe5) [0xb7d0f455] Apr 03 10:23:47 master: Error: service(imap): child 27371 killed with signal 6 (core dumped) Apr 03 10:23:50 imap(user(a)domain.com): Error: dotlock /var/mail/d/ domain.com/user/Maildir/dovecot-uidlist.lock was immediately deleted under us Apr 03 10:23:50 imap(user(a)domain.com): Error: dotlock /var/mail/d/ domain.com/user/Maildir/dovecot-uidlist.lock was immediately deleted under us Apr 03 10:23:50 imap(user(a)domain.com): Warning: Our dotlock file /var/ mail/d/domain.com/user/Maildir/dovecot-uidlist.lock was deleted (locked 0 secs ago, touched 0 secs ago) Apr 03 10:23:50 imap(user(a)domain.com): Warning: Our dotlock file /var/ mail/d/domain.com/user/Maildir/dovecot-uidlist.lock was deleted (locked 0 secs ago, touched 0 secs ago) Apr 03 10:23:50 imap(user(a)domain.com): Error: Log synchronization error at seq=2,offset=8188 for /var/mail/dovecot_indexes/d/domain.com/ user/.INBOX/dovecot.index: Append with UID 32, but next_uid = 33 Apr 03 10:23:50 imap(user(a)domain.com): Warning: fscking index file / var/mail/dovecot_indexes/d/domain.com/user/.INBOX/dovecot.index Apr 03 10:23:50 imap(user(a)domain.com): Error: Log synchronization error at seq=2,offset=8188 for /var/mail/dovecot_indexes/d/domain.com/ user/.INBOX/dovecot.index: Append with UID 32, but next_uid = 33 Apr 03 10:23:50 imap(user(a)domain.com): Warning: fscking index file / var/mail/dovecot_indexes/d/domain.com/user/.INBOX/dovecot.index Apr 03 10:23:50 imap(user(a)domain.com): Warning: Our dotlock file /var/ mail/d/domain.com/user/Maildir/dovecot-uidlist.lock was overridden (locked 0 secs ago, touched 0 secs ago) Apr 03 10:23:50 imap(user(a)domain.com): Error: dotlock /var/mail/d/ domain.com/user/Maildir/dovecot-uidlist.lock was immediately recreated under us Apr 03 10:23:50 imap(user(a)domain.com): Error: Log synchronization error at seq=2,offset=8188 for /var/mail/dovecot_indexes/d/domain.com/ user/.INBOX/dovecot.index: Append with UID 32, but next_uid = 33 Apr 03 10:23:50 imap(user(a)domain.com): Warning: fscking index file / var/mail/dovecot_indexes/d/domain.com/user/.INBOX/dovecot.index The backtrace : Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. [New process 27371] #0 0xb7f85424 in __kernel_vsyscall () (gdb) bt full #0 0xb7f85424 in __kernel_vsyscall () No symbol table info available. #1 0xb7d24640 in raise () from /lib/i686/cmov/libc.so.6 No symbol table info available. #2 0xb7d26018 in abort () from /lib/i686/cmov/libc.so.6 No symbol table info available. #3 0xb7e9add5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:164 backtrace = 0x80643d0 "/usr/local/dovecot2/lib/dovecot/libdovecot.so. 0 [0xb7e9adc1] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0 [0xb7e9ae3f] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(i_error +0) [0xb7e9b0f8] "... #4 0xb7e9ae3f in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0xb7f6f1c4 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfffda44 "\2228??\221") at failures.c:592 No locals. #5 0xb7e9b0f8 in i_panic (format=0xb7f6f1c4 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:230 No locals. #6 0xb7f3e9c2 in index_transaction_rollback (t=0x80b2a90) at index- transaction.c:144 box = (struct mailbox *) 0x808d340 itrans = (struct mail_index_transaction *) 0x0 __FUNCTION__ = "index_transaction_rollback" #7 0xb7cdaaea in quota_mailbox_transaction_rollback (ctx=0x80b2a90) at quota-storage.c:112 qt = (struct quota_transaction_context *) 0x80a9628 #8 0xb7ef03f0 in mailbox_transaction_rollback (_t=0x808d780) at mail- storage.c:1155 t = (struct mailbox_transaction_context *) 0x6aeb #9 0xb7cda323 in quota_mailbox_sync_cleanup (qbox=0x808d6c0) at quota- storage.c:246 No locals. #10 0xb7cda4df in quota_mailbox_sync_notify (box=0x808d340, uid=0, sync_type=<value optimized out>) at quota-storage.c:274 qbox = (struct quota_mailbox *) 0x808d6c0 i = <value optimized out> count = <value optimized out> size = <value optimized out> #11 0xb7f52bb7 in maildir_sync_index (ctx=0x80b45a0, partial=true) at maildir-sync-index.c:631 mbox = (struct maildir_mailbox *) 0x808d340 view = (struct mail_index_view *) 0x80a9270 view2 = (struct mail_index_view *) 0x0 iter = (struct maildir_uidlist_iter_ctx *) 0x0 trans = (struct mail_index_transaction *) 0x80b42c8 hdr = (const struct mail_index_header *) 0x80a85f8 empty_hdr = {major_version = 0 '\0', minor_version = 0 '\0', base_header_size = 0, header_size = 0, record_size = 576, compat_flags = 8 '\b', unused = "???", indexid = 3084301177, flags = 3085242720, uid_validity = 28, next_uid = 3085743644, messages_count = 134956776, unused_old_recent_messages_count = 576, seen_messages_count = 3221216296, deleted_messages_count = 3085530619, first_recent_uid = 3085747040, first_unseen_uid_lowwater = 0, first_deleted_uid_lowwater = 0, log_file_seq = 576, log_file_tail_offset = 28, log_file_head_offset = 1, sync_size = 13256344077235912704, sync_stamp = 3085747040, day_stamp = 134956776, day_first_uid = {3221216328, 3085530784, 3085747040, 3085781192, 3086502160, 3085743644, 4294967295, 3086618612}} rec = <value optimized out> seq = 0 seq2 = 0 uid = 29 prev_uid = 29 uflags = 0 filename = 0x80aee58 "1270283027.M108835P27367.test- mail,S=1837,W=1881:2," uid_validity = 1270283075 next_uid = <value optimized out> hdr_next_uid = 30 first_recent_uid = 30 first_uid = 1 changes = 4 ret = 0 time_before_sync = 1270283027 expunged_guid_128 = "?????o\216\bl\236?\000?8=\216" expunged = false full_rescan = false __FUNCTION__ = "maildir_sync_index" #12 0xb7f50f70 in maildir_transaction_save_commit_pre (_ctx=0x80ada00) at maildir-save.c:765 _t = (struct mailbox_transaction_context *) 0x80a9d38 last_mf = <value optimized out> sync_flags = <value optimized out> ret = <value optimized out> __FUNCTION__ = "maildir_transaction_save_commit_pre" #13 0xb7f3ee27 in index_transaction_index_commit (index_trans=0x80aa258, result_r=0xbfffddcc) at index-transaction.c:27 it = (struct index_transaction_context *) 0x80a9d38 ibox = (struct index_mailbox_context *) 0x808d558 ret = <value optimized out> __FUNCTION__ = "index_transaction_index_commit" #14 0xb7f08ee5 in mail_index_transaction_commit_full (_t=0xbfffdde8, result_r=0xbfffddcc) at mail-index-transaction.c:237 t = (struct mail_index_transaction *) 0x80aa258 index = (struct mail_index *) 0x806e708 index_undeleted = false #15 0xb7f3ea53 in index_transaction_commit (t=0x80a9d38, changes_r=0xbfffde8c) at index-transaction.c:123 box = (struct mailbox *) 0x808d340 itrans = (struct mail_index_transaction *) 0x0 result = {log_file_seq = 0, log_file_offset = 0, commit_size = 0, ignored_uid_changes = 0, ignored_modseq_changes = 0} ret = <value optimized out> __FUNCTION__ = "index_transaction_commit" #16 0xb7cdab81 in quota_mailbox_transaction_commit (ctx=0x80a9d38, changes_r=0xbfffde8c) at quota-storage.c:94 qt = (struct quota_transaction_context *) 0x80aa628 #17 0xb7ef0c72 in mailbox_transaction_commit_get_changes (_t=0x80893c8, changes_r=0xbfffde8c) at mail-storage.c:1143 _data_stack_cur_id = 4 t = (struct mailbox_transaction_context *) 0x80a9d38 ret = <value optimized out> #18 0x0804eab2 in cmd_append_continue_parsing (cmd=0x8089328) at cmd- append.c:265 sync_flags = <value optimized out> imap_flags = <value optimized out> changes = {pool = 0x80b3308, uid_validity = 0, saved_uids = {arr = {buffer = 0x80b3320, element_size = 8}, v = 0x80b3320, v_modifiable = 0x80b3320}, ignored_uid_changes = 0, ignored_modseq_changes = 0} msg = <value optimized out> client = (struct client *) 0x8084318 ctx = (struct cmd_append_context *) 0x80893b8 args = (const struct imap_arg *) 0x80ab218 flags_list = <value optimized out> flags = <value optimized out> keywords_list = <value optimized out> keywords = <value optimized out> internal_date_str = <value optimized out> internal_date = <value optimized out> ret = <value optimized out> timezone_offset = <value optimized out> save_count = <value optimized out> nonsync = <value optimized out> __FUNCTION__ = "cmd_append_continue_parsing" #19 0x0804e8cb in cmd_append_continue_message (cmd=0x8089328) at cmd- append.c:446 client = (struct client *) 0x8084318 ctx = (struct cmd_append_context *) 0x80893b8 size = 0 ret = <value optimized out> #20 0x0804ed02 in cmd_append_continue_parsing (cmd=0x8089328) at cmd- append.c:379 client = (struct client *) 0x8084318 ctx = (struct cmd_append_context *) 0x80893b8 args = (const struct imap_arg *) 0x80ab218 flags_list = (const struct imap_arg *) 0x0 flags = 0 keywords_list = (const char * const *) 0x80ab1e0 keywords = (struct mail_keywords *) 0x0 internal_date_str = 0x0 internal_date = -1 ret = 0 timezone_offset = 0 save_count = <value optimized out> nonsync = true __FUNCTION__ = "cmd_append_continue_parsing" #21 0x0804f069 in cmd_append (cmd=0x8089328) at cmd-append.c:540 client = (struct client *) 0x8084318 ctx = (struct cmd_append_context *) 0x80893b8 mailbox = 0x808abd8 "INBOX" #22 0x080562dc in client_command_input (cmd=0x8089328) at imap- client.c:647 client = (struct client *) 0x8084318 command = <value optimized out> __FUNCTION__ = "client_command_input" #23 0x08056379 in client_command_input (cmd=0x8089328) at imap- client.c:697 client = (struct client *) 0x8084318 command = <value optimized out> __FUNCTION__ = "client_command_input" #24 0x080564ed in client_handle_input (client=0x8084318) at imap- client.c:738 _data_stack_cur_id = 3 ret = false remove_io = <value optimized out> handled_commands = false __FUNCTION__ = "client_handle_input" #25 0x08056f0f in client_input (client=0x8084318) at imap-client.c:789 cmd = <value optimized out> output = (struct ostream *) 0x8083054 bytes = <value optimized out> __FUNCTION__ = "client_input" #26 0xb7ea7425 in io_loop_handler_run (ioloop=0x806c358) at ioloop- epoll.c:208 ctx = (struct ioloop_handler_context *) 0x806c478 event = (const struct epoll_event *) 0x806c4b8 list = (struct io_list *) 0x80830d8 io = (struct io_file *) 0x80830b0 tv = {tv_sec = 1799, tv_usec = 999126} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #27 0xb7ea6470 in io_loop_run (ioloop=0x806c358) at ioloop.c:350 No locals. #28 0xb7e93eaa in master_service_run (service=0x806c2a8, callback=0x805faa0 <client_connected>) at master-service.c:486 No locals. #29 0x0805f9ed in main (argc=Cannot access memory at address 0x0 ) at main.c:323 service_flags = <value optimized out> storage_service_flags = <value optimized out> postlogin_socket_path = 0x0 username = 0x0 c = <value optimized out> set_roots = {0x8062760, 0x0} (gdb) I don't have errors with clients=1 seed=123 msgs=100000000 random secs=600. -- Guillaume de Lafond Aqua Ray

2 1

[Dovecot] Ignoring the quota by the LDA?
by Holger Richter 07 Jun '10

07 Jun '10

Is it possible to configure dovecot in a manner that only the imap process respects the quota, and the local delivery ignores completely the quota? I think it should happen if I don't activate the quota plugin in the lda section but only in the imap section. protocol lda { ... # mail_plugins = ... } protocol imap { ... mail_plugins = quota imap_quota ... } Will it work or will it result in a big mess? I've the aim that a mail will never be rejected because the recipient is over his/her quota. Regards, Holger

3 4

[Dovecot] Problems with the IMAP proxy after upgrading from dovecot 1.1.16 to 1.211
by Holger Richter 07 Jun '10

07 Jun '10

We have frequent timeout problems after upgrading our imap servers from dovecot 1.1.16 to dovecot 1.2.11. One server acts as proxy only, and the other one is the "real" imap server". The credentials for the proxy service are stored in a remote MYSQL database. There were no trouble with dovecot 1.1.16. But now, with the most recent version, we get frequent login failures. It seems dovecot reconnects too late to the MySQL database after a timeout, after sending the SQL query. Here's a piece of my log file: May 7 14:46:32 ttt dovecot: auth(default): new auth connection: pid=5136 May 7 14:46:42 ttt dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=xxx.xxx.xxx.xxx^Irip=yyy.yyy.yyy.yyy^Ilport=sss^Irport=26480^Iresp=<hidden> May 7 14:46:42 ttt dovecot: auth-worker(default): sql(uid,yyy.yyy.yyy.yyy): query: SELECT NULL as password, destuser, host, 'zzz' as port, 'Y' as proxy, '0' as proxy_timeout, 'Y' as nopassword, 'Y' as nodelay from accounts where user ='uid'; May 7 14:47:42 ttt dovecot: auth(default): worker-server(uid,yyy.yyy.yyy.yyy): Aborted: Lookup timed out May 7 14:47:42 ttt dovecot: auth-worker(default): mysql: Connected to lll.lll.lll.lll (imapauth) May 7 14:47:44 ttt dovecot: auth(default): client out: FAIL^I1^Iuser=uid^Itemp May 7 14:47:49 ttt dovecot: imap-login: Disconnected (auth failed, 1 attempts): user=<uid>, method=PLAIN, rip=yyy.yyy.yyy.yyy, lip=xxx.xxx.xxx.xxx, TLS May 7 14:48:26 ttt dovecot: auth(default): new auth connection: pid=5159 May 7 14:48:47 ttt dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=xxx.xxx.xxx.xxx^Irip=yyy.yyy.yyy.yyy^Ilport=sss^Irport=6243^Iresp=<hidden> May 7 14:48:47 ttt dovecot: auth-worker(default): sql(uid,yyy.yyy.yyy.yyy): query: SELECT NULL as password, destuser, host, 'zzz' as port, 'Y' as proxy, '0' as proxy_timeout, 'Y' as nopassword, 'Y' as nodelay from accounts where user ='uid'; May 7 14:48:47 ttt dovecot: auth(default): client out: OK^I1^Iuser=uid^Idestuser=luid^Ihost=mmm.mmm.mmm.mmm^Iport=zzz^Iproxy^Iproxy_timeout=0^Ipass=<hidden> May 7 14:48:47 ttt dovecot: imap-login: proxy(uid): started proxying to mmm.mmm.mmm.mmm:zzz/luid: user=<uid>, method=PLAIN, rip=yyy.yyy.yyy.yyy, lip=xxx.xxx.xxx.xxx, TLS May 7 14:48:48 ttt dovecot: imap-login: proxy(uid): disconnecting yyy.yyy.yyy.yyy As you can see, the second login attempt is always successful. Of course I've tried out various values (0, 60, 90, 300) for the proxy_timeout parameter - but without any success.

2 2

[Dovecot] authentification failure: double quotes in password
by Martin Ott 07 Jun '10

07 Jun '10

we use Passdb LDAP with authentication binds against an Active Directory Server. The problem with one of our users seems to be the usage of double quotes in his password, as the windows-login works: /var/log/dovecot-info.log auth(default): Info: ldap(testuser 77.22.xx.xxx): invalid credentials (given password: xxxxx"xxxxxxx) Which chars in passwords does the dovecot auth process not like? Is there something similar to auth_username_chars for passwords? thanks, martin

2 2

[Dovecot] raw backtrace in masses
by John Adams 06 Jun '10

06 Jun '10

Hi I've got huge amounts of May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): close(/home/user/Mail/R-Help.lock) failed: Disc quota exceeded May 3 15:47:37 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:37 host dovecot: [ID 583609 mail.error] dovecot: child 3892 (imap) killed with signal 6 (core dumps disabled) May 3 15:47:49 host dovecot: [ID 583609 mail.error] IMAP(user): Raw backtrace: 0xb0e58 -> 0xb0894 -> 0x552b4 -> 0x55508 -> 0x55774 -> 0x55d9c -> 0x5759c -> 0x57ad0 -> 0x713cc -> 0x64284 -> 0x57be0 -> 0x71178 -> 0x6841c -> 0x76a38 -> 0x76a6c -> 0x25a08 -> 0x2afd4 -> 0x2bee4 -> 0x2bea0 -> 0x2c1f8 -> 0x2cb4c -> 0xb9450 -> 0xb8d00 -> 0x35294 -> 0x246e8 May 3 15:47:49 host dovecot: [ID 583609 mail.error] dovecot: child 4277 (imap) killed with signal 6 (core dumps disabled) The backtrace is always the same content. is this a disc quota problem? Dovecot is 1.2.11, managesieve patched. Thanks

3 9

[Dovecot] mdbox error with 2.0.beta5
by Mike Abbott 05 Jun '10

05 Jun '10

Running 2.0.beta5 on Mac OS X with HFS+J, I often see this error in the log: Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Error: mdbox /var/spool/imap/dovecot/mail/mailboxes/INBOX/Foobar/dbox-Mails: map uidvalidity mismatch (1273852899 vs 1273853949) Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Disconnected: Internal error occurred. Refer to server log for more information. [2010-05-14 12:25:59] bytes=1337/4443 Fri May 14 12:25:59 gromit dovecot[5466]: imap(pid 8101 user joe): Warning: mdbox /var/spool/imap/dovecot/mail/storage: rebuilding indexes The logs also reveal that this user was logged in twice at the time. There appear to be two issues here: the uidvalidity mismatch, and the path in the "rebuilding indexes" message does not match the path in the "uidvalidity mismatch" error.

2 6

[Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
by Thomas Leuxner 04 Jun '10

04 Jun '10

Hi, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831 points to broken data at offset=1438073 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831 points to broken data at offset=1438073 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Disconnected: Internal error occurred. Refer to server log for more information. [2010-03-09 13:56:28] bytes=74358/28147042 Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): dbox /var/vmail/leuxner.net/tlx/mdbox/storage: rebuilding indexes Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=2075210): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx(a)leuxner.net): dbox: Copy of the broken file saved to /var/vmail/leuxner.net/tlx/mdbox/storage/m.59.broken Mar 9 13:56:29 spectre dovecot: imap(tlx(a)leuxner.net): Panic: file index-sync.c: line 40 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Mar 9 13:56:29 spectre dovecot: imap(tlx(a)leuxner.net): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d92b2] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d931a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f184c7d96c3] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0) [0x7f184ca84010] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mailbox_set_recent_seq+0x3c) [0x7f184ca8404c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x37b) [0x7f184caafddb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x12) [0x7f184cab00c2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x43) [0x7f184cab0133] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7f184ca414e1] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE](imap_sync_init+0x68) [0x417db8] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE] [0x40ab5e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x9b) [0x7f184c7e342b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x6f) [0x7f184c7e3f8f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f184c7e3168] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f184c7d3143] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE](main+0x191) [0x418681] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f184c0601a6] -> dovecot/imap [tlx(a)leuxner.net 80.187.100.24 IDLE] [0x4084e9] Mar 9 13:56:29 spectre dovecot: master: service(imap): child 32643 killed with signal 6 (core dumped) [14:02] root spectre:/# gdb /usr/lib/dovecot/imap /var/vmail/leuxner.net/tlx/core GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... warning: Can't read pathname for load map: Input/output error. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot-storage.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib01_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib10_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...Reading symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done. done. Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. [New process 32643] #0 0x00007f184c073ed5 in raise () from /lib/libc.so.6 (gdb) bt full #0 0x00007f184c073ed5 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00007f184c0753f3 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x00007f184c7d92c5 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:164 backtrace = 0x61f0e8 "/usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d92b2] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f184c7d931a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f184c7d96c3] -> /usr/lib/dovecot/libdovecot-st"... #3 0x00007f184c7d931a in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=<value optimized out>, args=<value optimized out>) at failures.c:592 No locals. #4 0x00007f184c7d96c3 in i_panic (format=<value optimized out>) at failures.c:230 args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffffffcd00, reg_save_area = 0x7fffffffcc40}} #5 0x00007f184ca84010 in index_mailbox_set_recent_uid (box=<value optimized out>, uid=4722) at index-sync.c:40 ibox = (struct index_mailbox_context *) 0x654890 __PRETTY_FUNCTION__ = "index_mailbox_set_recent_uid" #6 0x00007f184ca8404c in index_mailbox_set_recent_seq (box=0x654508, view=0x665040, seq1=2, seq2=44) at index-sync.c:57 uid = 4722 #7 0x00007f184caafddb in mdbox_sync_begin (mbox=0x654508, flags=<value optimized out>, ctx_r=0x7fffffffcea8) at mdbox-sync.c:141 storage = (struct mail_storage *) 0x648c78 ctx = (struct mdbox_sync_context *) 0x657260 sync_flags = <value optimized out> ret = 1 storage_rebuilt = false #8 0x00007f184cab00c2 in mdbox_sync (mbox=0x7f83, flags=32643) at mdbox-sync.c:286 sync_ctx = (struct mdbox_sync_context *) 0x654508 #9 0x00007f184cab0133 in mdbox_storage_sync_init (box=0x654508, flags=0) at mdbox-sync.c:310 mdbox_sync_flags = 32643 #10 0x00007f184ca414e1 in mailbox_sync_init (box=0x654508, flags=0) at mail-storage.c:848 _data_stack_cur_id = 0 ctx = <value optimized out> #11 0x0000000000417db8 in imap_sync_init (client=0x64f9d8, box=<value optimized out>, imap_flags=0, flags=0) at imap-sync.c:142 ctx = <value optimized out> __PRETTY_FUNCTION__ = "imap_sync_init" #12 0x000000000040ab5e in idle_sync_now (box=<value optimized out>, ctx=0x650228) at cmd-idle.c:122 __PRETTY_FUNCTION__ = "idle_sync_now" #13 0x00007f184c7e342b in io_loop_handle_timeouts (ioloop=0x6275c0) at ioloop.c:328 _data_stack_cur_id = 2 #14 0x00007f184c7e3f8f in io_loop_handler_run (ioloop=0x6275c0) at ioloop-epoll.c:180 ctx = (struct ioloop_handler_context *) 0x6277d0 event = <value optimized out> list = <value optimized out> io = <value optimized out> tv = {tv_sec = 0, tv_usec = 499327} t_id = <value optimized out> msecs = 500 ret = 0 call = <value optimized out> #15 0x00007f184c7e3168 in io_loop_run (ioloop=0x6275c0) at ioloop.c:350 No locals. #16 0x00007f184c7d3143 in master_service_run (service=0x627490, callback=0x7f83) at master-service.c:478 No locals. #17 0x0000000000418681 in main (argc=1, argv=0x627370) at main.c:313 service_flags = <value optimized out> storage_service_flags = <value optimized out> postlogin_socket_path = 0x0 set_roots = {0x41b980, 0x0} (gdb) Regards Thomas

2 11

[Dovecot] dsync panic in dsync-worker-local.c - 2.0.beta4
by Frode Nordahl 04 Jun '10

04 Jun '10

Hello, While testing mailbox conversion I encountered a Panic in dsync on a few users mailboxes. Running dovecot 2.0.beta4 on RedHat Enterprise Linux 5 (x86_64). I tried to compile the code with -ggdb and debug some more before posting this, but I was unsuccessful. Running dsync from a source tree is hard because of all the dependencies on shares libraries. Is it possbile to build static binaries? Panic message and backtrace included below (anonymized): dsync(user): Error: o_stream_send_istream(/home/user/mdbox/storage/temp.1271871137.P25074Q1M330350.localhost.localdomain) failed: Bad file descriptor dsync(user): Panic: file dsync-worker-local.c: line 1460 (local_worker_save_msg_continue): assertion failed: (ret == -1) dsync(user): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3da92343a0] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x37) [0x3da9234487] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3da92338c8] -> /usr/bin/dsync [0x40db83] -> /usr/bin/dsync [0x40dc5e] -> /usr/bin/dsync(dsync_worker_msg_save+0x79) [0x40d429] -> /usr/bin/dsync [0x408b4c] -> /usr/bin/dsync [0x40d88d] -> /usr/bin/dsync(dsync_worker_msg_get+0x81) [0x40d061] -> /usr/bin/dsync [0x4085fe] -> /usr/bin/dsync [0x40868d] -> /usr/bin/dsync [0x4087d5] -> /usr/bin/dsync(dsync_brain_msg_sync_more+0x3f5) [0x408395] -> /usr/bin/dsync(dsync_brain_sync+0x93f) [0x40720f] -> /usr/bin/dsync [0x4078e0] -> /usr/bin/dsync(dsync_brain_sync+0x42e) [0x406cfe] -> /usr/bin/dsync [0x4079e1] -> /usr/bin/dsync(dsync_brain_sync+0x3f0) [0x406cc0] -> /usr/bin/dsync(dsync_brain_sync_all+0x18) [0x407728] -> /usr/bin/dsync(main+0x436) [0x406156] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d18a1d994] -> /usr/bin/dsync [0x405c29] -- Frode Nordahl

2 1

[Dovecot] 2.0.beta4, Panic: stream doesn't support seeking backwards
by Juergen Daubert 04 Jun '10

04 Jun '10

Hi, got the following with beta4 while uploading messages from a local mbox to the dovecot server in my LAN, tested with mutt and sylpheed, the same action works with 1.2.11: Mar 29 13:42:46 [dovecot] imap(juergen): Panic: stream doesn't support seeking backwards Mar 29 13:42:46 [dovecot] imap(juergen): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76b7ec4] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76b7f2c] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0xb76b8193] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c02cd] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_seek+0xbb) [0xb76be1db] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c08a9] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x40) [0xb76be570] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x6d) [0xb76a7b6d] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4302] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a498f] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a3f61] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76a4072] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_seek+0xbb) [0xb76be1db] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x52) [0xb76be262] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76c246d] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x6e) [0xb76be27e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_save_continue+0x4c) [0xb776ca6c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x14) [0xb7708964] -> dovecot/imap [0x804e32f] -> dovecot/imap [0x804ed31] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd1) [0xb76c38f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x29) [0xb76c29f9] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x25) [0xb76b1c45] -> dovecot/imap(main+0x1b3) [0x805da13] -> /lib/libc.so.6(__libc_start_main+0xdb) [0xb7559a3b] -> dovecot/imap [0x804e161] Mar 29 13:42:46 [dovecot] master: service(imap): child 21107 killed with signal 6 (core dumps disabled) # dovecot -n # 2.0.beta4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.10 i686 listen = * login_access_sockets = tcpwrap passdb { driver = shadow } service tcpwrap { unix_listener login/tcpwrap { mode = 0666 } } ssl_cert = </etc/ssl/certs/dovecot.crt ssl_key = </etc/ssl/keys/dovecot.key userdb { driver = passwd } Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

3 16

[Dovecot] userdb prefetch not compatible with ssl_require_client_cert
by zhong ming wu 04 Jun '10

04 Jun '10

Dear List I looked into docs but couldn't see any where that says of this incompatibility. Anywhere this is confirmed in the doc? Thanks mr.wu

2 3

[Dovecot] v2.0.beta4: conversion of v1.2 configuration
by Pascal Volk 04 Jun '10

04 Jun '10

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-trunk-amd64 x86_64 Debian squeeze/sid listen = 192.168.111.222 [2a01 service imap-login { inet_listener imap { port = 198 } } service managesieve-login { inet_listener managesieve { port = 198 } } service managesieve { executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } service pop3-login { inet_listener pop3 { port = 198 } } # missing section: #protocol lda { # … #} # missing setting #postmaster_address The corresponding parts from v1.2 configuration: protocols = imap imaps managesieve pop3 pop3s listen = 192.168.111.222 [2a01:198:37a:1::1] protocol managesieve { mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/managesieve } protocol lda { postmaster_address = f007ba11.1008605(a)localdomain.org mail_plugins = sieve } Why is the lda section missing? Because it is not listed in v1.2's protocols setting? (only an idea/wild guess) Regards, Pascal -- The trapper recommends today: deadbeef.1008606(a)localdomain.org

3 3

[Dovecot] master users with dovecot2 braek down to allowed domain
by Robert Schetterer 03 Jun '10

03 Jun '10

Hi, i think ive asked it before perhaps this feature can be included in dovecot2 couldnt get it run with dovecot 1.2.x if i use the postfixadmin superuser,domainadmin,domainuser layout so there are domainadmins defined in a sql table it would be a nice feature to break it down to be master only at there related domains via sql lookup at recent i think there is only the chance to give master rights to all adresses for users defined as masters -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] returned error 83 (Out of memory)
by J Contad 02 Jun '10

02 Jun '10

Hello! I've setup dovecot a few months ago, and it was working pretty swimmingly. Then, out of nowhere, we started getting this error: Apr 21 19:15:17 IMAP(xx(a)xxx.com): Fatal: block_alloc(1073741824): Out of memory Apr 21 19:15:17 IMAP(xx(a)xxx.com): Error: Raw backtrace: imap [0x49e5e0] -> imap [0x49e643] -> imap [0x49dba1] -> imap [0x4a7f6d] -> imap [0x4a7f98] -> imap [0x4a8028] -> imap [0x49bf6f] -> imap(buffer_write+0xe4) [0x49c334] -> imap(mail_cache_lookup_headers+0x146) [0x46dcf6] -> imap [0x458162] -> imap(index_mail_get_first_header+0x45) [0x458685] -> imap [0x45fe44] -> imap [0x460008] -> imap [0x4796d1] -> imap(hash2_lookup+0x64) [0x4a1c94] -> imap(mail_index_strmap_view_sync_add+0x85) [0x47ab05] -> imap(mail_thread_init+0x2a5) [0x4602f5] -> imap(cmd_thread+0x161) [0x41f931] -> imap(cmd_uid+0x78) [0x41fb38] -> imap [0x42079c] -> imap [0x420852] -> imap(client_handle_input+0x3f) [0x42098f] -> imap(client_input+0x5f) [0x4214df] -> imap(io_loop_handler_run+0xf8) [0x4a63a8] -> imap(io_loop_run+0x1d) [0x4a54ed] -> imap(main+0x620) [0x428db0] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3f75e1d8a4] -> imap [0x419969] Apr 21 19:15:17 dovecot: Error: child 25918 (imap) returned error 83 (Out of memory - see mail_process_size setting) The folder (which is shared) has about 8 thousand emails in it. I'm not sure if it's pertinent, but the dovecot.index.cache file is about 8MB. Help? Cheers, -- John

3 2

[Dovecot] Dovecot install problem
by David 02 Jun '10

02 Jun '10

I am trying to set up a new web and mail server i have postfix now working but dovecot will not allow me to login and retrieve the emails so below isa portion of the log file passwd-file /var/mail/vhosts/xxxx.net/shadow: stat() failed: Permission denied passwd-file(xxxxx@xxxx.net,::ffff:0.0.0.0): no passwd file: /var/mail/vhosts/xxxx.net/shadow Dovecot -n output # 1.0.7: /etc/dovecot.conf 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 mail_location: Maildir:/var/mail/vhosts/%d/%n 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/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login CRAM-MD5 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/shadow userdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix The passwd shadow file -rw-r----- 1 root root 210 May 24 21:39 passwd -rw-r----- 1 root root 327 May 24 21:39 shadow So who whould own these files? What should the perrmissions be?

4 7

[Dovecot] recipient_delimiter
by Phil Howard 02 Jun '10

02 Jun '10

I have recipient_delimiter = + in main.cf (Postfix). But deliveries to dovecot/deliver are still being rejected. It appears that the full email is still in the envelope (e.g. phil+howard(a)example.com which I want to be delivered to phil(a)example.com) Is that how it's supposed to work and Dovecot just doesn't support this?

4 29

Re: [Dovecot] draft-ietf-morg-list-specialuse-01 - IMAP LIST extension for special-use mailboxes
by Nikolay Shopik 01 Jun '10

01 Jun '10

On 20.05.2010 14:40, Timo Sirainen wrote: > On 20.5.2010, at 12.11, Nikolay Shopik wrote: > >> I don't think this really need per-user option. This is basically "system folders" and MUA will decide on their local names. Combining with autocreate plugin seems reasonable. > > Autocreate plugin would be useful only if it was a per-user option. Then it could create some kind of a file into the created mailbox. > > If it was a global option .. could it be just something as simple as > > list_specialuse = \Trash:Trash "\Sent:Sent Messages" etc. > > or > > list_specialuse_trash = Trash > list_specialuse_sent = Sent > etc. > > I don't really like either of them.. > What's wrong with these examples for global option, second one looks good for me.

3 4

[Dovecot] purge maildir folder after sa-learn
by Florian Effenberger 01 Jun '10

01 Jun '10

Hello, I am looking for a command-line utility to automatically purge one Maildir folder. I want to periodically run sa-learn from cron, and after the spam learning folder has been added to the Bayes database, its contents should be deleted. I've searched a bit, but only found a few old utilities or some telnet+expect scripts, which both didn't look too reliable. Is there any command-line utility to delete all contents of a Maildir folder, or is there any other solution? Thanks, Florian

6 16

Re: [Dovecot] cur folder e-mails are not shown...
by Gonzalo Aguilar Delgado 01 Jun '10

01 Jun '10

>Since you didn't claim you actually are missing mail, just seeing more Nope. As I suffer the same problem from Evolution and ThunderBird >They could be "deleted" (actually marked for deletion, physically >removed upon expunge). Those would have a T flag in the file name after >the comma. Your MUA Evolution shows them in the Trash (virtual) folder. I tried all this but nothing shown. It's like cur folder is not shown. >They could have been flagged Junk, and only be displayed in the Junk >(virtual) folder. Junk folder is almost empty since I have SpamAsassin in place >You could have a search active, hiding some mail. I checked this also. But's not. >You could have specifically hidden them. See the View menu. I checked show all. But only a few appears. The one deleted by spam filter in the client. What else can be?

2 2

[Dovecot] RTFM: Manual pages for Dovecot v2.0
by Pascal Volk 01 Jun '10

01 Jun '10

Hello Dovecot admins. I've started writing manual pages for Dovecot v2.0. I'm sure they are not perfect yet. I'd like to ask you all to read the manual pages. It would be nice to get some ideas/suggestions/improvements. So that that the Dovecot v2.0.0 release could be distributed with /fine manuals/. The manual pages are available at: http://wiki2.dovecot.org/ManPages This is also the intended place for 'discussions' about the man pages. Regards, Pascal -- The trapper recommends today: cafebabe.1007713(a)localdomain.org

2 3

Re: [Dovecot] quota and postfix virtual users
by gbotero＠emailforall.no-ip.org 01 Jun '10

01 Jun '10

hi, Simone Caruso, thanks for your answer but i have some questions i test the script in the console and he works he read the quota pased by mysql and then quota_rule ok but he update the maildirsize file??? and this script have to be called from postfix or dovecot?? thanks for all, sorry for my english ;) Guillermo Botero Leticia, Amazonas - Colombia gbospina(a)gmail.com

2 1

[Dovecot] Error: file_dotlock_open() failed with file $FILE ENOENT
by Pascal Volk 31 May '10

31 May '10

I've deleted some empty IMAP folders, using Thunderbird. But before deleting them, I had a look into Trash directory on the filesystem: /home/pvo/mdbox/mailboxes/Trash/ ├── dbox-Mails │ ├── dovecot.index │ ├── dovecot.index.backup │ ├── dovecot.index.cache │ └── dovecot.index.log ├── Dev │ └── dbox-Mails │ └── dovecot.index.log ├── S4 │ └── dbox-Mails │ └── dovecot.index.log └── Server4 └── dbox-Mails └── dovecot.index.log (Yeah, looks good, no dbox-GUID file.) After deleting all IMAP folders from Trash I found this lines in the log file: Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Apr 06 05:44:36 imap(pvo): Error: file_dotlock_open() failed with file /home/pvo/mdbox/mailboxes/Trash/S4/dbox-Mails/dovecot.index.log: No such file or directory Regards, Pascal -- The trapper recommends today: fabaceae.1009606(a)localdomain.org

2 1

[Dovecot] dovecot-2.0-pigeonhole/ManageSieve: wrong service name
by Pascal Volk 31 May '10

31 May '10

Hi Stephan, ManageSieve uses the wrong™ service name for the authdb lookup. With dovecot-1.2-managesieve the service name was changed from 'managesieve' to 'sieve'. So I altered my table layout in order to make the query "SELECT userid AS "user", password FROM dovecotpassword('%Ln', '%Ld') WHERE %Ls" work again. When I try to login on the sieve port 4190/tcp, I find this in my dovecot.log: auth: Error: pgsql: Query failed, retrying: ERROR: column "managesieve" does not exist auth: Error: LINE 1: ...", password FROM dovecotpassword('user', 'example.org') WHERE managesiev... Regards, Pascal -- The trapper recommends today: defaced.1015004(a)localdomain.org

3 4

[Dovecot] Permanent flags not announced and public mailbox with per-user index
by Julien Danjou 31 May '10

31 May '10

Hi, I've a set of public mailboxes that all users can access. The index is stored per user, so each user can mark the message as read for themselves. This is with dovecot 1.2.10. However, when selecting the mailbox, system flags are not announced as permanent but only as session flags: 3619 SELECT "public.Admin" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 324 EXISTS * 0 RECENT * OK [UNSEEN 171] First unseen. * OK [UIDVALIDITY 1254326934] UIDs valid * OK [UIDNEXT 1102] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest 3445 OK [READ-ONLY] Select completed. I think (reading the RFC, but I bet you know it better than me) that FLAGS should also been set in PERMANENTFLAGS since they can be permanent. The relevant code seems to be in commands-util.c (dovecot 1.2.11): void client_send_mailbox_flags(struct client *client, bool selecting) { […] if (mailbox_is_readonly(client->mailbox)) { client_send_line(client, "* OK [PERMANENTFLAGS ()] " "Read-only mailbox."); } else { […] } } Even if it's true that the Maildir is read-only, it's still possible to store \Seen permanently. Am I getting things wrong, or is this a bug? If I'm correct, a simple fix MAY be not to send the PERMANENTFLAGS at all since the RFC says: OK [PERMANENTFLAGS (<list of flags>)] A list of message flags that the client can change permanently. If this is missing, the client should assume that all flags can be changed permanently. Thanks, -- Julien Danjou // ᐰ <julien(a)danjou.info> http://julien.danjou.info

2 6

[Dovecot] Dovecot 2.0beta4 HG 11189: dovecot-uidvalidity warning with mdbox mailboxes
by Thomas Leuxner 31 May '10

31 May '10

Hi, the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly. ==> /var/log/dovecot.log <== Apr 24 14:35:09 spectre dovecot: imap(tlx(a)leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such file or directory $ ls -al /var/vmail/leuxner.net/tlx/mdbox total 36 drwx--S--- 4 vmail vmail 4096 2010-04-24 14:37 . drwx--S--- 4 vmail vmail 4096 2010-04-19 10:23 .. -rw------- 1 vmail vmail 386 2010-03-25 19:58 dovecot-acl-list -rw------- 1 vmail vmail 2952 2010-04-24 14:35 dovecot.mailbox.log -rw------- 1 vmail vmail 53 2010-04-24 14:37 dovecot-quota -rw------- 1 vmail vmail 8 2010-04-24 14:35 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 2010-04-24 14:35 dovecot-uidvalidity.4bd2e57d drwx--S--- 15 vmail vmail 4096 2010-03-17 19:57 mailboxes drwx--S--- 2 vmail vmail 4096 2010-04-24 14:37 storage -rw------- 1 vmail vmail 1639 2010-04-24 14:35 subscriptions # 2.0.beta4 (6a3eaad2bae6): /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_verbose = yes mail_location = mdbox:~/mdbox mail_plugins = acl quota namespace { hidden = no inbox = yes location = prefix = separator = / type = private } namespace { list = yes location = maildir:/var/vmail/public:LAYOUT=fs:INDEX=~/public prefix = Public/ separator = / subscriptions = no type = public } passdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } plugin { acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/conf.d/%d/sieve } protocols = imap lmtp service auth-worker { user = doveauth } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth } service imap-login { inet_listener imap { address = 1.2.3.4 port = 143 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/host_domain.crt ssl_key = </etc/ssl/private/host_domain_2010.key syslog_facility = local1 userdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } verbose_proctitle = yes protocol imap { mail_plugins = $mail_plugins imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = $mail_plugins sieve } Regards Thomas

2 1

[Dovecot] Dovecot 2.0.beta5: dovecot-uidlist: Duplicate file entry at line X
by Chris Laif 31 May '10

31 May '10

Hi, I'm using dovecot 2.0.beta5 (IMAP and LMTP+sieve) and I'm getting lots of errors like this: Warning: /data/mail/4567/Maildir/dovecot-uidlist: Duplicate file entry at line 3: 1274182284.M635158P16414.mail,S=767,W=785:2,S (uid 5 -> 16) All data is stored on local disk (ext3, no NFS!). As this is a fresh installation of dovecot I do not know if older versions work better. One user complained about loosing email from inbox but I guess that's probably a user error :) I think that the error might be related to deliveries via LMTP as this (new) functionality has not been tested extensivly (?) Regards, Chris ./configure \ --with-pgsql \ --with-ioloop=best \ --without-shadow \ --without-pam \ --without-nss \ --with-storages=maildir \ --without-vpopmail # 2.0.beta5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4 auth_cache_negative_ttl = 60 s auth_cache_size = 10485760 auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no first_valid_gid = 1234 first_valid_uid = 1234 info_log_path = /dev/stderr last_valid_gid = 1234 last_valid_uid = 1234 mail_location = maildir:~/Maildir passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = squat sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = -reject -vacation -enotify -notify } protocols = imap lmtp managesieve service lmtp { inet_listener { port = 24 } } service managesieve-login { inet_listener sieve { address = 10.2.3.4 } } ssl_cert = </etc/dovecot/ssl.crt ssl_key = </etc/dovecot/ssl.key userdb { args = uid=1234 gid=1234 home=/data/mail/%u driver = static } verbose_proctitle = yes protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 10 mail_plugins = fts fts_squat } protocol lmtp { mail_plugins = sieve

2 2

[Dovecot] cur folder e-mails are not shown...
by Gonzalo Aguilar Delgado 31 May '10

31 May '10

Hi All! I realized that I have only e-mails from last 13 days. I see that I have lots more in the cur folder inside my Maildir folder. The problem is that I cannot see them. Permissions seems to be right: drwx------ 2 gaguilar gaguilar 1081344 2010-05-28 12:53 cur -rw------- 1 gaguilar gaguilar 4798145 2010-05-28 12:52 deliver.info -rw------- 1 gaguilar gaguilar 0 2010-04-17 21:17 deliver.log -rw------- 1 gaguilar gaguilar 191344 2010-05-28 12:51 dovecot.index -rw------- 1 gaguilar gaguilar 708608 2010-05-28 12:52 dovecot.index.cache -rw------- 1 gaguilar gaguilar 26356 2010-05-28 12:53 dovecot.index.log -rw------- 1 gaguilar gaguilar 35 2010-04-24 19:57 dovecot-keywords -rw------- 1 gaguilar gaguilar 746874 2010-05-28 12:52 dovecot-uidlist -rw------- 1 gaguilar gaguilar 8 2010-05-28 12:46 dovecot-uidvalidity -rw------- 1 gaguilar gaguilar 0 2010-04-17 00:45 dovecot-uidvalidity.4bc8e88d drwx------ 2 gaguilar gaguilar 32768 2010-05-28 12:52 new -rw------- 1 gaguilar gaguilar 2742243 2010-05-28 12:52 procmail.log -rw------- 1 gaguilar gaguilar 48 2010-05-28 12:46 subscriptions drwx------ 2 gaguilar gaguilar 4096 2010-05-28 12:52 tmp dovecot --version 1.1.11 What can be the problem? ____________________________________

3 5

[Dovecot] 1.2.11, mbox, new mail
by Stan Hoeppner 31 May '10

31 May '10

With 1.2.11 and mbox storage, the delay time in pulling new mail headers to the client from imap folders seems to be directly proportional to mailbox size, regardless of the number of new messages. At present, if the mailbox is large, pulling new headers is rather painfully slow. Is this expected behavior? Especially given that the client already has all the "old" mails in the folder cached, and thus wouldn't be asking for them? Is there a setting(s) I can change to optimize/fix this? -- Stan

4 8

[Dovecot] strange sieve situation
by Andy Dills 31 May '10

31 May '10

Hi there, I've been working on rolling out the "deliver" service so we can implement sieve. Dovecot 1.2.11, Postfix 2.6.6, FreeBSD 8, installed by ports. Clustered environment, NFS backend. Everything is working great for the most part, I'm using it to sort a copy of my personal email on a test server. However, I noticed two emails were not properly sorted. I had added a rule (using Ingo, nice little piece of software) to redirect the nightly FreeBSD security output emails into a folder "servers". However, nothing had triggered that rule, and the "Maildir/.servers" directory had not yet been created. Then, three of the "security outputs" came in at one time: May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: failed to store into mailbox 'servers': Mailbox already exists May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070109.D8F5E159913(a)mail-out01.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070110.17A781B53B9(a)mail-out02.xecu.net>: stored mail into mailbox 'servers' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: msgid=<20100529070108.F2F0B7F5D4(a)mail-out04.xecu.net>: stored mail into mailbox 'INBOX' May 29 03:01:48 mg8 dovecot: deliver(andytest(a)xecu.net): sieve: execution of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve failed, but implicit keep was successful That's the order they appeared in my logfile. I'm assuming they were all sent to deliver at the same time, they all thought they needed to make the directory, the one with msgid 20100529070110.17A781B53B9(a)mail-out02.xecu.net was able to make the directory and get delivered, whereas the other two freaked out because they couldn't make the directory they thought needed to be made, and just sent the mail to the inbox. That's a reasonable approach, although I wonder if deliver/sieve could be (or perhaps "has been in 2.0") adjusted to more intelligently handle that edge case. Also, I'm wondering about "dovecot_destination_recipient_limit = 1". I have that set in my main.cf, but I'm not 100% positive it's taking effect. # grep dovecot /usr/local/etc/postfix/main.cf dovecot_destination_recipient_limit = 1 virtual_transport = dovecot # grep dovecot /usr/local/etc/postfix/master.cf dovecot unix - n n - - pipe flags=DRhu user=mailman argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} # postconf | grep dovecot smtpd_sasl_type = dovecot virtual_transport = dovecot # postconf | grep destination_recipient_limit default_destination_recipient_limit = 50 lmtp_destination_recipient_limit = $default_destination_recipient_limit local_destination_recipient_limit = 1 relay_destination_recipient_limit = $default_destination_recipient_limit smtp_destination_recipient_limit = $default_destination_recipient_limit virtual_destination_recipient_limit = $default_destination_recipient_limit Is "dovecot_destination_recipient_limit" being converted into local_ ? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 1

[Dovecot] Unresolved client rejection
by Greg Pearson 31 May '10

31 May '10

Hi, would it be possible to prevent users who try to login from an unresolved IP from connecting to Dovecot IMAP? I have a suspicion that it should be done via the authentication module (ie PAM) but I am not sure (if this is the case could someone recommend a good resource or even a solution). For example sendmail has a relevant macro to achieve this, I was wondering if Dovecot can have similar behavior. Thanks

2 1

Re: [Dovecot] Dovecot and Apples Mail.app
by Gerhard Waldemair 31 May '10

31 May '10

thanks for your answer. There is only 1 Account in Mail.app I have imigratet from Courier and there I had no Problem with all the settings. Is it possible that the index file is damaged or something like that ? Gerhard Am 28.05.10 17:56, schrieb Timo Sirainen: > > On Thu, 2010-05-27 at 10:17 +0200, Gerhard Waldemair wrote: > > >> Now I have the problem, that I get mail under Mail.app double. (same >> header, Message-ID ,...) >> >> When I use Thudnerbird under MacOS there is all OK. >> > That doesn't make any sense. Only thing I can think of is that you > created two identical accounts to Mail.app.. > > >> Are there some Configs that I need to make for MacOS / Mail.app ? >> > No. > >

1 0