August 2012 - dovecot

[Dovecot] segfault in mail_user_get_home()
by Lazy 31 Aug '12

31 Aug '12

gdb ./src/imap/.libs/imap Reading symbols from /usr/src/dovecot-2.1.9/src/imap/.libs/imap...done. (gdb) run Starting program: /usr/src/dovecot-2.1.9/src/imap/.libs/imap warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". process 1104 is executing new program: /usr/local/dovecot/bin/doveconf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". process 1104 is executing new program: /usr/src/dovecot-2.1.9/src/imap/.libs/imap [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7b2a0ff in mail_user_get_home (user=0x0, home_r=0x7fffffffe308) at mail-user.c:310 310 if (user->home_looked_up) { (gdb) bt #0 0x00007ffff7b2a0ff in mail_user_get_home (user=0x0, home_r=0x7fffffffe308) at mail-user.c:310 #1 0x00007ffff7ad172e in mdbox_storage_find_root_dir (ns=0x648610) at mdbox-storage.c:90 #2 0x00007ffff7ad180c in mdbox_storage_autodetect (ns=0x648610, set=0x7fffffffe4d0) at mdbox-storage.c:113 #3 0x00007ffff7b2345d in mail_storage_autodetect (ns=0x648610, set=0x7fffffffe4d0) at mail-storage.c:105 #4 0x00007ffff7b2369d in mail_storage_get_class (ns=0x648610, driver=0x0, list_set=0x7fffffffe4d0, flags=0, error_r=0x7fffffffe5b8) at mail-storage.c:180 #5 0x00007ffff7b23c90 in mail_storage_create (ns=0x648610, driver=0x0, flags=0, error_r=0x7fffffffe5b8) at mail-storage.c:342 #6 0x00007ffff7b1c62a in namespace_add (user=0x649be0, ns_set=0x64a8c8, unexpanded_ns_set=0x64a1c0, mail_set=0x64a440, ns_p=0x645380, error_r=0x7fffffffe6e8) at mail-namespace.c:126 #7 0x00007ffff7b1ccbb in mail_namespaces_init (user=0x649be0, error_r=0x7fffffffe6e8) at mail-namespace.c:289 #8 0x00007ffff7b34a64 in mail_storage_service_init_post (ctx=0x633460, user=0x633e08, priv=0x7fffffffe6f0, mail_user_r=0x7fffffffe7b8, error_r=0x7fffffffe6e8) at mail-storage-service.c:641 #9 0x00007ffff7b35dd6 in mail_storage_service_next (ctx=0x633460, user=0x633e08, mail_user_r=0x7fffffffe7b8) at mail-storage-service.c:1114 #10 0x00007ffff7b35efa in mail_storage_service_lookup_next (ctx=0x633460, input=0x7fffffffe810, user_r=0x7fffffffe7c0, mail_user_r=0x7fffffffe7b8, error_r=0x7fffffffe808) at mail-storage-service.c:1149 #11 0x000000000041f61c in client_create_from_input (input=0x7fffffffe810, login_client=0x7fffffffe880, fd_in=0, fd_out=1, input_buf=0x0, error_r=0x7fffffffe808) at main.c:202 #12 0x000000000041f859 in main_stdio_run (username=0x0) at main.c:247 #13 0x000000000041fd0a in main (argc=1, argv=0x631370) at main.c:381 /usr/local/dovecot/bin/doveconf -n # 2.1.9: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32 x86_64 Debian wheezy/sid namespace test { list = children location = maildir:/root/test prefix = test. subscriptions = yes type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = subscriptions = yes } passdb { driver = pam } ssl = no userdb { driver = passwd } without type = shared there is no segfault, I understand this config might not work (invoking imap directly) but it should't segfault. Regards, Michal Grzedzicki

2 2

[Dovecot] Variables in LDAP userdb
by Alex Crow 31 Aug '12

31 Aug '12

Hi Timo, Is it OK to have dovecot variables in entries in an LDAP userdb? Say I wanted to set the mail userdb parameter to override mail_location, would it work by having an entry in LDAP (eg for mailMessageStore attrib) like: mdbox:/home/email/%d/%n:INDEX=/home/indexes/%d/%1n/%n:ALT=/home/email_archive/%d/%1n/%n and those % variables will still be expanded by dovecot? Or would I be required to replace them in the LDAP directory with their actual values? Cheers Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc Domain House, 5-7 Singer Street, London EC2A 4BQ Tel: (020) 7608 4900 Fax: (020) 7608 5300 (Registered office: as above; Registered in England and Wales under number: 3727592) Authorised and regulated by the Financial Services Authority (entered on the FSA Register; number: 190856)

2 3

[Dovecot] Merge multiple doveadm commands
by Ralf Hildebrandt 31 Aug '12

31 Aug '12

Can I merge these three commands into one? doveadm expunge -u %s mailbox \"INBOX.Deleted Messages\" NOT NEW doveadm expunge -u %s mailbox INBOX.Trash NOT NEW doveadm expunge -u %s mailbox INBOX deleted -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

[Dovecot] doveadm commands returning 139 at director servers
by Angel L. Mateo 31 Aug '12

31 Aug '12

Hello, I have configured director in front of dovecot imap/pop/lmtp servers. When I need to manipulate a user mailbox, I use doveadm commands at director server's, with -S option. But some commands return exit code 139 when command returns more than 40 entries (I think). For example, the command: sudo doveadm fetch -u amateo hdr mailbox Trash HEADER Subject "nyctalus11/" executed at the backend server returns 952 mails, but executed at director server with -S option, returns only 40 mails and exit code 139. I'm using dovecot 2.1.5 and I attached doveconf -n at director and backend servers. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

1 1

[Dovecot] deliver doesn't update cache index with mbox
by Gerhard Wiesinger 30 Aug '12

30 Aug '12

Hello Timo, I'm having a problem with mbox that opening folder is slow when new mails are delivered to a folder. I'm delivering through the deliver program. Deliver updates index files but IHMO not completely correct. Therefore I compared index files before and after: 1.) Just delivered 2.) After accessing through imap via Thunderbird diff looks like (stripped down to the relevant things): INDEX: -first recent uid ......... = 25847 +first recent uid ......... = 25848 -log file tail offset ..... = 16468 -log file head offset ..... = 16468 +log file tail offset ..... = 16828 +log file head offset ..... = 16828 - - sync_mtime . = 2012-08-30 19:38:05 + - sync_mtime . = 2012-08-30 20:09:23 - - dirty_flag . = 1 + - dirty_flag . = 0 - - highest_modseq = 11162 + - highest_modseq = 11163 - - log_offset ... = 16468 + - log_offset ... = 16828 CACHE: -used_file_size ....... = 6385696 +used_file_size ....... = 6392132 RECORD: seq=25663, uid=25835, flags=0x00 - - ext 0 keywords : (0000) - - ext 1 modseq : 11156 (942b000000000000) + - ext 0 keywords : (0100) + - ext 1 modseq : 11163 (9b2b000000000000) - ext 2 mbox : 42923286 (16f58e0200000000) - - ext 3 cache : 0 (00000000) + - ext 3 cache : 6385696 (20706100) - ext 4 header-md5: (00000000000000000000000000000000) + - cache offset=6385696 size=488, prev_offset = 0 + - hdr.BCC: + - hdr.CC: + - hdr.CONTENT-TYPE: 18: Content-Type: text/plain; charset=us-ascii + - hdr.DATE: 13: Date: Thu, 30 Aug 2012 19:37:24 +0200 <some other hdr.xxxxx lines removed> + - size.virtual: 1081 (3904000000000000) Same patterns from record: 25664-25675 What does dirty_flag=1 mean? Why are the cache headers missing and not written by deliver? Any ideas? Config is below. Thank you. Ciao, Gerhard # 2.1.9: /etc/dovecot/dovecot.conf # OS: Linux listen = * mail_full_filesystem_access = yes mail_location = mbox:~:INBOX=/var/mail/%u mbox_lazy_writes = no mbox_write_locks = fcntl passdb { driver = pam } postmaster_address = postmaster@domain protocols = imap service auth { unix_listener auth-userdb { group = users mode = 0660 } } service imap-login { inet_listener imap { port = 0 } } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog } ssl_cert = </etc/pki/dovecot/dovecot-extern.pem ssl_key = </etc/pki/dovecot/private/dovecot-extern.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep } protocol lda { lda_mailbox_autocreate = yes log_timestamp = %Y.%m.%d %H:%M:%S%t mail_debug = yes mail_location = mbox:~/Mail:INBOX=/var/mail/%u }

1 0

[Dovecot] FS Quotas, what am I doing wrong?
by Kelsey Cummings 30 Aug '12

30 Aug '12

I'm not able to get the FS quota module to behave as I expect. Depsite having function fs quotas and dovecot apparently configured to use then, the quotas appear to be empty and/or not configured. Any clues? # quota kgc Disk quotas for user kgc (uid 500): Filesystem blocks quota limit grace files quota limit grace /dev/sda3 1229460 7000000 8000000 103776 5000000 6000000 # doveadm quota get -u kgc Quota name Type Value Limit % User user STORAGE 0 - 0 User user MESSAGE 0 - 0 # telnet 0 143 ... A003 GETQUOTAROOT INBOX <- Not sure this is correct A003 OK No quota. imap-login: Login: user=<kgc>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6048, secured, session=<1CGqXm7IhwB/AAAB> imap: Debug: Loading modules from directory: /usr/lib64/dovecot imap: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so imap: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so imap(kgc): Debug: Effective uid=500, gid=501, home=/home/kgc imap(kgc): Debug: Quota root: name=User user backend=fs args=inode_per_mail:noenforcing imap(kgc): Debug: maildir++: root=/home/kgc/Maildir, index=, control=, inbox=/home/kgc/Maildir, alt= imap(kgc): Debug: fs quota add mailbox dir = /home/kgc/Maildir imap(kgc): Debug: fs quota block device = /dev/sda3 imap(kgc): Debug: fs quota mount point = / imap(kgc): Debug: fs quota mount type = ext4 # 2.1.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.5.1.el6.x86_64 x86_64 Scientific Linux release 6.0 (Carbon) mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = quota mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = fs:User user:inode_per_mail:noenforcing } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_plugins = quota imap_quota } -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

1 0

[Dovecot] IMAP IDLE - iPhone?
by dovecot＠noboost.org 29 Aug '12

29 Aug '12

Hi All, Probably a very common question now days. I'd like to configure our iPhones at work to go directly to my dovecot server (currently dovecot-2.0.9-2.el6_1.1.x86_64). Using the IMAP IDLE (push email) protocol. Has anyone successfully deployed this? If yes, did you have to use an app from the Apple store? For me the IMAP process works, however it's clearly not notifying the client when new email is detected on the server. cya Craig

15 30

[Dovecot] Dovecot Director Output buffer full
by Dominic Malolepszy 29 Aug '12

29 Aug '12

Hi, I have been seeing the following messages in logs on all my Dovecot servers each running both a dovecot-director instance and a dovecot pop3/imap backend. These logs appear to relate to problems with the director. Aug 28 16:09:52 dovecot01 dovecot: director: Error: director(10.0.0.2:9090/right): Output buffer full, disconnecting Aug 28 16:10:01 dovecot01 dovecot: director: Error: Ring SYNC appears to have got lost, resending Aug 28 16:10:02 dovecot01 dovecot: director: Error: Director 10.0.0.2:9090/right disconnected Aug 28 16:09:51 dovecot02 dovecot: director: Error: director(10.0.0.3:9090/right): Output buffer full, disconnecting Aug 28 16:09:57 dovecot02 dovecot: director: Error: Ring SYNC appears to have got lost, resending Aug 28 16:10:01 dovecot02 dovecot: director: Error: Director 10.0.0.3:9090/right disconnected Aug 28 16:10:02 dovecot02 dovecot: director: Error: director(10.0.0.1:9090/left): Ping timed out, disconnecting Aug 28 16:13:15 dovecot02 dovecot: director: Warning: Delaying new user requests until ring is synced Note dovecot01 has IP 10.0.0.1 and dovecot02 has IP 10.0.0.2 and so on. This seems to show up when I enable the poolmon script (https://github.com/brandond/poolmon) on all the servers, and all servers start simultaneous logins to each others Dovecot backends. I did notice that the poolmon script has been flapping vhost weights a lot (I am looking at making the script handle transient errors better), which means that it is connecting to the dovecot-director socket every few minutes and changing vhost weights from 100 to 0 and vice-versa. Is there some sort of limit in the Dovecot Director that is being exceeded that should be tweaked? # 2.1.5: /etc/dovecot-director/dovecot.conf # OS: Linux 2.6.32-279.el6.mccqfix.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.3 (Santiago) auth_cache_size = 100 M auth_default_realm = example.com auth_failure_delay = 5 secs auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 auth_worker_max_count = 600 base_dir = /var/run/dovecot-director/ director_mail_servers = 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5 director_servers = 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5 disable_plaintext_auth = no instance_name = dovecot-dir passdb { args = /etc/dovecot-director/dovecot-sql.conf driver = sql } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 10.0.0.1 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { address = 10.0.0.1 port = 143 } inet_listener imaps { address = 10.0.0.1 port = 993 ssl = yes } process_min_avail = 100 } service pop3-login { executable = pop3-login director inet_listener pop3 { address = 10.0.0.1 port = 110 } inet_listener pop3s { address = 10.0.0.1 port = 995 ssl = yes } process_min_avail = 100 } verbose_proctitle = yes

1 0

[Dovecot] Size of Mailbox affecting the sending of mail?
by Tim Smith 29 Aug '12

29 Aug '12

Hi, I didn't know where to post this one so I'll start off with you guys and then try Postfix if I'm barking up the wrong tree! Having set up my mail server (Dovecot/Postfix), users are experiencing long delays (a couple of minutes) when sending mail from mail client such as Thunderbird - this increases with attachments. Having had a brief discussion with someone, they mentioned that the reason that this may be to do with the size of the mailbox. I couldn't see the rationale behind this unless Dovecot is syncing the mailbox after every sent mail (due to possibly saving the sent item?) The mail is being delivered successfully but the amount of time it is taking to complete the action is far too long! Sorry this is a bit vague but any advice on trying to diagnose the problem would be appreciated. Thanks in advance! Tim

6 9

[Dovecot] quota: ignore deleted messages (?)
by Sven Hartge 28 Aug '12

28 Aug '12

Hi! I am currently in the process of preparing a migration of our old Courier-based IMAP/POP server setup to a Dovecot-based one. During this process I came across the following problem with the difference Courier and Dovecot handle deleted messages and mail quota. Quote from http://www.courier-mta.org/imap/README.maildirquota.html: ,---- | The default application configuration that uses this maildirquota | library does not count deleted messages, and any contents of the Trash | folder, against the quota. Messages that are marked as deleted (but not | yet actually removed), or messages that are moved to the Trash folder | (which is subject to automatic purging) do not count towards the set | quota. `---- Ignoring the content (or increasing the quota) of the Trash folder is easy and no problem, but ignoring deleted messages seems impossible without changes to the code. While deleted messages are still stored on the server and still take up space until they are expunged, counting them against the quota is somewhat counter-intuitive because most clients don't show those mails and the normal user is unaware the mails he deleted are still there and take up space. Worse yet, if the client uses move-to-Trash, a user deleting mails will double the used space (until Expunge is used) and this may push him over his quota and thus cause any new mail delivery to fail. Unfortunately as our users are used to the courier way of handling the quota this will cause trouble after the migration. And this setup is run at a University, so I don't have any control over the clients a user uses and the behavior of said clients so I am not able to disable the move-to-Trash feature or force an immediate Expunge after a delete. So I propose an additional flag for the quota_rule config option to be able to enable a more lax interpretation of the quota enforcement: quota_rule = *:storage=1G:ignoredeleted quota_rule2 = Trash:storage=+100M Of course I would then have a nightly cronjob which force-expunges all deleted messages so that users can't store mails infinitely in their mailboxes. Thanks for your time and Grüße, Sven. -- Sigmentation fault. Core dumped.

5 18