- dovecot - dovecot.org

sql delete problem
by Tóth Csaba 24 Jan '16

24 Jan '16

Dear List! I have a dovecot installment with postgresql based user management. My problem is i see this in postgresql's log file: root@c13:/var/lib/postgresql/9.4/main/pg_log# cat postgresql-2016-01-24_12.log | grep 26105 2016-01-24 16:34:43 CET [26105-1] maildata@mail ERROR: permission denied for relation i3sysadm_email_account 2016-01-24 16:34:43 CET [26105-2] maildata@mail STATEMENT: DELETE FROM i3sysadm_email_account WHERE userid = 'account(a)mydomain.com' This is the error message from dovecot side (i have a lot, so this is from another date): root@c10:/var/log/dovecot# cat mail.log | grep "Jan 24 17:41:29" Jan 24 17:41:29 dict: Info: pgsql(127.0.0.1): Disconnected from database, retrying commit Jan 24 17:41:29 dict: Error: sql dict: commit failed: ERROR: permission denied for relation i3sysadm_email_account (query: DELETE FROM i3sysadm_email_account WHERE userid = 'account(a)mydomain.com') Why the hack dovecot want to delete my e-mail account? Luckily it don't have the permission.. I tried to look in the source code for "delete from", but founded just a general sql handle method. One possiblity is dovecot try to delete a cascaded information, but what can it be? Please help, how can i fix this. Thanks in advance, Csaba root@c10:/var/log/dovecot# dovecot --version 2.2.9 root@c10:/var/log/dovecot# dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-44-generic x86_64 Ubuntu 14.10 auth_cache_negative_ttl = 0 auth_failure_delay = 3 secs auth_master_user_separator = * auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb base_dir = /var/run/dovecot/ dict { expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_uid = 5000 hostname = mail.mydomain.com lda_mailbox_autocreate = yes listen = 87.229.104.6, :: lmtp_rcpt_check_quota = yes log_path = /var/log/dovecot/mail.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = 192.168.0.0/24 mail_access_groups = dovenull mail_gid = dovenull mail_location = sdbox:~/sdbox mail_plugins = quota mail_uid = dovenull managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes quota = dict:User quota::proxy::quota quota_grace = 10%% quota_rule = *:storage=100M recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap lmtp sieve pop3" service auth-postlogin { executable = script-login /etc/dovecot/update_date_smtp.sh user = $default_internal_user } service auth-worker { unix_listener auth-worker { group = $default_internal_user mode = 0660 user = dovecot } user = $default_internal_user } service auth { executable = auth auth-postlogin unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } user = $default_internal_user } service dict { unix_listener dict { group = $default_internal_user mode = 0666 user = $default_internal_user } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap-postlogin { executable = script-login /etc/dovecot/update_date_imap.sh user = $default_internal_user } service imap { executable = imap imap-postlogin } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3-postlogin { executable = script-login /etc/dovecot/update_date_pop3.sh user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin } shutdown_clients = no ssl_cert = </etc/dovecot/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/dovecot/private/dovecot.pem ssl_protocols = !SSLv2 !SSLv3 submission_host = 127.0.0.1:25 userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { info_log_path = /var/log/dovecot/lmtp.log mail_plugins = quota quota sieve postmaster_address = postmaster(a)mydomain.com } protocol lda { mail_plugins = quota sieve } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 mail_plugins = quota imap_quota } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } root@c10:/etc/dovecot# grep -v '^ *$#.*$\?$' dovecot-sql.conf.ext driver = pgsql connect = host=127.0.0.1 port=5432 dbname=mail user=maildata password=* default_pass_scheme = SSHA512 user_query = SELECT userdb_home AS home, userdb_uid AS uid, userdb_gid AS gid, \ mail_location AS mail, quota_rule \ FROM i3sysadm_email_account WHERE userid = '%Lu' AND active is true AND active_domain is true password_query = SELECT userid AS user, password, \ userdb_home, userdb_uid, userdb_gid, \ mail_location, quota_rule \ FROM i3sysadm_email_account WHERE userid = '%Lu' \ and active IS true AND active_domain IS true iterate_query = SELECT userid FROM i3sysadm_email_account \ WHERE active IS true AND active_domain IS true

2 1

How to skip errors on doveadm backup for migration ?
by Christoph Adomeit 24 Jan '16

24 Jan '16

Hi there, I have to migrate data out of a very old (debian 4) and buggy cyrus mailserver. About 40 Users with 200000 Messages each. Doveadm backup works quite well and gives me most of the mails. About every 100.000 Mail cannot be exported by cyrus. I do not want to bother about these errors. Maybe it is filesystem, maybe it is memory leak, or cyrus bug or whatever. My problem is that doveadm backup exits with an error if it cannot read a mail. Is there some way or option to make doveadm backup just skip the errors and continue with the next message ? I want to use doveadm sync because it preserves the uids of the mails. Imapsync works great but does not prserve uids. cyrus2dovecot is not an option because it does not work incremental and conversion would take far too long. Any ideas what I can do ? Thanks Christoph

3 5

Sieve "foreverypart" and "mime" extensions (RFC 5703) now implemented
by Stephan Bosch 24 Jan '16

24 Jan '16

Hi, I have finally managed to implement the Sieve "foreverypart" and "mime" extensions (RFC 5703). These are now included in the main Mercurial repository and will be included in the next release. I will be fixing a few minor details in the coming week; e.g., interaction with "include" and "editheader" extensions needs more work. Still, in the mean time, those of you who are interested can already test this feature a bit. It is not a small feature, so knowing bugs early is helpful. You can install it from the Mercurial repository or get the latest Debian packages from Xi. When I finish the last details (probably next week), I will release a first RC version of Pigeonhole v0.4.10 right away. Regards, Stephan.

2 2

Segfault in acl_mailbox_get_aclobj w/ dovecot
by D[r]eadlock M 23 Jan '16

23 Jan '16

Hello, I've being trying to play with shared mailboxes but experienced a segfault: [New LWP 9611] Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt f #0 0x00007f5b72f429b2 in acl_mailbox_get_aclobj (box=<optimized out>) at acl-mailbox.c:31 abox = 0x0 #1 0x00007f5b72d30fcc in cmd_myrights (cmd=0x7f5b75c97480) at imap-acl-plugin.c:331 ns = <optimized out> box = 0x7f5b75ca4520 mailbox = 0x7f5b75c752a8 "shared" orig_mailbox = 0x7f5b75c80be0 "shared" rights = 0x7f5b75c75108 str = <optimized out> #2 0x00007f5b73f2e09c in command_exec (cmd=cmd@entry=0x7f5b75c97480) at imap-commands.c:158 hook = 0x7f5b75c7e0f0 ret = <optimized out> #3 0x00007f5b73f2cfb2 in client_command_input (cmd=0x7f5b75c97480) at imap-client.c:778 client = 0x7f5b75c96880 command = <optimized out> __FUNCTION__ = "client_command_input" #4 0x00007f5b73f2d066 in client_command_input (cmd=0x7f5b75c97480) at imap-client.c:839 client = 0x7f5b75c96880 command = <optimized out> __FUNCTION__ = "client_command_input" #5 0x00007f5b73f2d39d in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x7f5b75c96880) at imap-client.c:877 No locals. #6 client_handle_input (client=0x7f5b75c96880) at imap-client.c:889 _data_stack_cur_id = 3 remove_io = false handled_commands = true client = 0x7f5b75c96880 #7 0x00007f5b73f2d745 in client_input (client=0x7f5b75c96880) at imap-client.c:931 cmd = 0x9f3f2 output = 0x7f5b75c972c0 bytes = 95 __FUNCTION__ = "client_input" #8 0x00007f5b73773d0f in io_loop_call_io (io=0x7f5b75c97390) at ioloop.c:441 ioloop = 0x7f5b75c7d740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #9 0x00007f5b73774d09 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f5b75c7d740) at ioloop-epoll.c:220 ctx = 0x7f5b75c7e3d0 io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999014} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #10 0x00007f5b73773d79 in io_loop_handler_run (ioloop=ioloop@entry=0x7f5b75c7d740) at ioloop.c:488 No locals. #11 0x00007f5b73773df8 in io_loop_run (ioloop=0x7f5b75c7d740) at ioloop.c:465 __FUNCTION__ = "io_loop_run" #12 0x00007f5b7371edc3 in master_service_run (service=0x7f5b75c7d5d0, callback=<optimized out>) at master-service.c:566 No locals. #13 0x00007f5b73f21254 in main (argc=1, argv=0x7f5b75c7d390) at main.c:400 set_roots = {0x7f5b74145980 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x7f5b75c75048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x7f5b73f371f0 <login_client_connected>, failure_callback = 0x7f5b73f36ed0 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 c = <optimized out> It happens when my client (mutt) tries to enter the shared/ folder. A filtered strace shows (note the 7 seconds between write and read, presumely the command sent by mutt): 8704 00:40:51.420843 open("/var/vmail/domain.tld/marc/Maildir/.Sent/dovecot-acl", O_RDONLY) = -1 ENOENT (No such file or directory) 8704 00:40:51.420978 stat("/var/vmail/domain.tld/marc/Maildir/dovecot-acl", 0x7fffc618dcb0) = -1 ENOENT (No such file or directory) 8704 00:40:51.421100 open("/var/vmail/domain.tld/shared-mailboxes", O_RDONLY) = 4 8704 00:40:51.421800 openat(AT_FDCWD, "/var/vmail/domain.tld/marc/Maildir", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 12 8704 00:40:51.422217 write(7, "* LIST (\\HasNoChildren \\Sent) \"/\" Sent\r\n* LIST (\\Noselect \\HasNoChildren) \"/\" shared\r\n* LIST (\\HasNoChildren) \"/\" INBOX\r\na0005 OK List completed.\r\n", 147) = 147 8704 00:40:58.235762 <... read resumed> "a0006 MYRIGHTS \"shared\"\r\na0007 STATUS \"Drafts\" (MESSAGES)\r\na0008 SELECT \"shared\"\r\n", 8137) = 82 I admit I've played a little with directories in /var/vmail/ and got a few 'permission denied' but I think I fixed them correctly (move /var/mail/domain.tld/marc into .../Maildir, who ended being root:root) To finish, my dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 mail_location = maildir:~/Maildir mail_plugins = acl namespace { location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/shared/%%n prefix = shared/%%n/ separator = / type = shared } namespace inbox { inbox = 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 = separator = / type = private } passdb { args = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/var/vmail/%d/shared-mailboxes } protocols = " imap lmtp" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/domain.tld/fullchain.pem ssl_key = </etc/letsencrypt/live/domain.tld/privkey.pem userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/shared/%n driver = static } protocol imap { mail_plugins = acl imap_acl } Thanks, Marc

2 1

2.2.21 imap crash - autoexpunge related?
by Robert Blayzor 22 Jan '16

22 Jan '16

dovecot --version 2.2.21 (5345f22) FreeBSD 10.2-RELEASE-p10 FreeBSD 10.2-RELEASE-p10 #0 r294322M: having repeated core dumps on imap process… autoexpunge issue? GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot-storage.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/dovecot/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib20_zlib_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib20_zlib_plugin.so Reading symbols from /lib/libz.so.6...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/lib/libbz2.so.4...done. Loaded symbols for /usr/lib/libbz2.so.4 Reading symbols from /usr/lib/liblzma.so.5...done. Loaded symbols for /usr/lib/liblzma.so.5 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000010cf9730 in o_stream_get_buffer_used_size (stream=0x0) at ostream.c:198 198 ostream.c: No such file or directory. in ostream.c (gdb) bt full #0 0x0000000010cf9730 in o_stream_get_buffer_used_size (stream=0x0) at ostream.c:198 _stream = (const struct ostream_private *) 0xd #1 0x0000000000435ac9 in notify_ok (mailbox=0x118e1c40, text=0x118063a8 "Stale mailbox lock file detected, will override in 0 seconds", context=0x11845840) at mail-storage-callbacks.c:13 client = (struct client *) 0x11845840 #2 0x000000001096f4e4 in index_storage_lock_notify (box=0x118e1c40, notify_type=MAILBOX_LOCK_NOTIFY_MAILBOX_OVERRIDE, secs_left=0) at index-storage.c:137 ibox = (struct index_mailbox_context *) 0x118e20b0 storage = (struct mail_storage *) 0x11873640 str = 0x118063a8 "Stale mailbox lock file detected, will override in 0 seconds" now = 1453427588 #3 0x00000000108fbedd in dotlock_callback (secs_left=0, stale=true, context=0x118e1c40) at maildir-uidlist.c:250 box = (struct mailbox *) 0x118e1c40 #4 0x0000000010ccba7c in dotlock_create (dotlock=0x118a8140, flags=DOTLOCK_CREATE_FLAG_NONBLOCK, write_pid=true, lock_path_r=0x7fffffffe4e0) at file-dotlock.c:549 secs_left = 0 set = (const struct dotlock_settings *) 0x118a8140 lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock" lock_info = {set = 0x118a8140, path = 0x118b59c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist", lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock", temp_path = 0x0, fd = -1, lock_info = {dev = 0, ino = 0, size = 0, ctime = 0, mtime = 0}, file_info = {dev = 0, ino = 0, size = 0, ctime = 0, mtime = 0}, last_pid_check = 0, last_change = 0, wait_usecs = 0, have_pid = 0, pid_read = 0, use_io_notify = 1, lock_stated = 1} st = {st_dev = 1, st_ino = 32767, st_mode = 0, st_nlink = 0, st_uid = 0, st_gid = 0, st_rdev = 0, st_atim = {tv_sec = 140737488348216, tv_nsec = 140737488347840}, st_mtim = {tv_sec = 12884901898, tv_nsec = 140737488348320}, st_ctim = {tv_sec = 167, tv_nsec = 0}, st_size = 275162112, st_blocks = 140737488348192, st_blksize = 275046283, st_flags = 0, st_gen = 4294960312, st_lspare = 32767, st_birthtim = {tv_sec = 140737488348216, tv_nsec = 277283844}} stale_notify_threshold = 60 change_secs = 1453427588 wait_left = 2841539708 now = 1453427588 max_wait_time = 0 last_notify = 1453427588 prev_last_change = 0 prev_wait_update = 0 tmp_path = (string_t *) 0x11806270 ret = 0 do_wait = false #5 0x0000000010ccaf87 in file_dotlock_create_real (dotlock=0x118a8140, flags=DOTLOCK_CREATE_FLAG_NONBLOCK) at file-dotlock.c:629 lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock" st = {st_dev = 284562744, st_ino = 0, st_mode = 58544, st_nlink = 65535, st_uid = 32767, st_gid = 282105456, st_rdev = 0, st_atim = {tv_sec = 140737488290687, tv_nsec = 50}, st_mtim = {tv_sec = 294345152, tv_nsec = 293746112}, st_ctim = {tv_sec = 284562744, tv_nsec = 294345152}, st_size = 140737488348368, st_blocks = 281883903, st_blksize = 96, st_flags = 0, st_gen = 293746112, st_lspare = 0, st_birthtim = {tv_sec = 140737488348416, tv_nsec = 281819373}} fd = 0 ret = 50 #6 0x0000000010ccae76 in file_dotlock_create (set=0x118dd138, path=0x118235c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist", flags=DOTLOCK_CREATE_FLAG_NONBLOCK, dotlock_r=0x118dd168) at file-dotlock.c:673 _data_stack_cur_id = 5 dotlock = (struct dotlock *) 0x118a8140 ret = 0 #7 0x00000000108fb891 in maildir_uidlist_lock_timeout (uidlist=0x118dd100, nonblock=true, refresh=true, refresh_when_locked=true) at maildir-uidlist.c:160 box = (struct mailbox *) 0x118e1c40 perm = (const struct mailbox_permissions *) 0x118e1e10 path = 0x118235c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist" old_mask = 63 dotlock_flags = DOTLOCK_CREATE_FLAG_NONBLOCK i = 0 ---Type <return> to continue, or q <return> to quit--- ret = -5216 #8 0x00000000108fe066 in maildir_uidlist_sync_lock (uidlist=0x118dd100, sync_flags=MAILDIR_UIDLIST_SYNC_TRYLOCK, locked_r=0x7fffffffe617) at maildir-uidlist.c:1608 nonblock = true refresh = true ret = -5184 #9 0x00000000108fdd86 in maildir_uidlist_sync_init (uidlist=0x118dd100, sync_flags=MAILDIR_UIDLIST_SYNC_TRYLOCK, sync_ctx_r=0x118061b8) at maildir-uidlist.c:1638 ctx = (struct maildir_uidlist_sync_ctx *) 0x118061b8 locked = false ret = 4 #10 0x00000000108fa021 in maildir_sync_context (ctx=0x11806188, forced=false, find_uid=0x0, lost_files_r=0x7fffffffe71f) at maildir-sync.c:871 sync_flags = MAILDIR_UIDLIST_SYNC_TRYLOCK flags = 4294960816 new_changed = true cur_changed = true lock_failure = false fname = 0x7fffffffe5a0 "àåÿÿÿ\177" why = 36 ret = 1 #11 0x00000000108f9400 in maildir_sync_run (mbox=0x118e1c40, flags=68, force_resync=false, uid=0x0, lost_files_r=0x7fffffffe71f) at maildir-sync.c:1023 _data_stack_cur_id = 4 ctx = (struct maildir_sync_context *) 0x11806188 retry = false lost_files = false ret = 294526016 #12 0x00000000108f96b0 in maildir_storage_sync_init (box=0x118e1c40, flags=68) at maildir-sync.c:1096 mbox = (struct maildir_mailbox *) 0x118e1c40 lost_files = false force_resync = false ret = 0 #13 0x00000000108b75b9 in mailbox_sync_init (box=0x118e1c40, flags=68) at mail-storage.c:1657 _data_stack_cur_id = 3 ctx = (struct mailbox_sync_context *) 0xc #14 0x00000000108b6891 in mailbox_sync (box=0x118e1c40, flags=68) at mail-storage.c:1705 ctx = (struct mailbox_sync_context *) 0x206 status = {sync_delayed_expunges = 1} #15 0x00000000108a6e65 in mailbox_autoexpunge (box=0x118e1c40, expire_time=1450835588) at mail-autoexpunge.c:29 t = (struct mailbox_transaction_context *) 0x11873640 mail = (struct mail *) 0x118e1c40 metadata = {guid = '\0' <repeats 15 times>, virtual_size = 0, physical_size = 0, first_save_date = 1450835021, cache_fields = 0x0, precache_fields = 0, backend_ns_prefix = 0x0, backend_ns_type = 0} hdr = (const struct mail_index_header *) 0x118b7f10 seq = 0 timestamp = 140737488349168 ret = 0 #16 0x00000000108a6d54 in mail_namespace_autoexpunge (ns=0x118a6020) at mail-autoexpunge.c:76 box_set__foreach_end = (const void *) 0x118b73f0 box_set = (struct mailbox_settings * const *) 0x118b73d8 box = (struct mailbox *) 0x118e1c40 ---Type <return> to continue, or q <return> to quit--- expire_time = 1450835588 #17 0x00000000108a6c54 in mail_user_autoexpunge (user=0x118b6040) at mail-autoexpunge.c:91 ns = (struct mail_namespace *) 0x118a6020 #18 0x00000000108c1b62 in mail_user_unref (_user=0x118458d0) at mail-user.c:167 user = (struct mail_user *) 0x118b6040 #19 0x00000000004216b4 in client_default_destroy (client=0x11845840, reason=0x0) at imap-client.c:390 cmd = (struct client_command_context *) 0x435c47 #20 0x000000000041f53d in client_destroy (client=0x11845840, reason=0x0) at imap-client.c:263 No locals. #21 0x000000000041eccb in client_input (client=0x11845840) at imap-client.c:1121 cmd = (struct client_command_context *) 0x2118401a0 output = (struct ostream *) 0x0 bytes = 11 #22 0x0000000010ce738f in io_loop_call_io (io=0x1187c240) at ioloop.c:559 ioloop = (struct ioloop *) 0x11821080 t_id = 2 #23 0x0000000010cea343 in io_loop_handler_run_internal (ioloop=0x11821080) at ioloop-kqueue.c:151 ctx = (struct ioloop_handler_context *) 0x118190a0 events = (struct kevent *) 0x1187d000 event = (const struct kevent *) 0x1187d000 tv = {tv_sec = 1799, tv_usec = 999920} ts = {tv_sec = 1799, tv_nsec = 999920000} io = (struct io_file *) 0x1187c240 events_count = 5 ret = 1 i = 0 #24 0x0000000010ce791e in io_loop_handler_run (ioloop=0x11821080) at ioloop.c:607 No locals. #25 0x0000000010ce773f in io_loop_run (ioloop=0x11821080) at ioloop.c:583 No locals. #26 0x0000000010c41aab in master_service_run (service=0x1181b140, callback=0x436ab0 <client_connected>) at master-service.c:640 No locals. #27 0x00000000004363c3 in main (argc=2, argv=0x7fffffffeba8) at main.c:442 set_roots = {0x441248, 0x0} login_set = {auth_socket_path = 0x11806040 "x`\200\021", postlogin_socket_path = 0x11806078 "", postlogin_timeout_secs = 60, callback = 0x436760 <login_client_connected>, failure_callback = 0x436a20 <login_client_failed>, request_auth_token = 1} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = -1 (gdb) For comparison crash on another server, similar: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot-storage.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/dovecot/lib10_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/local/lib/dovecot/lib20_zlib_plugin.so...done. Loaded symbols for /usr/local/lib/dovecot/lib20_zlib_plugin.so Reading symbols from /lib/libz.so.6...done. Loaded symbols for /lib/libz.so.6 Reading symbols from /usr/lib/libbz2.so.4...done. Loaded symbols for /usr/lib/libbz2.so.4 Reading symbols from /usr/lib/liblzma.so.5...done. Loaded symbols for /usr/lib/liblzma.so.5 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000010cf9730 in o_stream_get_buffer_used_size (stream=0x0) at ostream.c:198 198 ostream.c: No such file or directory. in ostream.c (gdb) bt full #0 0x0000000010cf9730 in o_stream_get_buffer_used_size (stream=0x0) at ostream.c:198 _stream = (const struct ostream_private *) 0xd #1 0x0000000000435ac9 in notify_ok (mailbox=0x118e1c40, text=0x118063a8 "Stale mailbox lock file detected, will override in 0 seconds", context=0x11845840) at mail-storage-callbacks.c:13 client = (struct client *) 0x11845840 #2 0x000000001096f4e4 in index_storage_lock_notify (box=0x118e1c40, notify_type=MAILBOX_LOCK_NOTIFY_MAILBOX_OVERRIDE, secs_left=0) at index-storage.c:137 ibox = (struct index_mailbox_context *) 0x118e20b0 storage = (struct mail_storage *) 0x11873640 str = 0x118063a8 "Stale mailbox lock file detected, will override in 0 seconds" now = 1453448110 #3 0x00000000108fbedd in dotlock_callback (secs_left=0, stale=true, context=0x118e1c40) at maildir-uidlist.c:250 box = (struct mailbox *) 0x118e1c40 #4 0x0000000010ccba7c in dotlock_create (dotlock=0x118a8140, flags=DOTLOCK_CREATE_FLAG_NONBLOCK, write_pid=true, lock_path_r=0x7fffffffe4e0) at file-dotlock.c:549 secs_left = 0 set = (const struct dotlock_settings *) 0x118a8140 lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock" lock_info = {set = 0x118a8140, path = 0x118b59c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist", lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock", temp_path = 0x0, fd = -1, lock_info = {dev = 0, ino = 0, size = 0, ctime = 0, mtime = 0}, file_info = {dev = 0, ino = 0, size = 0, ctime = 0, mtime = 0}, last_pid_check = 0, last_change = 0, wait_usecs = 0, have_pid = 0, pid_read = 0, use_io_notify = 1, lock_stated = 1} st = {st_dev = 1, st_ino = 32767, st_mode = 0, st_nlink = 0, st_uid = 0, st_gid = 0, st_rdev = 0, st_atim = {tv_sec = 140737488348216, tv_nsec = 140737488347840}, st_mtim = {tv_sec = 12884901898, tv_nsec = 140737488348320}, st_ctim = {tv_sec = 167, tv_nsec = 0}, st_size = 275162112, st_blocks = 140737488348192, st_blksize = 275046283, st_flags = 0, st_gen = 4294960312, st_lspare = 32767, st_birthtim = {tv_sec = 140737488348216, tv_nsec = 277283844}} stale_notify_threshold = 60 change_secs = 1453448110 wait_left = 2841519186 now = 1453448110 max_wait_time = 0 last_notify = 1453448110 prev_last_change = 0 prev_wait_update = 0 tmp_path = (string_t *) 0x11806270 ret = 0 do_wait = false #5 0x0000000010ccaf87 in file_dotlock_create_real (dotlock=0x118a8140, flags=DOTLOCK_CREATE_FLAG_NONBLOCK) at file-dotlock.c:629 lock_path = 0x11806220 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist.lock" st = {st_dev = 284562744, st_ino = 0, st_mode = 58544, st_nlink = 65535, st_uid = 32767, st_gid = 282105456, st_rdev = 0, st_atim = {tv_sec = 140737488290687, tv_nsec = 50}, st_mtim = {tv_sec = 294345152, tv_nsec = 293746112}, st_ctim = {tv_sec = 284562744, tv_nsec = 294345152}, st_size = 140737488348368, st_blocks = 281883903, st_blksize = 96, st_flags = 0, st_gen = 293746112, st_lspare = 0, st_birthtim = {tv_sec = 140737488348416, tv_nsec = 281819373}} fd = 0 ret = 50 #6 0x0000000010ccae76 in file_dotlock_create (set=0x118dd138, path=0x118235c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist", flags=DOTLOCK_CREATE_FLAG_NONBLOCK, dotlock_r=0x118dd168) at file-dotlock.c:673 _data_stack_cur_id = 5 dotlock = (struct dotlock *) 0x118a8140 ret = 0 #7 0x00000000108fb891 in maildir_uidlist_lock_timeout (uidlist=0x118dd100, nonblock=true, refresh=true, refresh_when_locked=true) at maildir-uidlist.c:160 box = (struct mailbox *) 0x118e1c40 perm = (const struct mailbox_permissions *) 0x118e1e10 path = 0x118235c0 "/var/mail/mbox1/0/2/Maildir/.Junk/dovecot-uidlist" old_mask = 63 dotlock_flags = DOTLOCK_CREATE_FLAG_NONBLOCK i = 0 ---Type <return> to continue, or q <return> to quit--- ret = -5216 #8 0x00000000108fe066 in maildir_uidlist_sync_lock (uidlist=0x118dd100, sync_flags=MAILDIR_UIDLIST_SYNC_TRYLOCK, locked_r=0x7fffffffe617) at maildir-uidlist.c:1608 nonblock = true refresh = true ret = -5184 #9 0x00000000108fdd86 in maildir_uidlist_sync_init (uidlist=0x118dd100, sync_flags=MAILDIR_UIDLIST_SYNC_TRYLOCK, sync_ctx_r=0x118061b8) at maildir-uidlist.c:1638 ctx = (struct maildir_uidlist_sync_ctx *) 0x118061b8 locked = false ret = 4 #10 0x00000000108fa021 in maildir_sync_context (ctx=0x11806188, forced=false, find_uid=0x0, lost_files_r=0x7fffffffe71f) at maildir-sync.c:871 sync_flags = MAILDIR_UIDLIST_SYNC_TRYLOCK flags = 4294960816 new_changed = true cur_changed = true lock_failure = false fname = 0x7fffffffe5a0 "àåÿÿÿ\177" why = 36 ret = 1 #11 0x00000000108f9400 in maildir_sync_run (mbox=0x118e1c40, flags=68, force_resync=false, uid=0x0, lost_files_r=0x7fffffffe71f) at maildir-sync.c:1023 _data_stack_cur_id = 4 ctx = (struct maildir_sync_context *) 0x11806188 retry = false lost_files = false ret = 294526016 #12 0x00000000108f96b0 in maildir_storage_sync_init (box=0x118e1c40, flags=68) at maildir-sync.c:1096 mbox = (struct maildir_mailbox *) 0x118e1c40 lost_files = false force_resync = false ret = 0 #13 0x00000000108b75b9 in mailbox_sync_init (box=0x118e1c40, flags=68) at mail-storage.c:1657 _data_stack_cur_id = 3 ctx = (struct mailbox_sync_context *) 0xc #14 0x00000000108b6891 in mailbox_sync (box=0x118e1c40, flags=68) at mail-storage.c:1705 ctx = (struct mailbox_sync_context *) 0x206 status = {sync_delayed_expunges = 1} #15 0x00000000108a6e65 in mailbox_autoexpunge (box=0x118e1c40, expire_time=1450856110) at mail-autoexpunge.c:29 t = (struct mailbox_transaction_context *) 0x11873640 mail = (struct mail *) 0x118e1c40 metadata = {guid = '\0' <repeats 15 times>, virtual_size = 0, physical_size = 0, first_save_date = 1450855115, cache_fields = 0x0, precache_fields = 0, backend_ns_prefix = 0x0, backend_ns_type = 0} hdr = (const struct mail_index_header *) 0x118b7f10 seq = 0 timestamp = 140737488349168 ret = 0 #16 0x00000000108a6d54 in mail_namespace_autoexpunge (ns=0x118a6020) at mail-autoexpunge.c:76 box_set__foreach_end = (const void *) 0x118b73f0 box_set = (struct mailbox_settings * const *) 0x118b73d8 box = (struct mailbox *) 0x118e1c40 ---Type <return> to continue, or q <return> to quit--- expire_time = 1450856110 #17 0x00000000108a6c54 in mail_user_autoexpunge (user=0x118b6040) at mail-autoexpunge.c:91 ns = (struct mail_namespace *) 0x118a6020 #18 0x00000000108c1b62 in mail_user_unref (_user=0x118458d0) at mail-user.c:167 user = (struct mail_user *) 0x118b6040 #19 0x00000000004216b4 in client_default_destroy (client=0x11845840, reason=0x0) at imap-client.c:390 cmd = (struct client_command_context *) 0x435c47 #20 0x000000000041f53d in client_destroy (client=0x11845840, reason=0x0) at imap-client.c:263 No locals. #21 0x000000000041eccb in client_input (client=0x11845840) at imap-client.c:1121 cmd = (struct client_command_context *) 0x2118401a0 output = (struct ostream *) 0x0 bytes = 11 #22 0x0000000010ce738f in io_loop_call_io (io=0x1187c240) at ioloop.c:559 ioloop = (struct ioloop *) 0x11821080 t_id = 2 #23 0x0000000010cea343 in io_loop_handler_run_internal (ioloop=0x11821080) at ioloop-kqueue.c:151 ctx = (struct ioloop_handler_context *) 0x118190a0 events = (struct kevent *) 0x1187d000 event = (const struct kevent *) 0x1187d000 tv = {tv_sec = 1799, tv_usec = 999858} ts = {tv_sec = 1799, tv_nsec = 999858000} io = (struct io_file *) 0x1187c240 events_count = 5 ret = 1 i = 0 #24 0x0000000010ce791e in io_loop_handler_run (ioloop=0x11821080) at ioloop.c:607 No locals. #25 0x0000000010ce773f in io_loop_run (ioloop=0x11821080) at ioloop.c:583 No locals. #26 0x0000000010c41aab in master_service_run (service=0x1181b140, callback=0x436ab0 <client_connected>) at master-service.c:640 No locals. #27 0x00000000004363c3 in main (argc=2, argv=0x7fffffffeba8) at main.c:442 set_roots = {0x441248, 0x0} login_set = {auth_socket_path = 0x11806040 "x`\200\021", postlogin_socket_path = 0x11806078 "", postlogin_timeout_secs = 60, callback = 0x436760 <login_client_connected>, failure_callback = 0x436a20 <login_client_failed>, request_auth_token = 1} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = -1 Current language: auto; currently minimal dovecot -n # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (6ddf62b87f60+) # OS: FreeBSD 10.2-RELEASE-p10 amd64 doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot.conf, but this config is /usr/local/etc/dovecot/dovecot.conf auth_cache_size = 10 M auth_cache_ttl = 5 mins auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_worker_max_count = 10 base_dir = /var/run/dovecot/ default_client_limit = 2000 default_process_limit = 200 disable_plaintext_auth = no first_valid_uid = 25 imap_idle_notify_interval = 4 mins log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Ready to serve. mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota mail_temp_dir = /var/tmp mailbox_list_index = yes maildir_very_dirty_syncs = yes managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body environment mailbox date index ihave duplicate mime foreverypart mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded (Mailbox is full) quota_rule = *:storage=1G quota_rule2 = Trash:ignore sieve = ~/.dovecot.sieve sieve_default = /etc/dovecot/sieve/global/JunkFolder.sieve sieve_dir = ~/.sieve sieve_extensions = -enotify sieve_global_dir = /etc/dovecot/sieve/global/ zlib_save = xz zlib_save_level = 6 } pop3_fast_size_lookups = yes pop3_save_uidl = yes protocols = imap pop3 lmtp sieve rejection_reason = Your message to <%t> was rejected:%n%n %r%n rejection_subject = [BOUNCE] %s service imap-login { inet_listener imap { port = 143 } process_min_avail = 4 service_count = 100 } service imap { executable = imap last-login } service last-login { user = mailnull } service lmtp { process_min_avail = 4 unix_listener lmtp { mode = 0666 } user = mailnull } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service managesieve { process_limit = 100 } service pop3-login { inet_listener pop3 { port = 110 } process_min_avail = 4 service_count = 100 } service pop3 { executable = pop3 last-login } ssl = no ssl_cipher_list = ALL:!SSLv2:!LOW:!ADH:!NULL:!DES:@STRENGTH ssl_protocols = !SSLv2 !SSLv3 submission_host = localhost:25 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = zlib quota sieve } protocol lda { mail_plugins = zlib quota } protocol imap { mail_max_userip_connections = 8 mail_plugins = zlib quota imap_quota } protocol pop3 { mail_max_userip_connections = 2 mail_plugins = zlib quota } protocol sieve { mail_max_userip_connections = 3 managesieve_implementation_string = Dovecot managesieve_max_line_length = 65536 }

2 1

how do I get the version of the pigeonhole-sieve plugin
by Heiko Schlittermann 22 Jan '16

22 Jan '16

Hello, as may parts of the dovecot configuration docs refer to sieve and it's specific versions, like NOTE: Pigeonhole versions before v0.3.1 do not support the lo … how do I get the Pigeonhole version my local dovecot uses? The package version number of the ubuntu package dovecot-sieve isn't telling me anything here, because it's bound to the dovecot version number. What do I miss here? Thank you. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

dovecot director redirect some user to always same backend
by Tobi 22 Jan '16

22 Jan '16

Hello list I have a question on how to enforce certain user(s) always to the same backend in a dovecot setup with director. So I changed my passdb-mysql query SELECT password AS password, username AS destuser, 'Y' as proxy, (CASE username WHEN LIKE 'user' THEN '10.66.99.6' ELSE null END) as host from mailbox WHERE username = '%u' AND active = 1; But then I saw in the dovecot manual that the director does nothing if the passdb query already returns a host field. So I'm quite unsure whether a host field with value NULL means that the host field is not present and therefore the director should insert it into the result or not. Thanks tobi

2 1

Hypothetical feature suggestion
by Stephen Feyrer 21 Jan '16

21 Jan '16

Hi, Assuming one sends an E-mail which in turn requires either an update or correction. The current practise is to send a subsequent E-mail with the new or corrected info. I would like to suggest a small feature. I recognise that this would require that the sending application would need to support this same feature. The sender should be able to edit a sent email, transmit a diff of the original and then the receiving mail store composite the changes into a new email. This could be with or without features to allow the review historic versions of said E-mail. Alternatively, regular expressions could be employed to achieve this effect (albeit, a more complex approach). This would provide a kind of Web 2 look on E-mail. -- Kind regards Stephen Feyrer

2 1

Help with sieve
by Joy 21 Jan '16

21 Jan '16

Dear Experts, I am having following script which is working perfectly on 3 server but not working as expected on new server. I have updated latest sieve software compiled from source, In case i use fileinto to move mail to other folder it works perfectly .. require ["fileinto","imap4flags","envelope","body"]; #1 if allof (header :contains ["Subject"] ["test"] ){ setflag "\\Seen"; addflag "\\Flagged"; addflag "BUG"; }

2 1

Multiple Domains
by Doug Hardie 20 Jan '16

20 Jan '16

I have Dovecot 2.2.19 running. However, one client has a rather unusual need. There are multiple domains that currently access their mail on the server. However, this on domain/client wants to use a different port for their users to access mail. Anyone on the standard port trying to download mail would receive an invalid user error (or whatever the proper error for that is). Likewise, only this clients users could access their mail on the new port. Is this possible? — Doug

2 2

Configure the sendmail with the dovecot.
by Lucky . 20 Jan '16

20 Jan '16

Hi Dovecot team/All, First of all, I always appreciated your contribution & effort. Can you please provide the step for configure sendmail with dovecot. We could not understand the parameter which mention in sendmail.cf file. Please provide the parameter description as well as where need to change exactly in sendmail.cf file. Thanks and Regards, Lucky ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================

3 4

dsync: loss of keywords in 2.2.13
by Benoit Branciard 20 Jan '16

20 Jan '16

After some tests, we found that "dsync backup" sometimes fails to copy all the IMAP "keywords" (labels) from the source mailbox to the backup one. Our Dovecot version is 2.2.13 (Debian Jessie package 1:2.2.13-12~deb8u1). We are migrating mailboxes from MBOX (with separate indexes) to MDBOX (with custom DIRNAME) format. The source mail_location is: mail_location = mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot/indexes/%16Hu/%u and the target: mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@@_ and we use the following dsync command to replicate (twice, a first "hot" run, and a second "cold" run with lda and user kicked off). dsync -o mail_access_groups=$mgroup -u "$login" backup "mdbox:$mdbhome/mdbox:DIRNAME=_@@_dbox-Mails_@@_" where $login is username, $mgroup is an UNIX group which has write access to the (temporary chowned/chmoded) mailbox, and $mdbhome is the new (MDBOX) user's home. It appears that some keywords get replicated, but some other do not. The only workaroud we found is to backup all keywords with "doveadm fetch 'mailbox uid flags' keywords '*'", an restore them on the new mailbox with "doveadm flags add". This solution yields no keyword loss. has this problem already been addressed ? -- Benoit BRANCIARD Service InfraStructures (SIS) Direction du Système d'Information et des Usages Numériques (DSIUN) Université Paris 1 Panthéon-Sorbonne Centre Pierre Mendès France 90 rue de Tolbiac - 75634 Paris cedex 13 - France Bur. B406 - Tél +33 1 44 07 89 68 - Fax +33 1 44 07 89 66 Accueil: +33 1 44 07 89 65 - Assistance-DSIUN(a)univ-paris1.fr http://dsi.univ-paris1.fr

1 0

sieve and authentication
by Brendan Kearney 20 Jan '16

20 Jan '16

when i telnet to the sieve instance running with dovecot, i see that SASL is supported, but i cannot get thunderbird to connect to the sieve instance. it seems that i am not providing the right auth methods for sieve to work. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate" "NOTIFY" "mailto" "SASL" "" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready." i am setup with gssapi and pain auth mechanisms and want to leverage Kerberos / SASL for authentication. what do i need to enable (and where) to get sieve working in a MUA? i tried adding the digest-md5 mechanism to the auth_mechanisms directive, but that does not work with Kerberos (or maybe my implementation of Kerberos in my environment). any ideas where i should be looking? thanks brendan

3 2

remote | local blocks in protocol settings
by Nikolaos Milas 20 Jan '16

20 Jan '16

Hello, Where can I find detailed documentation on how "remote" & "local" blocks are used in protocol configuration to provide specific settings for particular IPs/Names? I've been searching around (wiki2, Google) but I found very few things. I also checked in the conf.d directory of the installation and couldn't find anything. One useful thread was here: http://www.dovecot.org/list/dovecot/2010-June/050069.html where we can read about the "filter" hierarchy: protocol name { remote <ip|name> { local <ip|name> { but I would really appreciate reading more complete documentation (and, hopefully, examples). Thanks, Nick

3 8

Re: remote | local blocks in protocol settings
by Joseph Tam 19 Jan '16

19 Jan '16

Nikolaos Milas <nmilas(a)noa.gr> wrote: >> ... >> Pragmatically, I set it high enough so that it meets the need of most >> clients, then deal with problems on a case by case basis >> ... > > Thank you very much Joseph for your quite useful advice and experience. > Are you monitoring using "doveadm who"? No, I occasionally look at log entries for "Maximum number of connections from user+IP exceeded" errors. I may look at the output of "doveadm who" if I want to see a breakdown of how many clients a user is using, or just getting an overall view of how my users are spread out. >>> 4. How can we set a different value to this directive for webmail >>> connections (coming from 127.0.0.1, ::1)? >> >> I don't know if there is another method, but at the very least, you >> can start another dovecot instance with another config file that does >> specific things for 127.0.0.1. > > I tried using a remote block for webmail, but without success yet. If you can get that working, that would be the better method. Running 2 different instances with 2 different config files might come in handy for cases where you have very different policies between localhost/remote networks. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: Increasing mail_max_userip_connections and sys resources
by Joseph Tam 19 Jan '16

19 Jan '16

> In our low-traffic server we have always kept the default value for IMAP > mail_max_userip_connections (10). > > The server has been working fine! (Thank you Timo for this!) > > However, recently we have been having: > > Maximum number of connections from user+IP exceeded > > errors both for IMAP and webmail users. > > Thus, we have now changed the value to 100. > > The questions: > > 1.Might this lead to overloading the server? > 2. Could another dovecot setting prevent the above setting from being > applied (e.g. due to connections exhaustion), i.e. should we also change > other setting(s)? > 3. What should we take into account when deciding the value for > mail_max_userip_connections? It depends on how many users you have, the number of simultaneous clients they use, and the #connections each client opens. Potentially, you could exhaust connection limits -- they usually don't max out memory or CPU or disk since most of the connections are idle. (There is a new IDLE hibernate feature that might help to minimize memory use by idle imap worker processes.) I haven't found a value that gets rid of users running into connection limits. If I set it to n, the next day someone will choke on n+1. This is a snapshot connections (count : #connections) which shows the typical decay: 25 1 14 2 14 3 7 4 9 5 1 6 2 7 1 8 1 10 Occasionally, some user's connection demand will spike and exceed the limit because - they started yat another client - they started global operation like searching - they're using a network that support roaming IP (I've tracked some users across the city on their bus ride.) Pragmatically, I set it high enough so that it meets the need of most clients, then deal with problems on a case by case basis (e.g. get them to lower their mail client's idle connection setting, or asking them to reduce the number of active clients by logging out). It also prevents what this setting was designed for: connection starvation by busy/buggy clients. Usually, hitting the limit doesn't produce problems as mail clients are smart enough to close idle connections or reuse them. If you only got a dozen users, setting it to 100 is feasible. If you got 1000 users, probably not. > 4. How can we set a different value to this directive for webmail > connections (coming from 127.0.0.1, ::1)? I don't know if there is another method, but at the very least, you can start another dovecot instance with another config file that does specific things for 127.0.0.1. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0)
by Timo Sirainen 19 Jan '16

19 Jan '16

> On 04 Jan 2016, at 09:58, Florian Pritz <bluewind(a)xinu.at> wrote: > > On 04.01.2016 15:49, Timo Sirainen wrote: >> What about: >> >>>> #5 0x000000000041dde6 in client_check_command_hangs (client=0x2363450) at imap-client.c:841 >>>> cmd = 0x0 >>>> unfinished_count = 0 >>>> have_wait_unfinished = true >>>> __FUNCTION__ = "client_check_command_hangs" >> >> Either the new code that's detecting hanging-bugs is somehow broken or it's actually preventing a hang by crashing instead, in which case the bug is elsewhere.. > > Output below. > > Sending a private mail because I don't know what that session ID in the > output can be used for. The session ID is harmless. Anyway, I'm having trouble figuring out how the crash could happen or how to reproduce it. According to the backtrace it seems like the client is running IDLE and then it sends "DONE\r\nNOOP\r\n" in same IP packet. But when doing that, I don't see a crash. Although during testing I did find several other bugs. Could you try patching and seeing if you still get the same crash after them? Or have you seen the crash after the initial few times? https://github.com/dovecot/core/commit/1ddf959a750f3860feff4ab3f0e908f32740… https://github.com/dovecot/core/commit/c8e9fa2ffa2566e75f0500808b1bc9bf5d9d… https://github.com/dovecot/core/commit/15307c2c91854e766bd9fb095d611a29b3f7… https://github.com/dovecot/core/commit/c7801f830c7d2e7d340065cdd5a5c795b172…

3 3

Temporary Lookup Failure
by Brad 18 Jan '16

18 Jan '16

Hi All, Have a CentOS 7, dovecot and postfix setup. Can get mail via 995 SSL/TLS Can send mail to virtual users and auto creation works using /etc/dovecot/passwd file via mail command. Using the dovecot lmtp and can login via 465 but the user lookup fails via postfix. in postfix main.cf have virtual_transport = lmtp:unix:private/dovecot-lmtp in dovecot.log I am seeing no errors in dovecot-info.log no errors either in maillog I am seeing: postfix/smtps/smtpd warning hash:/etc/postfix/virtual is unavailable open database /etc/postfix/virtual.db No such file. Note: I did go through creating the virtual.db and associated files but figured that it cant be correct as I want lmtp to handle it and it didn't work anyways, so I removed it. NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 <user@domain> Temporary lookup failure from=<user@domain> to=<user@domain> proto=ESMTP helo=<localhost.localdomain> -- obfuscated Tried every article I could find on the Internet to resolve this with out much luck. Any pointers would be greatly appreciated or if you need specific config details just let me know. Thanks, Brad

4 6

Dovecot doesn't listen on port 143, 993 in SSL
by 남설 18 Jan '16

18 Jan '16

Dear Dovecot Team First of all, I always appreciated your contribution & effort. Dovecot is very good tool for me for a while since my 2 years Linux start. But, 3 days ago, I upgraded my ubuntu 15.04 to 15.10 Then, I realized that my dovecot mail sever didn't work. So I simply terminated all the packages and reinstall it. It means I can't remeber what my previous setting was in my memory. So, dovecot in run is ver 2.2.18 now. Dovecot -n shows below and there is no "SSL" option. then all the port 143, 993 opens(It's not accesible somehow from clients but it's next matter) ----------------------No SSL version------------------------ auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = 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 = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } userdb { driver = passwd } ----------------------------------------------------------- But, If I turn on SSL option with encrypt key and certicate, all port 143, 993 just disappeared. I treaded this issue in ubuntu ASK but still no proper answer so far http://askubuntu.com/questions/722072/dovecot-doesnt-listen-on-993imaps --------------------------SSL option version---------------- auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = 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 = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } *ssl_cert = </etc/dovecot/dovecot.csr>** **ssl_key = </etc/dovecot/private/dovecot.key>* userdb { driver = passwd } -------------------------------------------------------------- Looing forward your reply Thanks in advance

3 2

mmap failed
by ＠lbutlr 18 Jan '16

18 Jan '16

Error: mmap() failed with file /home/user/Maildir/.Archive/dovecot.index.cache: Cannot allocate memory I have default_vsz_limit = 512 M in my conf file. (This error only occurs with a single user’s .Archive index, but that user has over 400,000 files int eh Archive mailbox) -- Let him who desires peace, prepare for war.

2 1

doveconf syntax question
by A. Schulze 18 Jan '16

18 Jan '16

Hello, I have one sieve extension enabled: /etc/dovecot/conf.d/20-sieve.conf: plugin { sieve_extensions = +vacation-seconds } now (months later) we want to enable an other extension. no big deal: /etc/dovecot/local.conf: plugin { sieve_extensions = +editheaders ... } This was wrong. We ASSUMED the plus would add the extension to the list. But at the end only +editheaders was activ. What's the right way to /add/ sieve_extensions from different config files? our guess "sieve_extensions = $sieve_extensions +editheaders" do not work: doveconf -a | grep sieve_extensions doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 22: Unknown variable: $sieve_extensions doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 22: Unknown variable: $sieve_extensions Andreas

2 2

Running without anvil?
by Dave Abrahams 18 Jan '16

18 Jan '16

Hi, I'm using dovecot as a local mail store on my laptop using preauth tunneling. It turns out I almost don't even need to start dovecot at all; the only reason it needs to be running is so that FTS indexing can be invoked. And because I don't want it to run any services, I can run it as an unprivileged user, so long as I turn them all off: # We don't want to serve any protocols, so we don't bind to any ports. # We can run everything as me. protocols = default_login_user = dave default_internal_user = dave The only thing is, I keep getting these in var/log/mail.log: anvil: Fatal: chroot(/Users/dave/brew/var/run/dovecot/empty) failed: Operation not permitted master: Error: service(anvil): command startup failed, throttling for 60 secs auth: Error: read(anvil-auth-penalty) failed: EOF Any suggestions? TIA, Dave

3 5

sieve - configuration problem
by Hajo Locke 18 Jan '16

18 Jan '16

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader sieve_pipe_bin_dir = /usr/local/bin/ sieve_filter_bin_dir = /usr/local/bin/ sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } i also activated managesieve which is working as well. Now iam looking for a way to run individual scripts for users. My idea is to have a system generated script which may run before or after the personal script. Additional the system scripts should not be viewed or changed by mailusers. So i tried with directives sieve_before and sieve_after: #CONF2 plugin { sieve = ~/sieve/.dovecot.sieve sieve_before = ~/sieve_before/.dovecot.sieve sieve_after = ~/sieve_after/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader sieve_pipe_bin_dir = /usr/local/bin/ sieve_filter_bin_dir = /usr/local/bin/ sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } every single script "~/sieve/.dovecot.sieve", "~/sieve_before/.dovecot.sieve" and "~/sieve_after/.dovecot.sieve" contains a small rule to add a new mailheader (X-Before, X-After, X-Middle) so i can watch what happens. The problem is: Every single script is working, but only when this directive is the only one which is activated in conf. As soon as i enable another directive absolut nothing is happen. It does not matter which combination of directives (sieve|sieve_before_sieve_after) is enabled or disabled. Just as a second one is enabled sieve seems to do nothing. Mail is delivered by lda but no songle one headerentry is added. What happens here and how to solve this? Currently i use dovecot 2.2.21 and sieve 0.4.11 Thanks, Hajo

2 2

Dockerfile for building latest github version
by KT Walrus 16 Jan '16

16 Jan '16

Is there a Dockerfile for building/installing the latest Dovecot version in a Docker Image? I don't see Dovecot in the Official Repositories on the Docker Hub like almost all the other popular open source software packages that I use. Why no Official Docker repo for Dovecot? All the user contributed repos containing Dovecot in the Docker Hub seem to just install from a distribution’s repo (like Ubuntu 14.04) but these packages seem to lag the most recent version of Dovecot that I see in GitHub. Kevin

1 0

Corrupted index cache file - migration with zlib
by Leon Kyneur 15 Jan '16

15 Jan '16

Hi I'm migrating some mailboxes from an old dovecot system where mailboxes are stored maildir uncompressed. I enabled zlib on the new system and migrated an account: doveadm -o mail_fsync=never backup -R -u tonyg imapc: when the account connects to the new system after a while i'm seeing the following error and the mailbox is no longer functioning: Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: read(/srv/vmail/532868/tonyg/mdbox/storage/m.1): FETCH BODY[] for mailbox INBOX UID 61 got too little data: 4106341 vs 6054268 Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: unlink(/srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: Corrupted index cache file /srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 61 Jan 15 13:58:06 S611 dovecot: imap(tonyg): FETCH failed in=181 out=4109653 Jan 15 13:58:06 S611 dovecot: auth-worker(6130): ldap(tonyg,144.132.1.90): unknown user Jan 15 13:58:06 S611 dovecot: imap-login: Login: user=<tonyg>, method=PLAIN, rip=144.132.1.90, lip=203.134.11.127, mpid=6746, secured, session=<7qqWklYpnGjLhgHK> Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: read(/srv/vmail/532868/tonyg/mdbox/storage/m.1): FETCH BODY[] for mailbox INBOX UID 61 got too little data: 4106341 vs 6054268 Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: unlink(/srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: Corrupted index cache file /srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 61 Jan 15 13:58:07 S611 dovecot: imap(tonyg): FETCH failed in=181 out=4109653 If i migrate the account without zlib everthing works fine and the error can't be reproduced. I have tried force-resync and index commands to no avail. Any ideas what's going on here? doveconf -n: [root@S611 532868]# doveconf -n # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (6ddf62b87f60+) # OS: Linux 3.10.0-327.4.4.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_debug = yes auth_verbose = yes imapc_features = rfc822.size fetch-headers imapc_host = removed imapc_master_user = removed imapc_password = # hidden, use -P to show it imapc_user = %u lmtp_proxy = yes login_trusted_networks = 192.168.10.0/24 mail_debug = yes mail_gid = vmail mail_location = mdbox:%h/mdbox:ALT=/altstorage%h/mdbox mail_plugins = quota zlib mail_prefetch_count = 50 mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart mdbox_rotate_size = 10 M namespace inbox { inbox = yes location = mailbox "Deleted Messages" { special_use = \Trash } 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 } 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 = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap-m2core.conf.ext driver = ldap } plugin { quota = dict:User quota::file:%h/dovecot-quota sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } pop3c_host = <removed> pop3c_password = # hidden, use -P to show it service lmtp { inet_listener lmtp { address = <removed> port = 24 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem verbose_proctitle = yes protocol imap { mail_plugins = quota imap_quota imap_zlib }

2 2

Courier generates new UIDVALIDITY
by Peer Heinlein 15 Jan '16

15 Jan '16

We just detected, that under some circumstances Courier-IMAP will generate a new UIDVALIDITY for every access to an IMAP-folder, if the folder had been created by a simple "mkdir" and not with maildirmake. Courier doesn't save his uidvalidity-file in this case. Courier DOES generate a sticky UIDVALIDITY after the first "real" access by a User through the IMAP-SELECT-command. That's why this problem isn't a "real" problem in the world. Courier does NOT create this IMAP-UIDVALIDITY if the user just uses POP3-access, because there the UIDVALIDITY isn't used. We have a migration scenario where we have many users with POP3-only access (so that they DO have many mails in der INBOX) and an incremental migration trough doveadm/dsync/imapc fails (caused by consequently changing UIDVALIDITYs). doveadm just uses the IMAP EXAMINE command to open the source IMAP-folder on the Courier's side readonly. Courier DOES handle this access "readonly" and doesn't consequently doesn't generate a UIDVALIDITY-file. Instead Courier uses random UIDVALIDITYS by every access and doveadm always has to copy all mails (and duplicates them if "-1 -R" is used!). To fix this problem and to make a migration and/or doveadm backup/sync much more reliable Dovecot should open the source folder with a SELECT command instead. (Maybe one SELECT and then change to EXAMINE, if you think EXAMINE would be more safe.) Maybe this is also relevant for a real permanent imapc-situation, where Dovecot/imapc is used to fix broken IMAP-implementations from an older backend. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

doveadm/dsync/imapc loose folder subscriptions
by Peer Heinlein 15 Jan '16

15 Jan '16

As I already wrote some days ago we're actually running a huge migration using doveadm/dsync-backup/imapc: doveadm -o imapc_user="$UNAME1" -o imapc_password="$PWORD1" -o imapc_host=$SERVER1 -o pop3c_user="$UNAME1" -o pop3c_password="$PWORD1" -o pop3c_host=$SERVER1 -D -v backup -R -u "$UNAME2" imapc: We just noticed that doveadm looses changes in folder subscriptions if a folder is copied again. a) Copy a mdbox-home of a user (using doveadm backup...) b) Change his subscriptions on the source-side OR change his subscripts on the destination-side OR delete his subscriptions-file. c) Copy that mdbox-home from that user again (using doveadm backup...) doveadm will copy & merge his mails, but he does NOT check for changes in folder subscriptions. As you can see in the attached logs, doveadm nitices changes in subscriptions: dsync(p100490p11): Debug: brain S: Local mailbox tree: INBOX.Trash guid=b36f688eae08506001091708006abe5a uid_validity=1368084367 uid_next=1206 subs=yes last_change=0 last_subs=0 dsync(p100490p11): Debug: brain M: Local mailbox tree: INBOX.Trash guid=b36f688eae08506001091708006abe5a uid_validity=1368084367 uid_next=1206 subs=no last_change=1448903088 last_subs=1448177531 but doesn't fix the subscriptions list: dsync(p100490p11): Debug: brain M: Mailbox INBOX.Trash: local=b36f688eae08506001091708006abe5a/1448903088/1, remote=b36f688eae08506001091708006abe5a/0/1: Mailboxes are equal Even a deletion of the subscriptions file doesn't work. doveadm does not create a new subscription file. This bug is heavy, because incremental backups made by doveadm backup aren't complete and reliable any more. Our biggest problem ist, that we changed the folder prefix and doveadm does change the folder names, but not the subscriptions. So we have several hundred thousand users with broken subscriptions (yes, sed can fix this, I know, but also we'd kill changes made by users during migration period). Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 2

Increasing mail_max_userip_connections and sys resources
by Nikolaos Milas 15 Jan '16

15 Jan '16

In our low-traffic server we have always kept the default value for IMAP mail_max_userip_connections (10). The server has been working fine! (Thank you Timo for this!) However, recently we have been having: Maximum number of connections from user+IP exceeded errors both for IMAP and webmail users. Thus, we have now changed the value to 100. The questions: 1.Might this lead to overloading the server? 2. Could another dovecot setting prevent the above setting from being applied (e.g. due to connections exhaustion), i.e. should we also change other setting(s)? 3. What should we take into account when deciding the value for mail_max_userip_connections? 4. How can we set a different value to this directive for webmail connections (coming from 127.0.0.1, ::1)? The config follows for your reference (I've only changed the real domain name). Thanks in advance for your help. Nick ----------------------------------------------------------------------------- # doveconf -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 # OS: Linux 2.6.18-407.el5 x86_64 CentOS release 5.11 (Final) auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no dsync_remote_cmd = ssh -l root vmail1.example.com doveadm dsync-server -u%u mail_gid = 500 mail_location = maildir:~/Maildir/ mail_plugins = quota mail_log notify replication mail_uid = 500 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = remote:vmail@vmail1.example.com quota = maildir:User quota quota_rule = *:storage=5G quota_rule2 = Trash:storage=+3%% quota_warning = storage=75%% quota-warning 75 %u quota_warning2 = storage=90%% quota-warning 90 %u } protocols = imap pop3 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } user = root } service imap-login { service_count = 1 vsz_limit = 64 M } service imap { executable = imap postlogin } service pop3-login { service_count = 1 vsz_limit = 64 M } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login -d rawlog } service quota-warning { executable = script /opt/mail1.sh unix_listener quota-warning { user = vmail } user = vmail } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_ca = </etc/pki/tls/certs/chain-1552.pem ssl_cert = </etc/pki/tls/certs/cert-1552.pem ssl_key = </etc/pki/tls/private/key-1552.pem ssl_protocols = !SSLv2 !SSLv3 syslog_facility = local1 userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 100 mail_plugins = quota imap_quota notify replication } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = quota notify replication pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master info_log_path = log_path = mail_plugins = quota notify replication postmaster_address = sysadmin(a)example.com sendmail_path = /usr/lib/sendmail } ------------------------------------------------------------------------------------

2 3

doveadm/dsync/imapc and foldernames including a "%"
by Peer Heinlein 14 Jan '16

14 Jan '16

We're using doveadm/dsync/imapc to migrate accounts from Courier to Dovecot 2.2.20. On the source-server some user have folder names including a "%" in their name. Looks like doveadm isn't able to handle that folder names. I always stops with: dsync(testtest): Error: Failed to access mailbox INBOX.Test%TEST: Mailbox does not exist, or must be subscribed to. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 2

Problem! Dovecot 2.2.9 does not send the information on ending the quota to user
by Serge Spinoza 13 Jan '16

13 Jan '16

Hi. I have Dovecot + Postfix + MySQL. Version of Postix: postfix_2.11.3-1ubuntu1_amd64 Version of Dovecot: 2.2.9 Operations system is: Ubuntu 15.04 x64 Postfix have patched (patch VDA - http://vda.sourceforge.net) for using with quota, it means that file "maildirsize" in mail directory already exists and changed when add/delete mail. Quota for virtual box take in MySQL db. ########################## Problem: Dovecot does not send the information on ending the quota to user. ########################## # dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab112.15 x86_64 Ubuntu 15.04 ext4 auth_debug = yes auth_default_realm = mydomain.ru auth_mechanisms = plain login auth_realms = znak-corp.ru debug_log_path = /var/log/dovecot-debug.log info_log_path = /var/log/dovecot.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot.log login_greeting = Welcome to OOO "Corporation ZNAK" mail_gid = 1000 mail_location = maildir:/var/vmail/%n@%d mail_plugins = " quota" mail_uid = 1000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { autocreate = INBOX autosubscribe = INBOX quota = maildir:User quota quota_rule = *:storage=10M #(this derective takes from mysql, but i wrote it just in case) quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=80%% quota-warning 80 %u } protocols = pop3 imap quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/dovecot-smtp-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = /usr/lib/dovecot/quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = </etc/ssl/mydomain.ru.crt ssl_key = </etc/ssl/mydomain.ru.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_plugins = " quota imap_quota autocreate" } protocol pop3 { mail_plugins = quota } protocol lda { mail_plugins = " quota autocreate" } ##### quota-warning.sh ##### #!/bin/sh PERCENT=$1 USER=$2 cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir:User quota:noenforcing" From: aaa(a)mydomain.ru Subject: Quota warning $PERCENT% Your mailbox is now $PERCENT% full. Please remove unnecessary emails to avoid new mail loosing. EOF ##### Script has chmod 777 ##### root@mx:~# ls -la /usr/local/bin/quota-warning.sh -rwxrwxrwx 1 vmail vmail 285 Dec 17 11:09 /usr/local/bin/quota-warning.sh Check the script this command is successful: # /usr/local/bin/quota-warning.sh 82 rrr(a)mydomain.ru (a letter is sent to rrr(a)mydomain.ru that box is filled to 82%) ##### dovecot-sql.conf.ext ##### driver = mysql connect = host=localhost dbname=postfix user=postfix password=xxxxxxx default_pass_scheme = MD5-CRYPT user_query = SELECT '/var/vmail/%n@%d' as home, 'maildir:/var/vmail/%n@%d'as mail, 1000 AS uid, 1000 AS gid, concat('*:bytes=', quota) AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' password_query = SELECT username as user, password, '/var/vmail/%n@%d' as userdb_home, 'maildir:/var/vmail/%n@%d' as userdb_mail, 1000 as userdb_uid, 1000 as userdb_gid, concat('*:bytes=', quota) AS userdb_quota_rule FROM mailbox WHERE username = '%u' AND active = '1' ##### Check that the socket has a quota-warning: # lsof |grep quota-warning dovecot 17277 root 57u unix 0xffff8802d7845b80 0t0 62354154 /var/run/dovecot/quota-warning ##### Verify that the plugin quota is running I doing like this: # doveadm -D -v quota get -u rrr(a)mydomain.ru Conclusion: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(rrr(a)mydomain.ru): Debug: Added userdb setting: mail=maildir:/var/vmail/rrr@mydomain.ru doveadm(rrr(a)mydomain.ru): Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 doveadm(rrr(a)mydomain.ru): Debug: Effective uid=1000, gid=1000, home=/var/vmail/rrr(a)mydomain.ru doveadm(rrr(a)mydomain.ru): Debug: Quota root: name=User quota backend=maildir args= doveadm(rrr(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=* bytes=10240000 messages=0 doveadm(rrr(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(rrr(a)mydomain.ru): Debug: Quota rule: root=User quota mailbox=SPAM ignored doveadm(rrr(a)mydomain.ru): Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 rrr(a)mydomain.ru doveadm(rrr(a)mydomain.ru): Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 rrr(a)mydomain.ru doveadm(rrr(a)mydomain.ru): Debug: Quota grace: root=User quota bytes=1024000 (10%) doveadm(rrr(a)mydomain.ru): Debug: maildir++: root=/var/vmail/rrr(a)mydomain.ru, index=, indexpvt=, control=, inbox=/var/vmail/rrr(a)mydomain.ru, alt= Quota name Type Value Limit % User quota STORAGE 9008 10000 90 User quota MESSAGE 6 - 0 ##### Those plugin is successfully loaded and checked. When removing/receiving emails percent of employment, respectively changes. I read in dovecot manual, that the notification send only when the quota border crossing - then I tested like this: Clears the box up to 60% and then send letters, which occupy about 5% more of allocated quota. And so the lead up to 95%. But reports of ending the quota not be sent. In what may be another problem? Thanks. ------------------ Serge

2 2

sieve - compile error
by Hajo Locke 13 Jan '16

13 Jan '16

Hello, try to upgrade my dovecot 2.2.18 installation from sieve 0.4.6 to newest sieve 0.4.11 I got this error at packaging: make[4]: Verzeichnis »/home/test/dovecot-2.2.18/pigeonhole/src/sieve-tools« wird betreten gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib-sieve -I../../src/lib-sieve-tool -I./debug -I/home/test/dovecot-2.2.18 -I/home/test/dovecot-2.2.18/src/lib -I/home/test/dovecot-2.2.18/src/lib-dict -I/home/test/dovecot-2.2.18/src/lib-dns -I/home/test/dovecot-2.2.18/src/lib-http -I/home/test/dovecot-2.2.18/src/lib-mail -I/home/test/dovecot-2.2.18/src/lib-imap -I/home/test/dovecot-2.2.18/src/lib-fs -I/home/test/dovecot-2.2.18/src/lib-charset -I/home/test/dovecot-2.2.18/src/lib-auth -I/home/test/dovecot-2.2.18/src/lib-master -I/home/test/dovecot-2.2.18/src/lib-ssl-iostream -I/home/test/dovecot-2.2.18/src/lib-compression -I/home/test/dovecot-2.2.18/src/lib-settings -I/home/test/dovecot-2.2.18/src/lib-test -I/home/test/dovecot-2.2.18/src/lib-sasl -I/home/test/dovecot-2.2.18/src/lib-stats -I/home/test/dovecot-2.2.18/src/lib-index -I/home/test/dovecot-2.2.18/src/lib-storage -I/home/test/dovecot-2.2.18/src/lib-storage/list -I/home/test/dovecot-2.2.18/src/lib-storage/index -I/home/test/dovecot-2.2.18/src/lib-storage/index/raw -I/home/test/dovecot-2.2.18/src/lib-imap-storage -I/home/test/dovecot-2.2.18/src/plugins/quota -D_FORTIFY_SOURCE=2 -std=gnu99 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I../.. -MT sievec.o -MD -MP -MF .deps/sievec.Tpo -c -o sievec.o sievec.c sievec.c: In function ‘main’: sievec.c:48:20: error: ‘EXIT_SUCCESS’ undeclared (first use in this function) int exit_status = EXIT_SUCCESS; ^ sievec.c:48:20: note: each undeclared identifier is reported only once for each function it appears in sievec.c:150:18: error: ‘EXIT_FAILURE’ undeclared (first use in this function) exit_status = EXIT_FAILURE; ^ make[4]: *** [sievec.o] Fehler 1 make[4]: Verzeichnis »/home/test/dovecot-2.2.18/pigeonhole/src/sieve-tools« wird verlassen make[3]: *** [all-recursive] Fehler 1 make[3]: Verzeichnis »/home/test/dovecot-2.2.18/pigeonhole/src« wird verlassen make[2]: *** [all-recursive] Fehler 1 make[2]: Verzeichnis »/home/test/dovecot-2.2.18/pigeonhole« wird verlassen make[1]: *** [all] Fehler 2 make[1]: Verzeichnis »/home/test/dovecot-2.2.18/pigeonhole« wird verlassen make: *** [build-stamp] Fehler 2 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2 Is sieve bundled to dovecotversion? i try it with dovecot 2.2.18. System is Ubuntu14, gcc 4.8.4 Thanks, Hajo

2 1

Re: Released Pigeonhole v0.4.11 for Dovecot v2.2.21
by Juan C. Blanco 12 Jan '16

12 Jan '16

Hello Stephan. > The release is available as follows: > > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… http://pigeonhole.dovecot.org/ seems to be down, right? Regards Juan C. > > Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for > more information. Have fun testing this release and don't hesitate to > notify me when there are any problems. > > Regards, > > -- > Stephan Bosch > stephan at rename-it.nl > > > -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Informáticos | E-mail: jcblanco(a)fi.upm.es | | Universidad Politécnica de Madrid | | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 6913 | +-------------------------------------------------------------------+

2 2

No SSL on some users
by Jonas Björklund 12 Jan '16

12 Jan '16

Hello, Is there a way to allow only certain users on IMAP/POP3 without SSL? Im running MySQL backend. /Jonas

2 1

TLS SNI Client Support
by absolutely_free＠libero.it 12 Jan '16

12 Jan '16

Hi,according to this page: http://wiki2.dovecot.org/SSL/SNIClientSupport (last change 2013) I would like to know if this limitation is still valid. # dovecot --version2.0.9 I am trying to configure Android default email client and I am not able at all to use TLS. With other clients I have no problem, so I think my server configuration is ok. Thank you

1 0

Missing Documentation
by Andre Helwig 12 Jan '16

12 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, could someone apply the folowing line to the wiki page at http://wiki2.dovecot.org/Tools/Doveadm/Sync Because it is write protected. - -R Reverse backup direction, so mails in location2 are backed up to default mail location. - -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-0 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWlN6oAAoJEAoTNwRDnEhRfyAH/RZmdQO4jevf8d6Y/CjW/Lkc H7Ny1tB4W+dZnY/Lap+VY4RER/QWfgVgPDrWm0FG1r73FBpPqxafVlMeh2TM9Daf ARSlBQltDl4GvUu3w+ANByUm/eHe3+3+/HavgJApCpJwaxDfgGBpJoEkTsNQSs6d t2NZYY1k/MJV+5Vk7YWatUnHNdK3H6DPz03e+GLQkh+Np0HScy95ispU1c6rirH0 ROb/4X/HPL2Isut3KHcgJ+f5SkHDueNCgM9kq/O72wq8c1GxAIn/Mwk0wQhdVsw/ VoCrsw/IcJ3k6cTeys8rYmpmBMu4LaNfMHoRXTB0X98KmpLHS99WwJ1fXI2Oegw= =flsG -----END PGP SIGNATURE-----

1 0

autoexpunge problems
by Olaf Hopp 12 Jan '16

12 Jan '16

Hello, I tried to use the new autoexpunge for my Trash folders I had in 15-mailboxes.conf mailbox Trash { special_use = \Trash auto = subscribe } (dovecot -n of the original config is below) and added just the line autoexpunge = 1h Just a short period on my test system. But it failed. In the log I see Dec 18 10:54:07 irams2 dovecot: imap(ms2test): Error: Failed to autoexpunge mailbox 'Trash': Invalid mailbox name 'Trash': Missing namespace prefix 'INBOX.' But in 10-mail.conf I have namespace inbox { prefix = INBOX. separator = . inbox = yes } So I changed the line "mailbox Trash" to "mailbox INBOX.Trash". I now have mailbox INBOX.Trash { special_use = \Trash auto = subscribe autoexpunge = 1h } Now it seems to work (Trash is emptied, log file is fine) but in the mail client I see two Trash folders. Once the normal one below INBOX and another one also called Trash which is under a new created folder named INBOX below the original INBOX Thus I have INBOX INBOX.Trash INBOX.INBOX.Trash autoexpunge seems to work, but this is not what I like to offer to my users. Any glues ? Olaf # 2.2.21 (5345f22): /opt/dovecot/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 (d61ff8a5af9e+) doveconf: Warning: service auth { client_limit=2000 } is lower than required under max. load (23192) doveconf: Warning: service anvil { client_limit=2000 } is lower than required under max. load (17195) # OS: Linux 2.6.32-573.12.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) auth_failure_delay = 3 secs auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_worker_max_count = 60 default_client_limit = 2000 default_process_limit = 3000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } mailbox spambox { auto = create special_use = \Junk } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = dovecot driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-master sieve_max_redirects = 20 } protocols = imap pop3 lmtp sieve sieve quota_full_tempfail = yes service imap-login { process_limit = 8192 process_min_avail = 16 service_count = 0 } service imap { process_limit = 8192 } service lmtp { executable = lmtp -L } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3 { process_limit = 8192 } ssl = required ssl_ca = </etc/pki/tls/certs/chain.pem ssl_cert = </etc/pki/tls/certs/imap.pem ssl_key = </etc/pki/tls/private/imap.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 syslog_facility = local3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 100 ssl_cert = </etc/pki/tls/certs/imap.pem ssl_key = </etc/pki/tls/private/imap.key } protocol pop3 { ssl_cert = </etc/pki/tls/certs/pop.pem ssl_key = </etc/pki/tls/private/pop.key } -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu atis.informatik.kit.edu www.kit.edu KIT – Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

2 2

Problems with doveadm backup in a dovecot director environment
by Tobi 12 Jan '16

12 Jan '16

Hi list I have configured my dovecot(s) in a frontend-backend setup using the director feature of dovecot. Works like charm, but I'm currently unable to use doveadm backup to "sync" the mailbox to a dovecot system which is not within director_mail_servers settings Before I added the director feature I could fire a simple doveadm backup -u myuser(a)mydomain.tld tcps:otherserver.mydomain.tld:2424 After activating the director the command above fails as the connection is always tried to be established to one of the servers specified in director_mail_servers. Is it possible to use doveadm backup towards a server which is not in director_mail_servers? I tried with the -o option of doveadm to override several settings like host or director_mail_servers but no success: the command still tries to connect to an ip from director_mail_servers and not to the destination given as parameter to the command. Is there anyway to achieve that? Thanks a lot for any help tobi

1 1

client setting "move to trash" in shared mailboxes
by Steffen Kaiser 12 Jan '16

12 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, does somebody run clients with "move to trash" on delete in conjunction with shared mailboxes successfully? When one tries to delete a mailbox in the shared namespace, Dovecot responds with "Can't rename mailboxes across specified storages" OK, the failure stems from the fact that the client (Thunderbird) tries to rename the mailbox into "Trash.mailbox" with the user's private namespace. Does somebody know of an AddOn to have Thunderbird move mailboxes into the shared user's Trash, for example? Does somebody uses "mark as deleted", but use a virtual folder as Trashbin? What option would I have, if the users expect a "trashbin" of some sort? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVpTAJHz1H7kL/d9rAQI3twgAsmZdUdYzwQ200j2ILE2XhG3Iy7oFSWd4 YrmOdw09Fr8JtrQIcsbu8BZyyBOse9CLNICQFkmfsSBEXSFX1v5IGfH98RcvhgaM pQwdY1SMctkI4nJHWkJFjC+SCQlDZmV6MVZD7pv+7VDjvvvh/jr0b/uQunYvPLle BEbz1hSssY8bFmWhZxddydzsYgQfFIHUR2VsINd/YHPZlUjJQUqkPwbmDZ4XVN+P WHXYaR4uhrn5arpibk0x5PG/9wlnQvMkStN/kZNBS4jfsKLz6RTQhKgeNmKXyoZD mjUK5r57GkU0MdrRNqQqbgOIrU9V0h1oBH7PFjVoaddw0pYECPlbuw== =hwNa -----END PGP SIGNATURE-----

1 0

password schemes when crypt() has no DES
by Stuart Henderson 12 Jan '16

12 Jan '16

https://github.com/dovecot/core/commit/54a1b3574acab5f778843f7f1e04d2d26d61… fixed a 'doveadm pw' crash "when trying to use CRYPT scheme when crypt() doesn't support DES" by testing to see if crypt would generate a DES password and, if not, disabling the scheme. I'm using Dovecot on OpenBSD with bcrypt passwords stored in LDAP as "{CRYPT}$2b$...". OpenLDAP is built with --enable-crypt which takes the same approach as Dovecot of just passing to crypt(), so before the above commit, both programs were able to authenticate. (Changing the scheme value stored in the ldap passdb to BLF-CRYPT would fix Dovecot but break things for other programs including OpenLDAP itself). For now I went with a dirty patch to get things working again, does anyone have an idea for a nicer fix? Thanks. --- src/auth/password-scheme-crypt.c.orig Fri Jan 8 01:04:13 2016 +++ src/auth/password-scheme-crypt.c Fri Jan 8 01:23:35 2016 @@ -111,7 +111,12 @@ static const struct { const char *salt; const char *expected; } sample[] = { +#ifdef __OpenBSD__ + { "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF", + "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" }, +#else { "08/15!test~4711", "JB", "JBOZ0DgmtucwE" }, +#endif { "08/15!test~4711", "$2a$04$0123456789abcdefABCDEF", "$2a$04$0123456789abcdefABCDE.N.drYX5yIAL1LkTaaZotW3yI0hQhZru" }, { "08/15!test~4711", "$5$rounds=1000$0123456789abcdef", @@ -124,8 +129,13 @@ static const struct { /* keep in sync with the sample struct above */ static const struct password_scheme crypt_schemes[] = { +#ifdef __OpenBSD__ { "CRYPT", PW_ENCODING_NONE, 0, crypt_verify, + crypt_generate_blowfisch }, +#else + { "CRYPT", PW_ENCODING_NONE, 0, crypt_verify, crypt_generate_des }, +#endif { "BLF-CRYPT", PW_ENCODING_NONE, 0, crypt_verify, crypt_generate_blowfisch }, { "SHA256-CRYPT", PW_ENCODING_NONE, 0, crypt_verify,

1 0

Dovecot code repository moved to Github
by Timo Sirainen 11 Jan '16

11 Jan '16

http://hg.dovecot.org/ is no longer being updated. The public repository exists now in https://github.com/dovecot/core instead. I'm not sure yet if we should continue pushing commit emails to dovecot-cvs list or if Github's internal notifications are enough. In any case dovecot-cvs list isn't working right now.

5 9

sieve - content checks with special chars
by Hajo Locke 11 Jan '16

11 Jan '16

Hello, currently i try subject tests with special chars and german umlauts öäü etc. if header :contains "subject" ["öööö äää"] { fileinto "umlauts"; } iam surprised, this is working out of the box. great! in procmail i had to add a second step by manual coding the needle with perl. is sieve reliable at this kind of tests or are there some special cases? iam worried about this, because it was to easy. confusing... ;) Thanks, Hajo

3 2

Enterprise Repository Access?
by Ben Johnson 10 Jan '16

10 Jan '16

Hello! I apologize if this has been asked already. (I did search before posting...) Is it still possible to obtain access to Dovecot's Enterprise Repository, for Ubuntu and Debian, at no cost? When last I registered for such access, I recall there being a "mock product" in the Dovecot Store that provided no-cost access to this repository. Any information in this regard is very much appreciated. Thank you in advance! -Ben

4 3

Directory delivery discombobulation
by mdb＠primelogic.com 10 Jan '16

10 Jan '16

Greetings, On a server running FreeBSD 8.2, I'm configuring Postfix 2.8.0 and Dovecot 1.2.16, using Dovecot for SASL and LDA. For reasons I won't go into, I don't want to upgrade anything on the server to current versions. I'm configuring for maildir with virtuals. Here's the directory structure I want to use: /usr/vmail/domain/username/cur,new,tmp And here's where Dovecot is delivering mail: /usr/vmail/domain/user/Maildir/cur,new,tmp Oddly, the first time I connected with Thunderbird (configured for IMAP), the following directories were created in /usr/vmail/domain/user/, i.e., below Maildir: .INBOX.Drafts .INBOX.Sent .Junk .Trash Thunderbird can see sent mail in .INBOX.Sent, but it can't see any mail in Maildir. Obviously, something is amiss in my configuration. Here's the dovecot -n output: # 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-RELEASE i386 ufs protocols: imap pop3 ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n maildir_very_dirty_syncs: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login username_format: %Lu passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=1000 gid=1000 home=/home/vmail/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: postfix group: postfix Note that I haven't defined mail_location as "maildir:~/Maildir," yet Dovecot is delivering to the Maildir directory (a directory I don't want). I'm not sure about the path in args: userdb: driver: static args: uid=1000 gid=1000 home=/home/vmail/%d/%n Here's the LDA config for virtuals in Postfix's master.conf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} I'm also unsure about the home_mailbox value in Postfix's main.cf. The docs say this: " Specify "Maildir/" for qmail-style delivery (the / is required)." And there was no alternative listed, so that's what I used: home_mailbox = Maildir/ However, does it designate a directory named Maildir? Not sure if they're relevant, but here are some additional config lines from Postfix's main.cf virtual_mailbox_domains = /etc/postfix/vhosts virtual_mailbox_base = /home/vmail/ virtual_mailbox_maps = hash:/etc/postfix/vmaps virtual_minimum_uid = 1000 virtual_uid_maps = static:1000 virtual_gid_maps = static:1000 smtpd_sasl_type = dovecot # Can be an absolute path, or relative to $queue_directory smtpd_sasl_path = /var/spool/postfix/private/auth # and the common settings to enable SASL: smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated,reject_unauth_destination Finally, "postconf -a" returns "dovecot," so SASL is copacetic. That's all I can think of that might be relevant. It sure would be nice if Dovecot would forget about the Maildir directory and deliver directly to the username/ directory so Thunderbird could access it, but other than setting the mail_location var to "maildir:/home/vmail/%d/%n," I'm at a loss. Thanks for your help. Doc

1 0

Pigeonhole code repository moved to Github
by Stephan Bosch 09 Jan '16

09 Jan '16

The public repository for Pigeonhole is now located at https://github.com/dovecot/pigeonhole . The repositories at http://hg.rename-it.nl are no longer updated.

1 0

2.2.13 fts-squat corrupt uidlist - wrong indexid
by dilieto＠lineone.net 09 Jan '16

09 Jan '16

I have the same problem described in this old thread: http://dovecot.org/list/dovecot/2012-April/135162.html I have done some debugging, by adding log messages to squat_uidlist_map_header and squat_trie_refresh. I have found that the "wrong indexid" warning is always triggered under the following conditions - uidlist->hdr.indexid != 0 - uidlist->trie->hdr.indexid == 0 - squat_trie_is_file_stale(trie) == 0 In other words it looks like the squat_uidlist_map_header function is called with an uninitialized trie, an initialized header, and a current (not stale) file. Because of the latter, squat_trie_refresh never calls squat_trie_open, the trie stays uninitialized and later triggers the warning. In addition the search results will only include mails added to the mailbox after the warning. By replacing the call to squat_trie_refresh with squat_trie_open in squat_uidlist_map_header, the warning no longer happens. Patch is attached. I am not sure this is the correct way of fixing the problem, but it works reliably.

1 0

Released Pigeonhole v0.4.11 for Dovecot v2.2.21
by Stephan Bosch 08 Jan '16

08 Jan '16

Hello Dovecot users, Here is the final v0.4.11 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the RC. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty or broken text part. - Fixed assert failure in handling of body parts that are converted to text. - Fixed header unfolding for (mime) headers parsed from any mime part. - Fixed trimming for (mime) headers parsed from any mime part. - Fixed erroneous changes to the message part tree structure performed when re-parsing the message. - LDA Sieve plugin: Fixed logging of actions; sometimes the configured log format was not followed. - LDA Sieve plugin: Fixed bug in error handling of script storage initialization. - Sieve Extprograms plugin: Ignored ENOTCONN error in shutdown(fd, SHUT_WR) call. - Fixed duplication of discard actions in the script result. Each discard was counted as a separate action, which means that action limit would be crossed too early. - Made sure that quota errors never get logged as errors in syslog. - Fixed handling of implicit keep for a partially executed transaction that yielded a temporary failure. - Fixed handling of global errors. If master and user error handler were identical, in some cases the log message could be lost. - Fixed AIX compile issue in message body parser. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

doveadm search -A tries to create mailboxes
by Bill Shirley 08 Jan '16

08 Jan '16

[0:root@elmo ~]$ rpm -q dovecot dovecot-2.2.18-2.fc22.x86_64 I got a surprise today when I tried the doveadm search function from: http://wiki2.dovecot.org/Plugins/Expire [0:root@elmo ~]$ doveadm search -A mailbox Trash savedbefore 30d doveadm(clamscan): Error: User initialization failed: Namespace '': mkdir(//Maildir) failed: Permission denied (euid=982(clamscan) egid=289(clamscan) missing +w perm: /, dir owned by 0:0 mode=0555) doveadm(clamscan): Error: User init failed doveadm(nm-openconnect): Error: User initialization failed: Namespace '': mkdir(//Maildir) failed: Permission denied (euid=986(nm-openconnect) egid=293(nm-openconnect) missing +w perm: /, dir owned by 0:0 mode=0555) doveadm(nm-openconnect): Error: User init failed doveadm(openvpn): Error: User initialization failed: Namespace '': mkdir(/etc/openvpn/Maildir) failed: Permission denied (euid=987(openvpn) egid=296(openvpn) missing +w perm: /etc/openvpn, dir owned by 0:0 mode=0755) doveadm(openvpn): Error: User init failed .. plus several more I wouldn't think the search function (or any operation) would try to create mailboxes. These are system user ids that don't have or need mailboxes. Is this correct? Bill

3 5

doveadm import - strange warning
by Ralf Hildebrandt 08 Jan '16

08 Jan '16

I'm using the doveadm import command to extract mails from my backup: % doveadm import -u restore(a)backup.invalid mdbox:/home/copymail/mdbox "" \ mailbox INBOX header Delivered-To backup+$SEARCHPATTERN(a)backup.invalid This works like a charm, I'm getting all the mails, and I can access the newly generated mailbox. But when executing the command I'm getting an annoying warning: doveadm(restore(a)backup.invalid): Error: chdir(/root/) failed: Permission denied (euid=1001(copymail) egid=1001(copymail) missing +x perm: /root, dir owned by 0:0 mode=0700) doveadm(restore(a)backup.invalid): Error: chdir(/root) failed: Permission denied I'm using a file based authentication: # cat passwd restore@backup.invalid:{SHA}+/...the.hash...:1001:1001:(gecos):/home/restore:: So why is "restore(a)backup.invalid" being associated with /root? I'm using 2:2.2.18-1~auto+91, but the warning has been around for ages :) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

5 7

strange interaction with MacOSX calendar server
by Jim Reid 08 Jan '16

08 Jan '16

I’ve installed and configured Apple’s calendar server. It seems to be working just fine. However it keeps trying to speak to my IMAP server — don’t know why — and the authentication attempts fail every 30 seconds or so. Here’s what’s in the calendar server logs: 2016-01-07 22:42:38+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver 2016-01-07 22:43:08+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver 2016-01-07 22:43:39+0000 [-] [caldav-1] [IMAP4DownloadProtocol (TLSMemoryBIOProtocol),client] [txdav.caldav.datastore.scheduling.imip.inbound.IMAP4DownloadProtocol#error] IMAP login failed for com.apple.calendarserver And in dovecot’s logs I see: Jan 7 22:47:43 hutch dovecot[63067]: imap-login: Disconnected (auth failed, 2 attempts in 4 secs): user=<com.apple.calendarserver>, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session=<wkMAQsYoVADDNulG> Jan 7 22:48:10 hutch dovecot[63067]: auth-worker(65378): Error: pam(com.apple.calendarserver,195.54.233.70): pam_acct_mgmt() failed: permission denied Jan 7 22:48:14 --- last message repeated 1 time --- Jan 7 22:48:14 hutch dovecot[63067]: imap-login: Disconnected (auth failed, 2 attempts in 4 secs): user=<com.apple.calendarserver>, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session=<dSvTQ8YoXQDDNulG> Jan 7 22:48:40 hutch dovecot[63067]: auth-worker(65378): Error: pam(com.apple.calendarserver,195.54.233.70): pam_acct_mgmt() failed: permission denied Jan 7 22:48:44 --- last message repeated 1 time — I tweaked dovecot to use AUTH PLAIN as well as CRAM-MD5. [The MD5 stuff has always worked fine for SMTP and IMAP over TLS.] I think /etc/pam.d/dovecot is OK too: % cat /etc/pam.d/dovecot # # as documented on Dovecot wiki auth required pam_opendirectory.so try_first_pass account required pam_nologin.so account required pam_opendirectory.so password required pam_opendirectory.so Here’s my dovecot.conf: # 2.2.5: dovecot.conf # OS: Darwin 12.5.0 x86_64 auth_mechanisms = plain login cram-md5 base_dir = /var/run/dovecot/ listen = *, [::] mail_debug = yes mail_privileged_group = mail mbox_write_locks = fcntl namespace inbox { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / type = private } namespace { inbox = no list = yes location = maildir:/var/imap/%u:LAYOUT=fs prefix = separator = / type = private } passdb { driver = pam args = failure_show_msg=yes } passdb { args = /usr/local/etc/dovecot-md5 driver = passwd-file } protocols = imap service auth { executable = /usr/local/libexec/dovecot/auth unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { client_limit = 32 executable = /usr/local/libexec/dovecot/imap-login inet_listener imap { port = 0 } process_limit = 128 process_min_avail = 3 service_count = 1 vsz_limit = 64 M } service imap { executable = /usr/local/libexec/dovecot/imap process_limit = 32 } service pop3-login { client_limit = 32 process_limit = 128 process_min_avail = 3 service_count = 1 vsz_limit = 64 M } service pop3 { process_limit = 32 } ssl_cert = </usr/local/etc/ssl/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </usr/local/etc/ssl/private/dovecot.pem syslog_facility = local4 userdb { driver = passwd } protocol imap { mail_max_userip_connections = 10 mail_plugin_dir = /usr/local/lib/dovecot/imap } protocol lda { postmaster_address = postmaster(a)example.com } Can someone please explain what’s going on and how to fix/troubleshoot it? Thanks. The endless error messages in the log don’t seem to be causing any problems to either the mail setup or the calendaer server. Famous last words… However they are a bit annoying and probably point to an underlying problem or misconfiguration that really should be fixed. By the way, the password used by the calendar server is for my MacOSX login (which should be getting picked up via PAM, right?) while a different one is used for the SMTP/IMAP MD5 challenge-response. I hope someone can clear up my confusion.

1 0

Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX?
by Peer Heinlein 07 Jan '16

07 Jan '16

We're running a huge imapc-Migration from an old Courier-IMAP to Dovecot. Courier always uses "INBOX."-prefix for his folders, so we set namespace inbox { [...] separator = . prefix = INBOX. [...] } on our new Dovecot 2.2.20 system. And also we added: imapc_list_prefix=INBOX to avoid the dublication of the INBOX prefix. At the end, doveadm/dsync/imapc see "INBOX.Virus", adds his Prefix, has "INBOX.INBOX.Virus", deletes his imapc_list_prefix and the end we have "INBOX.Virus" again which is identical to the source folder from Courier. Works perfect BUT: It looks like there is a "hidden feature" in Dovecot that always maps "INBOX.INBOX" back to "INBOX". For me that looks like a workaround for broken mailclients to fix some of the common problems after changing the namespace prefix. I never heard about that "hidden feature", but even if I don't (!) have INBOX.INBOX: root@imap01:~/MIGRATION # doveadm mailbox list -u test INBOX INBOX.Virus INBOX.Spam INBOX.Trash I'm always able to access INBOX.INBOX which is identical to INBOX: root@imap01:~/MIGRATION # doveadm fetch -u test uid mailbox INBOX.INBOX uid: 1 Looks like there is such a magic-mapping and looks like this "hard coded mapping" (?) breaks the imapc_list_prefix-magic. If the user has on the SOURCE-server (Courier): Source-Server: INBOX (5 messages) INBOX.Inbox (3 messages) and I do migrate that user using doveadm/dsync/imapc, this user has on the DESTINATION-server (Dovecot) Destination-server: INBOX (5 messages) INBOX.Inbox (5 messages from "real INBOX") and his 3 messages from INBOX.Inbox are lost. I can NOT find any errors in the debug/error-output of doveadm/dsync/imapc. From the view of doveadm everything worked perfect as you can see in the attached logfile. Or am I completly wrong?! Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 4

doveadm proxy kick shows always "0 connections kicked"?!
by Peer Heinlein 06 Jan '16

06 Jan '16

On Dovecot 2.2.20: There *IS* a user connected: root@mailproxy02:~ # doveadm proxy list | grep testuser username proto src ip dest ip port testuser imap xx.xx.xx.xx yy.yy.yy.yy 143 But if I kick him there are always "0 connections kicked": root@mailproxy02:~ # doveadm proxy kick testuser 0 connections kicked ...even if the user's gone after I kicked him. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

1 0

allow_nets=local in passdb gets "auth: Panic"
by SATOH Fumiyasu 05 Jan '16

05 Jan '16

Hi, I have the following configuration in my dovecot.conf for Dovecot 2.2.21: passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = allow_nets=local,127.0.0.1,10.255.1.0/24 } This triggers "auth: Panic" on POP3/IMAP logins as the below: Dec 22 14:57:39 localhost dovecot: auth: ldap(u0000,::1,<oiF8SHYngqsAAAAAAAAAAAAAAAAAAAAB>): allow_nets: Invalid network 'local' Dec 22 14:57:39 localhost dovecot: auth: Panic: file net.c: line 1137 (net_is_in_network): assertion failed: (IPADDR_IS_V6(ip) == IPADDR_IS_V6(net_ip)) `doveadm auth test <username> <password>` is no problem as expected. What's wrong? Regards, -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 3

Replication - user permissions
by Petter Gunnerud 05 Jan '16

05 Jan '16

When setting up dsync for replication, what should the user permissions be for sync over ssh? I'm running virtual users only. Postfix and Dovecot services run as mail:mail. All the maildir folders are owned by mail:mail and permissions are 700. User mail is not allowed login. So whats the best practice in respect to security to allow for dsync over ssh? So of the options I consider: 1) change postfix/dovecot settings so that maildirs are created with 770 permissions, then create a user dsync:mail that is allowed for ssh login. 2) permit user mail to login using ssh 3)go with tcp sync rather than ssh Other suggestions? PG

1 0

Replication - hostname issue
by Petter Gunnerud 05 Jan '16

05 Jan '16

I have postfix/dovecot setup on a virtual gentoo server. It's been in service for almost two years without any issues. Now I want to set up a spare server to replicate mails from the one running. I copied the vm files to the second host server, changed the ip, hostname and hosts file for the copy and followed the dovecot replication doc. The last point in the doc tells to rundovecot --hostdomainto make sure the hostnames differ... To my surprise the command returned "localhost" on both servers. How do I set the hostname for dovecot service?(The hostname command returns the servers hostnames.)Will a change in dovecot hostname make all clients redownload all their mail? A second question. When configuring dovecot replication. Should the settings be done on the master server or the stand by server, or both? (Doc doesn't say anything regarding this) PG

2 2

2.2.21 imap core dump after enabling autoexpunge
by Tomi Vainio 04 Jan '16

04 Jan '16

Hi, I've enabled autoexpunge for Trash and Junk. Now imap process core dumps occasionally. Tomppa > program terminated by signal SEGV (no mapping at the fault address) > 0xff0dc2e0: o_stream_get_buffer_used_size : ld [%o0 + 20], %o0 > Current function is notify_ok (optimized) > 13 if (o_stream_get_buffer_used_size(client->output) != 0) > (dbx) where > [1] o_stream_get_buffer_used_size(0x0, 0x83ee8, 0x83ee8, 0x5f520, 0xfffe681c, 0xff13a978), at 0xff0dc2e0 > =>[2] notify_ok(mailbox = 0x90188, text = 0x83ee8 "Stale mailbox lock file detected, will override in 0 seconds", context = 0xa3588) (optimized), at 0x5f524 (line ~13) in "mail-storage-callbacks.c" > [3] dotlock_callback(0x0, 0x1, 0x90188, 0x567a61fe, 0xff1352a0, 0x2), at 0xff1ff478 > [4] dotlock_create(0xcc3d8, 0x2dc6c0, 0x1, 0x0, 0x0, 0x567a61fe), at 0xff0b0e68 > [5] file_dotlock_create_real(0xcc3d8, 0x1, 0x541c, 0x4, 0xff1352a0, 0xff13a6bc), at 0xff0b1104 > [6] file_dotlock_create(0xbf674, 0x8f990, 0x1, 0xbf690, 0x5, 0xcc3d8), at 0xff0b126c > [7] maildir_uidlist_lock_timeout(0xbf648, 0x1, 0x1, 0x1, 0x3f, 0x26c00), at 0xff1ff0ec > [8] maildir_uidlist_sync_lock(0xbf648, 0x8, 0xffbff59f, 0x1, 0x1, 0xf19c8), at 0xff2035bc > [9] maildir_uidlist_sync_init(0xbf648, 0x8, 0x83d20, 0x1, 0x44, 0xff2f502c), at 0xff203680 > [10] maildir_sync_context(0x83d08, 0x1, 0x0, 0xffbff707, 0x83d20, 0x83d08), at 0xff1fe290 > [11] maildir_sync_run(0x90188, 0x44, 0x0, 0x0, 0x0, 0x90420), at 0xff1fe74c > [12] maildir_storage_sync_init(0x90188, 0x44, 0x541c, 0x0, 0x80, 0xff2f502c), at 0xff1feaa0 > [13] mailbox_sync(0x90188, 0x44, 0x0, 0x4, 0x44, 0x90388), at 0xff1b91cc > [14] index_mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0x0, 0xff2f502c, 0x0), at 0xff273858 > [15] maildir_mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0xfffffff8, 0x0, 0xff2f502c), at 0xff1f9e4c > [16] mailbox_get_metadata(0x90188, 0x40, 0xffbff910, 0x0, 0xff2f502c, 0x2), at 0xff1b8ecc > [17] mailbox_autoexpunge(0x90188, 0x5651837e, 0xa1e28, 0xa2630, 0x0, 0x0), at 0xff1a6fcc > [18] mail_user_autoexpunge(0x9eaf4, 0x8, 0x5651837e, 0xff2f502c, 0x9c290, 0xffbff9ac), at 0xff1a72e8 > [19] mail_user_unref(0x9de20, 0xfffd135c, 0xff2f502c, 0x1, 0xff2c6388, 0xa35d4), at 0xff1c328c > [20] client_default_destroy(client = 0xa3588, reason = <value unavailable>) (optimized), at 0x41c8c (line ~390) in "imap-client.c" > [21] io_loop_call_io(0x9ca18, 0xfffdbba8, 0x0, 0xff1352a0, 0x8c6b8, 0x24400), at 0xff0c8fd4 > [22] io_loop_handler_run_internal(0x8c6b8, 0x1, 0x0, 0x8d1b8, 0x1, 0x9ca18), at 0xff0cadd8 > [23] io_loop_run(0x8c6b8, 0x1, 0xc0, 0xff13b26c, 0xff1352a0, 0x8d1b8), at 0xff0c90fc > [24] master_service_run(0x8c608, 0x60fe0, 0x1, 0x80, 0x27c00, 0x2), at 0xff0236c8 > [25] main(argc = <value unavailable>, argv = 0x1) (optimized), at 0x619c4 (line ~442) in "main.c" > (dbx) > # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf > # OS: SunOS 5.10 sun4u > base_dir = /var/run/dovecot/ > dsync_remote_cmd = ssh -l%{login} %{host} /usr/local/bin/doveadm dsync-server -u%u -U > first_valid_uid = 100 > last_valid_uid = 199 > mail_location = maildir:~/Maildir > mail_plugins = fts fts_solr > namespace inbox { > inbox = yes > location = > mailbox "Deleted Messages" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > auto = create > autoexpunge = 31 days > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Spam { > special_use = \Junk > } > mailbox Trash { > autoexpunge = 31 days > special_use = \Trash > } > prefix = > } > passdb { > driver = pam > } > plugin { > fts = solr > fts_autoindex = yes > fts_solr = url=http://127.0.0.1:8983/solr/ break-imap-search > } > protocols = imap > service auth { > user = root > } > service imap-login { > inet_listener imap { > address = localhost > port = 143 > } > inet_listener imaps { > address = * > port = 993 > } > } > ssl_cert = </etc/mail/certs/server-all.crt > ssl_cipher_list = AES128+EECDH:AES128+EDH > ssl_dh_parameters_length = 2048 > ssl_key = </etc/mail/certs/server.key > ssl_prefer_server_ciphers = yes > ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = passwd > }

2 2

Re: segfault in dict_transaction_rollback() on doveadm quota recalc -u
by Lazy 04 Jan '16

04 Jan '16

Bump > Hi, > > We have a dovecot cluster with nfs storage, 2 directors and 3 > imap/pop3/lmtp backends. > > Redis is used as a dict backend with a dict proxy. > > dict { > quota = redis:host=127.0.0.1:prefix=user/ > } > > plugin { > > quota = dict:User quota::proxy::quota > > } > > Redis server is behind haproxy working in tcp mode. > > doveadm quota recalc -u user always couses dict process segfault (called > from imap backend or director host), otherwise quota is working correctly. > > > #0 dict_transaction_rollback (_ctx=_ctx@entry=0xea5fd0) at dict.c:194 > 194 ctx->dict->v.transaction_rollback(ctx); > (gdb) bt > #0 dict_transaction_rollback (_ctx=_ctx@entry=0xea5fd0) at dict.c:194 > #1 0x0000000000404d4d in dict_connection_destroy (conn=conn@entry=0xea5af0) > at dict-connection.c:166 > #2 0x0000000000405098 in dict_connection_input (conn=<optimized out>) at > dict-connection.c:127 > #3 dict_connection_input (conn=0xea5af0) at dict-connection.c:96 > #4 0x00007fbf886fe4fb in io_loop_call_io (io=0xeab550) at ioloop.c:501 > #5 0x00007fbf886ff54b in io_loop_handler_run_internal (ioloop=ioloop@entry=0xe9f730) > at ioloop-epoll.c:220 > #6 0x00007fbf886fe589 in io_loop_handler_run (ioloop=ioloop@entry=0xe9f730) > at ioloop.c:548 > #7 0x00007fbf886fe608 in io_loop_run (ioloop=0xe9f730) at ioloop.c:525 > #8 0x00007fbf8869fbc3 in master_service_run (service=0xe9f5c0, > callback=callback@entry=0x4059c0 <client_connected>) at > master-service.c:581 > #9 0x0000000000404ad8 in main (argc=1, argv=0xe9f390) at main.c:105 > (gdb) p ctx > $1 = (struct dict_transaction_context *) 0x0 > > > dovecot 2.2.18, redis server 2.8 > > > > Regards Michal >

2 2

[BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0)
by Florian Pritz 04 Jan '16

04 Jan '16

Hi, I'm seeing the following in my logs. Twice so far, no idea what caused it. I do however have the core dump if that is of any use. > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa64ea) [0x7f6f99fa64ea] -> /usr/lib/dovecot/libdovecot.so.0(+0xa7a18) [0x7f6f99fa7a18] -> /usr/lib/dovecot/libdovecot.so.0(i_ > fatal+0) [0x7f6f99fa686d] -> dovecot/imap() [0x41dde6] -> dovecot/imap(client_continue_pending_input+0xd6) [0x41df50] -> dovecot/imap() [0x4122a9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0xcd) [0x7f6f99fc3b01] -> /usr/lib/dovec > ot/libdovecot.so.0(io_loop_handler_run_internal+0x209) [0x7f6f99fc606e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x24) [0x7f6f99fc3caa] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0xaf) [0x7f6f99fc3bf6] -> /usr/lib/dovec > ot/libdovecot.so.0(master_service_run+0x2e) [0x7f6f99f317af] -> dovecot/imap(main+0x2da) [0x430da2] -> /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f6f99b7c610] -> dovecot/imap(_start+0x29) [0x40c639] > Jan 4 11:14:11 karif dovecot[20876]: imap(username): Fatal: master: service(imap): child 19463 killed with signal 6 (core dumped) In case it is easier to read, here's a gdb backtrace: > #0 0x00007f6f99b8f5f8 in raise () from /usr/lib/libc.so.6 > #1 0x00007f6f99b90a7a in abort () from /usr/lib/libc.so.6 > #2 0x00007f6f99fa6539 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 > #3 0x00007f6f99fa7a18 in i_internal_fatal_handler (ctx=0x7ffe660d4700, format=0x438a60 "file %s: line %d (%s): assertion failed: (%s)", args=0x7ffe660d4720) at failures.c:670 > #4 0x00007f6f99fa686d in i_panic (format=0x438a60 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 > #5 0x000000000041dde6 in client_check_command_hangs (client=0x2363450) at imap-client.c:841 > #6 0x000000000041df50 in client_continue_pending_input (client=0x2363450) at imap-client.c:884 > #7 0x00000000004122a9 in idle_client_input (ctx=0x23642a8) at cmd-idle.c:111 > #8 0x00007f6f99fc3b01 in io_loop_call_io (io=0x2374600) at ioloop.c:559 > #9 0x00007f6f99fc606e in io_loop_handler_run_internal (ioloop=0x232c740) at ioloop-epoll.c:220 > #10 0x00007f6f99fc3caa in io_loop_handler_run (ioloop=0x232c740) at ioloop.c:607 > #11 0x00007f6f99fc3bf6 in io_loop_run (ioloop=0x232c740) at ioloop.c:583 > #12 0x00007f6f99f317af in master_service_run (service=0x232c5e0, callback=0x430a35 <client_connected>) at master-service.c:640 > #13 0x0000000000430da2 in main (argc=1, argv=0x232c390) at main.c:442 Florian

3 3

postmaster domain
by Timothy Murphy 04 Jan '16

04 Jan '16

I recently upgraded a remote server to CentOS-7.2, after which email stopped coming through. I suspect that this was probably due to the fact that I had started a version of dovecot installed some time ago. I found messages in /var/log/maillog like Jan 4 12:56:56 alfred postfix/lmtp[7612]: 20A662202B4: to=<root(a)gayleard.eu>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=34272, delays=34272/0.16/0.01/0.05, dsn=4.3.0, status=deferred (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 <root(a)gayleard.eu> Invalid user settings. Refer to server log for more information. (in reply to RCPT TO command)) Googling for this, I found the suggestion that one should insert the following postmaster_address line in /etc/dovecot/conf.d/20-lmtp protocol lmtp { postmaster_address = postmaster(a)alfred.eu # Space separated list of plugins to load (default is global ail_plugins). mail_plugins = $mail_plugins sieve } (alfred.eu being the server's domain). This seems to have solved the problem, after re-starting dovecot. I'm wondering if this was an issue that arose some time ago, and if so whether my solution was the recommended one? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

1 0

Re: Howto get information about quota used
by Макаров Денис 04 Jan '16

04 Jan '16

I tried this for correct user: sudo doveadm quota get -u user Quota name Type Value Limit % User STORAGE 0 614400 0 User MESSAGE 0 - 0 Ok, limit is correct. But why value and % = 0? Via Thunderbird I see 52%. >> Hello guys! >> >> I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. >> >> I wanna know how to get information about quota used of current email. >> >> I can do this with IMAP client like Thunderbird, but how I can do it >> on server? > Try this: > > # doveadm quota get -A > ... > > p@rick > -- Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

1 1

How to debug lmtpd?
by kjonca＠o2.pl 04 Jan '16

04 Jan '16

1. I have dovecot installation with lmtp 2. there are some sieve filter which call mailpost to put mails in my news server. 3. SOME mails are not mailposted :( I do not know why. Moreover these mails filtered by dovecot-lda ARE mailposted whit the same sieve filter. 4. How can I debug lmtp and it's descendant processes? strace -ff only? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Boys, you have ALL been selected to LEAVE th' PLANET in 15 minutes!!

2 1

Double folders?
by Frank W 04 Jan '16

04 Jan '16

Hi, I upgraded my dovecot install from 2.0.19 to 2.2.19. I haved update the configuration, accordingly, but I when I open roundcube, I see multiple folders like sent, trash, facebook, etc... I not sure if am missing something or not. Here is my configure: [root@mgmt ~]# cat dovecot_config.txt # 2.2.19: /etc/dovecot/dovecot.conf # OS: Linux 3.4.4 armv5tel Gentoo Base System release 2.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no first_valid_gid = 207 first_valid_uid = 207 last_valid_gid = 207 last_valid_uid = 207 listen = *, [::] mail_gid = 207 mail_location = maildir:/var/vmail/%u/Maildir/:INDEX=/var/vmail/%u/indexes mail_plugins = quota mail_uid = 207 namespace { inbox = yes location = prefix = INBOX. separator = . name = } namespace { location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = imap pop3 service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { user = $default_internal_user name = auth-worker } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/auth } unix_listener { group = mail mode = 0666 user = mail path = auth-userdb } name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/postfix/ssl/mail.xxxxxx.net.crt ssl_cipher_list = ALL:!LOW:!SSLv2 ssl_key = </etc/postfix/ssl/mail.xxxxxxx.net.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_plugins = quota imap_quota service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol pop3 { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

2 1

Released Pigeonhole v0.4.11.rc1 for Dovecot v2.2.21
by Stephan Bosch 04 Jan '16

04 Jan '16

Hello Dovecot users, First, a happy new year to you all! :) In the last few weeks I got quite a few bug reports. I also found a few things myself. Some of the bugs are quite annoying, so a new release is necessary. First, I release RC1. If all is well, I'll release the definitive Pigeonhole v0.4.11 within the next few days. Changelog v0.4.11: - Sieve mime extension: Fixed the header :mime :anychild test to work properly outside a foreverypart loop. - Several fixes in message body part handling: - Fixed assert failure occurring when text extraction is attempted on an empty or broken text part. - Fixed assert failure in handling of body parts that are converted to text. - Fixed header unfolding for (mime) headers parsed from any mime part. - Fixed trimming for (mime) headers parsed from any mime part. - Fixed erroneous changes to the message part tree structure performed when re-parsing the message. - LDA Sieve plugin: Fixed logging of actions; sometimes the configured log format was not followed. - LDA Sieve plugin: Fixed bug in error handling of script storage initialization. - Sieve Extprograms plugin: Ignored ENOTCONN error in shutdown(fd, SHUT_WR) call. - Fixed duplication of discard actions in the script result. Each discard was counted as a separate action, which means that action limit would be crossed too early. - Made sure that quota errors never get logged as errors in syslog. - Fixed handling of implicit keep for a partially executed transaction that yielded a temporary failure. - Fixed handling of global errors. If master and user error handler were identical, in some cases the log message could be lost. - Fixed AIX compile issue in message body parser. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.11… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.11… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Howto get information about quota used
by Макаров Денис 03 Jan '16

03 Jan '16

Hello guys! I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. I wanna know how to get information about quota used of current email. I can do this with IMAP client like Thunderbird, but how I can do it on server? doveconf -n | grep quota mail_plugins = quota, antispam quota = maildir:User quota_exceeded_message = Message quota_rule = *:storage=100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u service quota-warning { executable = /usr/local/bin/quota-warning.sh mail_plugins = quota imap_quota mail_plugins = quota sieve For each mailboxes I use quota limits from MySQL. -- С уважением, *Макаров Денис* *почта*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com> Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

2 1

SASL binds
by Brendan Kearney 01 Jan '16

01 Jan '16

i am looking to get SASL binds working in Dovecot for userdb lookups, and i am not sure what i might be doing wrong. Dovecot version - 2.2.19 running on Fedora 22. MIT Kerberos and OpenLDAP are being used. my LDAP configs: uris = ldap://server1.bpk2.com ldap://server2.bpk2.com sasl_bind = yes sasl_mech = gssapi sasl_realm = BPK2.COM sasl_authz_id = imap/imap.bpk2.com(a)BPK2.COM base = dc=bpk2,dc=com the above results in the below error logs: Jan 01 13:56:58 mail auth[16747]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available) Jan 01 13:56:58 mail dovecot[16722]: auth-worker(16747): Error: LDAP: binding failed (dn (none)): Local error, SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available) i am assuming the keytab, /etc/dovecot/dovecot.keytab would be used to bind to the directory, but i am not sure. the auth_krb5_keytab directive is set with the absolute path and keytab name. is there something i am missing, such as a /etc/sasl2/dovecot.conf file? in the directory, i am mapping the Kerberos ID to LDAP user object as such: uid=imap\/(.*).bpk2.com,cn=bpk2.com,cn=gssapi,cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com if i change the sasl_authz_id to uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com, and restart dovecot, i still get the same error. can anyone shed light on where i am going wrong? thanks in advance, brendan

1 0

doveadm expunge no longer works
by Fabian Groffen 31 Dec '15

31 Dec '15

Heya, Just upgraded from 2.2.19 to dovecot-2.2.21 and noticed expunging mail no longer works. # doveadm expunge -u theuser MAILBOX spam all Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) Clearly, I've already got all in there, so I tried capitalising, etc. Looking at the code, I see expunge_search_args_is_msgset_or_ok apparently is failing. I'm wondering if this function [1] is actually doing what it is supposed to do, since it uses return, instead a var to figure out whether it is ok or not. In my case, just because it finds MAILBOX it returns without looking whether there is any further arguments. Or am I missing the point here (and how should I expunge a folder of mail?) Thanks, Fabian [1] https://github.com/dovecot/core/blob/6971937a6f3e93844dbd43bdbe903628e21a94… -- Fabian Groffen Gentoo on a different level

1 1

sieve-filter to script fails with SHUT_WR
by Mark Stover 31 Dec '15

31 Dec '15

Trying to make vnd.dovecot.filter to exchange an email with my script. (I have a vnd.dovecot.pipe script working, so I'm pretty sure it's not the configuration...) I'm passing the email using stdin/stdout and _not_ using sockets. My script receives the email and processes it, but the filter process fails: lda(<username>): Error: shutdown(/usr/local/lib/dovecot-sieve/sieve-filter/CleanAttachments.py, SHUT_WR) failed: Socket is not connected lda(<username>): Error: sieve: 20-filter-incoming: line 15: filter action: failed to execute to program `CleanAttachments.py' Not sure, what I'm doing wrong... Thanks, Mark $ doveconf -n # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Darwin 15.2.0 x86_64 lda_mailbox_autocreate = yes mail_location = maildir:~/Maildir maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes plugin { sieve = file:~/.dovecot/sieve;active=~/.dovecot/sieve/user.sieve sieve_before = /usr/local/lib/dovecot-sieve/sieve.d/ sieve_execute_bin_dir = /usr/local/lib/dovecot-sieve/sieve-execute sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter +vnd.dovecot.debug sieve_filter_bin_dir = /usr/local/lib/dovecot-sieve/sieve-filter sieve_pipe_bin_dir = /usr/local/lib/dovecot-sieve/sieve-pipe sieve_plugins = sieve_extprograms sieve_user_log = ~/.dovecot/sieve/sieve.log } postmaster_address = mstover(a)cisco.com protocol lda { info_log_path = log_path = mail_plugins = " sieve" } Sieve Script: require [ "variables", "envelope", "vnd.dovecot.debug", "vnd.dovecot.filter" ]; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Received message TO=${to} FROM=${from}"; filter "CleanAttachments.py"; debug_log "Returned from CleanAttachments"; if envelope :matches "to" "*" { set "to" "${1}"; } if envelope :matches "from" "*" { set "from" "${1}"; } debug_log "Returned message TO=${to} FROM=${from}";

2 2

LMTP crashes on Debian with dovecot backports from rename-it.nl
by Christian Schmidt 30 Dec '15

30 Dec '15

Hello dovecot-users, we're running Debian 7.9 with dovecot from Stephan Bosch's repository: deb http://xi.rename-it.nl/debian/ oldstable-auto/dovecot-2.2 main Starting with dovecot 2.2.20-1 build 28, we suddenly discovered that some mails (to be locally delivered) "got stuck". dovecot's log revealed messages like the following one: Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8360f) [0x7f58fce4f60f] -> /usr/lib/dovecot/libdovecot.so.0(+0x8366e) [0x7f58fce4f66e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f58fcdf8a3e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x3cc75) [0x7f58fd107c75] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xabeda) [0x7f58fd176eda] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xba) [0x7f58fd17723a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x38) [0x7f58fd108cd8] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x1b5c) [0x7f58fb16cb5c] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x22e9) [0x7f58fb16d2e9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(notify_contexts_mail_copy+0x46) [0x7f58fb371576] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x2750) [0x7f58fb372750] -> /usr/lib/dovecot/modules/lib10_quota_plugin.so(+0xbc20) [0x7f58fb580c20] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x7d) [0x7f58fd11305d] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x171) [0x7f58fd4019c1]-> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x11b) [0x7f58fd401dfb] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x7263) [0x7f58fd831263] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x79d9) [0x7f58fd8319d9] -> /usr/lib/dovecot /libdovecot.so.0(io_loop_call_io+0x5b) [0x7f58fce6282b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7f58fce63c07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f58fce628d5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f58fce62a78] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f58fcdfe443] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](main+0x19c) [0x7f58fd82f8dc] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f58fca5fead] -> dovecot/lmtp [DATA MAILRECIPIENT(a)chemie.uni-hamburg.de](+0x59ad) [0x7f58fd82f9ad] Dec 29 09:56:50 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Fatal: master: service(lmtp): child 15897 killed with signal 6 (core dumps disabled) Dec 29 09:56:51 mailhost dovecot: lmtp(MAILRECIPIENT(a)chemie.uni-hamburg.de): Panic: file ../../../src/lib/array.h: line 219 (array_idx_i): assertion failed: (idx * array->element_size < array->buffer->used) All dovecot builds newer than 2.2.20-1~auto+26 show the same behaviour. Is there anything we can do? # doveconf -n # 2.2.20 (): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 ext4 auth_default_realm = chemie.uni-hamburg.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = vmail mail_location = maildir:/mail/%d/%n/Maildir mail_plugins = acl mail_log notify quota zlib mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart imapflags notify namespace { list = children location = maildir:/mail/%%d/%%n/Maildir:INDEX=/mail/%d/%n/shared/%%u:CONTROL=/mail/%d/%n/shared/%%u prefix = SHARED/%%u/ separator = / type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:Mailbox-Quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = postmaster(a)chemie.uni-hamburg.de protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 8 service_count = 0 vsz_limit = 256 M } service imap { executable = imap postlogin process_limit = 1024 vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/lmtp-dovecot { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login -d rawlog } ssl = required ssl_ca = </ssl/CA.pem ssl_cert = </ssl/cert.pem ssl_key = </ssl/cert.key ssl_protocols = !SSLv2 !SSLv3 syslog_facility = daemon userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = acl mail_log notify quota zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota zlib sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = acl mail_log notify quota zlib imap_acl imap_quota imap_zlib } protocol sieve { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 50 } Thanks & kind regards, Christian Schmidt -- No signature available.

3 6

Re: sieve-filter crashes
by kjonca＠o2.pl 30 Dec '15

30 Dec '15

I tried to post earlier, but something goes wrong. KJ kjonca(a)o2.pl (Kamil Jońca) writes: > I want to refilter my mails in inbox so I tried to use: > > sieve-filter -e -W -D -C -v ~/.dovecot.sieve INBOX > > on three messages I got: > > info: filtering: [Fri, 28 Dec 2012 15:40:33 -0500; 14399 bytes] `[SPAM] Keep Defective by Design fight...'. > sieve-filter(kjonca): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') > sieve-filter(kjonca): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x82462) [0x7f2012002462] -> /usr/lib/dovecot/libdovecot.so.0(+0x824d9) [0x7f20120024d9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f2011fa9a01] -> /usr/lib/dovecot/libdovecot.so.0(+0xa9098) [0x7f2012029098] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5f1dc) [0x7f20128211dc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_match+0xf1) [0x7f2012807721] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x5fa85) [0x7f2012821a85] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0xe7) [0x7f20127fe657] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f20127fe7db] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4faca) [0x7f2012811aca] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7f2012812637] -> /usr/bin/sieve-filter(main+0x754) [0x7f2012c96d24] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f20119f4b45] -> /usr/bin/sieve-filter(+0x43ca) [0x7f2012c973ca] > > > # 2.2.19 (a9c75e48cf8c): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.9 > # OS: Linux 3.16.0-4-amd64 x86_64 Debian stretch/sid > > KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html A stitch in time saves nine.

3 3

How to apply the patch for disable SSL3 on Dovecot 2.0.9
by Marco 29 Dec '15

29 Dec '15

Hi,I see on Dovecot 2.0.9 is no possibile disable SSL3 Until I wait the panel of my server will look into this issue and maybe put a more updated version, how I can fix this?I found on the Internet http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-poodl… also link to the patch http://www.mail-archive.com/dovecot@dovecot.org/msg59945.html I don't know what to do for fix the SSL 3 Issue I AM On CentoOs 6.3Thanks.

2 1

Howto get information about quota used
by Макаров Денис 29 Dec '15

29 Dec '15

Hello guys! I have Dovecot server (version: 2.2.9) with quota and imap_quota plugins. I wanna know how to get information about quota used of current email. I can do this with IMAP client like Thunderbird, but how I can do it on server? doveconf -n | grep quota mail_plugins = quota, antispam quota = maildir:User quota_exceeded_message = Message quota_rule = *:storage=100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u service quota-warning { executable = /usr/local/bin/quota-warning.sh mail_plugins = quota imap_quota mail_plugins = quota sieve For each mailboxes I use quota limits from MySQL. -- С уважением, *Макаров Денис* *почта*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com> Best regards, *Makarov Denis* *email*: makarovdenis11(a)gmail.com <mailto:makarovdenis11@gmail.com>

2 1

Query regarding migration from Maillenium to Dovecot mail server
by Sirisha R 29 Dec '15

29 Dec '15

Hi, We have few queries regarding dovecot mail server. Our application used to supported maillenium mail server, but soon this server is going to retire. So we are planning to migrate our application mail server to dovecot for which we seek your help. Previously, the mailboxes that our application used to support were under att domain, then the mailboxes were migrated to maillenium mail server, and aliases of the existing att mailboxes were created by maillenium support group, so that any mail sent to the att mailbox automatically gets redirected to maillenium alias mailbox. For instance, for the mailbox abc.att.com, an alias was created as abc(a)maillenium.att.com<mailto:abc@maillenium.att.com>. Maillenium support group provided us mailServerHost, mailServerUsername and mailServerPassword. We seek your help in migrating from Maillenium mail system to Dovecot. Thanks & Regards, R Sirisha This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

1 0

Sieve: Invalid/unknown path to storage
by Kay-Michael Voit 25 Dec '15

25 Dec '15

Hi, I have just updated from Ubuntu 15.04 to 15.10. Unfortunately, sieve scripts are not recognized anymore. Here is my version: > dovecot --version > 2.2.18 > apt-cache policy dovecot-sieve > dovecot-sieve: > Installed: 1:2.2.18-2ubuntu2 > Candidate: 1:2.2.18-2ubuntu2 > Version table: > *** 1:2.2.18-2ubuntu2 0 > 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages > 100 /var/lib/dpkg/status And this is the log entry: > Dec 25 09:24:12 home-le dovecot: lda(user1): Warning: sieve: file > storage: Active sieve script symlink /home/user1/.dovecot.sieve is > broken: Invalid/unknown path to storage (points to /home/user1/sieve). > Dec 25 09:24:12 home-le dovecot: lda(user1): > msgid=<567CFD2C.7070301(a)example.org>: saved mail to INBOX > Dec 25 09:24:12 home-le postfix/local[28536]: 70876BD035A: > to=<user1(a)example.org>, relay=local, delay=0.07, > delays=0.02/0.01/0/0.04, dsn=2.0.0, status=sent (delivered to command: > /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot.conf -m "${EXTENSION}") It is not a permission issue (though there should even be one with more restrictive permissions) > otheruser@home-le:~$ cat /home/user1/.dovecot.sieve > require ["variables","date", "include"]; > > include :personal "00-delete"; > include :personal "01-spam"; > include :personal "50-bulk_filter"; It is apparently also not a path normalization issue (also according to the correct "points to" path in the log). I used an absolute path in the symlink: > user1@home-le:~$ ls -la .dovecot.sieve > lrwxrwxrwx 1 user1 user1 33 Dec 25 09:23 .dovecot.sieve -> > /home/kay/sieve/managesieve.sieve Any idea what could be wrong here? Here is my dovecot -n output: > namespace inbox { > inbox = 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 = > separator = . > type = private > } > passdb { > driver = pam > } > plugin { > sieve = file:~/.dovecot.sieve > sieve_dir = ~/sieve > } > postmaster_address = postmaster(a)example.net > protocols = " imap sieve" > service managesieve-login { > inet_listener sieve { > port = 4190 > } > } > ssl_ca = </etc/ssl/certs/startssl.ca.pem > ssl_cert = </etc/ssl/certs/net.example.home-le.pem > ssl_key = </etc/ssl/private/net.example.home-le.key > submission_host = 192.168.153.1 > userdb { > driver = passwd > } > protocol lda { > mail_plugins = " sieve" > } > protocol imap { > mail_max_userip_connections = 50 > }

2 2

Debug Dovecot Plugin (shared library)
by David Becher 24 Dec '15

24 Dec '15

Hey! I was just wondering what would be the best way to debug a plugin I am currently writing for dovecot. The plugin basically registers a new IMAP capability and I want to set a breakpoint to the "cmd_handle_new_capability" function (thats just a function name for better explaining purposes). Right now I have opened a connection via openssl ('openssl s_client -connect example:143 -starttls imap') to be able to mess around with the my server. Then I am able to login into the server via 'a login "username" "password"' and feed the server with my self created IMAP capability command. I know that I can start gdb and attach to an already running process via its PID. But how do I know which process I have to attach to? Looking at the output of 'top' it seems to be an instance of the 'imap' command PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13413 vmail 20 0 21004 1844 1524 S 0.0 0.0 0:00.00 Iman But its only started the exact moment I issue my IMAP command towards the server, so of course I am not fast enough to track down the PID before the function has returned, so the process handling the command seems to be up only for the short period of time to handle the command, there is no process before which I can attach to. My current workaround is that I put a tail onto /var/log/mail.log and from within my shared library function (cmd_handle_new_capability) I log the PID of the current process, then sleep(10) for 10 seconds, which gives me enough time to have a look at mail.log to get to know the PID which I then can attach to. But isn't there a better way to do this? Maybe attach to the process which originally creates the new process handling the IMAP command and then stepping into it? I hope someone can help me out :) All the best, David

2 2

Dovecot 2.2.20 autoexpunge
by Robert Blayzor 23 Dec '15

23 Dec '15

I have configured autoexpunge on some folders: namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } After adding these and restarting, logging in and out several times, I still see messages days/weeks past the autoexpunge setting. I checked the logs but never see any autoexpunge messages logged. Is there something else that needs to be set to trigger this? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

4 6

dsync and namespaces
by Charlie Hothersall-Thomas 22 Dec '15

22 Dec '15

`doveconf -n' output: > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-229.20.1.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) > listen = * > mail_location = maildir:~/Maildir/ > namespace { > inbox = yes > location = > prefix = > separator = / > type = private > } > namespace { > location = maildir:/srv/mail/ > prefix = Public/ > separator = / > subscriptions = no > type = public > } > passdb { > driver = pam > } > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > userdb { > driver = passwd > } I have some public mailboxes in /srv/mail -- Public/Alpha and Public/Mike -- using configuration taken more or less verbatim from http://wiki2.dovecot.org/SharedMailboxes/Public. These are stored in Maildir format; here's a sample of how things look on disk at the moment: > /srv/mail/ > ├── .Alpha > │ ├── cur > │ │ └── 1450775948.M24820P23708.cht,S=8186,W=8360:2,S > │ ├── dovecot.index.cache > │ ├── dovecot.index.log > │ ├── dovecot-uidlist > │ ├── maildirfolder > │ ├── new > │ └── tmp > ├── cur > ├── dovecot.index.log > ├── dovecot-uidlist > ├── dovecot-uidvalidity > ├── dovecot-uidvalidity.5679158d > ├── maildirfolder > ├── .Mike > │ ├── cur > │ │ ├── 1450775948.M202327P23708.cht,S=8405,W=8576:2,S > │ │ ├── 1450775948.M257575P23708.cht,S=5590,W=5732:2,S > │ ├── dovecot.index.cache > │ ├── dovecot.index.log > │ ├── dovecot-uidlist > │ ├── maildirfolder > │ ├── new > │ └── tmp > ├── new > └── tmp I'm trying to convert these public mailboxes from Maildir to mdbox format. My end goal is a directory structure like the following. I obtained this example by emptying /srv/mail, changing `location = maildir:/srv/mail/' to use mdbox, and then delivering some messages into Public/Alpha and Public/Mike: > /srv/mail/ > ├── dovecot-uidvalidity > ├── dovecot-uidvalidity.567915fa > ├── mailboxes > │ ├── Alpha > │ │ └── dbox-Mails > │ │ ├── dovecot.index.cache > │ │ └── dovecot.index.log > │ ├── dbox-Mails > │ │ └── dovecot.index.log > │ └── Mike > │ └── dbox-Mails > │ ├── dovecot.index.cache > │ └── dovecot.index.log > └── storage > ├── dovecot.map.index.log > └── m.1 I know that dsync can be used to convert between mailbox formats, but is this possible in conjunction with namespaces? I can convert one of my mailboxes to an arbitrary mdbox location on disk using... > dsync -o mail_location=mdbox:/tmp/dbox/ mirror maildir:/srv/mail/.Mike/ ... although this puts the messages inside an INBOX mailbox: > /tmp/dbox/ > ├── mailboxes > │ └── INBOX > │ └── dbox-Mails > │ ├── dovecot.index.cache > │ └── dovecot.index.log > └── storage > ├── dovecot.map.index.log > └── m.1 I could run this once per public mailbox, writing each to a different mdbox location, but am unaware of a method to merge them such that they would work with my Public/ namespace. Is it possible to use dsync to convert my public Maildir mailboxes to mdbox, resulting in my desired directory structure above? I think I want to be able to tell dsync the location as a mailbox name, rather than a disk location, although this doesn't appear to be possible. If not, is there another solution? My best idea at the moment is to make the configuration change and then re-deliver all messages by mailbox name. Thanks in advance, and happy holidays, -- Charlie Hothersall-Thomas | w: https://charlie.ht | e: me(a)charlie.ht | pgp: 4096R/C3676E3E

1 0

[bug][Pigeonhole 0.4.10] Missing msgid
by Alexander Moisseev 22 Dec '15

22 Dec '15

Pigeonhole 0.4.10 doesn't log msgid for some messages. Dec 16 09:57:57 mx dovecot: lmtp(user1(a)example.com): EbLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.BE1DF1FFD8(a)cp.bitrix24.com>: forwarded to <user3(a)example.com> Dec 16 09:57:57 mx dovecot: lmtp(user1(a)example.com): EbLlL2gLcVYCBgEAPZa6/Q: sieve: stored mail into mailbox 'INBOX' Dec 16 09:57:57 mx dovecot: lmtp(user2(a)example.com): FrLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.C77BB1FFD8(a)cp.bitrix24.com>: forwarded to <user3(a)example.com> Dec 16 09:57:57 mx dovecot: lmtp(user2(a)example.com): FrLlL2gLcVYCBgEAPZa6/Q: sieve: msgid=<20151216065756.C77BB1FFD8(a)cp.bitrix24.com>: stored mail into mailbox 'bitrix'

2 6

Where exactly are these Junk]Trash etc folders stored?
by Robert Chalmers 22 Dec '15

22 Dec '15

These folders are stored somewhere .. but where? mailbox Trash { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox virtual/All { # if you have a virtual "All messages" mailbox auto = no special_use = \All }

2 1

Thanks again for Dovecot
by Steve Litt 21 Dec '15

21 Dec '15

Hi all, All email clients suck. IMHO Claws-Mail sucks less, but even on the Claws-Mail mailing list there are all sorts of problems discussed. Most of these problems are a moot point for me, because I use Claws-Mail only as a window into my locally hosted Dovecot IMAP server. Claws-Mail is like a little window into Dovecot. Meanwhile, all those "don't quite work right" functionalities normally done by an email client I do outside of Claws. For filtering, I use Procmail, which sorts messages into the correct (Dovecot) folders and sends trolls to /dev/null. If Claws-Mail ever becomes as lame as Kmail, I can just switch to another email client, because most of my setup is in Dovecot and the input to Dovecot. Email clients are interchangeable for me, and this REALLY makes my life less worrysome. And Dovecot does one thing and does it right. It never breaks. Thank you for this great tool! SteveT Steve Litt November 2015 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques

1 0

questions for a unusual master/slave like mail-server setup
by Christoph Anton Mitterer 21 Dec '15

21 Dec '15

Hey folks. I was planning since a long time for some more advanced mail server setup (described below), which basically has some weird ;) master/slave ideas behind. It's probably a bit more complicated (and maybe also a bit more insane) than the usual mail server setup, so I'd be happy about any advice and some questions answered: There are two mailservers (dovecot, as you may have guessed ;) ): - IMAP shall be used; using POP3 is not planned. - A format in which each mail is stored in a separate file shall be used. That leaves for either maildir or sdbox, where I'd prefer maildir, as I like to be able to loose the indexes. - Each (per user) mailbox shall have many subfolders and will receive loads of mail (including from several high traffic mailing lists). - Mail filtering shall take place *at least* on the "online" server, probably either with sieve or maildrop. - One of the mailservers is always "online", directly connected to the internet (and globally available). - The other mailserver is "offline", not directly connected to the internet (and only locally available). The "online" mailserver: - Is in a not fully trusted location (i.e. at some ISP). - Has somewhat limited storage. - Makes the mails on it available to MUAs connecting from anywhere. - Receives mail from various sources, e.g. via postfix/LDA or something like fetchmail. - Has only a parts of *all* mails, that means for example: - *All* mail from some personal contacts. - Only the last 1 year for low volume mailing lists. - Only the last 4 months for high volume mailing lists. The "offline" mailserver: - Is in a trusted location (beneath my pillow ;) ). - Has enough storage for the purposes of mail. - Makes all mails available to MUAs connecting from the LAN. - Receives mails from the "online" mailserver, when manually "moved" to it via some MUA over IMAP. - Has *all* mails. Client's MUAs, may connect to both, but the "offline" server will only be available at home. As you can imagine, the idea is basically the following: I get large amounts of mails, from all kind of mailing lists as well as personal mail. All that is filtered to a tree hierarchy of folders. There's a not fully secure mailserver, where mail arrives and which I can use when I'm on the way. It contains either just recent mails (the amount depending on the traffic of the list) or for selected senders/lists everything, and I control basically on a per folder basis how much should be retained (all, last 10 years, last week, etc.). There's another server, where *all* mail should eventually end up, for archival and security reasons. This implies obviously, that some of the mail is on both servers, some only on the "offline" server, and that this may vary from folder to folder. Further, on both servers, I may want to add filters, which basically split up a folder, e.g. of high traffic lists, so that mail of previous years or months is moved to subfolder structures, e.g.: linux-kernel +--2014 \--2013 and so on. So far, all that wouldn't be too difficult,... but as you can imagine, I'd like to have a bit more, which actually makes things quite tricky. How the two mailservers shall synchronise: I don't want to "simply" rsync - the whole system needs to be a bit smarter: 1) It's okay to assume, that synchronisation happens only at discrete times and not continuously (the "offline" server doesn't run always). 2) It would be ok, if the synchronisation requires a downtime of the "online" mailserver (i.e. the LDA). Since btrfs is used, I could also easily do snapshots. 3) One can also assume that, when synchronisation happens, the "offline" server contains at least all those folders, that the "online" server has as well (and possibly more). 4) Obviously, only maildir's cur/ directories should be synced (stuff in tmp&new may be still arriving). 5) As mentioned previously, not all mail may stay on the "online" server, depending on the folder, it will either stay permanently, or only for some period. 6) However, on the "offline" server, all mail stays, unless I manually delete it. 7) One must assume, that mails on *both* servers: - change their IMAP status (as in (S)een, (A)nswered, (F)lagged, etc.) - are moved to other mail folders - may be deleted via MUAs (not clear yet where this can happen) - "Fresh" mail, however, only appears on the "online" server. 8) Mails, once on the "offline" server, shouldn't be rewritten, in the sense that the mail is deleted and recreated (hopefully with the same content), which could happen either wenn the status of the mail changes or when it's moved to another folder (on the other server). The reason is simply, that I wouldn't fully trust the online server, so once the mail is local, it should be immutable (except for the status and folder location). The last, two points make things pretty difficult, or at least I wouldn't see a straightforward solution. (4) would be quite easy, e.g. when rsync would be used, then I'd just rsync all the cur/ directory. The rsync would happen not using --delete, so that mail which is no longer on the "online" server, doesn't get deleted from the "offline" server. (5) one could do, by "simply", on a per folder basis, remove mails older than X on the "online" server, after it has been copied to the "offline" server. An already existing tool for doing that would be nice, though. (7) and (8) is IMHO the most difficult: The only idea I have so far assumes that each mail file has an ID, which is unique for the *whole* mailbox (not just for each folder, as the mails may be moved between folders). The idea would be roughly, the following: * When I synchronise, I either shut down the LDA or make a snapshot of the "online" server's mailbox and work with that. * Then, I make a list (ID, status and pathname) of *all* mails on the online server and another one of *all* mails of the offline server. * Then, I probably scan for duplicate IDs in each list... just to be safe. * Then I process the mail lists as follows: a) If an ID is on *both* servers with the same status and pathname, than that mail had been previously synced already and neither moved nor changed its status since then. Nothing to do. b) If an ID is on *both* servers but with different pathnames or status, then the mail has either been moved or it's status has changed. Consequently, I would move/rename the mail to match the new location and/or IMAP-status. I would move/rename that with the older ctime to match the one with the newer (ctime gets set at move or rename and thus at status change). Even if an attacker would have fiddled with the "online" server's time or somehow else my system times were bogus, the worst that would happen was, that status changes are lost or mail ends up in the wrong folder. c) If an ID is on the "offline" server but not the "online" server, it could be either a mail that has already been garbage collected on the "online" server (so nothing would needed to be done),... or it could be mail hat was removed (via a MUA) on the "online" server and that should as well be removed on the "offline" server, either automatically, or manually after checking. How to find out which of that applies!? d) If an ID is on the "online" server but not the "offline" server, it could be either fresh mail that would needed to be synced,... or it could be mail that was removed on the "offline" server and should as well deleted on the "online" server, either automatically, or manually after checking. (a) and (b) are again rather simple, (c) and (d) not so much... Possible solutions that I could think of: - Either simply don't sync the removal of mails from the "online" server to the "offline" server and vice-versa. It will anyway happen rather rarely. - Remember a list of all IDs, that have been garbage collected on the "online" server. - Remebmer a list of all IDs, that have been removed via MUAs. => not sure if that's easily doable, probably not, is there any dierct way one could do this with dovecot. - Something to find out which mail has been gone on both, the each, the "offline" and the "online" server, since the last synchronisation, via tricks using the snapshot features of btrfs. - Somehow using the date of now and the last synchronisation and the mtimes (which are here basically like creation times, as the mail file contents never change). But I guess that would only work for (d) and not for (c),... and I'd rather not depend on times too much. * In any case, I could give the user a list of mails that would be deleted, for double checking. I actually think this would scale, as I don't expect many mails to be manually deleted through the MUA *once they had been synced*. After that, I think the two servers should be in sync - in the sense described in the beginning. Some further parts of the idea: As said, snapshots and the refcopy feature of btrfs could be quite helpful. So I could basically keep: - the "online" mailserver's mailbox - as of the last sync - as of now - the "offline" mailserver's mailbox - as of the last sync - as of now at the disk of the "offline" server without much additional cost. They'd all share reflinks and wouldn't use (much) additional space (except for fs meta-data) and I could use the snapshots to find out which files were deleted on either of the two servers since last time. Actually copying new mail from the "online" server to the offline server's disk (in the "as of now" area), could then happen via rsync'ing every cur/ from the "online" server to the "offline" server, with --delete and --ignore-existing (as I don't trust the "online" server and mail file contents should be immutable). So... questions... :D 1) Obviously, does anyone know a better solution, or has some improvements, other ideas? Or are there any problems with the above, which I haven't realised, or would you think it would work? 2) Does dovecot *ever* change the contents (i.e. the file contents) of a maildir mail file? 3) As ID I'd have thought that the maildir mail filename might work, e.g. 1234567890.M20046P2137.mailserver,S=4542,W=4642:2,Sb I mean especially the first part: 1234567890.M20046P2137.mailserver Is that unique across *all* folders of a mailbox? AFAIU, that name would be determined by whatever delivers the mail, right? So can I somehow configure that to make it unique? 4) Does dovecot ever change anything from the maildir mail filenames, except anything after the ":" above? I.e. would it ever change: 1234567890.M20046P2137.mailserver,S=4542,W=4642 ? 5) Would dovecot every copy, truncate+copy or somehow else rewrite files, instead of just moving them (i.e. thus possibly changing inodes, reflinks or that like)? 6) AFAIU, when using maildir, dovecots index files can get completely lost,... and one can fully "recover" all mails and their status. The only "bad" thing that might happen is that MUAs re-load all mail, right? 7) How graceful does dovceot handle the situation when mail is added or removed to/from cur/ by not using dovecot's IMAP,... especially with respect to index files. In the above solution I'd do a lot adding/moving/deleting files in maildirs, which would be done purely at the (file) system level, so the index would quite often get invalidated. How does it recognise that (if at all)? And is this generally stable, or should I rather remove any indexes after syncing and have them rebuilt by that? 8) All the above doesn't handle yet the thing of having yearly/monthly/etc. archive subfolders as described above, like: linux-kernel +--2014 \--2013 possibly on *both* "online" and "offline" server and possibly even in a different layout. I'm not yet sure whether this would be easily doable with the above solution,... my basic idea would be simply consider any such "archive" subfolders as the same than the "base" folder during syncing... and afterwards do re-order the mails on the "offline" and "online" server's folders as necessary. For example, if the "online" server has: linux-kernel +--01 +--02 +--03 ... \--12 in other words, one archive folder for the each of the last 12 months. While the "offline" server has: linux-kernel +--2014 \--2013 The script would then e.g. move the files to their new folders. => does anyone know, whether such thing exists already, i.e. a tool that sorts the mails into maildir subfolders, based on years, months, etc? 9) As said before, I'd like to be able to loose any indexes, but AFAICS, my solution wouldn't anyway work with sdbox. But if there's an sdbox based solution that makes everything much easier, do not hesitate to tell me :) 10) In the long-term I hope to be able to do something that makes server-side search (i.e. through the big fat mail archive) much faster (or is that already supported in dovecot?). I haven't really looked at all into that topic (just know about notmuch[0]). Anyway, if anyone sees problems in my above solution, when that would be used with something that gives me better server side search (i.e. some indexing solution),... I'd be happy to hear about that as well. Thanks a lot so far, Chris. [0] https://notmuchmail.org/

1 0

Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
by Jeff Stedfast 20 Dec '15

20 Dec '15

Hi all, I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against. What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax. According to rfc6154, a server is supposed to advertise the CREATE-SPECIAL-USE extension if it supports this: An IMAP server that supports this OPTIONAL feature will advertise the "CREATE-SPECIAL-USE" capability string. Clients MUST NOT use the "USE" parameter unless the server advertises the capability. Note that this capability string is different from the "SPECIAL-USE" string defined above, and a server that supports both functions MUST advertise both capability strings. Has this been fixed in a newer version, perhaps? Or could it be a misconfiguration on my part? Attached is my dovecot configuration (gotten via dovecot -n). Thanks, Jeff

2 2

Multiple IPs and hostname
by Thilo Engelbracht 18 Dec '15

18 Dec '15

Hi, I'm running postfix as SMTP-server and dovecot as IMAP-server. The server has multiple IPs, and postfix is configured that every domain is using a separate IPv4-address. Examle: foo1.com --> 11.22.33.44 foo2.com --> 22.33.44.55 foo3.com --> 33.44.55.66 bar.org --> 66.77.88.99 The hostname of the server is: mail.bar.org Now I have a request from one of my customers, who is using 3 different domains: - foo1.com - foo2.com - foo3.com If he receives a mail to "user(a)foo1.com", the header of the mail looks like this: Return-Path: <somebody(a)web.de> Delivered-To: <user(a)foo1.com> (II) Received: from mail.bar.org by mail.bar.org (Dovecot) with LMTP id V[...]wAAvP/pag for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:37 +0100 (I) Received: from mout.web.de (mout.web.de [212.227.17.11]) (using TLSv1.2 with cipher ECDHE-[...]-SHA384 (256/256 bits)) (No client certificate requested) by mail.foo1.com (Postfix) with ESMTPS id A[...]9 for <user(a)foo1.com>; Sun, 29 Nov 2015 13:45:36 +0100 (CET) As you can see in (I), postfix receives the mail and added a header with the correct hostname: mail.foo1.com But dovecot adds an additional header (see II). Here, the hostname of the system is visible. This is correct, because dovecot -n | grep -i hostname returns: hostname = mail.bar.org But my customer asks me if it's possible that only his domain is visible in the header: So, if somebody sends a mail to "user(a)foo1.com", only the hostname "mail.foo1.com" should be visible in the mail header. And if somebody sends a mail to "user(a)foo2.com", only the hostname "mail.foo2.com" should be visible in the mail header. Is there a way to do this? Thank you in advance. Kind regards Thilo

2 3

Merry Christmas
by IT Security Inc. 18 Dec '15

18 Dec '15

Merry Christmas from IT Security Inc. 12/18/2015 Visit us online Merry Christmas to you and your family from Hugh Haggerty, myself and everyone else at IT Security,Inc. Albert Whale Hugh Haggerty IT Security Inc. Merry Christmas! IT Security, Inc. 519 Nichols Road Pittsburgh, PA 15237 | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=B710C911120204FA&emailID=689&sendID=307&triggerID= | in2contact.co/front/tracking.jsp?clientID=858&campaignID=188&userID=731&linkID=EB9D07803CDFE734&emailID=689&sendID=307&triggerID=

1 0

limiting autoexpunge to a service
by Burckhard Schmidt 18 Dec '15

18 Dec '15

Hello, like described at wiki "Mailbox settings": protocol imap { namespace inbox { mailbox Spam { autoexpunge = 10d } } } I tried to use autoexpunge inside lmtp: 20-lmtp.conf: protocol lmtp { mail_plugins = $mail_plugins sieve postmaster_address = ... info_log_path = /var/log/dovecot-lmtp.log sendmail_path = /opt/csw/sbin/sendmail namespace inbox { mailbox Junk { autoexpunge = 10d } } (line 23) } But I get an error during start of dovecot (same with service imap): doveconf: Fatal: Error in configuration file /usr/dovecot/etc/dovecot/conf.d/20-lmtp.conf line 23: Garbage after '{' /usr/dovecot/sbin/dovecot -n # 2.2.21 (): /usr/dovecot-2.2.21/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.10 Is it only a problem of doveconf? -- Regards --- Burckhard Schmidt Abteilung Systemsoftware und Kommunikation ZE Computer- und Medienservice der Humboldt-Universität zu Berlin Postanschrift: Unter den Linden 6, 10099 Berlin Standort: Rudower Chaussee 26; 12489 Berlin Tel.: +49-30-2093-70058 Fax: +49-30-2093-70199 Mail: bschmidt(a)cms.hu-berlin.de

1 0

Last chance to order the Dovecot book
by Peer Heinlein 18 Dec '15

18 Dec '15

Hi, as some people migth know I've written a book about Dovecot that has also been translated and published in English. Thanks for Timos great help and detailled background informations he provided to me. Unfortunately my book publisher has to shutdown his business at the end of 2015 -- right now. During the next few days you'll have the last chance to order the english version of the dovecot book at amazon, if you're interested in. Please don't wait too long. I think they'll stop offering the book before christmas and then it's gone. http://www.dovecot-book.com/online-shop/als-e-book-bestellen/ MAYBE we'll be able to re-publish it next year. Maybe. If not -- this will be the last chance to order it. Peer (The german version of the book will be still available at http://www.dovecot-buch.de) -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

Deleting Public Mailbox?
by Dag Nygren 17 Dec '15

17 Dec '15

Hi! What am I doing wrong here? Mission: Delete old empty sub mailboxes in our Public mailspace acl-file contents: MailingLists user=dag lrwstipekxa MailingLists/* user=dag lrwstipekxa Didn't work from my mail client so tried: Command tried: % doveadm mailbox delete -s MailingLists/Glibc -u dag doveadm(dag): Error: Can't delete mailbox MailingLists/Glibc: Permission denied % doveadm acl debug -u dag "MailingLists/Egcs" doveadm(dag): Info: Mailbox 'Egcs' is in namespace 'MailingLists/' doveadm(dag): Info: Mailbox path: /usr/local/var/mail/MailingLists/mailboxes/Egcs/dbox-Mails doveadm(dag): Info: All message flags are shared across users in mailbox doveadm(dag): Info: User dag has rights: lookup read write write-seen write-deleted insert post expunge create delete admin doveadm(dag): Error: Mailbox not found from dovecot-acl-list, rebuilding doveadm(dag): Info: Mailbox is in public namespace doveadm(dag): Info: Mailbox MailingLists/Egcs is visible in LIST Must be a config I have wrong. Would like to get rid of them... Best Dag

2 4

userdb username change ignored when using (My)SQL was: Re: userdb username changed
by Péter Márton 17 Dec '15

17 Dec '15

Hi! It works when using LDAP. I've duplicated the "username change" debug line, just to see that the variables are really updated: Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(ppp(a)example.net): username changed ppp(a)example.net -> uppp Apr 20 14:30:27 imap21 dovecot: auth-worker(27127): Debug: sql(uppp): username changed uppp -> uppp Apr 20 14:30:27 imap21 dovecot: auth: Debug: userdb out: USER#0111#011ppp@example.net#011home=/home/ppp#011uid=500#011gid=500#011quota_rule=*:storage=3100b:messages=1024 And the answer is of course yes. Just the userdb out string has the wrong value. The right value is lost somewhere. But where? Regards, Peter Log of the (for me unusable) LDAP query: Apr 20 14:28:07 imap21 dovecot: auth: Debug: master in: USER#0111#011m2500j6#011service=doveadm Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): user search: base=ou=Users,ou=Mail,dc=bnet,dc=at scope=subtree filter=(uid=m2500j6) fields=mailHost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): result: mailHost=localhost; mailHost unused Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(m2500j6): username changed m2500j6 -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): username changed localhost -> localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: ldap(localhost): result: mailHost=localhost Apr 20 14:28:07 imap21 dovecot: auth: Debug: userdb out: USER#0111#011localhost#011

2 4

doveadm-server does NOT know fts commands
by SATOH Fumiyasu 16 Dec '15

16 Dec '15

Hi, I'm using Dovecot 2.2.13 with Dovecot Director, Doveadm server and FTS. I want to run doveadm on Director hosts, but Dovecot server on backend hosts reject "fts *" commands. On Dovecot Director hosts: # doveadm fts optimize -u u0001(a)example.jp # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp # echo $? 75 doveadm index -u u0001(a)example.jp INBOX # echo $? 0 On Dovecot backend hosts: # grep doveadm /var/log/maillog Jul 14 10:25:40 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts optimize Jul 14 10:25:51 backend dovecot: doveadm: Error: doveadm: Client sent unknown command: fts rescan Is this doveadm-server restriction? On Dovecot backend hosts (2): # doveadm fts optimize -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm fts rescan -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server # echo $? 75 # doveadm index -u u0001(a)example.jp -S /var/run/dovecot/doveadm-server INBOX # echo $? 0 # doveadm fts optimize -u u0001(a)example.jp # echo $? 0 # doveadm fts rescan -u u0001(a)example.jp # echo $? 0 # doveadm index -u u0001(a)example.jp INBOX # echo $? 0 -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA

2 3

Assert failure in 2.2.20: imap-fetch.c:554 (ctx->client->output_cmd_lock || ctx->client->output_cmd_lock == cmd)
by Peter Eriksson 16 Dec '15

16 Dec '15

Just got another core-dump from Dovecot's imap process on our mail server. Dovecot 2.2.20 Solaris 10 / x86 Maildir Output from syslog: Dec 14 10:58:12 mail dovecot: [ID 583609 mail.crit] imap(oling): Panic: file imap-fetch.c: line 554: assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Dec 14 10:58:15 mail dovecot: [ID 583609 mail.crit] imap(oling): Fatal: master: service(imap): child 2167 killed with signal 6 (core dumped) Checked the users' Maildir for files modified around this time and found: -rw------- 1 oling root 15743 Dec 14 10:54 .Deleted Messages/cur/1450099463.M318113P13582.mail,S=15743,W=16026:2,RSbcd Don't know if it's related though. Data from the core-dump / debugger: # /pkg/studio/default/bin/dbx /ifm/pkg/dovecot/default/libexec/dovecot/imap imap.2167.306 ... program terminated by signal ABRT (Abort) 0xfffffd7ffeb81eca: __lwp_kill+0x000a: jae __lwp_kill+0x18 [ 0xfffffd7ffeb81ed8, .+0xe ] Current function is default_fatal_finish 201 abort(); (dbx) where [1] __lwp_kill(0x1, 0x6, 0xfffffe88d2948e40, 0xfffffd7ffeb827be, 0x4552555443, 0x0), at 0xfffffd7ffeb81eca [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb7a7d3 [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb26fe9 [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7ffeb05f60 =>[5] default_fatal_finish(type = LOG_TYPE_PANIC, status = 0), line 201 in "failures.c" [6] i_internal_fatal_handler(ctx = 0xfffffd7fffdff858, format = 0x492df0 "file %s: line %d: assertion failed: (%s)", args = 0xfffffd7fffdff840), line 670 in "failures.c" [7] i_panic(format = 0x492df0 "file %s: line %d: assertion failed: (%s)", ... = 0x467f4f, ...), line 275 in "failures.c" [8] imap_fetch_more(ctx = 0x736b00, cmd = 0x7369a8), line 554 in "imap-fetch.c" [9] cmd_fetch(cmd = 0x7369a8), line 297 in "cmd-fetch.c" [10] command_exec(cmd = 0x7369a8), line 172 in "imap-commands.c" [11] client_command_input(cmd = 0x7369a8), line 948 in "imap-client.c" [12] client_command_input(cmd = 0x7369a8), line 1008 in "imap-client.c" [13] client_handle_next_command(client = 0x4d16c0, remove_io_r = 0xfffffd7fffdffa7d), line 1022 in "imap-client.c" [14] client_handle_input(client = 0x4d16c0), line 1058 in "imap-client.c" [15] client_input(client = 0x4d16c0), line 1105 in "imap-client.c" [16] io_loop_call_io(io = 0x5bab00), line 559 in "ioloop.c" [17] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [18] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [19] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [20] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [21] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) print cmd cmd = 0x7369a8 (dbx) print ctx->client->output_cmd_lock ctx->client->output_cmd_lock = 0x72e0f8 (dbx) print *cmd *cmd = { prev = (nil) next = 0x72e0f8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x736ac0 "150.11" name = 0x736ac8 "UID FETCH" args = 0x736ad8 "12663:12665 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x437220 = &cmd_fetch(struct client_command_context *cmd) context = (nil) module_contexts = { arr = { buffer = 0x736a58 element_size = 8U } v = 0x736a58 v_modifiable = 0x736a58 } parser = 0x4d3d40 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 1450087092 tv_usec = 924042 } start_ioloop_wait_usecs = 119688401U running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 } (dbx) print *(ctx->client->output_cmd_lock) *ctx->client->output_cmd_lock = { prev = 0x7369a8 next = 0x72d8c8 client = 0x4d16c0 pool = 0x4d1eb0 tag = 0x72e208 "149.11" name = 0x72e210 "UID FETCH" args = 0x72e220 "12666 (BODY.PEEK[] BODYSTRUCTURE)" cmd_flags = COMMAND_FLAG_BREAKS_SEQS func = 0x4371b0 = &`imap`cmd-fetch.c`cmd_fetch_continue(struct client_command_context *cmd) context = 0x72e248 module_contexts = { arr = { buffer = 0x72e1a8 element_size = 8U } v = 0x72e1a8 v_modifiable = 0x72e1a8 } parser = 0x5bb410 state = CLIENT_COMMAND_STATE_WAIT_OUTPUT start_time = { tv_sec = 1450087092 tv_usec = 923420 } start_ioloop_wait_usecs = 119688382U running_usecs = 538U bytes_in = 33U bytes_out = 32994U sync = (nil) uid = 1U cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 1U tagline_sent = 0 } -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 2

LIST command should not interpret wildcards in reference
by Robert Siemer 16 Dec '15

16 Dec '15

Hello everyone, I believe this is erroneously implemented in Dovecot: >>> for i in c.list_folders('deleteme.*.folder', '%'): ... print(i) ... ((b'\\HasNoChildren',), b'.', 'deleteme.*.folder') ((b'\\HasNoChildren',), b'.', 'deleteme.deleteme.deleteme.folder') We see here an interactive python session, which launches LIST "deleteme.*.folder" "%" over the wire and receives two mailboxes as answer. The response is already parsed, but that’s not important for my point: according to RFC3501 section 6.3.8 LIST Command, the arguments are “reference name” and “mailbox name with possible wildcards”. Both arguments are allowed to contain wildcard characters, but they have no special meaning in the reference. Dovecot 2.2.18 doesn’t do that right: the second mailbox should not be listed, because it is not a subfolder of reference. Is this a known issue? Regards, Robert

2 2

And one more core-dump in imap:str.c str_append(cstr = NULL)
by Peter Eriksson 16 Dec '15

16 Dec '15

Dovecot 2.2.20 Solaris 10 / x86 Maildir q (dbx) where [1] strlen(0x0, 0x0, 0x491baa, 0x0, 0x4d1ed0, 0x4d1ed0), at 0xfffffd7ffeaf6dd0 =>[2] str_append(str = 0x4a9120, cstr = (nil)), line 96 in "str.c" [3] client_get_commands_status(client = 0x4d16c0), line 282 in "imap-client.c" [4] client_log_disconnect(client = 0x4d16c0, reason = 0xfffffd7ffee24d80 "Connection closed"), line 322 in "imap-client.c" [5] client_default_destroy(client = 0x4d16c0, reason = (nil)), line 336 in "imap-client.c" [6] client_destroy(client = 0x4d16c0, reason = (nil)), line 263 in "imap-client.c" [7] client_input(client = 0x4d16c0), line 1099 in "imap-client.c" [8] io_loop_call_io(io = 0x5073b0), line 559 in "ioloop.c" [9] io_loop_handler_run_internal(ioloop = 0x4b2580), line 211 in "ioloop-poll.c" [10] io_loop_handler_run(ioloop = 0x4b2580), line 607 in "ioloop.c" [11] io_loop_run(ioloop = 0x4b2580), line 583 in "ioloop.c" [12] master_service_run(service = 0x4b2450, callback = 0x482690 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" [13] main(argc = 1, argv = 0xfffffd7fffdffcb8), line 442 in "main.c" (dbx) frame 3 Current function is client_get_commands_status 282 str_append(str, cmd->name); (dbx) print *cmd *cmd = { prev = (nil) next = (nil) client = 0x4d16c0 pool = 0x4d1eb0 tag = (nil) name = (nil) args = (nil) cmd_flags = <unknown enum member 0> func = (nil) context = (nil) module_contexts = { arr = { buffer = 0x4d1f80 element_size = 8U } v = 0x4d1f80 v_modifiable = 0x4d1f80 } parser = 0x4b8f90 state = CLIENT_COMMAND_STATE_WAIT_INPUT start_time = { tv_sec = 0 tv_usec = 0 } start_ioloop_wait_usecs = 0 running_usecs = 0 bytes_in = 0 bytes_out = 0 sync = (nil) uid = 0 cancel = 0 param_error = 0 search_save_result = 0 search_save_result_used = 0 temp_executed = 0 tagline_sent = 0 executing = 0 } (dbx) list 280 str_append(str, " ("); 281 for (cmd = client->command_queue; cmd != NULL; cmd = cmd->next) { 282 str_append(str, cmd->name); 283 if (cmd->next != NULL) 284 str_append_c(str, ','); 285 running_usecs += cmd->running_usecs; 286 bytes_in += cmd->bytes_in; 287 bytes_out += cmd->bytes_out; 288 last_cmd = cmd; 289 } Probably related to these entries in the syslog: Dec 11 16:18:47 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9238, TLS, session=<CUwE16Am3fhR6X TA> Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=5683 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=168 out=4713 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=194 out=1016 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=182 out=970 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=193 out=895 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=196 out=995 Dec 11 16:18:50 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=184 out=894 Dec 11 16:18:51 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9273, TLS, session=<1uJB16AmtOhR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=81.233.116.192, lip=130.236.160.9, mpid=9278, TLS, session=<kR5Q16AmaOZR6X TA> Dec 11 16:18:52 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10796, TLS, session=<GvSJ5qAms9CC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap-login: Login: user=<perje>, method=PLAIN, rip=130.236.172.166, lip=130.236.160.9, mpid=10803, TLS, session=<nVqS5qAmttCC 7Kym> Dec 11 16:23:08 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:23:13 mail dovecot: [ID 583609 mail.info] imap(perje): Connection closed in=150 out=491 Dec 11 16:24:10 mail dovecot: [ID 583609 mail.crit] imap(perje): Fatal: master: service(imap): child 9006 killed with signal 11 (core dumped) (Would have been nice with a pid number in the syslog output :-) -- [Ll.U] Peter Eriksson KITVS-IFM & ITI-NET IT.LiU.SE +46-70 518 2786

2 1

Error: fcntl(write-lock) locking failed
by Marcin Janowski 16 Dec '15

16 Dec '15

Hello, one month ago I moved my smtp and imap server to other environment with /var/vmail on NFS. After this move i have warnings about too long "Locking transaction log", but today i have errors about "fcntl(write-lock) locking failed ". What this means? This is my dovecot config: # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2000) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1603) # OS: Linux 3.19.0-31-generic x86_64 Ubuntu 14.04.3 LTS nfs auth_mechanisms = plain login auth_worker_max_count = 300 default_process_limit = 400 mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = zlib managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = 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 = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/vmail/globalsieverc sieve_dir = ~/sieve } postmaster_address = postmaster(a)smtp.DOMAIN protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap { process_limit = 1024 } ssl_cert = </etc/ssl/private/DOMAIN.crt ssl_key = </etc/ssl/private/DOMAIN.key userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol lda { mail_plugins = zlib sieve } protocol imap { mail_max_userip_connections = 100 } And this is errors from few day: 2015-12-14 15:33:35 1450103615 Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 15:32:44 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:36:35 1450092995 Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:36:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 12:18:35 1450091915 Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail//Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 14 12:18:25 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-14 09:10:35 1450080635 Dec 14 09:10:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.cache: No locks available 2015-12-13 13:40:35 1450010435 Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 13:40:06 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-13 10:48:35 1450000115 Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: fcntl(write-lock) locking failed for file /var/vmail/.../Maildir/dovecot.index.log: No locks available Dec 13 10:48:19 smtp-atena dovecot: imap(...): Error: mail_index_wait_lock_fd() failed with file /var/vmail/.../Maildir/dovecot.index.log: No locks available 2015-12-12 08:36:35 1449905795 Dec 12 08:36:30 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 12 08:36:31 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 31 seconds 2015-12-12 08:35:35 1449905735 Dec 12 08:35:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-12 08:34:36 1449905676 Dec 12 08:34:27 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 11:48:36 1449830916 Dec 11 11:47:48 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:55:35 1449820535 Dec 11 08:55:03 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds Dec 11 08:55:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 120 seconds 2015-12-11 08:54:35 1449820475 Dec 11 08:54:33 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:53:35 1449820415 Dec 11 08:53:32 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds 2015-12-11 08:52:35 1449820355 Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds Dec 11 08:51:59 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 90 seconds 2015-12-11 08:51:35 1449820295 Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds Dec 11 08:51:29 smtp-atena dovecot: imap(...): Warning: Locking transaction log file /var/vmail/.../Maildir/dovecot.index.log took 60 seconds

2 1

Dovecot SASL and GSSAPI (IPA)
by Ranbir 15 Dec '15

15 Dec '15

Hi Everyone, I'm currently using dovecot SASL in postfix and passwd-file in dovecot for authenticating my users. I want to switch to using IPA instead. I have both the postfix (mailman01) and dovecot (mailman02) servers joined to the IPA domain. I have GSSAPI working in dovecot for IMAP. But, the SASL GSSAPI authentication in postfix fails with this error: warning: unknown[10.200.5.100]: SASL GSSAPI authentication failed: This is what dovecot logs: Dec 12 22:31:54 mailman02 dovecot: auth: Debug: auth client connected (pid=0) Dec 12 22:31:54 mailman02 dovecot: auth: Debug: client in: AUTH 1 GSSAPI service=smtp nologin lip=10.200.9.14 rip=10.200.5.100 secured resp=<hidden> Dec 12 22:31:54 mailman02 dovecot: auth: Debug: gssapi(?,10.200.5.100): Obtaining credentials for smtp(a)mailman02.theinside.rnr Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Unspecified GSS failure. Minor code may provide more information Dec 12 22:31:54 mailman02 dovecot: auth: gssapi(?,10.200.5.100): While processing incoming data: Wrong principal in request Dec 12 22:31:56 mailman02 dovecot: auth: Debug: client passdb out: FAIL 1 I've tried changing the "smtpd_sasl_local_domain" in postfix's main.cf file to "mailman02.theinside.rnr", but I get the same errors in dovecot and postfix. Right now the config in postfix looks like this: import_environment="KRB5_KTNAME=/etc/postfix/smtp.keytab" smtpd_sasl_local_domain = mailman01.theoutside.rnr Does what I'm trying to do make sense? If so, how do I fix it? Do I have to stop using dovecot sasl in postfix and switch to cyrus sasl? -- Ranbir

2 3

Ideas needed for archiving
by Ben 15 Dec '15

15 Dec '15

I've been asked by a user whether it's possible to stop their IMAP client downloading messages older than a given date. Whilst I'm guessing it may well be possible to do this client-side using folders and subscriptions, it got me thinking .... is there a way to do this server side on dovecot ? i.e. is there a way to "hide" messages from a user without having to archive them off into a seperate account ? thanks

2 2

Released Pigeonhole v0.4.10 for Dovecot v2.2.21
by Stephan Bosch 14 Dec '15

14 Dec '15

Hello Dovecot users, I got a bit stalled by our recent switch to Git, but here is the final v0.4.10 release of Pigeonhole for Dovecot v2.2.21. Nothing of consequence changed since the last RC. Changelog v0.4.10: + Implemented the Sieve mime and foreverypart extensions (RFC 5703). These are fully implemented. The interaction with the editheader extension needs some work, but this should not influence most uses; i.e., changes by the editheader extension are not always visible using foreverypart/mime. + Sieve body extension: Properly implemented the `:text' body transform. It now extracts text for HTML message parts. + Sieve enotify extension: mailto method: Implemented the sieve_notify_mailto_envelope_from setting. This allows configuring the source of the notification sender address for e-mail notifications. This is similar to what already can be configured for redirect. + Added a sieve_enabled (defaults to 'yes') setting that allows explicitly disabling Sieve processing for particular users. This used to be possible by setting `sieve=', but ever since the sieve_before, sieve_after and sieve_default settings were added, this method was not reliable anymore. - variables extension: Fixed handling of empty string by the `:length' set modifier. An empty string yielded an empty string rather than "0". - Fixed memory leak in the Sieve script byte code dumping facility. Extension contexts were never actually freed. - Fixed handling of implicit keep when the last Sieve script is a global one. In that case the implicit keep action was executed in global context, which could mean that trivial (quota) errors ended up in the system log file, rather than the user log file. - doveadm sieve plugin: Fixed crashes caused by incorrect context allocation in the sieve command implementations. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.10… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 2

v2.2.21 released
by Timo Sirainen 13 Dec '15

13 Dec '15

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig Due to a bit bad doveadm bugs in v2.2.20 here's a fixed v2.2.21. Also from this release forward we're finally using git with branches to make new releases. So new releases will have a bit more time to stabilize in the branch before they're being released (while still allowing new features to be developed in the master development branch). We already did something like this for the enterprise releases, but now it's done for community releases as well. - doveadm mailbox list (and some others) were broken in v2.2.20 - director: Fixed making backend changes when running with only a single director server. - virtual plugin: Fixed crash when trying to open nonexistent autocreated backend mailbox.

2 3

2.2.21: doveadm expunge is broken
by Alexander Moisseev 13 Dec '15

13 Dec '15

# doveadm expunge -u user(a)example.com MAILBOX Trash ALL Fatal: expunge: To avoid accidents, each branch in search query must contain something else besides MAILBOX (e.g. just add "all" if you want everything) -- Alexander

2 1

2.2.21: panic in stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user)
by Jakub Jankowski 13 Dec '15

13 Dec '15

Hi, I've just upgraded dovecot to 2.2.21 (from 2.2.18), and I'm getting a crash when doing dsync backup: $ dsync -v -u user(a)domain.com backup maildir:/backup/maildirs/domain.com/user/Maildir dsync(user(a)domain.com): Panic: file stats-plugin.c: line 324 (stats_user_deinit): assertion failed: (stats_global_user == user) dsync(user(a)domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x7e4b4) [0x7f543d3c74b4] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7e529) [0x7f543d3c7529] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f543d372300] -> /usr/lib64/dovecot/lib90_stats_plugin.so(+0x4116) [0x7f543c95a116] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_user_unref+0x35) [0x7f543d68efd5] -> /usr/bin/dsync [shasta(a)toxcorp.com done]() [0x420f90] -> /usr/bin/dsync [user(a)domain.com done](doveadm_mail_try_run+0x28c) [0x421edc] -> /usr/bin/dsync [user(a)domain.com done](main+0x2ff) [0x413a2f] -> /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f543cd80870] -> /usr/bin/dsync [user(a)domain.com done](_start+0x29) [0x413bb9] Aborted This gets logged to syslog when it happens: Dec 13 02:12:33 host dovecot: imap-login: Login: user=<user(a)domain.com>, method=PLAIN, rip=A.B.C.D, lip=A.B.C.D, mpid=1576, TLS Dec 13 02:13:09 host dovecot: stats: Error: Mail server input error: CONNECT: Duplicate session ID 4rqRBSXGbFbDBgAAOpfmEQ for user user(a)domain.com service doveadm It definitely wasn't happening on 2.2.18 (I skipped .19 and .20). Here's my configuration (with some things sanitized): $ dovecot -n # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 4.3.2 x86_64 Slackware 14.2 auth_cache_negative_ttl = 1 mins auth_cache_size = 4 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = sha1 default_vsz_limit = 512 M deliver_log_format = msgid=%m psize=%p vsize=%w: %$ first_valid_gid = 500 first_valid_uid = 500 hostname = host.domain.com last_valid_gid = 500 last_valid_uid = 500 listen = * login_greeting = IMAP server ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_location = mdbox:~/mdbox:ALT=/var/vmail/altmdbox/%Ld/%Ln/altmdbox mail_plugins = " stats" mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = scheme=CRYPT username_format=%Lu /etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_default = /var/vmail/_sieve/default.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes } pop3_client_workarounds = outlook-no-nuls postmaster_address = postmaster(a)domain.com protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } service imap { process_limit = 128 } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } unix_listener lmtp-vmail { group = vmail mode = 0660 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 32 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 64 } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/ssl/certs/cert.pem ssl_key = </etc/ssl/private/key.pem stats_command_min_time = 1 days stats_domain_min_time = 1 days stats_ip_min_time = 1 days stats_memory_limit = 32 M stats_session_min_time = 1 days stats_user_min_time = 1 days userdb { args = uid=vmail gid=vmail home=/var/vmail/mdbox/%Ld/%Ln driver = static } verbose_proctitle = yes protocol lda { mail_plugins = " stats sieve" } protocol imap { mail_max_userip_connections = 20 mail_plugins = " stats imap_stats" } protocol lmtp { mail_plugins = " stats sieve" } $ Let me know if there's anything else that I can provide to help narrowing it down. Cheers, shasta -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D

2 1

System-user-controllable custom passwords and mail locations
by Michal Petrucha 12 Dec '15

12 Dec '15

Hello everyone, I'd like to set up dovecot so that it uses the standard system accounts, but with different passwords specific to email. Seems like a fairly common setup, but the catch is, I want the users to be able to set their passwords themselves, without needing any assistance from a server administrator. I'm wondering what's the easiest way of implementing this. From what I've understood, this requirement would probably rule out a separate passwd-file (since the standard Linux passwd doesn't seem to support using a custom passwd file), SQL, flat-file dict, and Redis (since you can't give users access only to their row, or dict key; it's either the entire database (or flat file), or nothing). (Of course, I could work around that limitation by writing a C program that I would install as SUID root, which would only change the invoking user's password, but I'd prefer not to start dumping arbitrary SUID binaries all over the place.) So, that would probably only leave me with LDAP, checkpassword, and the FS dict backend. I can imagine how I could get LDAP to do this -- add some extra attribute for each user, and put together a simple script to change passwords, say, in Python, that would bind as the user and write the new password. However, this would require me to store the system user account database in LDAP, which is kind of overkill on at least one of the servers I want this setup on, where I know for certain that there won't ever be more than a handful of users. Checkpassword would probably work, too; perhaps by looking into some file in the user's $HOME or such. I'm not entirely certain about the security, or performance implications of that approach. With the FS dict backend, I could probably point it to a directory, in which every user would own a file containing their password, that no one else could write to. I haven't been able to find any more details about the structure of this directory hierarchy, though, or the contents of the individual files, so I don't know whether this is a viable approach, or not. My questions are, then: Is there some other way of implementing separate passwords that the users can set themselves that I'm overlooking? Is one of the three approaches described above a bad idea for some reason I don't see? Is there some kind of “standard solution” to this problem? The other thing I wanted to ask about is marginally related; I'd like to be able to allow users to customize the layout in which they store their mail. For instance, some users like to have their INBOX as an mbox in /var/mail, and other maildirs in ~/Maildirs/, others prefer having everything as a mix maildirs and mboxes in ~/mail, etc. Looking at the MailLocation wiki page, it seems like the only option, if I want to customize the location per user, is to set it in the userdb, but since we only have system users everywhere, it seems we have to use the passwd userdb, which doesn't support this kind of per-user customization (even on servers where PAM/NSS are configured to use LDAP). Again, am I overlooking something here? Is there nothing similar to ~/.imaprc, which is supported by certain versions of some other IMAP servers? Thanks in advance for any insights, Michal

1 0

Dovecot 1.2.15 and Convert Password Schemes
by Chuck Peters 11 Dec '15

11 Dec '15

Can I convert the password hashes with the older Dovecot? http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes shows how it can potentially be done with Dovecot 2.1, but when I try it with Dovecot 1.2.15, I'm not seeing a way to make it work. Any suggestions? This is an old Debian 6 system that's overdue for an upgrade. In the test environment upgrading OpenLDAP to Debian 8 I discovered most of our users passwords probably won't work. The hashes appear to be a old Unix DES based hash, ie base64 decoded ldif shows something like the following: userPassword:: {crypt}Aipcuzoh3eiVE Passwords stored in the SSHA hash seem to work fine. If given the password, a shell script could create the hashes with slappasswd and/or a SHA512 hash (using doveadm or mkpasswd) for use on Debian 8. # cat /usr/local/bin/dovecot-environment.sh #!/bin/sh set > /tmp/dovecot-environment exec /usr/lib/dovecot/imap "$@" I can show the /tmp/dovecot-environment if you like, but it's not showing the password as a variable... This system is using Debian's Dovecot package 1.2.15-7+deb6u1. Dovecot 2.1.7-7~bpo60+1 is available as a backport, but I would prefer not to upgrade Dovecot on the production system if I don't need to, or have some other reason such as some features for using IMAP for the migration. https://packages.debian.org/search?keywords=dovecot-common Thanks, Chuck # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686-bigmem i686 Debian 6.0.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/lfrr/ca/thishost.crt ssl_key_file: /etc/lfrr/ca/thishost.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 verbose_proctitle: yes mail_privileged_group: mail mail_location: mbox:%h:INBOX=/var/mail/%Lu mbox_write_locks: fcntl dotlock mail_executable(default): /usr/local/bin/dovecot-environment.sh mail_executable(imap): /usr/local/bin/dovecot-environment.sh mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes auth default: mechanisms: plain login debug_passwords: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: /etc/passwd userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: dirsize quota_rule: *:storage=204800 I should note, I think the default_pass_scheme = CRYPT doesn't do anything with auth_bind = yes. # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf hosts = 127.0.0.1 sasl_bind = no auth_bind = yes auth_bind_userdn = uid=%u,ou=People,dc=ccil,dc=org ldap_version = 3 base = ou=People,dc=ccil,dc=org pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT

1 0

autoexpunge creates special_use folder
by Tom Sommer 11 Dec '15

11 Dec '15

namespace inbox { mailbox Spam { special_use = \Spam auto = create autoexpunge = 30d } } This creates the "Spam" folder in the filesystem on login/logout, even though it shouldn't. If I remove autoexpunge, the folder is not created. -- Tom Sommer

2 1