- dovecot - dovecot.org

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

> For a given computational effort, you get the most bang-for-the-buck by > choosing large parameters (and checking very carefully that they are > "safe") rather than smaller parameters (and/or checking them less > carefully) which you then regenerate. This discussion (on the OpenSSH mailing list) http://marc.info/?t=143221614200001 may be helpful to those thinking about this.

1 0

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

>But when you write NOT to regenerate, are you saying that using larger primes makes regenerating unnecessary, or are you telling us that it's somehow harmful? For a given computational effort, you get the most bang-for-the-buck by choosing large parameters (and checking very carefully that they are "safe") rather than smaller parameters (and/or checking them less carefully) which you then regenerate. Every time you regenerate, there's a small (but finite) probability that the new parameters are actually unsafe. You'd do better using those CPU cycles to improve the proof that your original set of parameters was safe (admittedly, no one actually does this), rather than generating a new set. Remember, the DH parameters (p,g) are NOT secret; they are transmitted in the clear everytime. As long as you're using Ephemeral Diffie-Hellman (choosing new exponents, a and b, for each session) with large safe DH parameters, it's hard to think of a threat model where you improve the security AT ALL by regenerating the DH parameters.

1 0

Re: FREAK/Logjam, and SSL protocols to use
by Jacques Distler 27 May '15

27 May '15

>It is not at this point emphasized anywhere, including on weakdh.org, that it is actually of high importance to regenerate your DH parameters frequently. That's not really correct. If you're using a prime of length at least 2048 bits, then the corresponding discrete-log problem is well-beyond the pre-computation ability of the NSA (or anyone else). It is computationally intensive to generate such large primes, p (and corresponding base parameter, g). You need to ensure that p is actually prime (the costly step [1]) and that g is primitive. Which is why most implementations have used shorter (<= 1024 bit) primes. Using shorter primes, and regenerating DH parameters at regular intervals, is only a linear-time improvement. By contrast, generating longer DH parameters (without bothering to regenerate) is an EXPONENTIAL improvement in security. So the best setting is to set ssl_dh_parameters_length as large as feasible ([2] recommends 2048 bits), and NOT to regenerate. [1] http://en.wikipedia.org/wiki/Miller%E2%80%93Rabin_primality_test [2] https://weakdh.org/sysadmin.html

2 1

FREAK/Logjam, and SSL protocols to use
by Ron Leach 27 May '15

27 May '15

List, good afternoon, I was reading up on a TLS Diffie Hellman protocol weakness described here https://weakdh.org/sysadmin.html which is similar to the earlier FREAK attack, and can result in downgrade of cipher suites. Part of the solution workaround that the researchers describe for Dovecot here https://weakdh.org/sysadmin.html includes altering DH parameters length to 2048, and re-specifying the allowable cipher suites - they give their suggestion. But the researchers make no comment on the allowable protocols that, in Dovecot, are controlled in 10-ssl.conf in the stanza headed # SSL protocols to use #ssl_protocols = !SSLv2 I couldn't find any advice on up-to-date SSL/TLS protocol settings in the Dovecot wiki, either (I looked in http://wiki2.dovecot.org/SSL/DovecotConfiguration ). At the moment our installation is using only the default settings for allowed protocols; I'm not sure what those defaults might be, but our 10-ssl.conf may only be disallowing SSLv2, if the 'example' entry is the default. We're running 2.2.15, and are due to upgrade to 2.2.18 shortly; quite possibly the defaults differ in a more recent release. What SSL protocols do folk on the list recommend should be allowed in Dovecot these days? (Actually, I mean which protocols really 'must' be disallowed?) regards, Ron

5 10

/etc/ssl/certs/dovecot.pem erased by OpenSuse's update mechanism
by Wolfgang Gross 27 May '15

27 May '15

Hi, this is not a genuine Dovecot bug, more a nuisance. It applies to OpenSuse 13.2 but maybe also to other Linux's. The standard installation of Dovecot (especially 10-ssl.conf) places the certificate dovecot.pem in /etc/ssl/certs. Sometimes during updates does OpenSuse renew all certificates in /etc/ssl/certs and erases dovecot.pem. This blocks further access to the mailbox. I found a similar report here: https://bbs.archlinux.de/viewtopic.php?id=27288 Workaround: Move dovecot.pem to another directory and change 10-ssl.conf accordingly. Regards Wolfgang Gross -- Dr. W. Gross Sektion Chirurgische Forschung Klinik für Allgemein-, Viszeral- und Transplantationschirurgie Universitätsklinikum Heidelberg Im Neuenheimer Feld 365, D-69120 Heidelberg, Germany Tel. ++49 (0)6221/566392, Fax: ++49 (0)6221/566402 WGross(a)uni-hd.de

3 3

Can email be shared between POP3 and shell account access?
by Steve Matzura 26 May '15

26 May '15

I needed to receive a message to admin(a)mydomain.com. I waited and waited for it, but it never showed up in the admin mailbox on the mydomain.com machine. So I looked for the admin account in /etc/dovecot.passwd, and there it was, plain-text password and all! I set up a retrieval system for the admin POP3 account and got all the messages I was waiting for, not to mention about 20 that I wasn't, which were obviously old and discardable. This got me to thinking, is it possible to have an account accessible not just via POP3 from the ouside, but through mail/mailx on the inside, and if so, how is that set up?

3 3

sieve: extract first chars of body in sieve script
by Ingo Thierack 26 May '15

26 May '15

Hello, is it possible to extract the first x chars of the body of an message to forward it, or the complete body inside an sieve script. I want to forward specific mails via telegram-messenger. No Problem to extract the "from" and the "subject". if header :matches "Subject" "*" { set "subject" "${1}"; } if header :matches "from" "*" { set "from" "${1}"; } pipe :copy :try "notify.sh" [ "(${from})# ${subject}" ]; But is it also possible for the body? If I can only pass the complete body, I can cut out the first x chars inside the notify-script. Can't find any hint for that. Regards Ingo

2 1

Segfault on "doveadm sync -u <an-specific-user> tcp:<other-node-ip>:port"
by Listas＠Adminlinux 26 May '15

26 May '15

Hi! When I run "doveadm sync -u <an-specific-user> tcp:192.168.0.2:12345", I get this error: http://pastebin.com/NxyyNGJk Only to one specific user... I've tried to repair with "doveadm force-resync", unsuccessfully. Is this known? Ubuntu14.04 + Dovecot-2.2.15. My doveconf -n: http://pastebin.com/25sURwJL Thanks! -- Thiago Henrique

1 0

Typo in systemd commit HG 8dc79a437858
by Thomas Leuxner 25 May '15

25 May '15

The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity

3 4

timeout for POP3 query.
by Christian Eichert 25 May '15

25 May '15

Is there a way to timeout POP3 query if they come to often? More precise I want to know if there is a setting in dovecot that makes it ignore pop3 requests from a certain user if they come more often then a certain amount of time. I am looking for a setting in dovecot, not a firewall solution. I would like dovecot to answer something like "requests come to often, please come back later." regards christian

2 1

Couldn't set transaction log view (seq 9..13)
by micah anderson 25 May '15

25 May '15

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir(a)internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error: /srv/maildirbackups/m/micah/daily.1/mailboxes/INBOX/dbox-Mails/dovecot.index: Couldn't set transaction log view (seq 9..13) dsync-remote(micah): Error: Failed to read transaction log for mailbox INBOX Re-running the dsync never fixes the issue. I'm happy to provide any additional information if so required to help track down this problem! micah

3 2

Controlling IP addresses for services
by Alex 24 May '15

24 May '15

Hi, I'm using dovecot-2.2.15 on fedora21 and would like to configure pop3s and imaps to only listen on localhost and internal addresses. It seems the listen= parameter only supports ports, not IP addresses. Is it possible to control which IPs the services listen on? I'm also interested in knowing the differences between pop3-login and just the pop3 service? Same with imap-login and imap? I've searched the wiki and still a bit confused. Thanks, Alex

5 5

Problem with sieve not triggering randomly?
by Chris Adams 23 May '15

23 May '15

I'm running CentOS 7.1 with Dovecot 2.2.10 (CentOS packaged version). I have Postfix feeding messages to Dovecot for local delivery via LMTP, and I have Amavisd for spam filtering. For messages above a certain threshold, Amavisd adds the "X-Spam-Flag: YES" header, and I file that into the Spam folder using a default (system-wide) sieve script (there aren't any per-user sieve scripts set up): require "fileinto"; if header :contains "X-Spam-Flag" "YES" { fileinto "Spam"; } I can see it work on my test messages and from lmtp log entries. However, it doesn't seem to always work. I had a user complain about a spam increase, and I looked in their mailbox. I see a message with the "X-Spam-Flag: YES" header, but it is in the INBOX (and the corresponding lmtp log entry shows that's where it went). Why would the sieve script work on some messages and not others? I don't see any errors in the log. I see a bunch of messages from the same source to different users, and they were all filed into INBOX, not Spam. Looking at the message in question, it is a pretty bogus message. There are multiple From: and Subject: headers. Would that cause sieve to "punt" on the message (but not log anything about it)? -- Chris Adams <cma(a)cmadams.net>

3 11

Dovecot-Director, (Manage)-Sieve und Remote-IP
by Benjamin Hück 23 May '15

23 May '15

Hello, I`ve got a question about Dovecot-Director and (Manage)-Sieve: is there any possibility to pass-through the original IP-address to the backend server? In this case I try to pass-through the IP-address of a webmail server. I`ve looked for a solution in different forums and tried it with the parameter "login_trusted_networks", however no success. The above solution is working with IMAP/POP3/LMTP, but not with Sieve. For any solutions or any hint I would be grateful. Best regards Benjamin Hück -- ________________________________ ________________________________ KEVAG Telekom GmbH Cusanusstr. 7 D-56073 Koblenz Fon: +49 261 20162-0 Fax: +49 261 20162-25100 http://www.kevag-telekom.de/ Geschäftsführer: Bernd Gowitzke, Gerd Thewalt Sitz der Gesellschaft: Koblenz, Amtsgericht Koblenz, HRB Nr. 5343 USt.IdNr. DE 18 77 67 843 St-Nr. 22/650/0182/7

2 2

Re: charset_to_utf8 assertion of remaining src_size
by Cassidy Larson 23 May '15

23 May '15

We're using FreeBSD 10.1 Thanks On Thu, May 21, 2015 at 4:56 PM, Xin Li <delphij(a)delphij.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 05/21/15 15:47, Cassidy Larson wrote: > > I've been seeing this same error as well now: > > > > Fatal: master: service(indexer-worker): child 20979 killed with > > signal 6 (core not dumped - set service indexer-worker { > > drop_priv_before_exec=yes }) Panic: file charset-iconv.c: line 132 > > (charset_to_utf8): assertion failed: (*src_size - pos <= > > CHARSET_MAX_PENDING_BUF_SIZE) > > Quick question -- Are you using FreeBSD (10.0+)? > > Cheers, > - -- > Xin LI <delphij(a)delphij.net> https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.1.4 (FreeBSD) > > iQIcBAEBCgAGBQJVXmKfAAoJEJW2GBstM+nspmoP/0CKS0g8ka/4uPF+jaq7+DD6 > 1PxCufdz/p528rclbXvEK3XE++sULihNVtO24TgXMOIJZB6jCfbfo+O17N9ZS7g9 > Vaz0r0URU28joAeDX/NR1yzYpHdo277RhXiPlKuyep+fEgi6Szm/mNaR+aCtYrge > 8Qm2U2eaHFQk/2qpyvC4ZlFzXSVIR+AIMSh87YqJSWSVd3PjNDLxZLDeUaQyygG5 > 1lW3lsy0yDOTISI58rXavOi7qa4qKo0ySDOMLct3GrdXzL5S8N/Pc3RnRTP5p9dY > 22cGoH3XloijWAef93qHSuPFuC9Yiko4g/FZAtfuQg6mCETvhPDfhXBgRf3IFYAr > vuMOyBX+3TrQQI+zz3aolou10WH+E+PPbJFFZcNq4sRGQYtSXBA4RmDDKU4NgwoB > gIzS43GjPidJTxdzEC+eedmS6Rt5wvyFaDK1h5+x/mgnfEie6E9Hfk8IBqRHZMUW > HixCmBnC3p1GN+R8rbPxjuycP06bB7YXLJ28o06gM2agrGv5vu83j+WqO2g6wJIP > hRKnyCVVPUeAnkLpS+7nXZwW5R/j8M5y7V8rbiYCX4q+zWCJZl/ac1G12zwva5k1 > MwyjciDP951soMM2RYsQQSE5RxRKMC03kqGt+qnBx3jBR7afzhOmcO9gcKQJEY5R > qjwnZ0voZtV7u2Ptcv1Q > =hWt9 > -----END PGP SIGNATURE----- >

3 2

RE: v2.2.18 released
by dovecot＠outputservices.com 22 May '15

22 May '15

On 05/22/15 12:24, James wrote: > On 22/05/2015 16:27, dovecot(a)outputservices.com wrote: >> I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment. >> >> Went from 2.2.15 to 2.2.17, then to 2.2.18 >> >> Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not. >> >> ----------------------------------- >> May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap >> May 15 09:27:37 ssl-params: Info: Generating SSL parameters >> May 15 09:27:37 ssl-params: Fatal: Couldn't load required plugin /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: dlopen() failed: ld.so.1: ssl-params: fatal: relocation error: file /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: symbol SSL_clear_options: referenced symbol not found > > > I suspect you have compiled with one SSL library and are running with another. > > Hints: > > 1. Check RPATH in libs: > $ dump -Lv /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so > > 2. unset LD_LIBRARY_PATH > > 3. Check which ssl libs are being used: > $ ldd /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so Yep, that is it. It found some old ssl libraries. I will go back and look at the compile command better. > > 4. and symbol check: > $ ldd -r /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so > > > > I assume your use of /tmp is temporary. Set prefix to, eg, /opt/tocevod. > > > > James. Thanks

1 0

RE: v2.2.18 released
by dovecot＠outputservices.com 22 May '15

22 May '15

I am just starting out and trying to get dovecot and postfix working in Solaris 10 environment. Went from 2.2.15 to 2.2.17, then to 2.2.18 Both version 2.2.17 & 2.2.18 gave this same error. 2.2.15 does not. ----------------------------------- May 15 09:27:37 master: Info: Dovecot v2.2.18 starting up for imap May 15 09:27:37 ssl-params: Info: Generating SSL parameters May 15 09:27:37 ssl-params: Fatal: Couldn't load required plugin /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: dlopen() failed: ld.so.1: ssl-params: fatal: relocation error: file /tmp/tocevod/lib/dovecot/libssl_iostream_openssl.so: symbol SSL_clear_options: referenced symbol not found May 15 09:27:37 ssl-params: Error: child process failed with status 22784 May 15 09:27:46 master: Warning: Killed with signal 15 (by pid=1848 uid=0 code=kill) ------------------------------------------------ doveconf -n # 2.2.18: /tmp/tocevod/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc log_path = /tmp/tocevod/log/log login_trusted_networks = 137.106.0.0/16 mail_location = mbox:~/posta:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = </dovecot/certs/dovecot.pem ssl_key = </dovecot/certs/dovecot.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap }

2 1

Couldn't create lock .dovecot-sync.lock
by listas＠adminlinux.com.br 22 May '15

22 May '15

Hi, In a cluster with two servers and replication via dovecot-dsync, this error is logged: server1 dovecot: dsync-server(<user>): Error: Couldn't create lock /var/lib/imap/user/6a/<user>/.dovecot-sync.lock: No such file or directory This is because "/var/lib/imap/user/6a/<user>/" doesn't exist in server1. In another cluster node, the directory exists and everything seems to work fine. In my view, this indicates that the first sync is failing. In the first user access Dovecot creates home_dir for him. But the sync is not happening at this time to create the home_dir on the other node. My confs with doveconf -n: http://www.adminlinux.com.br/newcluster_doveconf.txt Thanks in advance! -- Thiago Henrique

2 2

Problems To Get Dovecot Running On FreeBSD: auth process crashes
by Christian Felsing 22 May '15

22 May '15

Hello, I ran into problems to get Dovecot running on FreeBSD. Steps for reproduction. Start Docot with dovecot -F (same result if started by rc script) telnet 192.168.116.38 110 Trying 192.168.116.38... Connected to freebsd. Escape character is '^]'. -ERR Disconnected: Auth process broken Connection closed by foreign host. logfile shows following: May 22 11:41:24 freebsd dovecot: master: Dovecot v2.2.18 starting up for imap, pop3, lmtp, sieve May 22 11:41:27 freebsd dovecot: auth: Error: auth: environment corrupt; missing value for DOVECOT_ May 22 11:41:27 freebsd dovecot: auth: Fatal: unsetenv(RESTRICT_SETUID) failed: Bad address May 22 11:41:27 freebsd dovecot: master: Error: service(auth): command startup failed, throttling for 2 secs May 22 11:41:27 freebsd dovecot: pop3-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 1 secs): user=<>, rip=192.168.116.1, lip=192.168.116.38, session=<cBLNdqgWWADAqHQB> May 22 11:41:32 freebsd dovecot: master: Warning: Killed with signal 2 (by pid=0 uid=0 code=kernel) Error message is quite meaningless regarding reason for crash. I am running same config on a Linux (Debian 8) host w/o problems. Is it a problem specific to FreeBSD? Christian ---cut here--- [root@freebsd /usr/local/etc/dovecot]# doveconf -n # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: FreeBSD 10.1-RELEASE-p10 amd64 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_ssl_username_from_cert = yes auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" auth_username_translation = "@#" auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 124 hostname = mail.taunusstein.net last_valid_uid = 124 lda_mailbox_autocreate = yes listen = 192.168.116.38 log_timestamp = %Y-%m-%d %H:%M:%S login_greeting = mail.taunusstein.net imap4/pop3 ready. mail_gid = 124 mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = 124 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 imapflags notify namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { driver = pam } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes autocreate = Trash autocreate2 = Drafts autosubscribe = Trash autosubscribe2 = Drafts fts = solr fts_solr = break-imap-search url=http://solr.lan:8983/solr/ quota = maildir:User quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } postmaster_address = postmaster(a)taunusstein.net protocols = imap pop3 lmtp sieve sendmail_path = /usr/lib/sendmail service anvil { client_limit = 4000 } service auth-worker { group = vmail } service auth { client_limit = 8000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 1024 } service imap-postlogin { executable = script-login /opt/dovecot-cf/bin/lastlogin.py } service imap { executable = imap imap-postlogin } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 1024 } service pop3-postlogin { executable = script-login /opt/dovecot-cf/bin/lastlogin.py } service pop3 { executable = pop3 pop3-postlogin } service quota-warning { user = vmail } ssl_cert = </usr/local/etc/dovecot/ssl/taunusstein.net.pem ssl_cipher_list = kEECDH:kEDH:AESGCM:ALL:+3DES:!RC4:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl_dh_parameters_length = 4096 ssl_key = </usr/local/etc/dovecot/ssl/taunusstein.net.key ssl_parameters_regenerate = 1 hours ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 TLSv1 TLSv1.1 TLSv1.2 ssl_require_crl = no userdb { args = /usr/local/etc/dovecot/dovecot-samba4.conf driver = ldap } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = " sieve acl" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = quota imap_quota acl imap_acl fts fts_solr } protocol lmtp { mail_plugins = quota sieve } protocol sieve { managesieve_logout_format = bytes ( in=%i : out=%o ) } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } ---cut here---

2 1

race condition? -> Error: dict quota: Quota update failed, it's now desynced
by Steffen Kaiser 22 May '15

22 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get this error now and then, but only for users, that share or use shared mailboxes. See this snippet: 2015-05-22 02:27:09 IMAP(<uid1>) [28776]: Info: Disconnected: Logged out in=21450 out=76933 2015-05-22 02:27:09 IMAP(<uid1>) [28774]: Info: Disconnected: Logged out in=3769 out=16379 2015-05-22 02:27:09 IMAP(<uid1>) [28770]: Info: Disconnected: Logged out in=641 out=394985 2015-05-22 02:27:09 IMAP(<uid1>) [28614]: Info: Disconnected: Logged out in=510 out=2178 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Info: expunge: box=users.<OTHER-UID>.INBOX, uid=8711, msgid=<008801d093ef$f46c00d0$dd440270$(a)example.com>, size=17433, vsize=17849, from=[cut] 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28830]: Info: Disconnected: Logged out in=555 out=2763 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Info: Disconnected: Logged out in=628 out=2851717 2015-05-22 02:27:09 IMAP(<uid1>) [28768]: Error: dict quota: Quota update failed, it's now desynced 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28827]: Info: Disconnected: Logged out in=267 out=1256 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28824]: Info: Disconnected: Logged out in=175 out=1073 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28831]: Info: Connection closed in=550 out=3197 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28663]: Info: expunge: box=INBOX, uid=8711, msgid=<008801d093ef$f46c00d0$dd440270$(a)example.com>, size=17433, vsize=17849, from=[cut] 2015-05-22 02:27:09 IMAP(<OTHER-UID>) [28663]: Info: Disconnected: Logged out in=800 out=25925 OTHER-UID shares the INBOX to uid1. Now, the _same_ message is about to delete once via the "sharing" uid and once from the consumer at the same time. My quota backend is Postgres, via quota = pgsql:/usr/local/dovecot-2.2.15/etc/dovecot/dovecot-dict-sql.conf.ext on Dovecot v2.2 hg 18272:466596200825 . I tried to replicate the error, by setting up two accounts, A shares INBOX to B, setup A and B in the same Thunderbird, configured that both A and B expunge the INBOX on termination of MUA, but I cannot reproduce that the same message is deleted twice in parallel. I also tried current hg's tip 8737:8906101589f9, but I cannot reproduce the error, no matter what I try. Also, I think, that in this very case the quota is OK still, because it had been updated for the sharing user OTHER-UID. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVV7xKHz1H7kL/d9rAQIlWAf+M0KHX2IjJufhamNlnlWJRhbGO+qmwnlh A6644yzn8vEtx3zHvOfvULAEZyWPsHlmMnu2YNKa3JrUYXte2zl1M7AzLR0Wsl9k xcBGxsbeRhqkDOrDoNRXMAZaTzWdqHDvXDGBujsh7+whjDh+Uv9uD0/LYxuRo+lb r54QF9qgSv4NLB4DlWhPMcwWjBWmTRu5kJGpU05jwlCgroZxkvB59FXaccMQXe5r ay9YWhBLz1qVVRg7ZsnY6ogwmlM/MyreI0o8A6iPfgDmrOcHjYbQ7jLGb7771vHJ SUjyC5NsU/A9HWr3jI2gmi2kSMIvPKOxHtUKpschLqBprbUkj0tNyg== =0bWX -----END PGP SIGNATURE-----

1 0

sieve permission problem with dovecot.svbin
by Cliff Hayes 22 May '15

22 May '15

Hello list, I am starting to see these in maillog: dovecot: lmtp(31949, dwright): Error: kXK3KnTpXFXNfAAAU+Cu/Q: sieve: binary open: failed to open: open(/var/spool/mail/dwright/.dovecot.svbin) failed: Permission denied (euid=520(dwright) egid=12(mail) missing +r perm: /var/spool/mail/dwright/.dovecot.svbin, euid is not dir owner) But the directory /var/spool/mail/dwright is owned by dwright:mail with permission set to 700. How do I fix? Here is my config: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 Scientific Linux release 6.5 (Carbon) auth_failure_delay = 5 secs auth_username_format = %Ln auth_verbose_passwords = plain mail_access_groups = mail mail_location = maildir:~/Maildir mail_plugins = " quota" 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 mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M sieve = ~/.dovecot.sieve sieve_after = /dovecotSieveAfter/ sieve_dir = ~/sieve } protocols = imap lmtp sieve service managesieve-login { inet_listener sieve { port = 4190 } } ssl_ca = </etc/pki/dovecot/certs/intermediate20150202.crt ssl_cert = </etc/pki/dovecot/certs/avalon20150202.crt ssl_key = </etc/pki/dovecot/private/avalon20150129.key ssl_verify_client_cert = yes userdb { args = /etc/dovecot/passwd driver = passwd-file } protocol lmtp { log_path = /var/log/dovecot-lmtp.log mail_plugins = " quota sieve" } protocol lda { log_path = /var/log/dovecot-lda.log mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" }

2 1

dovecot 2.2.18 and ssl_parameters_regenerate
by django＠nausch.org 22 May '15

22 May '15

HI Timo, On http://wiki2.dovecot.org/SSL/DovecotConfiguration I read in chapter SSL security settings: When Dovecot starts up for the first time, it generates new 512bit and 1024bit Diffie Hellman parameters and saves them into <prefix>/var/lib/dovecot/ssl-parameters.dat. After the initial creation they're by default regenerated every week. With newer computers the generation shouldn't take more than a few seconds, but with older computers it can take as long as half an hour. The extra security gained by the regeneration is quite small, so with slower computers, for Dovecot versions prior to v2.2, you might want to disable it If I discover the default-value of ssl_parameters_regenerate I receive: # doveconf -d ssl_parameters_regenerate ssl_parameters_regenerate = 0 In your doku you wrote, that dovecot will regenerate every week. :/ ? I set it to "1 hours" and watch if /var/lib/dovecot/ssl-parameters.dat is build every hour, but nothing happens. ssl-parameters.dat is only rebuild, if I change ssl_dh_parameters_length What's the problem? What I've made false? ttyl Django -- http://dokuwiki.nausch.org http://wetterstation-pliening.info http://ebersberger-liedersammlung.de

1 0

charset_to_utf8 assertion of remaining src_size
by Xin Li 22 May '15

22 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, I have seen the following assertion fails on my own mail server (indexer-worker): Panic: file charset-iconv.c: line 132 (charset_to_utf8): assertion failed: (*src_size - pos <= CHARSET_MAX_PENDING_BUF_SIZE) However, when charset_to_utf8_try returns FALSE (e.g. iconv() got EINVAL or EILSEQ), the for loop in charset_to_utf8 may end earlier, and there may be additional pending characters, and the assertion doesn't seem always hold in the error case, perhaps we should assert that pos is non-zero in the error case? Cheers, - -- Xin LI <delphij(a)delphij.net> https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.2 (FreeBSD) iQIcBAEBCgAGBQJVVjO/AAoJEJW2GBstM+nsbKUP/29fYdZArCiUSStK0hCtRvC3 o4L35zq4iP4WUry7VqNtdMg2Uiythei9l0JokNOJAy2ZDktJ3ns9CArXHi/pJE7/ V8374Iu9ygb4tzDvcNY/353SFkN+Sw4pJzSGJTelVT8nHxahQMtN7E0u26l54zNx p1H8rgt2nVA8eRvKL9MrhudN3eSI2+Jq4HX+dR4/Tu4qLkSU1nqi8sopQxNXzW4C 4XG4haSbTtXLu0H1MGa8y5pmwrFmZEluNOBm2SOww+UqeteD/MwE/pgA7g+cQx8l /t3FWzSe4C9HROV1VGW5V5HDM7cDvNJZ+nxQGI6L6qInkCBqQx/muIb9nIe7dhro tiHIuX4h8X2zaga+iD+B9fkf4QpDUc11WYE+0DUArb2cNTTAgeTXQ68+g0Q+UC8s OxUVDA4KwOSzkpEifDgvVCdgPG7U87SGe9NlMGjSZvAIEPsww16A3f2IaM4fhFa2 lVuTh1wq8phdWXLbCbZ0F36hAyxVbbwC5Xyj4Ygy3QL4RiBC7CJJ8I4f1lRLnoFz 1Wg0/M7psXBLVN7vx2MKtK5Rj1OvMOKmL4VpkhKcnp2z/Y9I5Qq2CP4C5uOv3DLJ JjoCsnVDpWJKQo6EPleb9OxVJF+NmjHd63zimXbuUyDJ7AJCsx/0m9mJZ5QYf+jU U3OqESCU5e5q++QLd2Kl =ksoA -----END PGP SIGNATURE-----

3 4

"doveadm backup" doesn't work anymore after upgrading to 2.2.18
by Jesus Cea 21 May '15

21 May '15

Until today I could do this to backup my primary IMAP4 server: """ doveadm backup ssh csi doveadm dsync-server """ It doesn't work anymore after upgrading to Dovecot 2.2.18: """ jcea@ubuntu:~$ doveadm backup ssh csi doveadm dsync-server Enter passphrase for key '/home/jcea/.ssh/id_rsa': dsync-remote(root): Error: Mailbox INBOX: Failed to get attribute vendor/vendor.dovecot/pvt/server/sieve/default: Mailbox attributes not enabled dsync-local(jcea): Error: Remote command returned error 65: ssh csi doveadm dsync-server dsync-server """ The first error is regular business: I don't have SIEVE in the backup, since it is a backup. I have seen this error forever, no consequences. Now in 2.2.18 I get the second error and the backup is aborted. It doesn't work anymore. I don't find any reference to error 65 anywhere. -- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz

2 2

Log mail access
by Philipp Brüll 20 May '15

20 May '15

Hello, is it somehow possible to log the access to a mail? The log entry should be written, if a user fetches a mail via imap or pop3. It would be convenient for debugging. I've checked the Logging-Wiki and the docs for the mail_log plugin, but they seem to log any event but "mail access". Best regards, Philipp

1 0