- dovecot - dovecot.org

Re: Updated my Dovecot certificate for the first time
by Joseph Tam 24 Nov '16

24 Nov '16

On Thu, 24 Nov 2016, Steve Litt wrote >> add the public part of the cert into your system's trusted CA store. > > Silly question, but how would you do that? You didn't say which OS you're running on (alpine runs on Windows as well), but I'll assume *nix. A previous poster showed you how to do it with a real certificate, and the steps are the same. However, the way I found out without too much fuss was to process trace my alpine process and see where it tied to load a cert $ strace -o trace.out alpine ... quit after connection $ grep -F cert traceout /1: open64("/etc/openssl/cert.pem", O_RDONLY) Err#2 ENOENT /1: stat("/etc/openssl/certs/cbf06781.0", 0xFFBF8E54) Err#2 ENOENT ... Your output will be different of course. The first load is the default pre-loaded root CAs (Thawte, etc.) supplied by OpenSSL, and the second, etc. are chained certificate lookups. You would replace the missing cert with your own self-signed public pem file. e.g. cp mypub.pem /etc/openssl/certs/cbf06781.0 For Windows, I don't know where it fetches it from. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: Updated my Dovecot certificate for the first time
by Joseph Tam 24 Nov '16

24 Nov '16

> Alpine still gives me a bad cert warning, saying I should either fix it > or disable checking. I haven't yet found a way to get Alpine to > discriminate between a valid self-signed cert and a bad one. Well, it can't discriminate since any certificate (except those in your trusted store) that asserts its own validity is suspect. You can either get alpine to not complain e.g. inbox-path={192.168.100.2:143/user=whatever/tls/novalidate-cert} or add the public part of the cert into your system's trusted CA store. Joseph Tam <jtam.home(a)gmail.com>

2 1

antispam plugin not working correctly
by Felix Zielcke 23 Nov '16

23 Nov '16

Hi, I've configured the antispam plugin like in the wiki to use the sa- learn-pipe.sh shell script. But it's not creating the log file in /tmp. Even if I add a "touch /tmp/x" in sa-learn-pipe.sh it's not created. So how I can check if it works correctly? dovecot version 2.2.26.0 /var/log/debug although contains: Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: mail copy: src spam: 1, dst spam: 0, src unsure: 0 Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program /usr/bin/sa-learn-pipe.sh Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program /usr/bin/sa-learn-pipe.sh Nov 23 18:36:49 daedalus imap [fzielcke(a)z-51.de 80.187.96.201 UID MOVE]: antispam: running mailtrain backend program parameter 1 --ham # doveconf -n |grep antispam antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/bin/sa-learn-pipe.sh antispam_pipe_program_notspam_arg = --ham antispam_pipe_program_spam_arg = --spam antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern_ignorecase = trash;Deleted * antispam_verbose_debug = 1 mail_plugins = acl zlib quota imap_zlib imap_acl imap_quota antispam

1 0

Active sieve script symbolic link doesn't update when changed.
by Steven Mainor 23 Nov '16

23 Nov '16

While setting up sieve on my email server I mistakenly setup a symlink (~/sieve/myfilter.svbin > ~/.dovecot.sieve) but I think that that should have been (~/sieve/myfilter.sieve > ~/.dovecot.sieve). I have fixed the mistake but dovecot/sieve still throws an error saying that the symlink still links to the wrong file. I have made sure the symlink is fixed (it links to ~/sieve/myfilter.sieve) and I tried restarting dovecot and the server but nothing works. I still get the error and my sieve filters aren't processed. Any help would be greatly appreciated. ~# grep sieve /var/log/syslog | nano temp.save Nov 23 01:32:09 1 dovecot: lda(steve(a)degga.net): Warning: sieve: file storage: Active Sieve script symlink /var/mail/vmail/degga.net/steve/.dovecot.sieve is broken: Invalid scriptname (points to myfilter.svbin). vmail@1:/var/mail/vmail/degga.net/steve/mail$ ls -l -a #redacted irrelevant stuff lrwxrwxrwx 1 vmail vmail 14 Nov 23 02:43 .dovecot.sieve -> myfilter.sieve vmail@1:/var/mail/vmail$ dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-47-generic x86_64 Ubuntu 16.04.1 LTS ext4 auth_mechanisms = plain login auth_verbose = yes mail_home =/var/mail/vmail/%d/%n mail_location = maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs 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 extracttext 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 = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_after = /var/mail/vmail/sieve-after sieve_before = /var/mail/vmail/sieve-before sieve_dir = ~/sieve } protocols = imap sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } # SSL information redacted here. userdb { args = uid=vmail gid=vmail home=/var/mail/vmail/%d/%n driver = static } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address =postmaster(a)degga.net quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n% r } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 }

2 2

Exim still accepting emails to nonexistent users
by Marti Markov 23 Nov '16

23 Nov '16

After adding the configuration bit: deny message = invalid recipient domains = +local_domains !verify = recipient/callout=no_cache from: http://wiki2.dovecot.org/LMTP/Exim <http://wiki2.dovecot.org/LMTP/Exim> running update-exim4.conf and service exim4 restart the server is still accepting emails to recipients that do not exist in dovecot. Any ideas?

3 6

Single user to have lrw to all mailboxes
by Marti Markov 23 Nov '16

23 Nov '16

I have implemented a global acl: * owner lrwstipkae INBOX.Spam owner lrwstipeka .Trash owner lrwsti INBOX.Trash owner lrw * user=master-user(a)mydomain.com lrs * owner lrwstipkae But the master-user then loses all other permissions on his own mailbox, he is left only with: lrs Any pointers on how to fix this?

1 0

Good email client to use with Dovecot?
by Steve Litt 22 Nov '16

22 Nov '16

Hi all, When I use an email client, its purpose is as a window into my Dovecot IMAP, and as a mechanism to reply to and send emails. I don't do filtering or calendaring on my email client (filtering via procmail direct to Dovecot). What email clients are all of you using to look at your IMAP email? Thanks, SteveT Steve Litt November 2016 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz

20 40

LDAP auth problems "unknown user"
by Nikolai Lusan 22 Nov '16

22 Nov '16

Hi, I am setting up a dovecot instance to host a bunch of virtual domains, with ldap backing for auth. I am using a single hostname for test purposes, with a couple of entries in the diectory. If I use auth binds I get a result, but this does not suit the end purpose of the server. If I use ldapsearch with the same base, search filter, and credentials as the ldap auth config I get the correct attributes returned, and I have bit of perl that verifies the password hash matches the password provided. I am running out of ideas here, I had thought of putting in a custom bit of perl and using the checkpassword method, but this is sub optimal. If anyone can help with this I'd be grateful. # dovecot --version 2.2.26.0 (23d1de6) # dovecot -n # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.8.0-1-amd64 x86_64 Debian stretch/sid ext3 auth_cache_size = 2 M auth_debug = yes auth_debug_passwords = yes auth_default_realm = maliuta.org auth_master_user_separator = * auth_mechanisms = plain login auth_realms = maliuta.org auth_verbose = yes auth_verbose_passwords = yes first_valid_uid = 117 last_valid_uid = 117 lda_mailbox_autocreate = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_gid = vmail mail_location = maildir:/var/spool/vmail/%d/%n/Maildir 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 extracttext 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 = } passdb { args = /etc/dovecot/ldap/maliuta.org-ldap.conf.ext driver = ldap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = $default_internal_user } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = # grep -v '^ *$#.*$\?$' /etc/dovecot/ldap/maliuta.org-ldap.conf.ext uris = ldap://localhost dn = cn=admin,dc=maliuta,dc=org dnpass = <secret> tls = yes tls_ca_cert_dir = /etc/ssl/certs auth_bind = no ldap_version = 3 base = ou=mail,dc=mailuta,dc=org scope = subtree default_pass_scheme = SSHA deref = never user_attrs = postfixDeliveryAddress=user user_filter = (&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)) pass_attrs = postfixDeliveryAddress=user,userPassword=password pass_filter = (&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixD eliveryAddress=%u)) iterate_attrs = uid=user iterate_filter = (objectClass=postfixMailPerson) # ldapsearch -H ldap://localhost:389 -x -D 'cn=admin,dc=maliuta,dc=org' -W -b "ou=mail,dc=maliuta,dc=org" -s sub -LLL -ZZ '(&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixDeliveryAddress=nikolai(a)test.maliuta.org))' uid userPassword Enter LDAP Password: dn: mail=nikolai(a)test.maliuta.org,ou=mail,dc=maliuta,dc=org uid: nikolai userPassword:: e1NTSEF9QVBZMTlaeGw1cWd0a25XeGxURXdqM2g5Yk5YL3BxOGY= ## From /var/log/mail.log Nov 20 07:24:20 kiliya dovecot: auth: Debug: auth client connected (pid=27086) Nov 20 07:24:20 kiliya dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=1kW2C65BFI2WZbl8#011lip=<local_ip>#011rip=<remote_ip>#011lport=143#011rport=36116#011local_name=<hostname>#011resp=AG5pa29sYWlAdGVzdC5tYWxpdXRhLm9yZwBmb29iYXIzMzQ0 (previous base64 data may contain sensitive data) Nov 20 07:24:20 kiliya dovecot: auth: Debug: ldap(nikolai(a)test.maliuta.org,<remote_ip>,<1kW2C65BFI2WZbl8>): cache miss Nov 20 07:24:20 kiliya dovecot: auth: Debug: ldap(nikolai(a)test.maliuta.org,<remote_ip,<1kW2C65BFI2WZbl8>): pass search: base=ou=mail,dc=mailuta,dc=org scope=subtree filter=(&(postfixDeliveryEnabled=TRUE)(objectClass=postfixMailPerson)(postfixDeliveryAddress=nikolai(a)test.maliuta.org)) fields=postfixDeliveryAddress,userPassword Nov 20 07:24:20 kiliya dovecot: auth: ldap(nikolai(a)test.maliuta.org,<remote_ip>,<1kW2C65BFI2WZbl8>): unknown user (given password: <correct_password>) Nov 20 07:24:22 kiliya dovecot: auth: Debug: client passdb out: FAIL#0111#011user=nikolai(a)test.maliuta.org -- Nikolai Lusan <nikolai(a)lusan.id.au>

2 2

Maildir migration from Dovecot to Dovecot
by Marco Hofmann (XenAdmin) 22 Nov '16

22 Nov '16

Hello everbody, I'm a proud user of Dovecot 2.2.9 on Ubuntu 14.04 LTS. I currently migrate all my Linux services to a new Debian 8 Jessie Server. On this server I installed and configured Dovecot 2.2.24. Now I search a way to migrate the two IMAP users I have on this server preserving all timestamps, folders and flags. Yes, only two ;-) I read the following two articles: http://wiki2.dovecot.org/Tools/Doveadm/Sync http://wiki2.dovecot.org/Migration/Dsync But I must say, that either these articles are not so good, or I act quite dumb. I understand that I have to use "doveadm backup" against my old server to make a one sync with all properties of each mail. What I miss are proper examples and that there are so many options, I could set. But what confuses me most is the the configuration file in (http://wiki2.dovecot.org/Migration/Dsync) which I don't know how to reference? Am I using the wrong guides, are the article someway misleading or is there anything else I'm overlooking? Thank you so much! -- Marco Hofmann https://www.meinekleinefarm.net/ Twitter: @ZomboBrain

2 1

nologin + reason -> logging reason
by Arkadiusz Miśkiewicz 22 Nov '16

22 Nov '16

Hi. I'm using nologin with own reason [1]. That works fine. For example pop3 client gets nice message like "-ERR [AUTH] Account is locked. Please contact support." Unfortunately maillog lacks information details about why user was not allowed to log in. pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<testuser>, method=LOGIN, rip=1.1.1.1, lip=2.2.2.2, session=<yIsRftBBmsrB7y2h> Is it possible to log "reason" there, too? (whether it is default/internal dovecot reason or my custom one). reason is the only thing in maillog that allows to distinguish why user was not allowed to log in. 1. http://wiki2.dovecot.org/PasswordDatabase/ExtraFields -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 5

Clients creating folders in root when using shared namespace
by Jon Cutting 21 Nov '16

21 Nov '16

We have set up dovecot to use a shared namespace, and it works well. However, when a client attempts to create a folder in the namespace, although dovecot responds with permission denied, it still goes on to create a folder, but in the root of our virtual mailbox folder (more confusingly, even issuing a LIST command for a non-existent subfolder creates the folder in the root). I've checked through the documentation for a misconfiguration but so far to no avail. Our steps to reproduce are as follows: * Create shared namespace (in our case we've used prefix Users/%%u/) * Share folder from one user to another so that the shared folder displays in LIST * Create a folder as a subfolder of the shared folder (i.e. . CREATE Users/testfolder) Expected behaviour: permission is denied and no folder is created Actual behaviour: permission is denied, but folder is created at the root of our vmail store (in the above example a folder /mnt/storage/vmail/testfolder would be created) Thanks, Jon Output from doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ext4 mail_location = maildir:/mnt/storage/vmail/%d/%n/Maildir mail_plugins = " quota zlib acl" 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 Users { list = children location = maildir:/mnt/storage/vmail/%%d/%%n/Maildir:INDEX=/mnt/storage/vmail/%d/%n/sharedindex/%%d/%%n/ prefix = Users/%%u/ separator = / subscriptions = no 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 = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/mnt/storage/vmail/%d/shared-mailboxes.db quota = maildir:User quota quota_rule = *:storage=50GB sieve = /mnt/storage/vmail/%d/%n/.dovecot.sieve sieve_before = /mnt/storage/vmail/dovecot.sieve sieve_dir = /mnt/storage/vmail/%d/%n/sieve zlib_save = gz zlib_save_level = 6 } protocols = imap lmtp sieve service imap-login { inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener lmtp { address = 0.0.0.0 port = 2003 } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } ssl = required ssl_ca = </etc/dovecot/dovecotca.pem ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/mnt/storage/vmail/%d/%n allow_all_users=yes driver = static } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " quota zlib acl imap_quota" } protocol lmtp { mail_plugins = " quota zlib acl sieve" }

1 0

[PATCH] Manually cleanup OpenSSL from dovecot_openssl_common_global_unref()
by Apollon Oikonomopoulos 21 Nov '16

21 Nov '16

OpenSSL 1.1 features a cleanup function that is automatically run on shutdown using atexit(3). This function frees all OpenSSL-allocated resources. In dovecot, OpenSSL is loaded indirectly using dlopen(3) against the relevant dovecot crypto module and is finally unloaded using dlclose(3). Until OpenSSL 1.0.1c this worked fine, however OpenSSL 1.0.1c makes sure[1] that the library stays loaded after the initial dlclose() so that the atexit(3) handlers can run on shutdown. This, together with the fact that dovecot uses custom allocation functions for OpenSSL and has already partially free()'d some of OpenSSL's resources in module_free(), leads to a segfault at process shutdown[2]. We fix this by explicitly calling OPENSSL_cleanup() during module unload. This is safe to do, as long as we will never want to subsequently re-initialize OpenSSL. [1] https://github.com/openssl/openssl/commit/4af9f7fe79ff82b90c16969b7e5871435… [2] https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=amd64&ver=1:2.2… Signed-off-by: Apollon Oikonomopoulos <apoikos(a)debian.org> --- src/lib-ssl-iostream/dovecot-openssl-common.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/lib-ssl-iostream/dovecot-openssl-common.c b/src/lib-ssl-iostream/dovecot-openssl-common.c index 51ea3ad..2bf6307 100644 --- a/src/lib-ssl-iostream/dovecot-openssl-common.c +++ b/src/lib-ssl-iostream/dovecot-openssl-common.c @@ -101,6 +101,9 @@ bool dovecot_openssl_common_global_unref(void) ERR_remove_thread_state(NULL); #endif ERR_free_strings(); +#if OPENSSL_VERSION_NUMBER >= 0x10100000L + OPENSSL_cleanup(); +#endif return FALSE; } -- 2.10.1

4 4

Index-cache sizes
by Tom Sommer 21 Nov '16

21 Nov '16

I had a customer with an INBOX cache of 400MB+ (5.5GB maildir) which gave me "Error: mmap_anon(474165248) failed: Cannot allocate memory" errors, then I deleted the cache files and ran 'doveadm index -u xxx(a)example.com "*"', now the INBOX cache is 7MB What is up with that? Is the cache now missing something or does it make sense to wipe cache files and reindex cache every-so-often? -- Tom

1 0

Feedback on first, i.e. novice-level, experiences with dovecot
by Michael Felt 21 Nov '16

21 Nov '16

a) google: "dovecot imap configuration" brought an article from 2005 as the first item: while I like debian and a bit of history you may want to ask yourself how to improve your site as the primary hit from google. FYI: years ago I had great results in the top of google searches - and then I made a major error - I moved my site to a new url and google forgot me. b) using your http://wiki.dovecot.org/QuickConfiguration as a guide: I built dovecot using --prefix=/opt (I abhor /usr/local these days - that is so 1984ish). The applications got installed in /opt/bin root@x066:/data/prj/aixtools/dovecot/core# ls -ltr /opt total 36 drwxr-xr-x 3 root root 4096 Nov 20 14:33 lib drwxr-xr-x 3 root root 4096 Nov 20 14:33 include drwxr-xr-x 6 root root 4096 Nov 20 14:33 share drwxr-xr-x 3 root root 4096 Nov 20 14:33 libexec drwxr-xr-x 2 root root 4096 Nov 20 14:33 sbin drwxr-xr-x 2 root root 4096 Nov 20 14:33 bin Are the directories 'make install' touched or made. root@x066:/data/prj/aixtools/dovecot/core# /opt/bin/doveconf -n # 2.3.devel (92c8109): /opt/etc/dovecot/dovecot.conf doveconf: Fatal: open(/opt/etc/dovecot/dovecot.conf) failed: No such file or directory where are example configs? root@x066:/data/prj/aixtools/dovecot/core# find /opt -name example-config root@x066:/data/prj/aixtools/dovecot/core# Not in /opt How about a default config? root@x066:/data/prj/aixtools/dovecot/core# find / -name dovecot /etc/init.d/dovecot /etc/pam.d/dovecot /etc/default/dovecot /etc/dovecot /var/lib/dovecot ^C Seems to be /etc/dovecot root@x066:/data/prj/aixtools/dovecot/core# ls -l /etc/dovecot total 40 drwxr-xr-x 2 root root 4096 Apr 30 2015 conf.d -rw-r--r-- 1 root root 4180 Jun 8 2014 dovecot.conf -rw-r----- 1 root dovecot 410 Jun 8 2014 dovecot-db.conf.ext -rw-r----- 1 root dovecot 782 Jun 8 2014 dovecot-dict-sql.conf.ext -rw-r--r-- 1 root dovecot 1363 Apr 30 2015 dovecot.pem -rw-r----- 1 root dovecot 5348 Jun 8 2014 dovecot-sql.conf.ext drwx------ 2 root root 4096 Apr 30 2015 private -rw-r--r-- 1 root root 121 Jun 8 2014 README and finally - read README to find the examples: root@x066:/data/prj/aixtools/dovecot/core# cat /etc/dovecot/README Configuration files go to this directory. See example configuration files in /usr/share/doc/dovecot-core/example-config/ Conclusion: --prefix=/opt is not applied everywhere. * More first impressions as I come to them - if you want them - as I hope this helps make dovecot better! Michael

2 4

doveadm service: verify client cert
by Matwey V. Kornilov 20 Nov '16

20 Nov '16

Hello, I want to open a socket for connecting doveadm using tcps. I do the following: service doveadm { inet_listener { port = 5001 ssl = yes } } At the same time, I would like to verify client certificates for connections goes to port 5001. I am trying to do the following, but it doesn't work: protocol doveadm { ssl_require_crl = yes ssl_verify_client_cert = yes } How could I achieve required behavior?

1 0

Compound Literal - xlc and gcc differences can be patched
by Michael Felt 19 Nov '16

19 Nov '16

Since I so miserably misspelled packaging - a new thread specific to the issue at hand. I found a "workaround". In short, xlc does not accept arrays of nested array - the bottom line (best message) is: 1506-995 (S) An aggregate containing a flexible array member cannot be used as a member of a structure or as an array element. At the core - all the other messages come because this (I shall call it nesting). For the test-http-auth.c file I have a patch (attached). make ran for while with no issue, then it started running into several files with this same style of specification - doveadm-dict.c being the first one. I ran "make -i" and I notice several files with this - for xlc - "unaccepted" syntax. Please look at the patch - what it basically is - and let me know whether you would consider accepting patches in this form (e.g., verify gcc (I assume) will accept it as well). If your answer is yes, I shall proceed with the additional files (learn how your MACROS work!) and send them to you. Again, initially I would just send one, e.g., doveadm-dict.c - to be sure your regular compiler also builds this alternate specification. Thank you for your consideration! Michael

2 5

Re: Good email client to use with Dovecot?
by Joseph Tam 19 Nov '16

19 Nov '16

Steve Litt asks > * And most important, where can I find the best, most unambiguous > Alpine documentation, that doesn't assume I know anything about > Alpine? The ~/.pinerc config file is well documented. There is a bewildering number of options, and you can tweak it just about anyway you like. Choice of mail readers tend to a religious issue. Users of a particular reader will only change when you pry their cold dead fingers off of it. Alpine is not a bad choice (I've been using it and it's predeccesor for decades), and I go through mail faster than most people I know as I can type faster than they can click buttons, scroll, and drag windows around. However, it sort of sucks when you read formatted mail HTML with lots of graphics). Joseph Tam <jtam.home(a)gmail.com>

1 0

Generalized looping possible in pigeonhole sieve?
by Jeff Kletsky 18 Nov '16

18 Nov '16

I'm struggling to achieve the kind of filtering with sieve that I was able to do with procmail. TL;DR I'd like a way to loop through a set of (address, destination) pairs in sieve so that I can maintain the (address, destination) pairs in one place and not have to explicitly write scores of nearly identical [...] if address :matches ["From", "Sender", "To", "Cc"] "address53" { fileinto "destination53" } if address :matches ["From", "Sender", "To", "Cc"] "address54" { fileinto "destination54" } [...] Longer: I've been using a table-based dispatch approach with procmail for years and it was working reasonably well. The approach uses list of pairs of address and destination boxes and doing a lookup based on the message to be delivered. With procmail, I collected the list of addresses and passed them to external scripts to do the lookup. If I just had a dozen boxes that I deal with, that would be straightforward to implement and maintain in sieve. As the list is an order of magnitude greater than that, maintaining the list of pairs in an external file and programmatically looping through it is a lot easier. I've looked at vnd.dovecot.execute and it certainly can return a destination box name given the input information. Unfortunately, the construct of (for example) address :matches "To" "*"' only returns the first address, not the list of addresses. I can't see a good way to get all the addressees from sieve to pass to the external program. If I have to pass the message (or at least the interesting headers) to the external program and then parse the address list myself, then I'm nearly all the way to just using a full-on external program to parse the whole message. While I'm not adverse to writing the whole thing in Python (or the like) and just using sieve as a thin shell, I'd like to make sure I'm not missing something in sieve. One way to achieve this would be to be able to loop through the pairs and using variable substitution for each iteration. I haven't seen anything in Dovecot Pigeonhole sieve that allows this. If you have any ideas on how to harness sieve for this, I'd appreciate it! Jeff

3 2

BUG: nopassword doesn't work with CRAM-MD5
by Arkadiusz Miśkiewicz 18 Nov '16

18 Nov '16

Hello. dovecot 2.2.26.0 When testing nopassword extra field (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields) with CRAM-MD5 dovecot doesn't allow any password (while it should) and returns " Authentication failed" while in logs: Nov 17 08:22:34 auth-worker(1551): Info: sql(pepe,127.0.0.1,<Y8amDXpBptV/AAAB>): Requested CRAM-MD5 scheme, but we have a NULL password NULL is there because our sql query returns empty password just like wiki says "nopassword: you want to allow all passwords, use an empty password and this field. " If password is returned in sql query then it fails, too: Nov 17 09:00:49 auth-worker(2206): Error: sql(pepe,127.0.0.1,<eO5vlnpBtNd/AAAB>): nopassword set but password is non- empty So looks to be a bug. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

3 6

Any way to simplify repeated use of same string-list?
by Jeff Kletsky 18 Nov '16

18 Nov '16

I often use the same set of header names when doing an 'address' comparison. I would prefer to be able to specify that once, then re-use it in several places. As an example set "address_mailman_fields" "\"To\", \"Cc\", \"From\", \"Errors-To\""; if address :domain :matches ["${address_mailman_fields}"] "example.com" { [...] } if address :domain :matches ["${address_mailman_fields}"] "dovecot.org" { [...] } or the like would be quite helpful. From what I can tell, even though the variable interpolation *looks* like a string-list, it isn't parsed as such. For example, from sieve-test output: sieve-test(jeff): Debug: Mailbox <filename> Opened mail UID=1 because: header "To", "Cc", "From", "Errors-To" (Cache file is unusable) testing: line 27: info: DEBUG: address ["${address_mailman_fields}"] didn't match. sieve-test(jeff): Debug: Mailbox <filename> Opened mail UID=1 because: header ["To", "Cc", "From", "Errors-To"] (Cache file is unusable) testing: line 34: info: DEBUG: address "[${address_mailman_fields}]" didn't match. Is there any trick available to specify a string-list once, then re-use it throughout the script? Thanks, Jeff

1 0

dovecot pre-install issue
by soumitri＠iitk.ac.in 17 Nov '16

17 Nov '16

Hello all, I am going for a dovecot director based setup (2 director+ 2 imap), more imap servers will be added later depending on demand/load. Presently I have 12000+ dovecot users with Maildir quota varying from 1 GB to 20GB. (peak hour IOPS 50000+) I am having 2 options in choosing dovecot version. 1) Old stable release. I.e RHEL, with prebuilt binary. This will be having less trouble in managing. Why RHEL still using version 2.2.10. 2) Latest release with best features and lesser known bugs. I.e CentOS7 with with latest compiled version. I have to be more involved if a bug is found. I will prefer a less admin work after the setup, with all/most features working. If you have a recent similar setup/dovecot gurus, Pl. suggest. With thanks & regards, -- Soumitri Mishra http://home.iitk.ac.in/~soumitri/

3 5

New Gmail Android App and Dovecot
by David Flanigan 16 Nov '16

16 Nov '16

Dovecot Users, I have a sudden new problem that has cropped up just recently and I am stumped. My implementation has been working for over a year with no issues. Version Data: Dovecot: v2.2.10 (using self signed certificates) openSSL: v1.01e Gmail Android App: v6.10.23 November 3, 2016 The issue: I use the iphone Gmail App to access my e-mail from phone and tablet. It is simple and supports multiple accounts very nicely. This has worked for better than 18 months without issue. This week I upgraded my Android app to the latest version of Gmail and I stopped getting incoming e-mail. I can still pick up via outlook and other tools I use, but just not the android version of Gmail. When I attempt to pick up mail i see the below error in my log file. _Nov 16 14:18:56 ns1 dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.10.10.198, lip=10.1.1.10, TLS: SSL_read() failed: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number, session=<73vF8W9BdgCmrL7G>_ Disconnect and no new e-mail. There is no error in the Gmail app that I can find. The Gmail app works fine with my other accounts (Gmail, work, etc) so I am wondering if it is a configuration issue on my side or Gmail App stopped supporting something I was using. My SSl config is RPM standard other than SSL=yes and my self signed certificates. Any thoughts would be appreciated. -- Kind Regards, David

3 2

Crashing when run against OpenSSL 1.1.0c
by Michael Marley 15 Nov '16

15 Nov '16

Hi, I am running Dovecot 2.2.26.0 compiled against OpenSSL 1.1 and, since upgrading to OpenSSL 1.1.0c, the "lmtp" process has been crashing with SIGSEGV whenever it receives SIGINT. This always happens a minute or so after the lmtp process handles a message. It can also be manually reproduced by sending SIGINT to one of the running lmtp processes. I am compiling and running on an Ubuntu 17.04 x86_64 system using GCC 6.2. Here is the output of me reproducing it with gdb: (gdb) signal SIGINT Continuing with signal SIGINT. Program received signal SIGSEGV, Segmentation fault. 0x00007f6748cc2fb0 in ?? () (gdb) bt #0 0x00007f6748cc2fb0 in ?? () #1 0x00007f674872ac60 in ossl_init_thread_stop (locals=<optimized out>) at crypto/init.c:336 #2 0x00007f674872aee4 in OPENSSL_cleanup () at crypto/init.c:391 #3 0x00007f67491052e0 in __run_exit_handlers (status=0, listp=0x7f674948c5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83 #4 0x00007f674910533a in __GI_exit (status=<optimized out>) at exit.c:105 #5 0x00007f67490eb3f8 in __libc_start_main (main=0x555b35fbfbc0 <main>, argc=1, argv=0x7ffd4ede3588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd4ede3578) at ../csu/libc-start.c:325 #6 0x0000555b35fbfe3a in _start () Here is the output of "doveconf -n": # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (623ae77) # OS: Linux 4.8.7-040807-generic x86_64 Ubuntu Zesty Zapus (development branch) auth_mechanisms = plain login auth_username_format = %Ln mail_location = mdbox:~/mdbox 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 extracttext 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 } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = michael(a)michaelmarley.com protocols = imap sieve lmtp service auth { client_limit = 1624 unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_ca = </etc/ssl/private/COMODORSADomainValidationSecureServerCA.crt ssl_cert = </etc/ssl/private/michaelmarley.com.crt ssl_cipher_list = HIGH !RC4 !aNULL !eNULL !3DES @STRENGTH ssl_dh_parameters_length = 4096 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } local_name matthewtmarley.com { ssl_ca = </etc/ssl/private/COMODORSADomainValidationSecureServerCA.crt ssl_cert = </etc/ssl/private/matthewtmarley.com.crt ssl_key = # hidden, use -P to show it } I tried recompiling Dovecot to see if that might do any good, but I got the same result. Also, I noticed that the "test-crypto" test in src/lib-dcrypt also crashes on exit (despite the fact that all the tests succeeded) with a very similar stacktrace: (gdb) run Starting program: /home/michael/Source/dovecot/core/src/lib-dcrypt/test-crypto [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". test_cipher_test_vectors ............................................. : ok test_cipher_aead_test_vectors ........................................ : ok test_hmac_test_vectors ............................................... : ok test_load_v1_keys .................................................... : ok test_load_v1_key ..................................................... : ok test_load_v1_public_key .............................................. : ok test_load_v2_key ..................................................... : ok test_load_v2_public_key .............................................. : ok test_get_info_v2_key ................................................. : ok test_gen_and_get_info_rsa_pem ........................................ : ok test_get_info_rsa_private_key ........................................ : ok test_get_info_invalid_keys ........................................... : ok test_get_info_key_encrypted .......................................... : ok test_get_info_pw_encrypted ........................................... : ok test_password_change ................................................. : ok test_load_invalid_keys ............................................... : ok 0 / 16 tests failed Program received signal SIGSEGV, Segmentation fault. 0x00007ffff75a5480 in ?? () (gdb) bt #0 0x00007ffff75a5480 in ?? () #1 0x00007ffff6ff7c60 in ossl_init_thread_stop (locals=<optimized out>) at crypto/init.c:336 #2 0x00007ffff6ff7ee4 in OPENSSL_cleanup () at crypto/init.c:391 #3 0x00007ffff78472e0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00007ffff784733a in exit () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007ffff782d3f8 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x000055555555f68a in _start () If there is anything I have missed or if there is any other way I can help, please let me know. Thanks, Michael Marley

3 3

lazy-load SNI?
by Felipe Gasper 15 Nov '16

15 Nov '16

Hello, We’re rolling out large SNI deployments for our mail servers. Each domain gets an entry like this in the config: local_name mail.foo.com { ssl_cert = </ssl/domain_tls/*.foo.com/combined ssl_key = </ssl/domain_tls/*.foo.com/combined } There are a couple problems we’re finding with this approach: 1) Dovecot wants to load everything at once, which has some machines taking up many GiB of memory just for Dovecot. Is there any way to defer loading of an SSL cert until a client actually requests it? 2) Any time we add or remove a domain, Dovecot’s SNI config matrix needs to be rebuilt. Is there a way to handle SNI requests dynamically via some sort of configuration plugin, so we wouldn’t need to rebuild the config on domain add/remove? I looked through the docs but couldn’t see a way to do this. Thank you in advance! -Felipe Gasper Mississauga, ON

4 12

[PATCH] ssl: fix reference to SSLv2 and disable SSLv3
by Apollon Oikonomopoulos 15 Nov '16

15 Nov '16

This is driven by the fact that OpenSSL 1.1 does not know about SSLv2 at all and dovecot's defaults simply make OpenSSL error out with "Unknown protocol 'SSLv2'"[1]. So we change the defaults to refer to SSLv2 iff OpenSSL seems to know something about it. While at it, it's also a good idea to disable SSLv3 by default as well. [1] https://bugs.debian.org/844347 Signed-off-by: Apollon Oikonomopoulos <apoikos(a)debian.org> --- doc/example-config/conf.d/10-ssl.conf | 2 +- src/lib-master/master-service-ssl-settings.c | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/example-config/conf.d/10-ssl.conf b/doc/example-config/conf.d/10-ssl.conf index 31b750c..2cd445b 100644 --- a/doc/example-config/conf.d/10-ssl.conf +++ b/doc/example-config/conf.d/10-ssl.conf @@ -46,7 +46,7 @@ ssl_key = </etc/ssl/private/dovecot.pem #ssl_dh_parameters_length = 1024 # SSL protocols to use -#ssl_protocols = !SSLv2 +#ssl_protocols = !SSLv3 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL diff --git a/src/lib-master/master-service-ssl-settings.c b/src/lib-master/master-service-ssl-settings.c index 4a05045..6b43f6c 100644 --- a/src/lib-master/master-service-ssl-settings.c +++ b/src/lib-master/master-service-ssl-settings.c @@ -44,7 +44,11 @@ static const struct master_service_ssl_settings master_service_ssl_default_setti .ssl_key = "", .ssl_key_password = "", .ssl_cipher_list = "ALL:!LOW:!SSLv2:!EXP:!aNULL", - .ssl_protocols = "!SSLv2", +#ifdef SSL_TXT_SSLV2 + .ssl_protocols = "!SSLv2 !SSLv3", +#else + .ssl_protocols = "!SSLv3", +#endif .ssl_cert_username_field = "commonName", .ssl_crypto_device = "", .ssl_verify_client_cert = FALSE, -- 2.10.1

2 1

save failed to open mailbox quarantine
by Eggert Ehmke FTV Spandau 15 Nov '16

15 Nov '16

I have dovecot 2.2.13 set up with spamassassin and amavis. This works fine so far, Spam emails are forwarded to "username+Quarantine(a)mydomain.de". The recipient_delimiter=+ is set, the Quarantine folder exists. However, Dovecot tries to deliver it to a folder quarantine, that does not exist. In the dovecot-deliver.log there are these lines: Nov 14 14:16:13 lda(username(a)mydomain.de): Info: msgid=<2707212.2aHC3KDWrN@wookie>: save failed to open mailbox quarantine: Mailbox doesn't exist: quarantine Nov 14 14:16:13 lda(username(a)mydomain.de): Info: msgid=<2707212.2aHC3KDWrN@xxxxxx>: saved mail to INBOX Indeed the message is found in the inbox. What can be done so the folder name is not converted to lower case?

2 5

How does one mark all messages as read (imap4flag "seen") with sieve?
by Ben Johnson 15 Nov '16

15 Nov '16

Hello! I had hoped that marking all messages that arrive to a specific mailbox as read/seen would be as simple as applying the following sieve script to all incoming mail for that mailbox user: ######################## require ["imap4flags"]; addflag "\\Seen"; ######################## With this script in-place, mail does not appear to be marked as read/seen. It arrives as it normally would, and my email client sees it as new mail. Is something more required? Or is it a bug/limitation in my email client? I've found many examples of "addflag "\\Seen";" on the web, but all of them are wrapped in conditional logic of some variety. This is a spam-training mailbox and I simply want everything marked as seen/read upon arrival so I'm not bothered/notified every time. Thanks for any pointers here! -Ben

3 12

dovecot / tcp-wrappers / FBSD 10.3
by Jim Pazarena 14 Nov '16

14 Nov '16

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error: connect(tcpwrap) failed: No such file or directory" Suggestions/Direction much appreciated.

3 2

Self-Signed Certificate issue
by Darryl Baker 13 Nov '16

13 Nov '16

My apologies if this is a repeat but my search of the archive did not turn it up in the recent past. If this has been covered just point me at the previous thread, please. I am running a small email site which I am moving from uw-imapd and Solaris to Ubuntu and Dovecot imaps and pop3s. I am trying to use a self-signed certificate for this site. I am using Thunderbird as the test client. I've tried both the pre-built snakeoil certificate and building a special one for dovecot. In /var/log/mail.err I keep getting what I am interpreting as a missing CA cert. The message is: dovecot: imap-login: Error: SSL: Stacked error: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 The certificate was created by: openssl req -new -x509 -days 365 -nodes -out /etc/ssl/certs/dovecot.pem -keyout /etc/ssl/private/dovecot.pem The Dovecot version is 2.2.22 (fe789d2) The Ubuntu version is 16.04 LTS current patches. *Darryl Baker*

3 3

help needed configuration of quota warning mails
by Götz Reinicke 13 Nov '16

13 Nov '16

Hi, we run dovecot 2.2.24 and from what I see, quota management with warning message is configured currently with "noenforcing". Our individual quota limit is stored in the users ldap DN which is fetched as I see from the logs and by "doveadm quota get -u" I tried to trigger the warning mail by going over the limit on my account step by step and can see that values are counted with the command above and in thunderbird by showing the orange and than red warning symbol at the bottom for me. But the warning mail script is not triggert. How may I debug this? /usr/local/bin/quota-warning.sh is owned currently by vmail and executable by vmail. Thanks for feedback and suggestion . /Götz

1 0

Dovecot lmtp
by Peter Fraser 13 Nov '16

13 Nov '16

Hi All I am migrating from dovecot-1.x where I had LDA running to dovecot2-2.2.26.0_1 where I am trying to set up LMTP. I have enabled a TCP/IP socket .Setting below. service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } and put this additional entry in postfix virtual_transport = lmtp:127.0.0.1:24 in 10-mail.conf my mail location is below mail_location=maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/tmp/index My problem is that when I enable lmtp, dovecot creates a new maildir at /home/vmail/user(a)domain.com and delivers the email there in a Maildir instead of using the default one at /home/vmail/username I researched it but I just can't seem to figure out why this is. I would really appreciate any help on this. Thanks in advance.

2 1

Redirect the emails from domain2 to domain1
by Quaquaraquà 11 Nov '16

11 Nov '16

Dear Dovecot and Exim users, I have a VPS using these two applications. I am transitioning from a domain_old to a domain_new. I'd like to redirect all the emails from domain_old to the local mailboxes of users @ domain_new. In exim I've assumed that it is enough to add domain_old to the list of local domains: domainlist local_domains = @ : domain_new : domain_old ... begin routers ... local_users: debug_print = "R: local_user for $local_part@$domain" driver = accept domains = +local_domains transport = dovecot_lmtp cannot_route_message = Unknown user However in Dovecot I'm checking both the username and the domain to perform the authentication: auth_username_format = %Lu passdb { driver = sql ; } password_query = SELECT username, domain, password FROM users WHERE username = '%n' AND domain = '%d' To have this system to work, I wish some special rule that rewrites the domain from domain_old to domain_new. But I'm not sure whether this needs to be done in exim or dovecot and how to add it? - Quaquaraqua'

3 2

How to Analyze Missing UIDs (and Files) in Maildirs?
by Jochen Bern 11 Nov '16

11 Nov '16

Hello everyone, I would like pointers on how to analyze the following situation, please: I'm running one test and one production dovecot IMAPS server for one of our platforms. The clients are essentially appliances we distribute, auth by client cert, virtual users only, mailboxes in maildir format: > auth_ssl_require_client_cert = yes > auth_ssl_username_from_cert = yes > auth_mechanisms = plain > ssl = required > ssl_cert = </etc/pki/dovecot/certs/... > ssl_key = </etc/pki/dovecot/private/... > ssl_ca = </etc/pki/dovecot/certs/... > ssl_verify_client_cert = yes > mail_location = maildir:~ > userdb { > driver = static > args = uid=... gid=... home=/home/.../%Ld_realm/%Ln > } > passdb { > driver = static > args = password=... > } The client certs have CNs unique to the appliance and no client besides that appliance is supposed to access the mailbox. Appliances take note of the UIDs they've seen (and not yet deleted) and expect to be able to re-access e-mails by the UIDs they know. (Needless to say, I keep my hands away from the cache files so as not to cause the UIDs to be reassigned.) The dovecot version used is updated along with the CentOS 6 source RPMs - which contain a 2.0.9 plus whatever patches CentOS backported - and receives two additional patches from me, one from current dovecot sources to improve closure of inactive SSL connections and one from me that turns the IMAP CREATE command into a NOP; the appliance code doesn't expect mailboxes to have folders besides INBOX. ------- QA is looking into an upcoming new feature that requires appliances to reread old e-mails, and got errors that UIDs the test appliances expected to still be on the (test) server weren't. I verified, the UIDs are indeed absent from the dovecot-uidlist files. The mails in question arrived *sometime* over the course of the last 12 months and must've vanished *sometime* since then ... ugh. No trace of what may have happened to them in any logs, of course. On the test server, I re-enabled logging of DELETE, UNDELETE and EXPUNGE commands, in case the appliances delete mails themselves and forget to update their own cache. Are there other IMAP commands that could remove mails, and thus should be added to the list? Would it be possible to have dovecot configured so that there's a log entry whenever a client tries to retrieve a UID that dovecot doesn't have in the maildir anymore? ------- While looking into the above issue, I noticed that a large number of mailboxes (test as well as production) have UIDs that *are* listed in dovecot-uidlist, yet, no corresponding file is present anymore. Example: > # grep -c : *_realm/$EXAMPLE_USER/dovecot-uidlist > 58 > # grep : *_realm/$EXAMPLE_USER/dovecot-uidlist | sed -e '2,57d' -e 's/ .*//' > 1 > 152 > # for PAIR in `grep : *_realm/$EXAMPLE_USER/dovecot-uidlist | sed -e 's/ .*:/:/'` ; do > > IMAP_UID=`echo $PAIR | sed -e 's/:.*//'`; BASE=`echo $PAIR | sed -e 's/.*://'` > > CNT=`find *_realm/$EXAMPLE_USER -type f -name "$BASE"'*' -ls | wc -l` > > if [ $CNT -ne 1 ]; then echo "Found $CNT files for UID $IMAP_UID"; fi; done > Found 0 files for UID 135 > Found 0 files for UID 136 > Found 0 files for UID 139 > Found 0 files for UID 142 > Found 0 files for UID 143 > Found 0 files for UID 144 > Found 0 files for UID 145 > Found 0 files for UID 150 > Found 0 files for UID 151 Is that normal behaviour? If not, how would I try to find out what happens there? Kind regards, -- Jochen Bern Systemingenieur Fon: +49 6151 9067-231 Fax: +49 6151 9067-290 E-Mail: jochen.bern(a)binect.de www.binect.de www.facebook.de/binect Binect GmbH Robert-Koch-Straße 9, 64331 Weiterstadt, DE Geschäftsführung: Christian Ladner, Dr. Frank Wermeyer, Nils Manegold Unternehmenssitz: Weiterstadt Register: Amtsgericht Darmstadt, HRB 94685 Umsatzsteuer-ID: DE 221 302 264 MAX 21-Unternehmensgruppe

1 0

Enterprise Edition: Any known access issues with the repo? Have existing accounts been expired?
by deoren 11 Nov '16

11 Nov '16

Hi, I'm getting errors when attempting to run apt-get update on an Ubuntu 14.04 box where I've had an existing EE installation for some time: > W: Failed to fetch https://apt.dovecot.fi/stable-2.2/ubuntu/trusty/dists/trusty/main/binary-am… HttpError401 > > W: Failed to fetch https://apt.dovecot.fi/stable-2.2/ubuntu/trusty/dists/trusty/main/binary-i3… HttpError401 > > E: Some index files failed to download. They have been ignored, or old ones used instead. I'm running 2.2.25.5 now and when I looked at the announcement forum[1] I see a posting[2] for 2.2.26.1, but nothing about repo changes. For what it is worth, I use the EE credentials on only a single node so I am hopefully not triggering any abuse thresholds. I tried accessing the URL used in the /etc/apt/sources.list.d/FILENAME.list file via a web browser and it isn't accepting the provided username/password. Have existing credentials been expired? If so, what is the next step to restore access? Thanks. References: [1] https://forum.open-xchange.com/forumdisplay.php?35-Dovecot-Announcements [2] http://software.open-xchange.com/products/dovecot/doc/Release_Notes_for_Dov…

2 1

Maildir filename has wrong S value - possible culprit
by Libor Pavlík 11 Nov '16

11 Nov '16

Hi, I'm new to dovecot but as I see in mailinglist archive this issue is old and I didn't find this in archive. One of cuplrits (I believe not the only possible) is spamassassin. It's added headers make exactly the difference between S value and filesize. Probably it's in the way emails are processed in "manufactory" of Qmail+Vpopmail+Spamassassin but now I'm not able to say how can it be repaired. As mentioned above I'm using solution with Qmail+Vpopmail+Spamassassin+Dovecot, my Dovecot version is 2.2.26.0. Libor Pavlík

1 0

post-delivery virus scan
by Brad Koehn 11 Nov '16

11 Nov '16

I have discovered that many times the virus definitions I use for scanning messages (ClamAV, with the unofficial signatures http://sanesecurity.com/usage/linux-scripts/) are updated some time after my server has received an infected email. It seems the virus creators are trying to race the virus definition creators to see who can deliver first; more than half of the infected messages are found after they’ve been delivered. Great. To help detect and remove the infected messages after they’ve been delivered to users’ mailboxes, I created a small script that iterates the INBOX and Junk mailbox directories, scans recent messages for viruses, and deletes them if found. The source of my script (run via cron) is here: https://gitlab.koehn.com/snippets/9 Unfortunately Dovecot doesn’t like it if messages are deleted (dbox) out from under it. I tried a doveadm force-resync on the folder containing the messages, but it seems Dovecot is still unhappy. At least on the new version (2.2.26.0) it doesn’t crash; 2.2.25 would panic and coredump when it discovered messages had been deleted. I’m wondering if there’s a better way to scan recent messages and eradicate them so the Dovecot isn’t upset when it happens. Maybe using doveadm search? Looking for suggestions. --- Brad

6 9

Re: How does one mark all messages as read (imap4flag "seen") with sieve?
by Ben Johnson 11 Nov '16

11 Nov '16

On 11/10/2016 2:02 AM, Aki Tuomi wrote: > Hi! > > Can you provide bt full from gbd? > > Install debug symbols and acquire core file > > Run gdb /path/to/bin /path/to/core > > Issue bt ful > > Send it to list. > > > Aki Tuomi > > Dovecot oy > > > > On November 10, 2016 at 2:42 AM Larry Rosenman <larryrtx(a)gmail.com> > wrote: > > looks to me from the coredump (although you pointed to the wrong binary) > that > deliver was PANIC()'ing with > > io_add(0x%x) called twice fd=%d, callback=%p -> %p > > I'm not sure what that message means, but maybe one of the dovecot folks > does. > > Are all the packages built together? > > Are you averse to compiling stuff yourself? Thanks so much for the assistance here, Larry and Aki. Aki, you had asked me to send this core-dump to the list when I asked about it back in September; I did post the "bt full" output at that time, but there were no further replies: http://www.dovecot.org/list/dovecot/2016-September/105428.html And for convenience, here is the "bt full" output I posted back then: http://pastebin.com/4xdGNXa6 So, this is where I'm confused: Larry, you mentioned "although you pointed to the wrong binary", which is a concern I had asked about back in September: http://www.dovecot.org/list/dovecot/2016-September/105424.html I still don't understand how this is pointing to the wrong binary: # gdb /usr/lib/dovecot/dovecot-lda /var/vmail/tmp/core-deliver-6-5000-5000-29125-1473732949 Is /usr/lib/dovecot/dovecot-lda not the binary that segfaulted here? Sure, the gdb output says, "Core was generated by `/usr/lib/dovecot/deliver ...", but on the system in question, that is a symlink pointing to /usr/lib/dovecot/dovecot-lda: # ls -lah /usr/lib/dovecot/deliver lrwxrwxrwx 1 root root 11 Sep 21 10:29 /usr/lib/dovecot/deliver -> dovecot-lda What am I missing here? The mismatch message does say something specific about this: warning: the debug information found in "/lib64/ld-2.23.so" does not match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch). Is this the result of pointing to the wrong executable when calling "gdb"? If so, where is the correct executable to pass as the fist argument? Again, for convenience, the pipe script I'm using: http://pastebin.com/zXzBDcvG And the debug output from said pipe script: http://pastebin.com/rz2f4S4G My full "doveconf -n": http://pastebin.com/hCgpA009 Thanks! -Ben

1 0

service doveadm : ssl problems
by nerbrume＠free.fr 10 Nov '16

10 Nov '16

Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal: /var/run/dovecot/auth-userdb: Configured passdbs don't support crentials lookups (to see if user is proxied, because doveadm_port is set) but rather specifying the port in the mail_replica setting : "mail_replica = tcps:my.domain.com:1465" (following a mail from here : http://www.dovecot.org/list/dovecot/2016-September/105356.html) So far, this seems to be working for me. 2) However, I'm having ssl problems. I have a let's encrypt certificate, and have concatened the CA cert and my server cert in a fullchain.pem. Excerpt from my ssl config : > ssl = yes > ssl_cert = </etc/letsencrypt/live/my.domain.com/fullchain.pem > ssl_key = </etc/letsencrypt/live/my.domain.comi/privkey.pem doveadm return me these errors (sudo -u dovecot doveadm -v sync -u user tcps:my.domain.com:12345) : > doveadm(casoli): Info: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com > doveadm(casoli): Error: doveadm server disconnected before handshake: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com > doveadm(casoli): Fatal: Disconnected from remote: Received invalid SSL certificate: unable to get local issuer certificate: /CN=my.domain.com Which I can reproduce with openssl (openssl s_client -showcerts -CApath /etc/ssl/certs -connect my.domain.com:12345) : > (...) > Verify return code: 21 (unable to verify the first certificate) Indeed, in this case, dovecot only returns the local part of the certificate (my.domain.com) and not the full chain (with the intermediate CA). While testing regular IMAPS with openssl is ok (openssl s_client -showcerts -CApath /etc/ssl/certs -connect my.domain.com:993) > (...) > Verify return code: 0 (ok) And I can see the full chain. So, it's seems to me that doveadm is somehow wrongly serving my certificate, truncating it, but I can't see why, and if this is a misconfiguratin on my part. I can post more config files or message outputs if needed, I kept them redacted here for the sake of brevity. Regards, N

2 2

Dovecot 2 LDAP "unknown user"
by Peter Fraser 10 Nov '16

10 Nov '16

Hi All I am using Dovecot dovecot2-2.2.25_6 on FreeBSD 11. I am trying to set up LDAP authentication to Active Director as I had it in version 1 of Dovecot. My settings are at bottom. When I run doveadm auth test username, I get back root@BSD-11:/usr/local/etc/dovecot # doveadm auth test username Password: passdb: user auth succeeded extra fields: user=username root@BSD-11:/usr/local/etc/dovecot # But when I run telnet 127.0.0.1 110 and try to log in it says unknown user. Error below in maillog. BSD-11 dovecot: pop3: Error: Authenticated user not found from userdb, auth lookup id=2262958081 (client-pid=2273 client-id=1) Nov 1 15:15:41 BSD-11 dovecot: pop3-login: Internal login failure (pid=2273 id=1) (internal failure, 1 successful auths): user= root@BSD-11:/usr/local/etc/dovecot # doveconf -n # 2.2.25 (7be1766): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p1 i386 auth_debug = yes auth_verbose = yes listen = * login_greeting = Mail Server ready. 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 { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } ssl_cert = </usr/local/etc/certs/certs/dovecot.pem ssl_key = </usr/local/etc/certs/private/dovecot.pem userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lda { mail_plugins = } #Contents of dovecot-ldap.conf.ext hosts = 192.168.153.143 dn = user(a)domain.com dnpass = password auth_bind = yes auth_bind_userdn = domain\%u ldap_version = 3 base = dc=domain,dc=com pass_filter = (&(objectclass=person)(uid=%u)) user_attrs = homeDirectory=/home/vmail/%u,uid=1002,gid=1002 Amy help would be appreciated.

3 9

question concerning junk folder
by Rajesh M 10 Nov '16

10 Nov '16

hi using centos 6.5, qmailtoaster, dovecot, spamassassin. i found that junk folder is specified under /etc/dovecot/conf.d/15-mailboxes.conf the issue is that this folder is getting created automatically and genuine emails from both within the server and also from external domains are being routed to the Junk folder. all these emails are not scanned by spamassasin. i wish to disable to creation of Junk folder and also routing of emails to the Junk folder. help required please. ##################### # NOTE: Assumes "namespace inbox" has been defined in 10-mail.conf. namespace inbox { # These mailboxes are widely used and could perhaps be created automatically: mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Trash { special_use = \Trash } ##################### rajesh

2 1

search body with wildcards
by W. de Hoog 10 Nov '16

10 Nov '16

Hi, A question. We are using fts_solr. When searching for content in BODY I noticed that dovecot only supports full words. "BODY calibration" returns results but "BODY calibra" does not. Nor "BODY calibra*". Solr does support searching with wildcards so why is it that dovecot does not? regards, -- Willem-Jan de Hoog

1 2

tons of dovecot/config processes
by Arkadiusz Miśkiewicz 10 Nov '16

10 Nov '16

Hi. I've noticed that dovecot (using 2.2.26.0 here) starts dovecot/config processes that stay for long time. Example: [root@ixion-pld ~]# service dovecot restart Stopping Dovecot service.......................................................................................................................................[ DONE ] Starting Dovecot service.......................................................................................................................................[ DONE ] [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13736 2480 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25337 0.0 0.0 9612 2416 ? S 09:40 0:00 dovecot/log root 25339 0.0 0.0 12496 3256 ? S 09:40 0:00 dovecot/config root 25341 0.0 0.0 132168 888 pts/1 S+ 09:40 0:00 grep dovecot [root@ixion-pld ~]# doveadm reload [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2720 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12496 3192 ? S 09:40 0:00 dovecot/config root 25348 0.0 0.0 132168 876 pts/1 S+ 09:40 0:00 grep dovecot so far good - only one dovecot/config. Lets connect to pop3 and keep connection [root@ixion-pld ~]# telnet localhost pop3 Trying 127.0.0.1.110... Connected to localhost. Escape character is '^]'. +OK Mail server ready. on the other console [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2720 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [2 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12496 3192 ? S 09:40 0:00 dovecot/config dovenull 25364 0.0 0.0 20908 4080 ? S 09:41 0:00 dovecot/pop3-login [127.0.0.1] dovecot 25365 0.0 0.0 100236 7776 ? S 09:41 0:00 dovecot/auth [0 wait, 0 passdb, 0 userdb] root 25368 0.0 0.0 132168 856 pts/1 S+ 09:41 0:00 grep dovecot so there is a client connected and one dovecot/config. Lets reload: [root@ixion-pld ~]# doveadm reload [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2752 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [2 connections] root 25344 0.0 0.0 9612 2428 ? S 09:40 0:00 dovecot/log root 25346 0.0 0.0 12920 3700 ? S 09:40 0:00 dovecot/config dovenull 25364 0.0 0.0 20908 4080 ? S 09:41 0:00 dovecot/pop3-login [127.0.0.1] dovecot 25365 0.0 0.0 100236 7776 ? S 09:41 0:00 dovecot/auth [0 wait, 0 passdb, 0 userdb] root 25371 0.0 0.0 9612 2196 ? S 09:41 0:00 dovecot/log root 25373 0.0 0.0 12496 3196 ? S 09:41 0:00 dovecot/config root 25375 0.0 0.0 132168 856 pts/1 S+ 09:41 0:00 grep dovecot now we have two dovecot/config processes. Second dovecot/config stays there until client disconnects (what for?). When clients disconnects we are back to single dovecot/config: [root@ixion-pld ~]# ps aux|grep dovecot root 25333 0.0 0.0 13872 2752 ? Ss 09:40 0:00 /usr/sbin/dovecot dovecot 25336 0.0 0.0 9480 924 ? S 09:40 0:00 dovecot/anvil [0 connections] root 25371 0.0 0.0 9612 2196 ? S 09:41 0:00 dovecot/log root 25373 0.0 0.0 12496 3196 ? S 09:41 0:00 dovecot/config root 25418 0.0 0.0 132168 852 pts/1 S+ 09:43 0:00 grep dovecot Now on production server where are tons of clients this looks more insane: # ps aux|grep dovecot/config | wc -l 56 Note that I'm running with shutdown_clients = no here (+ high performance auth/login variant). So looks like something is not right here. Obviously with shutdown_clients=yes this doesn't occur since clients are disconnected. doveadm reload can happen every 2 minutes (because dovecot requires reload when SSL certificates change; new domain gets added, new cert gets automatically created -> reload, certificate is renewed (every 2 months) -> reload etc) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Dovecot processes turning zombie
by Adrian POPA 10 Nov '16

10 Nov '16

Hi I am running Ubuntu 14.04 (plan to go to 16.04) with Postfix and Dovecot 2.2.9 from Ubuntu repository. Dovecot configuration has not changed dramatically since the days of Ubuntu 12.04 (can't remember Dovecot version). In the last months, connection to Dovecot IMAP service become more and more dificult. First Ubuntu Thunderbird refused to connect, than Android phones. The last one connecting regularly was an old XP laptop(!). Now it's facing problems too. Again, I did not make any configuration changes lately so only system upgrades (libraries) may have caused this. The first thing to notice was that some Dovecot processes are going zombie (defunct). At startup "ssl-params", then sometimes "auth", "imap-login" and rarely "config". Turning on debug logging in Dovecot show that offending process "is ignoring idle SIGINT". And "auth client limit (1000) reached". This behavior also impacts on Postfix delivery through Dovecot LDA with "status=deferred (temporary failure)" (I turned off mail sending with -e in lda invocation). Another thing is SLL connection. Attempts to test with openssl s_client show that Dovecot is not responding after ClientHelo when it should normally send server certificate. The very same certificate is used with Postfix and it works (I can send mails through Postfix) but IMAP connections to Dovecot do not. There is no protocol mismatch because I have try a local SSL connection (same computer). Initial messages are TLS1.2 but nothing in response. So my question is: did you faced such problems and found a cause (and maybe a fix)? Upgrading to Ubuntu 16.04 with whatever Dovecot version it provides may resolve the issues? Thanks

1 0

<-FIN <-RST ->FIN,ACK <-RST on SSL connection shutdown
by Heiko Schlittermann 10 Nov '16

10 Nov '16

Hello, a typical connection close, tcpdump'ed on the server side, looks as follows: 21:44:01.168131 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [FP.], seq 3982457856:3982457959, ack 1570044906, win 243, options [nop,nop,TS val 138698279 ecr 159494908], length 103 21:44:01.172405 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [R], seq 3982457960, win 0, length 0 21:44:01.172442 IP xxx.xxx.3.96.35518 > xxx.xxx.3.101.143: Flags [F.], seq 32, ack 104, win 342, options [nop,nop,TS val 159494909 ecr 138698279], length 0 21:44:01.172471 IP xxx.xxx.3.101.143 > xxx.xxx.3.96.35518: Flags [R], seq 3982457960, win 0, length 0 The server closes (FIN) the connection, and already 4.274 ms later the server sends a RST to the client. The clients response to FIN arrives some μs later. (On the client side the order of the packages is different (FIN from Server, FIN,ACK from client, RST from Server, RST from Server) This behaviour seems to be odd (the client side firewall complains about the unexpected packages). I can reproduce it using openssl -connect … -starttls imap .. on the client side. It happens on IMAP+STARTTLS as well as on IMAPS. It does not happen on plaintext IMAP. There I see the expected shudown handshake FIN - FIN,ACK - ACK. Dovecot version is 2.2.24 (a82c823) 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 ------------ -

1 0

Backing up dovecot mailboxes
by Jerry 09 Nov '16

09 Nov '16

Does anyone have a working solution as to how I can use "doveadm backup" to back up a virtual users mailbox to a removable USB device. I keep receiving numerous errors and no files are backed up although the directories are created. -- Jerry

3 2

Indexing failed: 500 Internal Server Error
by W. de Hoog 09 Nov '16

09 Nov '16

Hi, While running doveadm index on a mailbox this gets printed: doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server Error doveadm(neil): Panic: file http-client-request.c: line 792 (http_client_request_send_payload): assertion failed: (ret == 0) doveadm(neil): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x88662) [0x7f0a52750662] -> /usr/lib/dovecot/libdovecot.so.0(+0x886d9) [0x7f0a527506d9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a526e9f81] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_send_payload+0xc8) [0x7f0a52703cf8] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x49) [0x7f0a518654a9] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x3187) [0x7f0a51861187] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x8667) [0x7f0a51ec8667] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0x4f1) [0x7f0a51ec8fb1] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xefce) [0x7f0a51ecefce] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x29) [0x7f0a52a045f9] -> /usr/bin/doveadm(+0x2e997) [0x565355d01997] -> /usr/bin/doveadm(+0x28dec) [0x565355cfbdec] -> /usr/bin/doveadm(+0x299ca) [0x565355cfc9ca] -> /usr/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x209) [0x565355cfd7d9] -> /usr/bin/doveadm(doveadm_cmd_run_ver2+0x555) [0x565355d0c715] -> /usr/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x565355d0c767] -> /usr/bin/doveadm(main+0x1da) [0x565355cecc7a] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f0a5231f830] -> /usr/bin/doveadm(_start+0x29) [0x565355ced059] $ dovecot -n # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (623ae77) # OS: Linux 4.4.0-45-generic x86_64 Ubuntu 16.04.1 LTS disable_plaintext_auth = no log_path = /var/log/dovecot.log mail_plugins = fts fts_solr mail_privileged_group = mail namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / } namespace { list = yes location = sdbox:/home/imapshared-sdbox prefix = shared/ separator = / subscriptions = no type = public } namespace inbox { location = sdbox:~/sdboxmail 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 { driver = pam } plugin { fts = solr fts_autoindex = yes fts_solr = break-imap-search url=http://localhost:8080/solr/ fts_squat = partial=4 full=10 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags } -- Willem-Jan de Hoog

3 6

Too many references: cannot splice
by Luis Ugalde 09 Nov '16

09 Nov '16

Hi, A while ago I sent an email regarding these "*ETOOMANYREFS* Too many references: cannot splice." that we've seen since Debian updated the Jessie kernel to 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 while older kernels, like 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 showed no errors at all. I was wondering if no one else is getting these errors, or if you know any workarounds that might probe useful, apart from downgrading the kernel. I would say that the infrastructure we're running is quite standard, with directors balancing users to NFS backed dovecot servers. Best regards, Luis Ugalde.

2 3

Repeat e-mail syndrome shows up in 2.2.26+
by The Doctor 09 Nov '16

09 Nov '16

Getting complaints from people about pop/imap issues. some people are getting repaeted e-mail. Other are not able to delete their e-mails from an IMAP lcient. Current configuration /usr/dovecot2/sbin/dovecot -n # 2.2.26.0 (23d1de6): /usr/dovecot2/etc/dovecot/dovecot.conf # OS: FreeBSD 11.0-RELEASE-p2 amd64 base_dir = /var/run/dovecot/ disable_plaintext_auth = no first_valid_uid = 100 info_log_path = /var/log/dovecot-info.log listen = [::] log_path = /var/log/dovecot.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_log_prefix = %Us(%u): mdbox_rotate_size = 2 k passdb { args = /etc/master.passwd driver = passwd-file } plugin { home = /usr/dovecot2 } service auth { executable = /usr/dovecot2/libexec/dovecot/auth user = root } service imap-login { chroot = login client_limit = 256 executable = /usr/dovecot2/libexec/dovecot/imap-login inet_listener imap { address = 204.209.81.1, 127.0.0.1 port = 143 } inet_listener imaps { address = 204.209.81.1, 127.0.0.1 port = 993 ssl = yes } process_limit = 128 process_min_avail = 3 service_count = 1 user = dovecot } service imap { executable = /usr/dovecot2/libexec/dovecot/imap process_limit = 512 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 204.209.81.1 127.0.0.1 ::1 port = 24 } process_min_avail = 5 } service pop3-login { chroot = login client_limit = 256 executable = /usr/dovecot2/libexec/dovecot/pop3-login inet_listener pop3 { address = 204.209.81.1 port = 110 } inet_listener pop3s { address = 204.209.81.1 port = 995 ssl = yes } process_limit = 128 process_min_avail = 3 service_count = 1 user = dovecot } service pop3 { executable = /usr/dovecot2/libexec/dovecot/pop3 process_limit = 512 } ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = /etc/passwd driver = passwd-file } verbose_ssl = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_idle_notify_interval = 2 mins imap_logout_format = bytes=%i/%o imap_max_line_length = 64 k mail_max_userip_connections = 10 mail_plugin_dir = /usr/dovecot2/lib/dovecot/imap ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it verbose_ssl = yes } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_lock_session = yes pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = yes pop3_reuse_xuidl = yes pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv ssl_cert = </usr/dovecot2/etc/dovecot/ssl/pop3.nk.ca.2016.chain.crt ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:aNULL ssl_key = # hidden, use -P to show it verbose_ssl = yes } protocol lmtp { auth_username_format = %Lu info_log_path = /var/log/dovecot-lmtp.log } Sorry about the indents. Anything causing these issues? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!!

6 13

that's just so amazing and wonderful
by mrgrim 08 Nov '16

08 Nov '16

Hi friend! Look at that amazing stuff, it is absolutely wonderful. Please take a look <http://bargain.jontrauner.com/e4tfx/5> Speak to you later, mrgrim

1 0

imapsieve pigeonhole plugin?
by Larry Rosenman 08 Nov '16

08 Nov '16

How do you enable the imapsieve plugin? I added sieve_plugins = imapsieve and it whines: hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d # service dovecot restart managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Stopping dovecot. Waiting for PIDS: 97491. managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Starting dovecot. managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 this plugin seems to be poorly documented. :( -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 11