- dovecot - dovecot.org

[Dovecot] 'unknown user' using dovecot LDA
by Charles Marcus 22 Dec '13

22 Dec '13

Ok, one more issue to resolve. The old server was still using the postfix/virtual for delivery, but the new one is using the dovecot LDA. Now, when an email generated locally by a cron job is delivered, this shows in the log: 2013-12-22T10:29:55-05:00 host postfix/pickup[31400]: C67FD90F676B2: uid=0 from=<newsrv+rkhunter(a)example.com> 2013-12-22T10:29:55-05:00 host postfix/cleanup[22349]: C67FD90F676B2: message-id=<20131222152955.C67FD90F676B2(a)smtp2.example.com> 2013-12-22T10:29:55-05:00 host postfix/qmgr[31401]: C67FD90F676B2: from=<newsrv+rkhunter(a)example.com>, size=1555, nrcpt=1 (queue active) 2013-12-22T10:29:55-05:00 host dovecot: auth-worker(22365): passwd(user1(a)example.com): unknown user 2013-12-22T10:29:55-05:00 host dovecot: lda(user1(a)example.com): msgid=<20131222152955.C67FD90F676B2(a)smtp2.example.com>: saved mail to INBOX 2013-12-22T10:29:55-05:00 host postfix/pipe[22361]: C67FD90F676B2: to=<user1+rkhunter-report(a)example.com>, relay=dovecot, delay=0.06, delays=0.02/0/0/0.04, dsn=2.0.0, status=sent (delivered via dovecot service) 2013-12-22T10:29:55-05:00 host postfix/qmgr[31401]: C67FD90F676B2: removed The mail was delivered (as the log also clearly shows), but what is with the 'unknown user'? I'm not sure how I can test my maps with dovecot, but testing with postfix shows: # postmap -q user1(a)example.com mysql:/etc/postfix/maps/mysql/vmm.cf example.com/user1/ Which is correct. And my dovecot-sql-conf.ext contains: driver = mysql connect = "host=localhost dbname=db_name user=dbuser password=password" default_pass_scheme = CRYPT password_query = \ SELECT username AS user, password \ FROM mailbox WHERE username = '%u' user_query = \ SELECT CONCAT('/var/vmail/', maildir) AS home \ FROM mailbox WHERE username = '%u' iterate_query = SELECT username AS user FROM mailbox I confirmed the db info is identical to what postfix is using. Oh - and in order to make sure that all usernames are lowercased, shouldn't I change '%u' above to '%Lu'? Appreciate any suggestions on where to go next... thanks -- Best regards, */Charles/*

3 4

[Dovecot] New server missing auth-worker entries in logs
by Charles Marcus 22 Dec '13

22 Dec '13

Hi all, Ok, I'm making progress on my new server, but there is an entry in the logs on the old/current server that is not showing p on the new one... lines like: dovecot: auth-worker(20284): mysql(localhost): Connected to database my_auth_db I've looked everywhere, compared settings, etc, and can't seem to find why I get this line on the old server and odn't on the new one. Anyone have a clue stick? Thanks

2 2

[Dovecot] File descriptor leak in sieve-extprograms
by Kirill A. Shutemov 21 Dec '13

21 Dec '13

I've tried to use sieve-filter for my inbox (~6000 messages). It failed after some work with this backtrace: sieve-filter(kas): Error: socketpair() failed: Too many open files sieve-filter(kas): Panic: file script-client-local.c: line 155 (script_client_local_disconnect): assertion failed: (pid >= 0) sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71) [0x7f020e717a71] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f020e717ada] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f020e6d32ee] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x4baf) [0x7f020dae0baf] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x58ca) [0x7f020dae18ca] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_fail+0x2f) [0x7f020dae199f] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_run+0xc4) [0x7f020dae1fd4] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x6134) [0x7f020dae2134] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x3ac) [0x7f020ecd1adc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x4a) [0x7f020ece05aa] -> /usr/bin/sieve-filter(main+0x6a9) [0x403b49] -> /usr/lib/libc.so.6(__libc_start_ma in+0xf5) [0x7f020e327bc5] -> /usr/bin/sieve-filter() [0x404111] The reason is file descriptor leak in "script client local". script_client_local_close_output() shutdowns write side of descriptor and sets sclient->fd_out to -1, but never closes the descriptor. I've tried to fix this by the patch below. Tests works fine, but sieve-filter crashed in other way: sieve-filter(kas): Panic: epoll_ctl(del, 13) failed: Bad file descriptor sieve-filter(kas): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66a71) [0x7f0ed406fa71] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0ed406fada] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0ed402b2ee] -> /usr/lib/dovecot/libdovecot.so.0(+0x776f5) [0x7f0ed40806f5] -> /usr/lib/dovecot/libdovecot.so.0(+0x8009a) [0x7f0ed408909a] -> /usr/lib/dovecot/libdovecot.so.0(io_stream_unref+0x25) [0x7f0ed40764c5] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_unref+0x26) [0x7f0ed4088136] -> /usr/lib/dovecot/libdovecot.so.0(+0x80e48) [0x7f0ed4089e48] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x27) [0x7f0ed407fa47] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7f0ed40807d7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ed407f5e8] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(script_client_run+0x9c) [0x7f0ed343af8c] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x6114) [0x 7f0ed343b114] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x3ac) [0x7f0ed4629adc] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x4a) [0x7f0ed46385aa] -> /usr/bin/sieve-filter(main+0x6a9) [0x403b49] -> /usr/lib/libc.so.6(__libc_start_main+0xf5) [0x7f0ed3c7fbc5] -> /usr/bin/sieve-filter() [0x404111] I failed to unfold this in a reasonable time. Any ideas? diff --git a/src/plugins/sieve-extprograms/script-client-local.c b/src/plugins/sieve-extprograms/script-client-local.c index 56d32f707c09..f54ef82132cf 100644 --- a/src/plugins/sieve-extprograms/script-client-local.c +++ b/src/plugins/sieve-extprograms/script-client-local.c @@ -139,7 +139,6 @@ static int script_client_local_close_output(struct script_client *sclient) i_error("shutdown(%s, SHUT_WR) failed: %m", sclient->path); return -1; } - sclient->fd_out = -1; return 1; } diff --git a/src/plugins/sieve-extprograms/script-client.c b/src/plugins/sieve-extprograms/script-client.c index 06a5d5d54ba9..6fefca4c9f26 100644 --- a/src/plugins/sieve-extprograms/script-client.c +++ b/src/plugins/sieve-extprograms/script-client.c @@ -68,7 +68,8 @@ static void script_client_disconnect if (sclient->fd_in != -1 && close(sclient->fd_in) < 0) i_error("close(%s) failed: %m", sclient->path); - if (sclient->fd_out != -1 && sclient->fd_out != sclient->fd_out) + if (sclient->fd_out != -1 && sclient->fd_out != sclient->fd_in + && close(sclient->fd_out) < 0) i_error("close(%s/out) failed: %m", sclient->path); sclient->fd_in = sclient->fd_out = -1; -- Kirill A. Shutemov

3 6

[Dovecot] Errors in log file
by Christian Rößner 21 Dec '13

21 Dec '13

Hi, just wonder about some errors I found with: doveadm log errors: … Dec 16 17:21:55 imap(roessner@****): Error: stat(/srv/mail/virtual/*****/roessner/.dovecot.sieve/tmp) failed: Not a directory … And this is correct, it is a link: .dovecot.sieve -> sieve/default.sieve I do not see, where I have an error in my config ;) root@mx ~ # doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.11.2-hardened x86_64 Gentoo Base System release 2.2 ext4 auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes default_vsz_limit = 512 M disable_plaintext_auth = no imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_access_groups = mail mail_attachment_dir = /srv/mail/copymail/attachments mail_gid = mail mail_location = maildir:/srv/mail/virtual/%d/%n mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape mail_privileged_group = mail 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 ihave namespace { list = children location = maildir:%%h prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk-E-Mail { auto = subscribe special_use = \Junk } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/sbin/ispcp-decrypt.py driver = checkpassword } plugin { acl = vfile acl_shared_dict = file:/srv/mail/virtual/shared-mailboxes.db fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. quota = dict:User quota::file:/srv/mail/virtual/%d/%n/dovecot-quota quota_grace = 10%% quota_rule = *:storage=2G:messages=20000 quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)deltaweb.de protocols = imap pop3 lmtp sieve service auth-worker { extra_groups = ssl-cert unix_listener auth-worker { mode = 0600 user = vmail } user = vmail } service auth { extra_groups = ssl-cert unix_listener /var/spool/postfix.relay/private/auth { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0660 user = vmail } user = vmail } service config { unix_listener config { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = ::1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_cert = </etc/ssl/certs/mx_deltaweb_de.crt ssl_key = </etc/ssl/private/mx_deltaweb_de.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape sieve } protocol lda { mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota acl fts fts_lucene zlib mail_log notify listescape imap_quota imap_acl imap_zlib } Any ideas? Thanks in advance :) Kind regards -Christian Rößner -- [*] 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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

3 5

[Dovecot] Ignoring mount points for secondary dovecot instance does not seem to work
by Jouko Nikula 21 Dec '13

21 Dec '13

Hello, I tried to ignore all mountpoints in Dovecot. I have two dovecot instances running: root@fileserver# doveadm instance list path name last used running /usr/local/var/run/dovecot dovecot 2013-12-21 08:09:34 yes /var/run/dovecot.smtp smtp-auth 2013-12-21 08:09:34 yes I give commands: root@fileserver# doveadm mount add '/*' ignore root@fileserver# doveadm -i smtp-auth mount add '/*' ignore And then restart dovecot. In the log I can see that the main instance is now ignoring my mountpoints, but the smtp-auth instance is still warning about my mountpoints. Is this a bug or am I missing something? My configurations are as follows: root@fileserver# doveconf -ni smtp-auth # 2.2.9: /usr/local/etc/dovecot/dovecot.conf.smtp # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 auth_mechanisms = plain login base_dir = /var/run/dovecot.smtp/ first_valid_uid = 123 instance_name = smtp-auth log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = mail mail_location = maildir:~/mail mail_uid = vmail passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = dovecot driver = pam } protocols = service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/imapd.pem ssl_key = </etc/ssl/private/imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } root@fileserver# doveconf -n # 2.2.9: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 auth_mechanisms = plain login first_valid_uid = 123 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = mail mail_location = maildir:~/mail mail_uid = vmail passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = session=yes dovecot driver = pam } protocols = imap service auth-worker { user = vmail } ssl_cert = </etc/ssl/certs/imapd.pem ssl_key = </etc/ssl/private/imapd.pem userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } regards, - Jouko

1 0

[Dovecot] Thank you!
by Steve Litt 20 Dec '13

20 Dec '13

Hi all, I've been on this list for 18 months but almost completely as a lurker. You know why? Because Dovecot never, ever, ever screws up on me or displays unexpected behavior, so I never have technical questions. Thank you for producing such a rock solid piece of software! SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance

1 0

Re: [Dovecot] configure lmtp to deliver to email addresses case insensitively
by Adrian Zaugg 20 Dec '13

20 Dec '13

Hi David > I believe RFC822 email addresses are case-insensitive, and (in some RFC 2821, Page 13, 1st paragraph: "The local-part of a mailbox MUST BE treated as case sensitive. Therefore, SMTP implementations MUST take care to preserve the case of mailbox local-parts. Mailbox domains are not case sensitive. In particular, for some hosts the user "smith" is different from the user "Smith". However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged." (http://tools.ietf.org/html/rfc2821#section-2.4) > cases, especially ones where there's just a mail server) it's entirely > possible that people remember their account names with some capital > letters that aren't in user db. (System knows you as > "mrsmithy(a)mail.domain", while the user may remember the account as > "MrSmithy(a)mail.domain" or "MrsMithy(a)mail.domain"...). Also, people with I just want login names to be case sensitive but not email addresses, and in spite of being treated as case insensitive email addresses should retain their case, just like defined and suggested in the RFC. This reduces support calls because it's con-formant and we have a clear policy: Usernames are always lower case, non-email addresses, the same simple and short name for all our services. There is nothing easier than this. We use this since 17 years and it works without confusion. If a user now spots that suddendly any capitalization of usernames is working when logging in to the webmail, how can I explain that this doesn't work with other services like FTP? > smartphones may not notice that the phone "helpfully" uppercased the > first letter of a lowercase user name. Forcing case reduces support > calls, which is always a good thing. That's why email addresses should be allowed containing capitalizations. On smartphone people tend to use MUAs and there the username is saved and not entered each and every time, so for the username this is less true, I think. Back to dovecot: Using LDA as a transport for the dovecot store, it used to work perfectly (with dovecot 1.x). It's just LMTP that spits, because it looks up the local part in the userdb, which is PAM in our case. I won't change PAM to act case insensitive: I'm not in the position to change a common sense in the computing world as it always was. It's enough Microsoft did that and probably just because of that we're having this discussion here... However, it's maybe best to lowercase the local part in the exim lmtp-transport and leave dovecot's LMTP in peace. Best regards, Adrian.

3 8

[Dovecot] Does quota-status respect quota_grace?
by Jiri Bourek 20 Dec '13

20 Dec '13

Hello, I have Dovecot 2.2.9 from Debian repository running on AMD64, ext4 filesystem for mail storage. Each mailbox has its own system user, quotas are enforced by file system. Quota settings in configuration are as follows (from doveconf -n): quota = fs:Domain quota:group:inode_per_mail quota2 = fs:Mailbox quota:user:inode_per_mail quota2_grace = 18%% quota_grace = 18%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO Quota rules are read from PostgreSQL (snippet) user_query = ... '*:bytes=' || domains.quota_size || 'M:messages=' || domains.quota_files as quota_rule, \ '*:bytes=' || mailboxes.quota_size || 'M:messages=' || mailboxes.quota_files as quota2_rule, \ ... As far as I can tell, quota enforcing in dovecot-lda works correctly. User is allowed one message which brings him over quota (provided the message fits into filesystem quota hard limit and quota_grace value), every other message after that is rejected. However policy service quota-status for Postfix seems to ignore the quota_grace value. When a message arrives which would make user go over quota (but which would not make him exceed the grace limit value), Postfix checks the policy service and is told to reject the message. I checked and dovecot itself is fine with the message - if I try to send it with the policy service check disabled, Postfix accepts it and so does dovecot-lda, the message is delivered into mailbox. My question is - is that intended behavior or bug in the quota-status? Appending some lines from debug log - as far as I can see there's not much in it though: dovecot: quota-status: Debug: Added userdb setting: mail=maildir:/home/mailboxes/t/e/test.info/test/:LAYOUT=fs:INDEX=/var/lib/dovecot-data/index/1010:CONTROL=/var/lib/dovecot-data/control/1010 dovecot: quota-status: Debug: Added userdb setting: plugin/quota2_rule=*:bytes=11M:messages=110 dovecot: quota-status: Debug: Added userdb setting: plugin/quota_rule=*:bytes=15M:messages=150 dovecot: quota-status(test(a)test.info): Debug: Effective uid=1010, gid=1007, home=/home/mailboxes/t/e/test.info/test/ dovecot: quota-status(test(a)test.info): Debug: Quota root: name=Domain quota backend=fs args=group:inode_per_mail dovecot: quota-status(test(a)test.info): Debug: Quota rule: root=Domain quota mailbox=* bytes=15728640 messages=150 dovecot: quota-status(test(a)test.info): Debug: Quota grace: root=Domain quota bytes=2831155 (18%) dovecot: quota-status(test(a)test.info): Debug: Quota root: name=Mailbox quota backend=fs args=user:inode_per_mail dovecot: quota-status(test(a)test.info): Debug: Quota rule: root=Mailbox quota mailbox=* bytes=11534336 messages=110 dovecot: quota-status(test(a)test.info): Debug: Quota grace: root=Mailbox quota bytes=2076180 (18%) dovecot: quota-status(test(a)test.info): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/home/mailboxes/t/e/test.info/test/:LAYOUT=fs:INDEX=/var/lib/dovecot-data/index/1010:CONTROL=/var/lib/dovecot-data/control/1010 dovecot: quota-status(test(a)test.info): Debug: fs: root=/home/mailboxes/t/e/test.info/test, index=/var/lib/dovecot-data/index/1010, indexpvt=, control=/var/lib/dovecot-data/control/1010, inbox=/home/mailboxes/t/e/test.info/test, alt= dovecot: quota-status(test(a)test.info): Debug: fs quota add mailbox dir = /home/mailboxes/t/e/test.info/test dovecot: quota-status(test(a)test.info): Debug: fs quota block device = /dev/sdc1 dovecot: quota-status(test(a)test.info): Debug: fs quota mount point = /home dovecot: quota-status(test(a)test.info): Debug: fs quota mount type = ext4

3 5

[Dovecot] mirror to download dovecot
by Edwardo Garcia 20 Dec '13

20 Dec '13

Halo, Is mirror to get 2.2.9? cannot get dovecot.org, this time out 4 xe-0-1-0-1-3664.r00.saplbr01.br.bb.gin.ntt.net (200.15.0.45) 6.946 ms 7.093 ms 6.899 ms 5 xe-4-1-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.3.217) 118.130 ms 118.111 ms 118.117 ms 6 ae-1.r05.miamfl02.us.bb.gin.ntt.net (129.250.2.185) 118.592 ms 118.735 ms 118.628 ms 7 * * * 8 * * * 9 * * * I use to get from dovecot.ausics.org but fail connect too, seem has DNS 127.0.0.1 ????? is any others run mirror?

3 3

[Dovecot] reproducible dsync backup panic (dovecot 2.2.7)
by Peter Benko 20 Dec '13

20 Dec '13

Hi all, I'm receiving a reproducible dsync backup panic for some of my users. The error message is as follows: dsync-remote(user@<removed>): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite) dsync-remote(user@<removed>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69b70) [0x7f922dad9b70] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f922dad9c4a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f922da94725] -> /usr/bin/dsync(dsync_brain_mailbox_tree_sync_change+0x382) [0x42f912] -> /usr/bin/dsync(dsync_brain_recv_mailbox_tree_deletes+0x10b) [0x42f4db] -> /usr/bin/dsync(dsync_brain_run+0x305) [0x42c6f5] -> /usr/bin/dsync() [0x42cbe8] -> /usr/bin/dsync() [0x43e040] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f922daea066] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xd7) [0x7f922daeaf07] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f922dae9b78] -> /usr/bin/dsync() [0x4297f9] -> /usr/bin/dsync() [0x4133cd] -> /usr/bin/dsync(doveadm_mail_try_run+0x251) [0x414091] -> /usr/bin/dsync(main+0x3c8) [0x412f78] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f922d704ead] -> /usr/bin/dsync() [0x413191] dsync-local(user@<removed>): Error: read(<remote-mail-server>) failed: EOF dsync-local(user@<removed>): Error: Remote command returned error 134 The command I'm using to back up individual user's mail is something like: sudo -u vmail dsync -v -u user(a)server.com -R backup ssh -i sshid-file login(a)server.com sudo -u vmail dsync -v -u user(a)server.com I use the above command at the backup server. The error started to appear a few weeks after we started using the new mail system. First it appeared for a single user, now it appears for some more users as well. It is deterministic and reproducible. Any ideas? I included the relevant part of my config below. Best regards, Peter ------------------------------------------------------------------- # 2.2.7 (5c876ed0c3e0): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.2 auth_master_user_separator = * auth_mechanisms = plain login hostname = <removed> listen = * login_greeting = $hostname IMAP server mail_attachment_dir = /mail/mailboxes/%d/_attachments_ mail_attachment_fs = sis-queue $mail_attachment_dir/queue:posix mail_attachment_min_size = 16 k mail_location = mdbox:~ mail_plugins = " zlib acl" mdbox_rotate_interval = 5 days mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = mdbox:/mail/mailboxes/%%d/%%n:INDEX=/mail/mailboxes/%%d/%%n prefix = Accounts/%%n/ separator = / subscriptions = no type = shared } passdb { args = /mail/config/dovecot/passwd driver = passwd-file } passdb { args = /mail/config/dovecot/passwd-master driver = passwd-file master = yes pass = yes } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/mail/mailboxes/%d/shared-mailboxes.db zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster@<removed> protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } syslog_facility = local6 userdb { args = uid=vmail gid=vmail master_user=%u home=/mail/mailboxes/%d/%n driver = static } protocol imap { mail_plugins = " zlib acl imap_acl" }

2 1