- dovecot - dovecot.org

replicator crashing - oom
by Daniel Miller 24 Mar '17

24 Mar '17

I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4638a14322] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x95e3f) [0x7f4638a7ae3f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x9608b) [0x7f4638a7b08b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xb15f8) [0x7f4638a965f8] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x93c42) [0x7f4638a78c42] -> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x74) [0x7f4638a78fb4] -> dovecot/replicator(replicator_queue_push+0x13b) [0x40519b] -> dovecot/replicator() [0x4049c2] -> dovecot/replicator() [0x4040a8] -> dovecot/replicator() [0x404275] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f4638a907d2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) [0x7f4638a91d17] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f4638a9086c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f4638a90a28] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4638a1dfc3] -> dovecot/replicator(main+0x17a) [0x40342a] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f4638640ec5] -> dovecot/replicator() [0x4034c5] Mar 21 14:47:00 bubba dovecot: replicator: Fatal: master: service(replicator): child 15650 killed with signal 6 (core dumped) -- Daniel

4 7

One way dsync replication with dsync -R
by Wolfgang Hennerbichler 24 Mar '17

24 Mar '17

Hi dovecot users, I’ve found the -R parameter for dsync. Does this enable one-way syncing if enabled on the slave in replication_dsync_parameters? The documentation doesn’t mention much what happens if I enable this on the “replciation slave”. Before you ask: Two way synchronisation causes issues in my installation (see the unanswered thread here: http://www.dovecot.org/list/dovecot/2017-March/107431.html) it causes unread, deleted messages to re-appear. I would hope that one-way synchronisation would avoid this, but I’d also like to know if the -R parameter is safe to use. I am also still wondering if anybody has a perfectly working 2-way-synchronised dovecot installation (and I’m interested in your dovecot -n). wogri

2 5

FTS on shared/virtual folders
by Daniel Miller 24 Mar '17

24 Mar '17

A question on how FTS is implemented with regards to shared & virtual mailbox. In particular - with Solr. Does Dovecot treat each shared and virtual mailbox as completely independent - which means Solr would reindex each appearance independently? If that's the case, has any thought been given to potentially identifying such queries and passing them to Solr against the "native" or private mailboxes that are referenced? -- Daniel

1 0

"Connection queue full" error
by Mark Moseley 24 Mar '17

24 Mar '17

Just a quickie: why is "Connection queue full" logged under Info, instead of something like error? Or at least have the word 'error' in it? Seems like a pretty error-ish thing to happen. Anything that causes the connection to fail from the server side should show up in a grep -i for error. I.e. I don't care about clients failing to match up SSL cipher suites; that's fine as Info (SSL errors ironically do have 'error' in them, though I assume that's coming from the ssl libs). But the server dropping connections due to running out of available daemons (and any other "server isn't working right" conditions) is definitely worthy of Error.

1 0

dsync with namespaces
by Tom Sommer 23 Mar '17

23 Mar '17

I have a major dsync headache which I am hoping someone can help me with. I have to migrate mails from a 'namespace/inbox/prefix=INBOX.' server to a 'namespace/inbox/prefix=' server. So I'm trying # dsync -o 'namespace/inbox/prefix=' sync -1 -f -u xx(a)xx.com tcp:1.2.3.4 It works fine for some accounts, however for others many hundreds and sometimes thousands of mails go missing from the destination inbox, and a resync doesn't pick them up. The debug output doesn't recognize these either. If I remove the 'namespace/inbox/prefix=' part, then I get 'Error: Couldn't find namespace for mailbox X' errors. Both source and destination is running 2.2.27 I can't imapsync :S Thanks. -- Tom

1 0

Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
by Ralf Hildebrandt 23 Mar '17

23 Mar '17

* Aki Tuomi <aki.tuomi(a)dovecot.fi>: > Could you send us the gdb bt full backtrace for the core file? Currently I can't get it to create coredumps doveconf -n: # 2.2.devel (3f97702): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (023f391) # OS: Linux 4.4.0-65-generic x86_64 Ubuntu 16.04.2 LTS auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = exchange-imap.charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no listen = *,:: mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_plugins = mail_log notify mail_uid = imapproxy passdb { args = host=exchange-imap.charite.de port=993 ssl=imaps default_fields = userdb_imapc_user=%u userdb_imapc_password=%w userdb_imapc_host=exchange-imap.charite.de userdb_imapc_ssl=imaps userdb_imapc_port=993 driver = imap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap service auth { inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/dovecot/dovecot.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_client_ca_file = /etc/ssl/certs/ca-certificates.crt ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } verbose_proctitle = yes Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 4

Ubuntu Dovecot 2.2.9 several Errors, Transaction log as well as BUG message
by Kein Name 23 Mar '17

23 Mar '17

Hello List, I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local filesystems and authentication done via mysql backend. Server is a Strato Virtual Server running 2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686 GNU/Linux Sometimes I see errors in the log like this for one user: Error: Transaction log /var/vmail/ example.net/jena/Maildir/.Archives.2017/dovecot.index.log: duplicate transaction log sequence (2) After seeing these, some time later, (mostly 2h), Dovecot starts to deny login from all clients with messages like this: Mar 23 01:32:27 h2312250 dovecot: auth: Error: BUG: Authentication client sent unknown handshake command: REQUEST?1804861441?19318?1?9ce500129289a0237e4e85a6c880a047?session_pid=19323... Mar 23 01:32:27 h2312250 dovecot: imap: Error: Authentication server didn't send valid SPID as expected: MECH#011PLAIN#011plaintext Mar 23 01:32:27 h2312250 dovecot: imap: Error: Disconnected from auth server, aborting (client-pid=19318 client-id=1) Mar 23 01:32:27 h2312250 dovecot: imap-login: Internal login failure (pid=19318 id=1) (internal failure, 1 successful auths): user=< user(a)example.net>, method=PLAIN, rip=X, lip=X, mpid=19323, session=<G9f4AltL4ABRqZ4X> I do not know if these problems have something to do with each other or not. But it happened several times now (maybe once or twice every month or so). When I restart Dovecot, the error seems gone for the moment, until it comes back in a month or some weeks. For reference, here is the running config: dovecot.conf # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab120.11 i686 Ubuntu 14.04.5 LTS auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { quota = maildir:User quota quota_rule = *:bytes=10M sieve = ~/dovecot.sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } ssl_cert = </etc/postfix/sslcert/mailserver.crt ssl_key = </etc/postfix/sslcert/mailserver.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol imap { mail_plugins = quota imap_quota } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = sieve quota postmaster_address = postmaster(a)example.net quota_full_tempfail = yes } dovecot-mysql.conf driver = mysql connect = host=localhost dbname=mail user=user password=XXX default_pass_scheme = CRYPT password_query = SELECT password FROM users WHERE email = '%u' user_query = SELECT CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/') AS home, CONCAT('maildir:/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir/') AS mail, 5000 AS uid, 5000 AS gid, concat('*:bytes=', quota) AS quota_rule FROM users WHERE email = '%u' Any help is appreciated. Thanks Stefan Koenig

2 2

dovecot configuration oops
by Liam Parker 23 Mar '17

23 Mar '17

Hi, I've just transitioned from using courier to dovecot. Thanks for making this possible. During the 'quite simple' transition process, I didn't do much prep as I'm in more of a more of a fix-compile-fix-compile mode rather than a 'read all the docs first' so you may just want to give up now :) If you are still with me, I just wanted to say, it wasn't completely obvious that I needed a password and a user database [PAM not virtual]. Maybe that's just me but anyway, I spent longer than I should have trying to get PAM to work before eventually realising 'internal error check server logs' meant 'where's your user database'. I guess I assumed PAM could cover it all. If you are in to that kind of thing (usability), it might be sensible to have some kind of "basic errors" check during the config file parse phase which picks up stuff like this and points out a more specific error. I did check the logs vigorously and I even turn on every kind of debug_ (to the extent I started getting plain text passwords in the log!) but the 'internal server error check logs' was actually the only log entry for this issue. In case the point is still unclear, I would have spent less time running in the wrong direction if the error message had been "At least one user database must be configured" or some such. I completely understand if your philosophy is "read the manual or suffer the consequences" and it wasn't a complete fail but a simple up front config check could have helped. Thanks for your time today, Kind Regards, Liam

2 1

Understanding quotas
by Robert Moskowitz 23 Mar '17

23 Mar '17

Just to level-set, I am using Centos7-arm which supplies Dovecot 2.2.10. I don't have access to a arm build or mock environment and use what is available (I DID try to install them but had dependency issues). Much of what I have is from campworld, but some I have picked up from other Centos mailserver builders. Also I am using Postfixadmin which provides quotas per user in mysql database. To access those quotas for dovecot, I have the following script: cat <<EOF>/etc/dovecot/dovecot-dict-quota.conf || exit 1 connect = host=localhost dbname=postfix user=postfix password=$Postfix_Database_Password map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } EOF Where $Postfix_Database_Password is an env variable in my install howto. I am setting up quota plugins as follows: sed -i "/#mail_plugins/ a mail_plugins = quota sieve" /etc/dovecot/conf.d/15-lda.conf sed -i "/#mail_plugins / a mail_plugins = quota imap_quota trash" /etc/dovecot/conf.d/20-imap.conf sed -i "/#mail_plugins/ a mail_plugins = quota" /etc/dovecot/conf.d/20-pop3.conf But I am having 'challenges' with how to actually enable quotas and understanding 90-quota.conf. I am starting from campworld's 'reduced' dovecot.conf seeing: dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } and plugin { quota = dict:user::proxy::quotadict acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf sieve_global_path = /home/sieve/globalfilter.sieve sieve = ~/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /home/sieve/ #sieve_extensions = +notify +imapflags sieve_max_script_size = 1M } I have put the sieve plugin lines into the 90-sieve.conf and the acl into 10-acl.conf. Trash is a separate matter for a later question... So I am looking for guidance as to how to integrate the Postfixadmin quota information properly into 90-quota.conf thank you

2 3

Re: replicator crashing - oom
by Daniel Miller 22 Mar '17

22 Mar '17

Think I got it: #0 0x00007fddaf597c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007fddaf59b028 in __GI_abort () at abort.c:89 #2 0x00007fddaf9c0c86 in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:201 #3 0x00007fddaf9c0d6e in i_internal_fatal_handler (ctx=0x7fff7197d000, format=<optimized out>, args=<optimized out>) at failures.c:670 #4 0x00007fddaf958322 in i_panic (format=format@entry=0x7fddafa047b8 "data stack: Out of memory when allocating %lu bytes") at failures.c:275 #5 0x00007fddaf9bee3f in mem_block_alloc (min_size=536870912) at data-stack.c:341 #6 0x00007fddaf9bf08b in t_malloc_real (size=size@entry=536870912, permanent=permanent@entry=true) at data-stack.c:396 #7 0x00007fddaf9bf0ca in t_malloc (size=size@entry=536870912) at data-stack.c:442 #8 0x00007fddaf9da5f8 in pool_data_stack_realloc (pool=<optimized out>, mem=0x7fdd99f59038, old_size=268435449, new_size=536870912) at mempool-datastack.c:126 #9 0x00007fddaf9bcc42 in p_realloc (new_size=<optimized out>, old_size=<optimized out>, mem=<optimized out>, pool=<optimized out>) at mempool.h:88 #10 buffer_alloc (buf=buf@entry=0xf849a8, size=536870912) at buffer.c:36 #11 0x00007fddaf9bcfb4 in buffer_check_limits (data_size=32, pos=268435424, buf=0xf849a8) at buffer.c:75 #12 buffer_write (_buf=0xf849a8, pos=268435424, data=0xfa0420, data_size=32) at buffer.c:187 #13 0x000000000040519b in array_append_i (count=1, data=0xfa0420, array=<synthetic pointer>) at ../../../src/lib/array.h:168 #14 replicator_queue_handle_sync_lookups (user=0xfa3fc0, queue=0xf92260) at replicator-queue.c:278 ---Type <return> to continue, or q <return> to quit--- #15 replicator_queue_push (queue=0xf92260, user=0xfa3fc0) at replicator-queue.c:296 #16 0x00000000004049c2 in dsync_callback (reply=DSYNC_REPLY_OK, state=0xf84590 "AQAAAHX+sC3O3gNSjAoAAOEwx0RQoclMAwAAAAQ", 'A' <repeats 20 times>, "DAAAAEu2cNfSIZk0oMgAAO8QcX0yhyUwDAAAAlg", 'A' <repeats 20 times>, "IAAADFjqMEUPIEU+IlAACdtazLUaHJTAcAAAAI", 'A' <repeats 20 times>, "BwAAAEfYPTqXct9VYRMAAJ21"..., context=0xfa1560) at replicator-brain.c:121 #17 0x00000000004040a8 in dsync_callback (client=0xfa14a0, state=<optimized out>, reply=DSYNC_REPLY_OK) at dsync-client.c:65 #18 0x0000000000404275 in dsync_input_line (line=0xf84988 "+", client=0xfa14a0) at dsync-client.c:132 #19 dsync_input (client=0xfa14a0) at dsync-client.c:153 #20 0x00007fddaf9d47d2 in io_loop_call_io (io=0xfa15a0) at ioloop.c:599 #21 0x00007fddaf9d5d17 in io_loop_handler_run_internal (ioloop=ioloop@entry=0xf8c720) at ioloop-epoll.c:223 #22 0x00007fddaf9d486c in io_loop_handler_run (ioloop=ioloop@entry=0xf8c720) at ioloop.c:648 #23 0x00007fddaf9d4a28 in io_loop_run (ioloop=0xf8c720) at ioloop.c:623 #24 0x00007fddaf961fc3 in master_service_run (service=0xf8c5c0, callback=callback@entry=0x404720 <client_connected>) at master-service.c:641 #25 0x000000000040342a in main (argc=1, argv=0xf8c390) at replicator.c:112 Daniel On 3/22/2017 9:11 AM, Daniel Miller wrote: > Where would I find the core file? I'm not finding anything obvious. > > The replicator path is /usr/local/libexec/dovecot/replicator > > Daniel > > On 3/22/2017 12:52 AM, Aki Tuomi wrote: >> Can you provide us gdb bt full dump? >> >> gdb /usr/libexec/dovecot/replicator /path/to/core >> >> on some systems, it's /usr/lib/dovecot/replicator >> >> Aki >> >> On 21.03.2017 23:48, Daniel Miller wrote: >>> I have the following in my log: >>> >>> Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of >>> memory when allocating 1073741864 bytes >>> Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4638a14322] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x95e3f) [0x7f4638a7ae3f] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x9608b) [0x7f4638a7b08b] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0xb15f8) [0x7f4638a965f8] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(+0x93c42) [0x7f4638a78c42] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x74) >>> [0x7f4638a78fb4] -> dovecot/replicator(replicator_queue_push+0x13b) >>> [0x40519b] -> dovecot/replicator() [0x4049c2] -> dovecot/replicator() >>> [0x4040a8] -> dovecot/replicator() [0x404275] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) >>> [0x7f4638a907d2] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xe7) >>> >>> [0x7f4638a91d17] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) >>> [0x7f4638a9086c] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) >>> [0x7f4638a90a28] -> >>> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) >>> [0x7f4638a1dfc3] -> dovecot/replicator(main+0x17a) [0x40342a] -> >>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) >>> [0x7f4638640ec5] -> dovecot/replicator() [0x4034c5] >>> Mar 21 14:47:00 bubba dovecot: replicator: Fatal: master: >>> service(replicator): child 15650 killed with signal 6 (core dumped) >>>

1 0

Permission denied when logrotating dovecot.log
by Michael Heuberger 22 Mar '17

22 Mar '17

Hello guys Having headaches here how to make logrotation for dovecot log files work. Having permission issues: michael.heuberger@xxx /e/l/daily ❯❯❯ sudo logrotate -fv dovecot.daily ⏎ reading config file dovecot.daily Handling 1 logs rotating pattern: /var/log/dovecot*.log forced from command line (10 rotations) empty log files are rotated, old logs are removed considering log /var/log/dovecot.log error: skipping "/var/log/dovecot.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. This is my current logrotation conf for dovecot: /var/log/dovecot*.log { rotate 10 missingok sharedscripts postrotate doveadm log reopen endscript } And the /var/log folder has these permissions: drwxrwxr-x 12 root syslog 4.0K Mar 19 12:43 log Any clues what's wrong? Thanks Michael -- Binary Kitchen Michael Heuberger 1/33 Parrish Road Sandringham Auckland 1025 (New Zealand) Mobile (text only) ... +64 21 261 89 81 Email ................ michael(a)binarykitchen.com Website .............. http://www.binarykitchen.com

5 9

SIS and mailbox restore
by Jean-Luc Oms 22 Mar '17

22 Mar '17

Still on the problem with dovecot 2.2.27 .... I use the single instance storage, and mdbox format. I use 2 zfs file systems, one for mailboxes, the other for attachements. I use znapzend to generate many zfs snapshots for backup purpose (inode numbers are preserved but it is unusefull). When I try to restore a deleted/purged mailbox with doveadm import I get the error of the first attachement missing in the SIS and the process stops. Option 1: the python script is working but it's really too long. * I restore all the SIS missing files since the snapshot date, preserving hard link count; * I restore the mailbox * I purge all the mailbox to delete the large number of unnecessery files restored Option 2: looking in the list archive I see that doveadm dump can guive me the msg.ext-ref that was missing to my knowledge. I try this use of doveadm dump: doveadm dump /MySnapShot/vmail/user/mdbox/storage/m.* Is this correct to get all the information I need ? I have to write a script to get msg.ext-ref for a particular msf.guid, or a specific mailbox Is there a way with doveadm dump to extract this type of information for a particular mailbox ? Thanks for your support. -- __________________________________________ Jean-Luc Oms STI-RéseauX - LIRMM - CNRS/UM2 161 rue Ada - BAT 4 - CC 477 34095 Montpellier cedex 5 Tel +33 4 67 41 85 93 Urg +33 6 32 01 04 17 __________________________________________

1 0

[Sieve] Is the way to run external script to get attachment?
by Konstantin Shalygin 22 Mar '17

22 Mar '17

Hello. Read all about Extprograms, but have a question. Use case: Every day we have couple messages with attachment (from one sender, this is one-way communication). This attachment is uploads to ownCloud. By hand... need some automation. As I see, pipe cat execute scripts with text data USER/FROM/SUBJECT - and I think with variables it can be any text data, how about attachment? How I see this: script executes and as arg receives from sieve attachment file, or message file and we can parse it for attachment. When we have attachment - upload to ownCloud via RESTapi and purge message. Found some realization for encrypt messages https://github.com/EtiennePerot/gpgit/blob/master/encmaildir.sh but for me more easy just connect to IMAP and do what I want (but I love sieve). Thanks. <http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms>

2 2

Problem with sieve_before
by Ger Hooton Scoil Chroí Íosa Blarney 22 Mar '17

22 Mar '17

Hi All, I cannot get the sieve_before to work. I have dovecot & sieve installed on Debian 7 as follows /etc/dovecot/conf.d/90-sieve.conf : plugin { # The path to the user's main active script. If ManageSieve is used, this the # location of the symbolic link controlled by ManageSieve. sieve = ~/.dovecot.sieve # The default Sieve script when the user has none. This is a path to a global # sieve script file, which gets executed ONLY if user's private Sieve script # doesn't exist. Be sure to pre-compile this script manually using the sievec # command line tool. # --> See sieve_before fore executing scripts before the user's personal # script. sieve_default = /var/lib/dovecot/sieve/default.sieve # Directory for :personal include scripts for the include extension. This # is also where the ManageSieve service stores the user's scripts. sieve_dir = ~/sieve/ # Directory for :global include scripts for the include extension. sieve_global_dir = /var/lib/dovecot/sieve/ # Path to a script file or a directory containing script files that need to be # executed before the user's script. If the path points to a directory, all # the Sieve scripts contained therein (with the proper .sieve extension) are # executed. The order of execution within a directory is determined by the # file names, using a normal 8bit per-character comparison. Multiple script # file or directory paths can be specified by appending an increasing number. sieve_before = /var/lib/dovecot/sieve/before #####sieve_before2 = /var/lib/dovecot/sieve/before/default2.sieve #sieve_before3 = (etc...) # Identical to sieve_before, only the specified scripts are executed after the # user's script (only when keep is still in effect!). Multiple script file or # directory paths can be specified by appending an increasing number. #sieve_after = #sieve_after2 = #sieve_after2 = (etc...) # Which Sieve language extensions are available to users. By default, all # supported extensions are available, except for deprecated extensions or # those that are still under development. Some system administrators may want # to disable certain Sieve extensions or enable those that are not available # by default. This setting can use '+' and '-' to specify differences relative # to the default. For example `sieve_extensions = +imapflags' will enable the # deprecated imapflags extension in addition to all extensions were already # enabled by default. #sieve_extensions = +notify +imapflags ................................. In /var/lib/dovecot/sieve/before I have : drwxrwxrwx 3 mail mail 4096 Mar 20 23:47 .. -rw-rw-rw- 1 root root 195 Mar 21 09:57 default2.svbin -rwxrwxrwx 1 mail mail 157 Mar 21 11:12 default2.sieve default2.sieve is as follows: require ["fileinto"]; if allof (header :matches "subject" "*JUNK*") { fileinto "INBOX.Junk"; } The users personal filters work. Thanks for your help. __________________________________________________ Please consider the environment before printing this email. Ger

3 13

getmail with dovecot delivering problems
by Samuel Reina Calvo 22 Mar '17

22 Mar '17

Hi there, I put together a mail server with postfix+dovecot+mysql with virtual users and it works just fine as internal mail server, but when i put ir under a multidrop email server it sends ok but so far coulnd make getmail to deliver mails correctly. the use of getmail + dovecot downloads email via pop3 but then put all the emails in the same inbox. my maildir is /var/vmail/[domain] getmalirc conf is [retriever]type = MultidropPOP3Retriver server username password envelope_recipient = delivered-to:1 [destination] type = MDA_external path = /usr/local/libexec/dovecot/deliverthen when i run sudo -H -u vmail bash -c 'getmail -g /etc/.getmail -r /etc/.getmail/getmailrc' i get all the time all the messages delivered into /var/vmail/vmail (being vmail the linux user who handles my virtual users) __________ Información de ESET NOD32 Antivirus, versión de la base de firmas de virus 14929 (20170213) __________ ESET NOD32 Antivirus ha comprobado este mensaje. http://www.eset.com

2 1

last_login LDAP - killed with signal 11 (core dumped)
by Leon Kyneur 22 Mar '17

22 Mar '17

Hi I am trying to configure the last_login plugin with LDAP dictionary which is causing dict service to crash. Not sure if this is a bug or some configuration parameter I'm getting wrong? Running latest dovecot but was having the same problem in earlier version 2.2.25 # dovecot --version 2.2.28 (bed8434) I have configured dovecot like so: dovecot.conf (before conf.d/*.conf: dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext lastlogin = ldap:/etc/dovecot/dovecot-ldap-dict.conf.ext } conf.d/10-master.conf service dict { # If dict proxy is used, mail processes should have access to its socket. # For example: mode=0660, group=vmail and global mail_access_groups=vmail unix_listener dict { mode = 0660 user = vmail group = vmail } } conf.d/20-imap.conf: protocol imap { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins last_login # Maximum number of IMAP connections allowed for a user from each IP address. # NOTE: The username is compared case-sensitively. #mail_max_userip_connections = 10 } 90-plugins.conf plugin { #setting_name = value #last_login_dict = proxy::lastlogin last_login_dict = proxy:dict:lastlogin zlib_save = gz zlib_save_level = 6 } dovecot-ldap-dict.conf.ext: uri = ldap://ldap.internal bind_dn = cn=Manager,dc=mail,dc=com password = XXXX tls = no debug = 1 map { pattern = last-login/$user filter = (&(mail=%{user})(objectClass=mailUser)) # the () is required base_dn = o=domains,dc=mail,dc=com username_attribute = mail value_attribute = lastLoginTime fields { mail=$user } } I don't see dovecot ever making a connection to the LDAP server I've configured in the dovecot-ldap-dict.conf.ext file. Log shows ==> /var/log/dovecot.log <== Mar 22 07:49:30 imap-login: Info: Login: user=<leon(a)mail.com>, method=PLAIN, rip=X.X.X.X, lip=X.X.X.X, mpid=36105, secured, session=<o0Lu/0xL4N3LhgGR> Mar 22 07:49:30 dict: Fatal: master: service(dict): child 36107 killed with signal 11 (core dumped) Mar 22 07:49:30 imap(leon(a)mail.com): Error: dict-client: Commit may have failed: Connection closed (reply took 0.015 secs) Mar 22 07:49:30 imap(leon(a)mail.com): Error: last_login_dict: Write was unconfirmed (timeout or disconnect) for user leon(a)mail.com Backtrace: # gdb /var/core/36107 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... [New LWP 36107] Reading symbols from /usr/libexec/dovecot/dict...Reading symbols from /usr/lib/debug/usr/libexec/dovecot/dict.debug...done. done. Missing separate debuginfo for Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/b0/07fede01895dec1aca9d8b8993fe27d70a3a20 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/dict'. Program terminated with signal 11, Segmentation fault. #0 0x0000000000000000 in ?? () (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00007fbcf11bd04f in cmd_begin (cmd=0x7fbcf2c02910, line=<optimized out>) at dict-commands.c:365 trans = 0x7fbcf2c029a0 id = 1 #2 0x00007fbcf11bdef8 in dict_command_input (conn=conn@entry=0x7fbcf2bf24d0, line=line@entry=0x7fbcf2bf48cb "B1") at dict-commands.c:625 cmd_func = 0x7fbcf13c85c0 <cmds+32> cmd = 0x7fbcf2c02910 ret = <optimized out> #3 0x00007fbcf11bc6ee in dict_connection_input_more (conn=0x7fbcf2bf24d0) at dict-connection.c:117 _data_stack_cur_id = 3 line = 0x7fbcf2bf48cb "B1" ret = <optimized out> #4 0x00007fbcf11bc7d2 in dict_connection_input (conn=0x7fbcf2bf24d0) at dict-connection.c:167 line = <optimized out> conn = 0x7fbcf2bf24d0 #5 0x00007fbcf0d1b2d2 in io_loop_call_io (io=0x7fbcf2bf2890) at ioloop.c:599 ioloop = 0x7fbcf2be0740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #6 0x00007fbcf0d1c95f in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7fbcf2be0740) at ioloop-epoll.c:223 ctx = 0x7fbcf2beded0 events = <optimized out> list = 0x7fbcf2bf28f0 io = <optimized out> tv = {tv_sec = 2147483, tv_usec = 0} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #7 0x00007fbcf0d1b36c in io_loop_handler_run (ioloop=ioloop@entry=0x7fbcf2be0740) at ioloop.c:648 No locals. #8 0x00007fbcf0d1b528 in io_loop_run (ioloop=0x7fbcf2be0740) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #9 0x00007fbcf0ca4603 in master_service_run (service=0x7fbcf2be05e0, callback=callback@entry=0x7fbcf11be150 <client_connected>) at master-service.c:641 No locals. #10 0x00007fbcf11bbff9 in main (argc=1, argv=0x7fbcf2be0390) at main.c:161 set_roots = {0x7fbcf13c88a0 <dict_setting_parser_info>, 0x0} error = 0x0

2 3

Help
by Bhushan Bhosale 22 Mar '17

22 Mar '17

Hello, I'm getting below error in /var/log/dovecot-proxy.log. Please help. Thanks in advance. Mar 21 14:40:36 tejas3 dovecot: director: Error: Director 192.168.1.11/in disconnected: Connection closed: Illegal seek (connected 0 secs, in=0 out=43, handshake ME not received Regards, Bhushan

2 1

dovecot POP3 log shows too many identical RETR entries
by Bappasaheb Nirmal 22 Mar '17

22 Mar '17

Hello, Dovecot log is showing too many POP3 RETR entries which are identical lines. I also suspect that it is causing high pop traffic eating most of the network bandwidth. Here are some of the lines out of 11009 in a day. Such pattern is observed only for few users. dovecot version is 2.1.17. ============== Mar 20 00:00:07 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:07 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=26645, secured, session=<5CGrmRlLyAAr861h> Mar 20 00:00:10 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:11 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=29932, secured, session=<k6/gmRlL3gAr861h> Mar 20 00:00:12 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:13 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=26819, secured, session=<3DX6mRlLUQAr861h> Mar 20 00:00:14 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:15 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=9636, secured, session=<x5ghmhlLjwAr861h> Mar 20 00:00:16 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:17 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4585, secured, session=<8Yw+mhlL0AAr861h> Mar 20 00:00:18 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:18 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=30049, secured, session=<UsJOmhlLmAAr861h> Mar 20 00:00:19 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:20 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=9636, secured, session=<B6VimhlLNgAr861h> Mar 20 00:00:20 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:20 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4584, secured, session=<pVpxmhlLPwAr861h> Mar 20 00:00:21 pi3 dovecot: pop3(user(a)example.com): Disconnected: Logged out top=0/0, retr=1/64014, del=0/1429, size=478762716 Mar 20 00:00:23 pi3 dovecot: pop3-login: Login: user=<user(a)example.com>, method=PLAIN, rip=43.243.173.97, lip=192.168.1.18, mpid=4585, secured, session=<MlGam ============== What could be the possible reason? Thanks, Bappasaheb

2 2

Crash on doveadm index
by Larry Rosenman 22 Mar '17

22 Mar '17

http://www.lerctr.org/~ler/dovecot/doveadm-2017-03-20.txt doveconf –n attached and at: http://www.lerctr.org/~ler/dovecot/doveconf.n.txt -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 4

Is it possible to use sieve when delivering via pipe to the dovecot deliver command ?
by Thomas Carrié 21 Mar '17

21 Mar '17

Hello, I am using Exim with this delivery configuration: virtual_delivery: driver = pipe command = /usr/lib/dovecot/deliver -d $local_part@$domain -f ... I have enabled manage-sieve and uploaded a simple sieve script that I can see on the server. man page of /usr/lib/dovecot/deliver says it supports sieve. Mail debug is enabled: $ dovecot -n | grep debug mail_debug = yes Delivering a mail shows only this line in dovecot log: Jan 21 17:38:51 myserver dovecot: lda(joe(a)something.com): msgid=<20170121183537.7313f219@homenetwork>: saved mail to INBOX According to page http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting#Sieve_Scripts_are… I should have a log saying that the sieve plugin is loaded Here is the sieve relevant parts of dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf ... plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } ... protocols = " imap sieve pop3 sieve" ... protocol lda { mail_plugins = " sieve" } Is there a requirement to use delivery via service (unix socket) so that sieve is enabled? Or is there a configuration thing I forgot ? Thank you for your help Thomas

2 2

Re: Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

Now I'm seeing a bunch of these: 02:28 bubba dovecot: dsync-local(user(a)mydomain.com): Error: bzlib.read(/var/mail/mydomain.com/user/mdbox/storage/m.20): corrupted data at 24123649 Mar 21 11:02:28 bubba dovecot: dsync-local(user(a)mydomain.com): Error: dsync(oldserver.host): read(zlib(/var/mail/mydomain.com/user/mdbox/storage/m.20)) failed: read(/var/mail/mydomain.com/user/mdbox/storage/m.20) failed: bzlib.read(/var/mail/mydomain.com/user/mdbox/storage/m.20): corrupted data at 24123649 (last sent=mail, last recv=mail_request (EOL)) Mar 21 11:02:28 bubba dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Error: dsync(localhost): read() failed: read((fd)) failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) Daniel On 3/20/2017 11:30 PM, Daniel Miller wrote: > I'm getting close - I believe I have one-way replication processing > now. It's amazing watching the mails magically appear in the new > server! I'll tender some updates to the wiki in the hopes it will > help others. > > At this time, I have two errors I haven't been able to eliminate with > config changes: > > dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Warning: > Transaction log file > /var/mail/mydomain.com/user/sdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log > was locked for 109 seconds (rotating while syncing) > Mar 20 23:22:04 bubba dovecot: dsync-local(user(a)mydomain.com): Error: > Remote command returned error 75: ssh -lvmail 192.168.0.4 doveadm > dsync-server -uuser(a)mydomain.com > > I don't know if the transaction lock issue will fix itself via > repeated replication runs. But I have no idea what the "error 75" is. > > Daniel > > > On 3/20/2017 10:05 PM, Daniel Miller wrote: >> I have an existing server using mdbox & sis. There is a quantity of >> corruption - I have no idea where it came in. I'd had a previous >> rebuild some years ago and I thought I had a clean datastore. By >> "corruption" I mean missing attachments and either missing or >> mixed-up emails. >> >> I've setup a new server on a virtual machine. Instead of copying the >> old configs I hand-adjusted individual settings using the current >> distribution example. The new server is running...but empty. >> >> So now my intent is to migrate the mail to the new machine. A few >> items to note: >> 1. The existing mail server is the virtual host. The mails are >> stored locally, in mdbox format, with sis enabled. And possibly zlib. >> 2. The new server, via VirtualBox, is presently configured for >> Maildir. I may change to sdbox - I'm now a little reserved about mdbox. >> 3. Instead of storing the mails within the virtual machine, I'm >> using the host's drive. This is via an exported NFS4 folder from the >> host, mounted on the guest, using the options: >> "auto,noatime,hard,intr,async,nordirplus". >> 4. My intent is to have the new virtual server become the primary >> mail server. The mail store will continue to be accessed by NFS4. No >> other servers or processes (besides backup) should access the mail >> store. >> >> So...my question is what is the best method for the migration? >> >> Reading the docs on Dovecot replication I'm still very unsure of how >> to implement it - particularly the "master-master" or "master-client" >> relationships. The docs are not 100% clear on which server gets >> which options. I can guess...which I'd really rather not do. But it >> seems to me getting one-way replication working would be the most >> "elegant" solution here. >> >> Manual dsync is also an option - but again I'm not on which machine I >> should execute which options. >> >> Imapsync is a possibility and the syntax is clear - but very slow in >> execution for 100k mails. >> >> Any suggestions or pointers would be welcome. >>

1 0

New Member
by Ger Hooton Scoil Chroí Íosa Blarney 21 Mar '17

21 Mar '17

Hi All, Before I start posting where /how can I check to see if the question I wish to ask about has already been covered? __________________________________________________ Please consider the environment before printing this email. Ger

3 2

Re: Dovecot can't connect to openldap over starttls [REQUEST OF OPENLDAP]
by info＠gwarband.de 21 Mar '17

21 Mar '17

Can sombody say something about this request? This is an email from the openldap-technical mailinglist from openldap. Systemdetails are mention in the other email. -------- Originalnachricht -------- Betreff: Re: Dovecot can't connect to openldap over starttls Datum: 2017-03-20 16:18 Absender: Dan White <dwhite(a)cafedemocracy.org> Empfänger: info(a)gwarband.de Kopie: openldap-technical(a)openldap.org On 03/20/17 16:06 +0100, info(a)gwarband.de wrote: >> Debug Dovecot's implementation of ldap_start_tls_s(). > I don't have any idea how to set a higher debug level to dovecot. In > my opinion I have the highest. So I can't deliver a greater log. I recommend consulting Dovecot's advice on how to run a debugger, or dig into the code which calls libldap.

2 8

doveadm-sync stateful
by Cédric ML 21 Mar '17

21 Mar '17

Hello, I'm trying to migrate mail accounts from an old server to a new one. As I need to migrate dozens of accounts which take about 1G each, I need to do stateful sync to make my migration in two times : 1 - I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1(a)olddomain.fr sync -s "" -R -1 -u user1(a)newdomain.fr imapc: > /tmp/firstsync.log 2>&1 my accounts are synced, and I get a "state" string (AQAAAHm4+Jk=) as the output of doveadm sync command. 2 - Changes are made on the old server, and I expect next dsync will sync only the changes / new mails. So I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1(a)olddomain.fr sync -s "AQAAAHm4+Jk=" -R -1 -u user1(a)newdomain.fr imapc: > /tmp/secondsync.log 2>&1 My problem is that state of messages are not synchronized (mails marked as read on old server are still unread on new server, mails moved on a folder on the old server are still in the INBOX of new server). The full debug of ran commands is available here : http://fpaste.scsys.co.uk/557551 The result of "doveconf -n" is available here : http://fpaste.scsys.co.uk/557552 I'm using version 2.2.27 Can anyone tell me if I'm doing something wrong ? How can I debug more ? Regards, Cédric

2 2

Re: Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

I'm getting close - I believe I have one-way replication processing now. It's amazing watching the mails magically appear in the new server! I'll tender some updates to the wiki in the hopes it will help others. At this time, I have two errors I haven't been able to eliminate with config changes: dovecot: doveadm: Error: dsync-remote(user(a)mydomain.com): Warning: Transaction log file /var/mail/mydomain.com/user/sdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log was locked for 109 seconds (rotating while syncing) Mar 20 23:22:04 bubba dovecot: dsync-local(user(a)mydomain.com): Error: Remote command returned error 75: ssh -lvmail 192.168.0.4 doveadm dsync-server -uuser(a)mydomain.com I don't know if the transaction lock issue will fix itself via repeated replication runs. But I have no idea what the "error 75" is. Daniel On 3/20/2017 10:05 PM, Daniel Miller wrote: > I have an existing server using mdbox & sis. There is a quantity of > corruption - I have no idea where it came in. I'd had a previous > rebuild some years ago and I thought I had a clean datastore. By > "corruption" I mean missing attachments and either missing or mixed-up > emails. > > I've setup a new server on a virtual machine. Instead of copying the > old configs I hand-adjusted individual settings using the current > distribution example. The new server is running...but empty. > > So now my intent is to migrate the mail to the new machine. A few > items to note: > 1. The existing mail server is the virtual host. The mails are > stored locally, in mdbox format, with sis enabled. And possibly zlib. > 2. The new server, via VirtualBox, is presently configured for > Maildir. I may change to sdbox - I'm now a little reserved about mdbox. > 3. Instead of storing the mails within the virtual machine, I'm using > the host's drive. This is via an exported NFS4 folder from the host, > mounted on the guest, using the options: > "auto,noatime,hard,intr,async,nordirplus". > 4. My intent is to have the new virtual server become the primary > mail server. The mail store will continue to be accessed by NFS4. No > other servers or processes (besides backup) should access the mail store. > > So...my question is what is the best method for the migration? > > Reading the docs on Dovecot replication I'm still very unsure of how > to implement it - particularly the "master-master" or "master-client" > relationships. The docs are not 100% clear on which server gets which > options. I can guess...which I'd really rather not do. But it seems > to me getting one-way replication working would be the most "elegant" > solution here. > > Manual dsync is also an option - but again I'm not on which machine I > should execute which options. > > Imapsync is a possibility and the syntax is clear - but very slow in > execution for 100k mails. > > Any suggestions or pointers would be welcome. >

1 0

Corruption & migration
by Daniel Miller 21 Mar '17

21 Mar '17

I have an existing server using mdbox & sis. There is a quantity of corruption - I have no idea where it came in. I'd had a previous rebuild some years ago and I thought I had a clean datastore. By "corruption" I mean missing attachments and either missing or mixed-up emails. I've setup a new server on a virtual machine. Instead of copying the old configs I hand-adjusted individual settings using the current distribution example. The new server is running...but empty. So now my intent is to migrate the mail to the new machine. A few items to note: 1. The existing mail server is the virtual host. The mails are stored locally, in mdbox format, with sis enabled. And possibly zlib. 2. The new server, via VirtualBox, is presently configured for Maildir. I may change to sdbox - I'm now a little reserved about mdbox. 3. Instead of storing the mails within the virtual machine, I'm using the host's drive. This is via an exported NFS4 folder from the host, mounted on the guest, using the options: "auto,noatime,hard,intr,async,nordirplus". 4. My intent is to have the new virtual server become the primary mail server. The mail store will continue to be accessed by NFS4. No other servers or processes (besides backup) should access the mail store. So...my question is what is the best method for the migration? Reading the docs on Dovecot replication I'm still very unsure of how to implement it - particularly the "master-master" or "master-client" relationships. The docs are not 100% clear on which server gets which options. I can guess...which I'd really rather not do. But it seems to me getting one-way replication working would be the most "elegant" solution here. Manual dsync is also an option - but again I'm not on which machine I should execute which options. Imapsync is a possibility and the syntax is clear - but very slow in execution for 100k mails. Any suggestions or pointers would be welcome. -- Daniel

1 0

Re: Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Joseph Tam 21 Mar '17

21 Mar '17

Sami Ketola writes: >> Can anyone with Solr installed confirm/refute this: does installing >> Solr keep iOS clients from roofing the connection count? > > I doubt it, but since IMAP SEARCH goes all the way down to the backends > mail_max_userip_connections can be used to limit the number of > connections. Understood -- that's the current situation I'm in now. Our iOS users would launch a search resulting in a connection burst, hit the connection cap, log out all IMAP sessions out, then start the cycle again. This sometimes lasts for 10's of minutes. I'm not sure what the users sees. Sample logs entries: Mar 19 01:21:30 server dovecot: imap-login: Login: user=<user> ... [... 14 similar logins removed ...] Mar 19 01:21:41 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:42 server dovecot: imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=16) : user=<user> ... Mar 19 01:21:42 server dovecot: imap(user): Logged out in=425 out=1107 [... 14 similar logouts removed ...] Mar 19 01:21:42 server dovecot: imap(user): Logged out in=382 out=1107 Mar 19 01:21:42 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:42 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:43 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:44 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1173 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1155 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1166 Mar 19 01:21:44 server dovecot: imap(user): Logged out in=442 out=1174 Mar 19 01:21:44 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:47 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:47 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:48 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:48 server dovecot: imap-login: Login: user=<user> ... Mar 19 01:21:49 server dovecot: imap-login: Login: user=<user> ... { ... and on and on for the next 10 minutes ... } However, there is a pause between each login that might be long enough to squeeze the search results in if given quickly enough. From the I/O stats, most of these searches have empty results. It probably won't prevent the connection cap problem, but it might minimize the length and severity of these connection storms. Of course, the real fix is for iOS mail-app developers to stop assuming the IMAP server is owned exclusively by the user by configuring some reasonable connection throttles. Joseph Tam <jtam.home(a)gmail.com>

2 1

Dovecot can't connect to openldap over starttls
by info＠gwarband.de 20 Mar '17

20 Mar '17

Hello guys, actually I'm trying to configure dovecot to access openldap for passwordcheck. My openldap is only allow access over "secure ldap". The dovecot can communicate with the openldap server but there is maybe a failure in the sslhandshake. Additional information you can find in the logs or in the dump below. Also I have my ldap config from dovecot in the links below. I have already created an bug reporting in the system of openldap but the answer was to get support from her. All datalinks: https://gwarband.de/openldap/dovecot.log https://gwarband.de/openldap/dovecot-ldap.conf https://gwarband.de/openldap/openldap.log https://gwarband.de/openldap/trace.dump The bugreportinglink from openldap: http://www.openldap.org/its/index.cgi/Incoming?id=8615 I hope you can help me. Regards. Tobias Warband

2 10

Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
by Ralf Hildebrandt 20 Mar '17

20 Mar '17

Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set: ssl_client_ca_file = </etc/ssl/certs/ca-certificates.crt But I'm still getting the error above. I addition, dovecot is crashing with SIGSEGV: Mar 20 13:28:23 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Mar 20 13:28:23 mproxy dovecot: auth: Error: imapc(email.charite.de:993): No SSL context Mar 20 13:28:23 mproxy dovecot: auth: Error: imap(la***sch,87.77.180.61): Disconnected from server Mar 20 13:28:23 mproxy postfix/submission/smtpd[32682]: warning: zb43d.pia.fu-berlin.de[87.77.180.61]: SASL PLAIN authentication failed: Connection lost to authentication server Mar 20 13:28:23 mproxy dovecot: auth: Fatal: master: service(auth): child 32685 killed with signal 11 (core dumped) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 5

doveadm proxy password
by Angel L. Mateo 20 Mar '17

20 Mar '17

Hi, I'm configuring a proxy host to connect to backend servers. As proxy is done based on an LDAP attribute of the user, I'm not using director. In the proxy server I have configured: doveadm_port = 24245 doveadm_password = secret And in the backend: service doveadm { inet_listener { port = 24245 } } local <mynetwork> { doveadm_password = secret } But when I run a doveadm command in the proxy I get: amateo_adm@musio10:/etc/dovecot/conf.d$ sudo doveadm quota get -u amateo(a)um.es doveadm(amateo(a)um.es): Error: doveadm authentication failed () doveadm(amateo(a)um.es): Error: myotis50.um.es:24245: Command quota get failed for amateo(a)um.es: EOF Quota name Type Value Limit % And in the backed I get: Mar 20 15:52:01 myotis50 dovecot: doveadm: Error: doveadm client authenticated with wrong password I have checked with tcpdump and in the command is sending the base64 encoding of "doveadmsecret" Any help? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

1 0

Re: Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Joseph Tam 20 Mar '17

20 Mar '17

Adi Pircalabu writes: > For us it is, we're periodically getting hammered by iOS devices that > try to open 300+ simultaneous IMAP connections for a single user from > the same IP, while the average hovers usually below 50 for the busier > mailboxes with many folders. Oh yeah, I've seen this. I think this happens when someone does a global pattern search, which causes the client to launch IMAP SEARCH commands on each and every mailbox. I've wondered whether installing Solr would alleviate this: it wouldn't directly address the connection limit problem, but perhaps it can return results fast enough to keep the concurrent connections count down. Can anyone with Solr installed confirm/refute this: does installing Solr keep iOS clients from roofing the connection count? Joseph Tam <jtam.home(a)gmail.com>

2 1

Mail restore and single storage attachement
by Jean-Luc Oms 20 Mar '17

20 Mar '17

Bonjour, I'm finishing the upgrade of an old installation of Dovecot/postfix mail system for my lab. In the configuration i plan ( dovecot 2.2.27 ), i choose to use: - mdbox format - single storage for attachements - 2 zfs file systems, one for mdboxes, the other for attachments The last tests before production concern my hability to restore a lost mail (or mailbox) ... (lot of changes when you are used to mbox format). 1) I uses doveadm import to restore part of mail from one of the zfs snapshot with a cde like: doveadm -Dv import -U bof2 -s -u bof2 mdbox:/mailpool/lirmm/.zfs/snapshot/zfs-auto-snap_frequent-2017-03-15-1645/vmail/bof2/mdbox Recup-AAAA mailbox AAAA I get this error: doveadm(bof2): Error: open() failed with file /mailpool/lirmm/.zfs/snapshot/zfs-auto-snap_frequent-2017-03-15-1645/vmail/bof2/mdbox/mailboxes/AAAA/dbox-Mails/dovecot.index.log: Read-only file system Thats right, my snapshot is ro, but why the import has to write to the source ? I'm missing something ? 2) I don't find any way to specify a source for attachements with the import command, then I first restore all the atachements from one snapshot, then make import, then purge. Is there a way to use a source for attachement file tree, or a command to find the mssing files for the import command ? Thanks -- __________________________________________ Jean-Luc Oms STI-RéseauX - LIRMM - CNRS/UM2 161 rue Ada - BAT 4 - CC 477 34095 Montpellier cedex 5 Tel +33 4 67 41 85 93 Urg +33 6 32 01 04 17 __________________________________________

1 1

Deploying Diffie-Hellman for TLS
by Jerry 20 Mar '17

20 Mar '17

I have been reading up on TLS and Dovecot and came across this URL: https://www.weakdh.org/sysadmin.html which recommended these settings for Dovecot. I would like to know if they are correct? Some much documentation on the web is pure garbage. Dovecot These changes should be made in /etc/dovecot.conf Cipher Suites ssl_cipher_list=ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_prefer_server_ciphers = yes (Dovecot 2.2.6 or greater) DH parameters #regenerates every week ssl_dh_parameters_length = 2048 Contrary to what the site recommends, I would have thought that changes should be made in the "10-ssl.conf" file. I am running "Dovecot 2.2.28" on a FreeBSD-11 machine with OpenSSL 1.0.2k, if that makes any difference. Thanks -- Jerry

2 1

Server migration
by Gandalf Corvotempesta 20 Mar '17

20 Mar '17

Hi to all. It's time to migrate an old server to a newer platform Some questions: 1) what happens by changing the pop3/IMAP server on the client? Is the client (Outlook, Thunderbird,...) smart enough to not download every message again? I'm asking this because the easier way to migrate would be move all mailboxes to the new server and then change the hostname on the client 2) what if I add a dovecot proxy on the new server, proxing back all requests to the older one, if the mailbox is still not migrated? Would the whole pop3/IMAP transaction happen through the proxy or there is something an http redirect (or anything similiar to the SIP protocol) ? 3) I think the response to this is no: is dovecot able to log the hostname used for the connection? I have multiple domains pointing to the same IP. Something like the Host header in Http.

2 1

[Bug] Mailbox aliases still broken
by azurit＠pobox.sk 20 Mar '17

20 Mar '17

Hi, about an year ago i was reporting a bug in mailbox aliases, which remains unfixed and unasnwered (probably totally ignored, don't understand why). I thought it was because the bug is old and already fixed but yesterday i upgraded to Dovecot 2.2.24 and problem persists. Here is the original report, everything, except the Dovecot version, is still correct: http://dovecot.org/list/dovecot/2015-June/101176.html Will this be fixed? Thanks for info. azur

4 7

dovecot problem with ssl
by Nilton Jose Rizzo 19 Mar '17

19 Mar '17

Hi all, I already searched for this error on google and nothing I never install dovecot, this is a first time. This error, I know, is too newbie and stupid, but I checked more than twice. root@server:/usr/local/etc/dovecot # sievec /home3/virtual/default.sieve doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-ssl.conf line 7: Unknown setting: ssl root@server:/usr/local/etc/dovecot # I'm running a FreeBSD 12-current and compile all from ports (mysql, dovecot2, portfix3.1, and all needs ports, but this error don't leave. I'm fowling this tutorial to install all, but when I'll run a sievec this stop with this error. I'm not new in FreeBSD, I'm have good experience in FreeBSD. --- /************************************************* **Nilton José Rizzo UFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **************************************************/

4 11

replication issues between to nodes
by Remko Lodder 18 Mar '17

18 Mar '17

Hi, Some time ago I posted the below but never got a reponse that I could work with. So i am retrying now in the hope that there might be a better idea/suggestion on how to approach this. Situation; I have two nodes, which should replicate to eachother. My main machine receives most mail and the other one receives mostly system messages and should get replicated. (This used to be delivered on both machines, but given the issues below I had to make sure that the customer email at least arrives on machine A, as detailed below). When a mail arrives on main machine (A) everything is fine and things are synchronised asap. Customers can see the email directly via webmail/imap. When a mail arrives on the secondary machine (B) the replication is not issued until machine A starts a sync session. Customers do not see the email on machine A via webmail/imap. When a mail arrives on A, the synchronisation occurs, and all messages on B, not yet on A, are synchronised as well. Customers can now see the email on machine A as well via webmail/imap. Sadly this can mean that emails that became visible are hours late (read: were delivered hours before, but not visible for the customer). Both machines are configured through puppet, only individual settings like IP addresses and certificates are different because well, they have to. I included the difference below, and both ‘doveconf -n’s. If someone has a suggestion on seeing why machine B is not issueing (or does not seem to issue) replication, let me know. I verified that I can connect to the remote machines via IPv4 and IPv6 (for doveadm / replication purposes). Difference between configurations; --- tmp1.txt 2017-03-18 15:18:41.000000000 +0100 +++ tmp2.txt 2017-03-18 15:18:56.000000000 +0100 @@ -55,7 +55,7 @@ imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size - mail_replica = tcps:mail.jr-hosting.nl:12346 + mail_replica = tcps:mail2.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve @@ -105,7 +105,7 @@ } service lmtp { inet_listener lmtp { - address = XXX/X 127.0.0.1 ::1 + address = YYYY/Y 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { @@ -123,8 +123,8 @@ mode = 0666 } } -ssl_ca = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/fullchain.pem -ssl_cert = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/cert.pem +ssl_ca = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/fullchain.pem +ssl_cert = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 Machine A (the best working machine) # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 11.0-RELEASE-p8 amd64 auth_mechanisms = plain login disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it haproxy_trusted_networks = XXXX/X lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " quota notify replication" 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 imapsieve namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcps:mail2.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)jr-hosting.nl protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -N -l 60 -U replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service doveadm { inet_listener { port = 12346 ssl = yes } } service imap-login { inet_listener imap_haproxy { haproxy = yes port = 10143 } inet_listener imaps_haproxy { haproxy = yes port = 10144 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { address = XXXX/X 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_ca = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/fullchain.pem ssl_cert = </usr/local/etc/letsencrypt/live/mail.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = quota sieve postmaster_address = postmaster(a)jr-hosting.nl } protocol lda { mail_plugins = " quota notify replication sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota notify replication imap_quota imap_sieve” } Machine B: # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 11.0-RELEASE-p8 amd64 auth_mechanisms = plain login disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it haproxy_trusted_networks = XXX/X lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_debug = yes mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " quota notify replication" 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 imapsieve namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcps:mail.jr-hosting.nl:12346 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)jr-hosting.nl protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -N -l 60 -U replication_max_conns = 100 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service doveadm { inet_listener { port = 12346 ssl = yes } } service imap-login { inet_listener imap_haproxy { haproxy = yes port = 10143 } inet_listener imaps_haproxy { haproxy = yes port = 10144 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { address = XXXX/X 127.0.0.1 ::1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_ca = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/fullchain.pem ssl_cert = </usr/local/etc/letsencrypt/live/mail2.jr-hosting.nl/cert.pem ssl_client_ca_file = /usr/local/certificates/letsencrypt-ca.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { auth_username_format = %n mail_plugins = quota sieve postmaster_address = postmaster(a)jr-hosting.nl } protocol lda { mail_plugins = " quota notify replication sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota notify replication imap_quota imap_sieve” }

1 0

sievec
by Robert Moskowitz 17 Mar '17

17 Mar '17

I am building a new mailserver on Centos7. My sieve is created with: mkdir /home/sieve cat <<EOF>/home/sieve/globalfilter.sieve || exit 1 require "fileinto"; if exists "X-Spam-Flag" { if header :contains "X-Spam-Flag" "NO" { } else { fileinto "Spam"; stop; } } if header :contains "subject" ["***SPAM***"] { fileinto "Spam"; stop; } EOF chown -R vmail:mail /home/sieve But in 90-sieve.conf there is the comment: # A path to a global sieve script file, which gets executed ONLY # if user's private Sieve script doesn't exist. Be sure to # pre-compile this script manually using the sievec command line # tool. #sieve_global_path = /var/lib/dovecot/sieve/default.sieve Do I run sievec on this script? And I found the following comment on a blog, about 3 years old: 2: Having a user-defined sieve script will cancel out the global script for redirecting spam. In the dovecot.conf, get rid of the sieve_global_path and sieve_global_dir, and instead use: sieve_before = /path/to/global.sieve -- what this will do is make sure that the global script runs before any user scripts, which allows the spam redirecting to actually work. What is current situation on this? thank you

4 8

Do I need to configure director?
by Angel L. Mateo 17 Mar '17

17 Mar '17

Hi, I'm configuring a farm of dovecot proxies redirecting users to backend servers. The decision of which backend server is used for a user is based in its ldap account information. In my previous configuration I was using an inherited director configuration in these proxy servers, but now I was wondering that because the decision is made according to user information, I don't need to run director. Do it? Is there any advantage of running director in this scenario? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 2

Replication Troubles
by Wolfgang Hennerbichler 16 Mar '17

16 Mar '17

Hi Dovecot Users, I’ve configured dovecot dsync replication and I see troubles in the logs and get user complaints which I can’t explain. I found similar threads on this mailinglist, but I couldn’t find a solution anywhere. Does anybody have dsync running without problems on a high volume mailserver? I see the following logs, examples given: Feb 17 18:16:49 dovecot dovecot: imap(zoechi): Warning: /var/mail/zoechi/dovecot-uidlist: Duplicate file entry at line 10395: 1487350019.M138380P28563.dovecot.wogri.at,S=18930,W=19377 (uid 41092 -> 41093) - retrying by re-reading from beginning with this one I’m not sure - it might be that this is completely OK because due to replication UIDs clash. Maybe that’s OK, but I couldn’t find a confirmation. Feb 17 18:16:49 dovecot dovecot: imap(zoechi): Warning: Maildir /var/mail/zoechi: Expunged message reappeared, giving a new UID (old uid=41092, file=1487350019.M138380P28563.dovecot.wogri.at,S=18930,W=19377) This one is definitely a problem, deleted messages re-appear in the mailbox. I made sure that the 2 hosts doing replication have different hostnames. I run 2.2.27 (from debian-jessie backports). Config below. Thanks for hints (or pointers to other example configs where dsync works without problems) # dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.8.14 x86_64 Debian 8.7 ext4 auth_verbose = yes debug_log_path = /var/log/dovecot.debug doveadm_password = # hidden, use -P to show it first_valid_gid = 106 first_valid_uid = 104 hostname = localhost last_valid_gid = 106 last_valid_uid = 104 mail_gid = dovecot mail_location = maildir:/var/mail/%n mail_plugins = quota fts fts_lucene virtual notify replication mail_temp_dir = /var/lib/dovecot/tmp mail_uid = dovecot 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 editheader namespace { list = children location = virtual:/var/mail/%n/virtual prefix = virtual. separator = . } namespace inbox { inbox = yes list = yes location = mailbox "Deleted Messages" { auto = subscribe special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = . subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { default_language = de fts = lucene fts_lucene = whitespace_chars=@. mail_replica = tcp:172.16.1.1:12345 quota = maildir:User quota quota_rule = *:storage=5G quota_rule2 = Trash:storage=+200M quota_rule3 = Spam:ignore quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = /etc/sieve/%n.sieve sieve_default = /etc/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +editheader } pop3_deleted_flag = $POP3Deleted postmaster_address = postmaster(a)wogri.at protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { user = dovecot } unix_listener replication-notify { user = dovecot } } service doveadm { inet_listener { port = 12345 } } service imap { process_limit = 1024 } service lmtp { inet_listener lmtp { port = 2003 } unix_listener lmtp { user = dovecot } user = dovecot } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service pop3 { process_limit = 1024 } service quota-warning { executable = script /usr/local/sbin/quota-warning.sh unix_listener quota-warning { user = dovecot } user = dovecot } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl = required ssl_cert = </etc/dovecot/server.cert.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = quota sieve virtual notify replication } protocol lda { mail_plugins = quota fts fts_lucene virtual notify replication sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota fts fts_lucene virtual notify replication imap_quota } protocol pop3 { mail_plugins = quota fts fts_lucene virtual notify replication } local 2a00:XXX::/64 { doveadm_password = # hidden, use -P to show it }

3 4

Timeout Leak
by Luciano Mannucci 16 Mar '17

16 Mar '17

Hello all, I've got 3 occurences of this message in my log file: auth: Warning: Timeout leak: 0x805e480 (auth-request-handler.c:550) Can I ignore it, or is it a syhmptom of something wrong? I'm running dovecot 2.2.28 (bed8434). I'll post my doveconf -n if it is worth investigating further... Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

2 2

'doveadm who' behind nginx mail proxy
by Edgaras Lukoševičius 16 Mar '17

16 Mar '17

Hello, we have configured nginx to work as mail proxy for backend dovecot servers. Dovecot servers behind nginx proxy are showing internal nginx ip address for every client when running 'doveadm who' instead of showing real client IP addresses. Is is possible to configure this setup to show real client IP addresses when running 'doveadm who' on internal dovecot servers or to configure nginx to show which user-ip pairs are proxied to which servers?

1 0

LDAP locking problems - home related
by Ganael Laplanche 16 Mar '17

16 Mar '17

Hi list, # dovecot --version 2.2.13 We use Dovecot LDA and I've discovered lots of messages stating that lock files cannot be written: Mar 16 12:02:03 mailhost dovecot: lda(someuser): Error: file_dotlock_open(/home/sg/someuser/.dovecot.lda-dupes) failed: No such file or directory That user's home directory is fetched from LDAP and does not exist locally on our 'mailhost' machine, so those error messages do make sense; I would like to fix that situation. In our current Dovecot configuration, only mail_location is set: mail_location = maildir:/var/mail/%u I would like to ignore the erroneous 'home' attribute fetched from LDAP and specify a common mail_home, i.e. set: mail_home = /var/mail/%u/home but if I understand correctly, that global mail_home configuration directive would still be overridden by the LDAP 'home' attribute fetched from passdb: [...] pass_attrs = supannAliasLogin=user,userPassword=password,\ homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid [...] Can I just remove homeDirectory from pass_attrs to skip fetching 'home' from LDAP and then set the global mail_home ? Also, if that works: We would switch from a situation where a home is set (but wrong) to one where it becomes valid. Can there be any side-effect in that case (apart from fixing locking problems) ? Finally, will mail_home (leaf) directory be created if it does not exist yet (parent directory exists) ? Best regards, -- Ganael Laplanche <ganael.laplanche(a)centralesupelec.fr> Unix Systems Engineer @CentraleSupelec Rennes

1 1

Dovecot 2.2.27 proxy - enforcing per client IP connection limits
by Adi Pircalabu 16 Mar '17

16 Mar '17

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 2.6.32-642.4.2.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 5 mins auth_cache_size = 16 M auth_cache_ttl = 18 hours default_client_limit = 6120 default_process_limit = 500 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +notify +imapflags } protocols = imap pop3 lmtp sieve service auth { client_limit = 6120 } service imap-login { process_limit = 2048 process_min_avail = 20 service_count = 0 vsz_limit = 256 M } service imap { process_limit = 2048 } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 vsz_limit = 128 M } service managesieve { process_limit = 1024 } service pop3 { process_limit = 1024 } [...] protocol imap { imap_capability = IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE mail_max_userip_connections = 50 } -- Adi Pircalabu

3 6

Postfix Ignoring lmtp, delivering straight to maildir
by Doug Barton 16 Mar '17

16 Mar '17

First I'd like to thank all the developers and contributors to dovecot. I've been using it for many years, and deeply appreciate your fine work. :) dovecot --version 2.2.22 (fe789d2) I have a working installation with postfix and dovecot, and I want to add sieve to it, so I am trying to configure postfix to use lmtp instead of 'virtual' for its delivery service. However it is ignoring that request, and for every message I get "status=sent (delivered to maildir)" and it shows up in my Inbox. On my mail host I have 1 normal user, let's say the username is 'myuser'. I have postfix configured to accept mail for several different domains, and each domain has a lot of different mail usernames (I use this for mailing lists and such). I use the virtual_maps feature of postfix, and have a map file that looks like this: abuse(a)dougbarton.us myuser hostmaster(a)dougbarton.us myuser dougb(a)dougbarton.us myuser ... All of this works great, and mail for all the different usernames and domains gets delivered into my one real user's Maildir, and I can see the mail with my IMAP clients. I've configured sieve in dovecot, and I can see the socket for lmtp in /var/spool/postfix/private/. I can also see the managesieve port in netstat, and I can use a sieve client to connect to it and edit scripts, etc. So according to all the tutorials I've read my next step is this in postfix' main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp which I did, and postfix restarts with no errors. But, it seems to avoid lmtp altogether, and as I mentioned above it delivers straight to my Maildir Inbox every time. I do have a sieve file, and the ~/dovecot.sieve symlink exists. I created a very simple filter: require ["fileinto", "imap4flags"]; if header :contains "Subject" "test" { fileinto "Junk"; } which my sieve client says is correct syntax. Still no joy. :-/ Any thoughts or suggestions are welcome. (And sorry this is so long, but based on my extensive searches it seems my configuration is a bit unique, so I explained it in some length.) Doug

3 5

Backing Up and Restoring mailboxes
by Jerry 15 Mar '17

15 Mar '17

I am going to be wiping clean my system and doing a complete upgrade. I have dovecot installed. I want to back up the mail system, and then be able to restore it. I thought that I could do this. doveadm -Dv backup -u user(a)example.com maildir:~/DoveBU Then I was going to gunzip that directory and put it onto a USB Drive. Now, after updating the system, I thought that I could just unzip the file from the USB drive. My question is, what command do I run to return the files to the same place they were originally. Assuming the structure was: "/var/mail/vmail/", what would I do? Thanks -- Jerry

1 0

FW: Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Never mind, I am stupid and did not read all available information. Needed to change permissions on /var/mail/* Thank You, Ken Z -----Original Message----- From: Ken Zachreson Sent: Wednesday, March 15, 2017 10:28 AM To: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Subject: Unable to create needed folders Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

Unable to create needed folders
by Ken Zachreson 15 Mar '17

15 Mar '17

Greetings, The log reports that a process cannot create the needed folders. Please review and tell me what I have done wrong. dovecot 2.0.9 # 2.0.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:85: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 2.6.32-642.15.1.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_mechanisms = plain login last_valid_gid = 520 last_valid_uid = 520 mail_location = mbox:~/mail/:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = dovecot driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } } service pop3-login { inet_listener pop3s { address = * } } ssl_ca = /etc/pki/tls/certs/gd_bundle-g2-g1.crt ssl_cert = </etc/pki/tls/certs/c1e209e3ca2e1e5.crt ssl_key = </etc/pki/tls/private/gcrcnet.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xv%08Xu } ERROR Message from log Mar 15 10:14:03 MultiTronic6 dovecot: imap-login: Login: user=<wifi.adm>, method=LOGIN, rip=xx.xx.xx.xx, lip=yy.yy.yy.yy, mpid=5973, TLS Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: chown(/home/wifi.adm/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=504(wifi.adm), group based on /var/mail/wifi.adm) Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Error: mkdir(/home/wifi.adm/mail/.imap/INBOX) failed: Operation not permitted Mar 15 10:14:03 MultiTronic6 dovecot: imap(wifi.adm): Connection closed bytes=39/423 Thank You, Ken Zachreson IT Manager, Grand Canyon Resort Corp 928-769-2629 928-769-2638 Help Desk

1 0

autocreate ONLY for new Users
by plataleas 15 Mar '17

15 Mar '17

Hi All We are currently migrating accounts to Dovecot. The existing accounts do have special folders with different names. (i.e. sent, sent-mail) The autocreate-function of "special folders" is useful. However we need this feature ONLY for new users. The existing accounts have a mapping for their own "special folders". There are discussions about this topic on the mailing list: /http://www.dovecot.org/list/dovecot/2014-August/097313.html https://dovecot.org/list/dovecot/2016-May/104296.html/ Did someone manage to implement this ? Are there workarounds? Thanks and regards plataleas

3 6

Custom cache_key for passdb-sql
by Tom Sommer 15 Mar '17

15 Mar '17

The cache_key for the SQL-passdb should be created automatically, but for some reason the service (%s) is not part of the key, and I need it to be I've tried to set a manual cache_key, but that fails: Mar 15 11:54:02 auth: Fatal: sql /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: Can't open configuration file /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip}: No such file or directory passdb { args = /etc/dovecot/dovecot-sql.conf cache_key=%s%u%{real_ip} driver = sql } Is this not possible? -- Tom

1 0

welcome plugin
by David Mehler 14 Mar '17

14 Mar '17

Hello, If anyone is using the welcome plugin in dovecot 2.2.x to sent a one-time new welcome email to new users can I get a look at your configuration? I'm stuck, I create a user and the welcome action does not execute. If you've got a script to send the mail can I get a look at that as well? Thanks. Dave.

3 2

Users with extra mailbox: namespace/mailbox in userdb lookup?
by MRob 14 Mar '17

14 Mar '17

Hello, We have a need for some users to have an additional folder created and subscribed for them. Is is possible to return an override for the default "namespace inbox" containing the needed mailbox definitions in the userdb lookup for such users? If so, how would the userdb lookup result be formatted? Presumably as just one long string, but how would the setting be named given there can't be a space in it? Can I replace the space with an underscore, e.g. userdb_namespace_inbox = '{ mailbox Drafts { auto=subscribe special_use = \Drafts } mailbox Trash { auto=subscribe special_use = \Trash } }' Or is there some other way to do this?

4 11

strange behaviour of dovecot
by Masaharu Kawada 14 Mar '17

14 Mar '17

Dear dovecot-list, Dovecot gives the below error messages and those errors go away after running 'systemctl restart dovecot'(Restarting dovecot service)', however, the same happens after a while later(like after 300 mails delivered). --- master : Error : service(anvil) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(log) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(ssl-params) : Initial Status notification no received in 30 seconds, killing the process master : Error : service(log) : child 3703 killed with signal 9 --- then the log process is not there so that no mail log gets captured in maillog: --- root 28036 0.0 0.0 19864 1604 ? Ss 11:45 0:00 /usr/sbin/dovecot -F dovecot 28074 0.0 0.0 9312 1000 ? S 11:46 0:00 dovecot/anvil root 28075 0.0 0.0 12324 2084 ? S 11:46 0:00 dovecot/config --- Does this have something to do with any limitation in dovecot configuration? If anyone in the list ever has similar or same experience, please give me a clue that shows where to look at from here. Thanks, -- Masaharu Kawada

2 2

Solr 6.4.2
by Daniel Miller 14 Mar '17

14 Mar '17

For those trying Solr - version 6.4.2 fixed a number of bugs in the 6.4.x series. Speed is incredible. If you haven't tried it - I strongly recommend it! And, using the included installation script (with Solr) combined with my schema - installation was painless. I'm now running in single core mode without issues (running in cloud mode with a single core seemed silly anyway). -- Daniel

1 0

Re: First time setting up Director Woes
by Jesse C. Smillie 13 Mar '17

13 Mar '17

Working again. Explains a lot actually. Inital box I was experimenting on PAM was already setup and had worked. That error I got caught up in was with SSSD and PAM wasn't working. Fixing the error shot myself in the foot in other ways. Thank you! -Jesse C. Smillie On 3/13/17 4:38 PM, Aki Tuomi wrote: >> On March 13, 2017 at 10:21 PM "Jesse C. Smillie" <jsmillie(a)gatewayk12.org> wrote: >> >> >> I'm trying to setup our first director server. Trying to keep the >> initial config simple really as just maybe a proof of concept and its >> got me pulling my hair out today. Initially I just tried to convert one >> of my already running IMAP servers to be a director just to see if I >> could do it. I modified the configs as it appeared they needed based on: >> >> https://wiki2.dovecot.org/Director >> http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy >> >> But it didn't work. Kept serving files locally instead of proxing off >> to the servers listed. > Remove this: > >> passdb { >> driver = pam >> } > Aki

1 0

First time setting up Director Woes
by Jesse C. Smillie 13 Mar '17

13 Mar '17

I'm trying to setup our first director server. Trying to keep the initial config simple really as just maybe a proof of concept and its got me pulling my hair out today. Initially I just tried to convert one of my already running IMAP servers to be a director just to see if I could do it. I modified the configs as it appeared they needed based on: https://wiki2.dovecot.org/Director http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy But it didn't work. Kept serving files locally instead of proxing off to the servers listed. -----------------------------------------------------------------------------------------------==== Mar 13 15:58:27 fugitoid dovecot: imap-login: Login: user=<makaveli>, method=PLAIN, rip=10.0.15.114, lip=10.1.12.221, mpid=3022, TLS, session=<YCCCIqJKmMIKAA9y> Mar 13 15:58:27 fugitoid dovecot: imap(makaveli): Error: User initialization failed: Namespace '': mkdir(/home/makaveli/Maildir) failed: Permission denied (euid=2605(makaveli) egid=1100(<unknown>) missing +w perm: /home, dir owned by 0:0 mode=0755) Mar 13 15:58:27 fugitoid dovecot: imap: Error: Invalid user settings. Refer to server log for more information. Thinking it was just something with that box (still running Dovecot 2.2.10 as well) I moved on to setup a new Centos7 server and go through the setup again and initially it was working for a few hours. -----------------------------------------------------------------------------------------------==== Mar 13 12:19:03 fugitoid dovecot: imap-login: proxy(makaveli): started proxying to 10.1.12.228:993: user=<makaveli>, method=PLAIN, rip=10.0.15.114, lip=10.1.12.221, TLS, session=<CzfaEZ9KXgAKAA9y> Then at some point I got side tracked by a pam error message and when I came back from working that out Dovecot was trying to authenticate users locally again. I really feel like I'm missing something here, but for the life of me I can't figure it out. Any ideas would be welcome. Thanks. # 2.2.28 (bed8434): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.10.2.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login default_client_limit = 1024 director_mail_servers = 10.1.12.229 10.1.12.228 10.1.12.225 director_servers = 10.1.12.221:9090 mail_fsync = always mail_nfs_storage = yes mbox_write_locks = fcntl 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 } passdb { args = proxy=y nopassword=y ssl=any-cert driver = static } protocols = imap service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imaps { port = 993 ssl = yes } } ssl = required ssl_ca = </etc/GoDaddy_SSL/gd_bundle.crt ssl_cert = </etc/GoDaddy_SSL/gatewayk12.cert ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = TLSv1 TLSv1.1 TLSv1.2 userdb { driver = passwd }

2 1

change mdbox rotation size?
by Dave McGuire 13 Mar '17

13 Mar '17

Hey folks. Is it possible/advisable to change the mdbox rotation size on an operational mdbox spool? If so, is there any way to "repackage" (for the lack of a better term) an existing mdbox spool to a different rotation size? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

1 0

Dict protocol changes string
by Nagy, Attila 13 Mar '17

13 Mar '17

Hi, I use pass and userdb with dict protocol in a similar way: key passdb { key = passdb^MAuth-User: %u^MAuth-Pass: %w^MAuth-Protocol: %s^MClient-IP: %r format = json } (^M is an \r character, inserted with vi CTRL-v + enter) Until 2.2.24 this has worked, but 2.2.25 seems to convert that ASCII 13 into an ASCII 1 and an "r". Python printout from what I get with 2.2.25: 'Lshared/passdb\x01rAuth-User: user\x01rAuth-Pass: pass\x01rAuth-Protocol: pop3\x01rClient-IP: 1.2.3.4' Is this change intentional? Why?

2 4

dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled)
by Basdove 13 Mar '17

13 Mar '17

Hi. Always the below log appraring log under /var/log/mail.log Is this right or How to resolve it. Ubuntu 16.04.2 LTS server edition Mar 13 06:13:20 home dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) Mar 13 06:13:30 home postfix/master[1495]: daemon started -- version 3.1.0, configuration /etc/postfix dovecot -n output -------------------------------------------------------------------- # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-64-generic x86_64 Ubuntu 16.04.2 LTS auth_mechanisms = plain login mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap pop3" service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_ca = >/etc/ssl/certs/01.pem ssl_cert = </etc/ssl/certs/cacert.pem ssl_key = </etc/ssl/private/cakey.pem ssl_key_password = # hidden, use -P to show it ssl_protocols = TLSv1 ssl_verify_client_cert = yes userdb { driver = passwd } ---------------------------------------------------------- Thanhs & Regards Baskaranand

2 1

I’m slightly shocked
by dovecot 11 Mar '17

11 Mar '17

Hey! Just take a look at that crazy stuff, I'm slightly shocked! Here it is http://web.wacinema.com/6869 Yours, dovecot

1 0

virtual all mails folder in dovecot
by Rahul Singh Badyal 11 Mar '17

11 Mar '17

I have Centos 7 mail server installed with dovecot and postfix with MariaDB. I am trying to add a virtual All Mails folder for every user so that they can have all mails such as inbox, sent in a single folder, something like gmail. Please help me for this. *Regards,* *Rahul*

2 1

(no subject)
by Rahul Singh Badyal 11 Mar '17

11 Mar '17

I have Centos 7 mail server installed with dovecot and postfix with MariaDB. I am trying to add a virtual All Mails folder for every user so that they can have all mails such as inbox, sent in a single folder, something like gmail. Please help me for this. *Regards,* *Rahul*

1 0

new article
by dovecot 11 Mar '17

11 Mar '17

Hi, There is an article I've written recently and I wanted to hear your thoughts about it, please read it here http://example.wowcinema.com/6f6e Best regards, dovecot

1 0

v2.2.28 released
by Timo Sirainen 10 Mar '17

10 Mar '17

http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache caching decisions. * Expunging mails writes GUID to dovecot.index.log now only if the GUID is quickly available from index/cache. * pop3c: Increase timeout for PASS command to 5 minutes. * Mail access errors are no longer ignored when searching or sorting. With IMAP the untagged SEARCH/SORT reply is still sent the same as before, but NO reply is returned instead of OK. + Make dovecot.list.index's filename configurable. This is needed when there are multiple namespaces pointing to the same mail root (e.g. lazy_expunge namespace for mdbox). + Add size.virtual to dovecot.index when folder vsizes are accessed (e.g. quota=count). This is mainly a workaround to avoid slow quota recalculation performance when message sizes get lost from dovecot.index.cache due to corruption or some other reason. + auth: Support OAUTHBEARER and XOAUTH2 mechanisms. Also support them in lib-dsasl for client side. + auth: Support filtering by SASL mechanism: passdb { mechanisms } + Shrink the mail processes' memory usage by not storing settings duplicated unnecessarily many times. + imap: Add imap_fetch_failure setting to control what happens when FETCH fails for some mails (see example-config). + imap: Include info about last command in disconnection log line. + imap: Created new SEARCH=X-MIMEPART extension. It's currently not advertised by default, since it's not fully implemented. + fts-solr: Add support for basic authentication. + Cassandra: Support automatically retrying failed queries if execution_retry_interval and execution_retry_times are set. + doveadm: Added "mailbox path" command. + mail_log plugin: If plugin { mail_log_cached_only=yes }, log the wanted fields only if it doesn't require opening the email. + mail_vsize_bg_after_count setting added (see example-config). + mail_sort_max_read_count setting added (see example-config). + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension even though it's advertised. - Index files: day_first_uid wasn't updated correctly since v2.2.26. This caused dovecot.index.cache to be non-optimal. - imap: SEARCH/SORT may have assert-crashed in client_check_command_hangs - imap: FETCH X-MAILBOX may have assert-crashed in virtual mailboxes. - imap: Running time in tagged command reply was often wrongly 0. - search: Using NOT n:* or NOT UID n:* wasn't handled correctly - director: doveadm director kick was broken - director: Fix crash when using director_flush_socket - director: Fix some bugs when moving users between backends - imapc: Various error handling fixes and improvements - master: doveadm process status output had a lot of duplicates. - autoexpunge: If mailbox's rename timestamp is newer than mail's save-timestamp, use it instead. This is useful when autoexpunging e.g. Trash/* and an entire mailbox is deleted by renaming it under Trash to prevent it from being autoexpunged too early. - autoexpunge: Multiple processes may have been trying to expunge the same mails simultaneously. This was problematic especially with lazy_expunge plugin. - auth: %{passdb:*} was empty in auth-worker processes - auth-policy: hashed_password was always sent empty. - dict-sql: Merge multiple UPDATEs to a single statement if possible. - fts-solr: Escape {} chars when sending queries - fts: fts_autoindex_exclude = \Special-use caused crashes - doveadm-server: Fix leaks and other problems when process is reused for multiple requests (service_count != 1) - sdbox: Fix assert-crash on mailbox create race - lda/lmtp: deliver_log_format values weren't entirely correct if Sieve was used. especially %{storage_id} was broken. - lmtp_user_concurrency_limit didn't work if userdb changed username

6 7

Maildirsize not updated
by chaouche yacine 08 Mar '17

08 Mar '17

Hello dovecot Problem : maildirsize and dovecot quota get have different values dovecot version : 2.2.13 happens with : some mailboxes This issue happens only to some mailboxes and only for a specific period of time until maildirsize gets updated by something (not me). I can't reproduce this now because it happened this morning and now its 2 PM and the problem is gone (maildirsize was updated). Anybody experienced the same situation ? -- Yassine.

3 6

iOS Mail app and rapid authenticate / disconnect on Dovecot proxy
by Robert Giles 07 Mar '17

07 Mar '17

Hi folks, I have a handful of iOS 10.2.1 Mail app IMAP clients that intermittently break into this unexplained authenticate-then-immediately-disconnect behavior when connecting to a RHEL7 Dovecot (dovecot-2.2.10-7.el7) proxy, providing proxied connections to a backend Panda/UW-IMAP server. From talking to the users, the activity would appear to be spontaneous (ie: not caused by user interaction with the device). The behavior doesn't seem to have any observable implications for the end user, other than momentarily hitting the Dovecot process_limit (which, if not raised to a rather large number, disrupts new IMAP proxy connections momentarily). I reckon this is not an issue with Dovecot, but I'm curious to know if other folks have observed this behavior when dealing with iOS Mail app clients? The log entries look like this: iOS 10 device = 172.16.0.1 RHEL7 Dovecot proxy host = 192.168.0.1 ("proxyhost") Panda/UW-IMAP target = panda.imap.tld Mar 6 12:11:00 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<VvzqehVKhwBCol00> Mar 6 12:11:00 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by client): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS: Disconnected, session=<VvzqehVKhwBCol00> Mar 6 12:11:01 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<jaXxehVKiABCol00> Mar 6 12:11:01 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<jaXxehVKiABCol00> Mar 6 12:11:01 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<RmX4ehVKiQBCol00> Mar 6 12:11:01 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<RmX4ehVKiQBCol00> Mar 6 12:11:02 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<inYBexVKigBCol00> Mar 6 12:11:02 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<inYBexVKigBCol00> Mar 6 12:11:02 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<GwAJexVKiwBCol00> Mar 6 12:11:02 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<GwAJexVKiwBCol00> Mar 6 12:11:03 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<asUPexVKswBCol00> Mar 6 12:11:03 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<asUPexVKswBCol00> Mar 6 12:11:03 proxyhost dovecot: imap-login: proxy(jdoe): started proxying to panda.imap.tld:993: user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<n9YYexVKjQBCol00> Mar 6 12:11:04 proxyhost dovecot: imap-login: proxy(jdoe): disconnecting 172.16.0.1 (Disconnected by server): user=<jdoe>, method=PLAIN, rip=172.16.0.1, lip=192.168.0.1, TLS, session=<n9YYexVKjQBCol00> ...and on and on, usually until the 'service imap-login' process_limit is reached. You could naturally apply some iptables rate-limiting to avoid hitting process_limit, but it'd be nice to have the iOS client simply behave properly instead. dovecot -n: --- # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.2.el7.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.3 (Maipo) auth_mechanisms = plain login auth_verbose = yes first_valid_uid = 1000 imap_capability = +I18NLEVEL=1 mbox_write_locks = fcntl passdb { args = nopassword=y default_fields = proxy=y ssl=any-cert host=panda.imap.tld driver = static } protocols = imap pop3 service imap-login { process_limit = 400-ish at the moment process_min_avail = 2 } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_ca = </etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem ssl_cert = <proxyhost.crt ssl_dh_parameters_length = 2048 ssl_key = <proxyhost.key ssl_protocols = !SSLv3 !SSLv3 ssl_require_crl = no userdb { driver = static } --- Thanks for any insight out there. Robert Giles

1 0

SiS hashes file ?
by Sai Kiran Gummaraj 07 Mar '17

07 Mar '17

Hello, In mdbox SiS POSIX mail box setting - There are hard-links under - <mail_attachment_dir>/ha/sh/<hash>-<guid-1> <mail_attachment_dir>/ha/sh/<hash>-<guid-2> Why is a copy of the file kept under hashes/<hash> ? -- Regards, Sai Kiran

1 0

Transitioning away from mail_location = maildir:~
by Chris Stankevitz 06 Mar '17

06 Mar '17

Hi, I have been using this setup for years: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~ I have since learned that mail_home and mail_location should be different. I plan to use this: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~/mail I would like the transition to be transparent for my email clients. I don't want mail/directories/sieve_scripts to disappear. 1. Should I manually create the maildir:~/mail directories? 2. Should I move files from /var/mail/vhosts/%d/%n into maildir:~/mail? Which files? (In other words: which files are "home directory" files and which files are "mail files"?) Thank you, Chris Example home directory: drwx------ . drwxr-xr-x .. drwx------ .Archives drwx------ .Archives.2016 drwx------ .Archives.2017 drwx------ .Drafts drwx------ .Junk drwx------ .Notes drwx------ .Sent drwx------ .Sent drwx------ .Trash drwx------ .work drwx------ .home drwx------ .todo lrwx------ .dovecot.sieve -rw------- .dovecot.sieve.log -rw------- .dovecot.sieve.log.0 -rw------- .dovecot.svbin drwx------ cur -rw------- dovecot-keywords -rw------- dovecot-uidlist -rw------- dovecot-uidvalidity -r--r--r-- dovecot-uidvalidity.55411048 -rw------- dovecot.index -rw------- dovecot.index.cache -rw------- dovecot.index.log -rw------- dovecot.mailbox.log drwx------ new drwx------ sieve -rw------- subscriptions drwx------ tmp $ dovecot -n # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 10.3-RELEASE-p11 amd64 lmtp_save_to_detail_mailbox = yes mail_gid = 1002 mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~ mail_privileged_group = vpostfix mail_uid = 1002 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 { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { recipient_delimiter = - sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve recipient_delimiter = - service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = xxx ssl_key = xxx userdb { args = username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = " sieve" postmaster_address = xxx } protocol lda { mail_plugins = " sieve" }

5 6

quota-warning: possible to have size also?
by dovecot＠avv.solutions 06 Mar '17

06 Mar '17

Hello Community, My dovecot setup works fine with quotas and quota-warning. I have a questions though: when running the warning script, the example foundis it possible to pass the *quota size *as argument also? This would be useful with per-user quota. e.g. /some/script xx% username *xxxbytes* (order is not relevant of course) Thank you for your help. Cheers

4 4

dovecot 2.2.x listening on multiple interfaces
by David Mehler 06 Mar '17

06 Mar '17

Hello, I'm wondering if it's possible to get dovecot to listen on multiple interfaces without designating * for everything? I've got a machine with three interfaces going to three different networks. I'm not wanting to let dovecot listen on all interfaces * just two of them, standard ports. Is this doable? Thanks. Dave.

2 1

Upgrade from 2.0. to 2.2
by Jakob Curdes 06 Mar '17

06 Mar '17

Hello, we have a centos 6 server running dovecot 2.0 provided with the OS, currently 2.0.9. We would like to upgrade to the 2.2.19 package provided by the mailserver.guru repo. I read the upgrading docs for 2.1 and 2.2 and found the following issues: 2.0 - 2.1: - define namespace inbox or delete 15-mailboxes.conf (we do not "care about special use mailboxes") - plugins and UTF-8: we do not use one of the listed plugins - to allow mixed usernames set auth_username_format to "nothing" - solr backend: not used in our setup - expire plugin: not used - dsync: not used 2.1 - 2.2 - fts-solr: not used (?) - autocreate: not used - other changes: trivial or not used Are there other things that we need to observe? Is a direct update from 2.0.9 to 2.2.19 feasible with the above precautions or do we need to put in a 2.1 version in between? Thank you for hints, Jakob

4 6

welcome plugin
by David Mehler 06 Mar '17

06 Mar '17

Hello, Is anyone using the welcome plugin? I'm trying to utilize it to send a message when a user first logs in to the system, containing important information for them to know. The plugin loads, I don't have a configuration problem, but the message never gets sent. What can I provide to more easily troubleshoot this? Thanks. Dave.

3 5

[enhancement] fts-solr low performance
by azurit＠pobox.sk 05 Mar '17

05 Mar '17

Hi, we have activated fts-solr about a week ago and immediately started to experience really *low* performance with MOVE and EXPUNGE commands. After several days of googling, tcpdumping and straceing i was able to find and resolve the problem. We are using Dovecot 2.2.27 from Debian Jessie (jessie-backports), which is doing a soft commit in solr after every MOVE or EXPUNGE command - this behavior cannot be, currently, changed. The problem is that this was causing every MOVE/EXPUNGE to take about 6 seconds to complete. The problem appears to be in very old version of Solr - 3.6.2 (!!). This is the only version which is shipped with current (Jessie) and also next (Stretch) version of Debian, don't ask my why, i don't understand it either. Solr versions below 4.0 are NOT supporting soft commits, so all commits are hard and this was the problem. Finally, i decided to patch our Dovecot to not send a commit at all and everything started to be super fast. I'm doing hard commits every minute via cron so the only consequence of this is that you cannot search for messages delivered before less then a minute (which you, usually, don't need to do anyway). While googling i also find out that Solr supports autoCommit function (and from version 4.0 also autoSoftCommit), so there's no reason for Dovecot to handle this on it's own (and potentially doing hundreds or thousands of soft commits every second) - you can just set Solr to, for example, do autoSoftCommit every second and autoCommit every minute: https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConf… Also this wiki page should be updated with warning about old versoins of Solr not supporting soft commits (you could also mention the auto[Soft]Commit function): http://wiki2.dovecot.org/Plugins/FTS/Solr I suggest to allow completely disable Solr commits in Dovecot by configuration, so people like me can handle this easily. What do you think? azur

1 0

fts_solr and connection via https://
by Jan Vonde 04 Mar '17

04 Mar '17

Hi, I am trying to get fts_solr working and my index server is available via HTTPS only. Dovecot is running on a Debian Jessie system and the Solr server has a letsencrypt certificate. My dovecot version is: 2.2.devel (a9ed8ae) The current setup is: 10-mail.conf: mail_plugins = fts fts_solr 90-fts.conf: plugin { fts = solr fts_autoindex = yes fts_solr = url=https://foo.example.com/solr/dovecot/ } When I try to index the mailboxes I am getting error messages like this: doveadm(user@host): Error: fts_solr: Lookup failed: 9002 Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) doveadm(user@host): Error: Mailbox INBOX: Status lookup failed: Internal error occurred. Refer to server log for more information. [2017-01-22 09:52:38] Segmentation fault Contacting the index server via curl on the command line on the same host works, it returns HTTP 200: user@host ~ $ curl -s -o /dev/null -w "%{http_code}" https://foo.example.com/solr/ 200 user@host ~ $ Currently I have the following ssl related settings: user@host ~ $ doveconf -n -P | grep -i ssl ssl_cert = </etc/ssl/certs/mail.example.org.crt ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/ssl/private/mail.example.org.key ssl_protocols = !SSLv2 !SSLv3 I tried adding the following settings but that didn't help: ssl_ca = < /etc/ssl/certs/ca-certificates.crt ssl_client_ca_dir = /etc/ssl/certs Can you give me a hint how I can get the ssl certificate accepted? Thanks in advance and have a nice day, Jan :-)

2 10

mdbox Inconsistency in map index
by bOnK 04 Mar '17

04 Mar '17

After a (power)crash two accounts have been corrupted. I tried to rescue things by running force-resync multiple times, but that didn't work out. Searching the archives, I found a recent suggestion (by Timo) to delete the index files, but I'm not sure which files to delete and what the consequences will be. When I deleted ``storage/dovecot.map.index'' in an unimportant account of my own, things only grew worse and I decided to delete the account and start fresh... Something I obviously don't want to do with the other account as it belongs to a client with about 2.5G mails (856 m.* files), which we don't want to lose. I have observed the following behavior in the logs: When a new mail arrives: (The second line below is always the same, however there's no mail with uid 12819 according to doveadm search uid 12819) Mar 04 11:43:28 lda(user): Warning: mdbox /var/mail/user/storage: Inconsistency in map index (117,1060 != 117,1883660) Mar 04 11:43:28 lda(user): Error: Log synchronization error at seq=117,offset=1546660 for /var/mail/user/storage/dovecot.map.index: Extension record inc drops number below zero (uid=12819, diff=-1, orig=0) Mar 04 11:43:28 lda(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:43:28 lda(user): Info: msgid=<d760229d563e99dc787acd0746b18b31(a)feedback.1dayfly.net>: saved mail to INBOX Mar 04 11:43:28 lda(user): Warning: mdbox /var/mail/user/storage: Inconsistency in map index (117,1060 != 117,1883784) Mar 04 11:43:28 lda(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:43:28 lda(user): Warning: mdbox /var/mail/user/storage: rebuilding indexes Mar 04 11:43:28 lda(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:43:28 imap(user): Error: /var/mail/user/mailboxes/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent Mar 04 11:43:28 imap(user): Info: IMAP session state is inconsistent, please relogin. in=2011 out=108358 deleted=0 expunged=0 trashed=0 When user logs in next (might be from another box/MUA) Mar 04 11:44:36 imap-login: Info: Login: user=<user>, method=PLAIN, rip=82.95.XX.XX, lip=37.97.XX.XX, mpid=14884, TLS, session=<VfvML+ZJuO9SX18R> Mar 04 11:44:37 imap(user): Warning: mdbox /var/mail/user/storage: Inconsistency in map index (117,1060 != 117,1884336) Mar 04 11:44:37 imap(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:44:37 imap(user): Warning: mdbox /var/mail/user/storage: rebuilding indexes Mar 04 11:44:37 imap(user): Error: /var/mail/user/mailboxes/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent Mar 04 11:44:37 imap(user): Info: IMAP session state is inconsistent, please relogin. in=331 out=178391 deleted=0 expunged=0 trashed=0 Mar 04 11:44:37 imap(user): Warning: mdbox /var/mail/user/storage: Inconsistency in map index (117,1060 != 117,1884396) Mar 04 11:44:37 imap(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:44:37 imap(user): Warning: fscking index file /var/mail/user/storage/dovecot.map.index Mar 04 11:44:37 imap-login: Info: Login: user=<user>, method=PLAIN, rip=82.95.XX.XX, lip=37.97.XX.XX, mpid=14886, TLS, session=<AUTbL+ZJuu9SX18R> Besides the nuisance of getting kicked of every time a new mail arrives, user cannot delete mails (as in: move to Trash). TL;DR: which files to delete and what will be the consequences? -- b.

1 0

letsencrypt
by David Mehler 04 Mar '17

04 Mar '17

Hello, I know some users here are using letsencrypt for their CA. If this is to off topic write me privately. I'm wanting letsencrypt to take over as my CA, replacing existing self signed certificates. I've got web working, a certificate for https sites and one for webmail as they have different names. What I'm now wanting to do is get letsencrypt going for my email setup, the smtp handled by postfix, but mail, and imap I believe are handled by dovecot. With the web it was easy just let apache serve the token that letsencrypt needed and I got certificates. How do I do this with regards email? I hope that's clear. Any help appreciated. Thanks. Dave.

8 9

Re: letsencrypt
by Joseph Tam 04 Mar '17

04 Mar '17

> Thanks. Is there another way of doing this? I've got a web server > running on 80 and 443. Are there any other options? I'm getting this list in digest mode, so it's possible by the time this gets to you, I will have repeated someone else' suggestion. In this situation, where your dovecot server lives on the same host as a web server (wembail?), and this web server is already going certificate renewal, then just change the certificate to use SNI extension and add all LS services that live on this host. (This does not count as a cert renewal, but a new cert). (E.g. if you are using a certbot to get a certifiticate for "webmail.mydomain", then add "pop3.mydomain", "imap.mydomain" and "smtp.mydomain" to the certificate.) Your web server will have to virtually host those domains for the purposes of mapping the token pickup folder. Then you can use the same certificate for all TLS services hosted on that server. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: letsencrypt
by Joseph Tam 03 Mar '17

03 Mar '17

David Mehler <dave.mehler(a)gmail.com> writes: > I'm wanting letsencrypt to take over as my CA, replacing existing self > signed certificates. I've got web working, a certificate for https > sites and one for webmail as they have different names. What I'm now > wanting to do is get letsencrypt going for my email setup, the smtp > handled by postfix, but mail, and imap I believe are handled by > dovecot. SMTP is handled by postfix, imap/pop is handled by dovecot. > With the web it was easy just let apache serve the token that > letsencrypt needed and I got certificates. How do I do this with > regards email? You can do the DNS challenge method if your server has the ability to update DNS entries, or you can use certbot clients in standalone-mode that will act as a simple web server just long enough to serve out the token to complete the authentication. Joseph Tam <jtam.home(a)gmail.com>

1 0

Director+NFS Experiences
by Mark Moseley 03 Mar '17

03 Mar '17

As someone who is about to begin the process of moving from maildir to mdbox on NFS (and therefore just about to start the 'director-ization' of everything) for ~6.5m mailboxes, I'm curious if anyone can share any experiences with it. The list is surprisingly quiet about this subject, and articles on google are mainly just about setting director up. I've yet to stumble across an article about someone's experiences with it. * How big of a director cluster do you use? I'm going to have millions of mailboxes behind 10 directors. I'm guessing that's plenty. It's actually split over two datacenters. In the larger, we've got about 200k connections currently, so in a perfectly-balanced world, each director would have 20k connections on it. I'm guessing that's child's play. Any good rule of thumb for ratio of 'backend servers::director servers'? In my larger DC, it's about 5::1. * Do you use the perl poolmon script or something else? The perl script was being weird for me, so I rewrote it in python but it basically does the exact same things. * Seen any issues with director? In testing, I managed to wedge things by having my poolmon script running on all the cluster boxes (I think). I've since rewritten it to run *only* on the lowest-numbered director. When it wedged, I had piles (read: hundreds per second) of log entries that said: Feb 12 06:25:03 director: Warning: director(10.1.20.5:9090/right): Host 10.1.17.3 is being updated before previous update had finished (down -> up) - setting to state=up vhosts=0 Feb 12 06:25:03 director: Warning: director(10.1.20.5:9090/right): Host 10.1.17.3 is being updated before previous update had finished (up -> down) - setting to state=down vhosts=0 Feb 12 06:25:03 director: Warning: director(10.1.20.3:9090/left): Host 10.1.17.3 is being updated before previous update had finished (down -> up) - setting to state=up vhosts=0 Feb 12 06:25:03 director: Warning: director(10.1.20.3:9090/left): Host 10.1.17.3 is being updated before previous update had finished (up -> down) - setting to state=down vhosts=0 Because it was in testing, I didn't notice it and it was like this for several days till dovecot was restarted on all the director nodes. I'm not 100% on what happened, but my *guess* is that two boxes tried to update the status of the same backend server in rapid succession. * Assuming you're using NFS, do you still see non-trivial amounts of indexes getting corrupted? * Again, assuming NFS and assuming at least some corrupted indexes, what's your guess for success rate % for dovecot recovering them automatically? And how about success rate % for ones that dovecot wasn't able to do automatically but you had to use doveadm to repair it? Really what I'm trying to figure out is 1) how often sysops will need to manually recover indexes; and 2) how often admins *can't* manually recover indexes? * if you have unrecoverable indexes (and assuming you have snapshots on your NFS server), does grabbing the most recent indexes from the snapshots always work for recovery (obviously, up till the point that the snapshot was taken)? * Any gotchas you've seen anywhere in a director-fied stack? I realize that's a broad question :) * Does one of your director nodes going down cause any issues? E.g. issues with the left and right nodes syncing with each other? Or when the director node comes back up? * Does a backend node going down cause a storm of reconnects? In the time between deploying director and getting mailboxes converted to mdbox, reconnects for us will mean cold local-disk dovecot caches. But hopefully consistent hashing helps with that? * Do you have consistent hashing turned on? I can't think of any reason not to have it turned on, but who knows * Any other configuration knobs (including sysctl) that you needed to futz with, vs the default? I appreciate any feedback!

8 14

Mailbox size in log file
by Sergio Bastian Rodríguez 03 Mar '17

03 Mar '17

Hello Dovecot list. I need that Dovecot log writes mailbox size in all POP / IMAP connections, but I do not know if Dovecot can do that. I have been searching about that with not successful. For example, this is the log of our last email platform, different than Dovecot: 06:48:14 025BEE83 POP3 LOGIN user 'xxx(a)xxx.com' MailboxSize = 61708 Capacity = 2% ...... 06:49:19 025BEE83 POP3 LOGOUT user 'xxx(a)xxx.com' MailboxSize = 14472 Capacity = 0% In this example we can know the mailbox size before and after the connection, and it shows that user has removed or downloaded all messages from server. Now in Dovecot we have no information about that, and I cannot find any plugin which gives this us functionality. Is it possible to have this feature in Dovecot? Thanks for your help. ________________________________ ------------------------------------------------------------------------ Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que TELECABLE DE ASTURIAS, S.A. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención o a través del teléfono (+ 34) 984191000 y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. ------------------------------------------------------------------------

3 4

Dovecot + SpamAssassin through dovecot-antispam
by Bernard 03 Mar '17

03 Mar '17

Hello, I am new to the list. /Waving at everyone/ I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd user), running as a Postfix transport. I am currently trying to switch it to a dovecot plugin in order to make it interactively work with the email storage (react to mail classification, being able to train it from already received emails, aso.) My problem is now making it able to access my emails. Here is my setup: userdb { driver = static args = uid=<fixed> gid=<fixed> home=/var/mail/vhosts/%d/%n } passdb { driver = passwd-file args = <path to passwords file> } mail_location = maildir:~/mail:LAYOUT=fs mail_privileged_group = vmail Translating into this on the FS: drwxrwsr-x root mail /var/mail/ drwxrws--- root vmail /var/mail/vhosts drwx--S--- vmail vmail /var/mail/vhosts/domain1 drwx--S--- vmail vmail /var/mail/vhosts/domain1/user1 drwx--S--- vmail vmail /var/mail/vhosts/domain1/user2 drwx--S--- vmail vmail /var/mail/vhosts/domain2 drwx--S--- vmail vmail /var/mail/vhosts/domain2/user1 The drwx--S--- access rights are propagated into lower branches/leafs. I am having a hard time understanding what to do, reading http://wiki2.dovecot.org/SharedMailboxes/Permissions, to make all the folders and subsequent files readable by the vmail group too. Based on this documentation, the way dovecot propagate permissions from parent folders is a bit cryptic to me. What needs to be done to achieve that? The idea would be that even if I decided to allocated per-virtual-user a system user for stored files, all the files would still be stored and accessible with the same system group. I understand this would be done with the help of mail_access_groups = vmail, right? FWIW, I am getting inspiration from the following explanations: https://www.christianroessler.net/tech/2015/spamassassin-dovecot-postfix.ht… If I understand correctly, the guy is bypassing the authentication completely with allow_all_users=yes, right? I do not want to do that anyway. I hope what I am trying to achieve is clear enough and that I provided information enough. Would you help me? --- Bernard

4 5

passdb evaluation order
by Angel L. Mateo 03 Mar '17

03 Mar '17

Hello, I could have several password databases in dovecot. And according to http://wiki.dovecot.org/PasswordDatabase these passwdbs could allow or deny users and they could have different result_failure and result_sucess behaviors. So the order in which they are evaluated may be significant. So, how do I define this order? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

3 2

Faster way to import Thunderbird pop emails into dovecot imap Maildirs?
by Ian Evans 03 Mar '17

03 Mar '17

Until recently, I was using POP on my desktop and imap to access my email on my phone and laptop. Got tired of not having everything everywhere, so decided to go full imap. Followed the suggestions online and created a new imap account for my site in Thunderbird and copied my pop folders over to the imap ones so that the emails would get uploaded to the dovecot server and Maildir folders. That worked for some smaller folders, but in a couple of folders, I have in excess of 20,000 emails. Thunderbird/Dovecot seems to choke on that, apparently timing out at some point. I've tried doing about 1000 messages at a time, but even that is taking more than an hour and I have to be around for each chunk. I'm sure someone here is going to point me to some eureka moment method of exporting the thunderbird folders to some format, sftp'ing them to the server and importing. Just want to be careful that I don't mess up the current batch of emails on the imap server. Thanks for any suggestions.

3 3

Re: Re: welcome plugin
by Larry Rosenman 03 Mar '17

03 Mar '17

Directory probably needs rx to allow search. On Mar 2, 2017 at 6:52 PM, <David Mehler <dave.mehler(a)gmail.com>> wrote: Hello, Thank you. My configuration is below. It looks like a perm problem, i've set +r on the directory and it is readable. One other thing I noticed when going through the log the testuser logs in, then logs out. Then logs in again, and then gets the error. Any ideas why the two logins? I see this all the time, a log in log out, then another log in log out then the email transaction. Thanks. Dave. # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 10.3-RELEASE-p11 amd64 ufs auth_default_realm = domain.tld auth_mechanisms = plain login cram-md5 dict { sqlquota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = mail.domain.tld imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 999 last_valid_uid = 999 lmtp_rcpt_check_quota = yes mail_gid = vmail mail_home = /home/vmail/%d/%n/home mail_location = maildir:/home/vmail/%d/%n:LAYOUT=fs mail_plugins = acl quota zlib welcome mail_server_admin = mailto:postmaster@domain.tld mail_uid = vmail mailbox_list_index = yes maildir_broken_filename_sizes = yes maildir_empty_new = yes maildir_stat_dirs = yes maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress tldparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify imapsieve namespace { list = yes location = maildir:/home/vmail/public:LAYOUT=fs prefix = public/ separator = / subscriptions = yes type = public } namespace inbox { hidden = no inbox = yes list = yes location = mailbox Drafts { auto = no special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = no special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/local/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = redis:host=127.0.0.1:port=6379 quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve = ~/.dovecot.sieve sieve_before = /usr/local/etc/dovecot/sieve/before.d sieve_extensions = +notify +imapflags sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)domain.tld protocols = imap service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12345 } } ssl_ca = /etc/ssl/certs/cacert.crt ssl_cert = </etc/ssl/certs/server.crt ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_options = no_tldpression ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = acl quota zlib welcome sieve } protocol lda { mail_plugins = acl quota zlib welcome quota sieve } protocol imap { mail_plugins = acl quota zlib welcome imap_acl imap_quota imap_sieve imap_zlib last_login } /var/log/maillog: Feb 28 14:52:06 hostname dovecot: imap-login: Login: user=<testuser(a)domain.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=5840, secured, session=<5EXYh5xJesx/AAAB> Feb 28 14:52:06 hostname dovecot: imap(testuser(a)domain.tld): Logged out in=102 out=1373 Feb 28 14:52:06 hostname dovecot: imap-login: Login: user=<testuser(a)domain.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=7724, secured, session=<0nPch5xJMeR/AAAB> Feb 28 14:52:06 hostname dovecot: lda(testuser(a)domain.tld): Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=143(dovecot) egid=143(dovecot) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) Feb 28 14:52:06 hostname dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. Feb 28 14:52:06 hostname dovecot: welcome: Fatal: master: service(welcome): child 8781 returned error 75 Feb 28 14:52:06 hostname dovecot: imap(testuser(a)domain.tld): Logged out in=234 out=1549 On 3/2/17, @lbutlr <kremels(a)kreme.com> wrote: > On 2017-03-02 (16:54 MST), David Mehler <dave.mehler(a)gmail.com> wrote: >> >> Is anyone using the welcome plugin? I'm trying to utilize it to send a >> message when a user first logs in to the system, containing important >> information for them to know. The plugin loads, I don't have a >> configuration problem, but the message never gets sent. > > I would say you DO have a configuration problem if the mail doesn’t get > sent. > >> What can I provide to more easily troubleshoot this? > > I’d start with the settings for the welcome plugin and any logs. > > > -- > Apple broke AppleScripting signatures in Mail.app, so no random signatures. >

1 0

IMAP MOVE command with FTS
by TACHIBANA Masashi 03 Mar '17

03 Mar '17

Hi, I'm using Dovecot 2.2.28 with fts. It seems to work fine almost things. But I found a bug (or my setting problem?) My setting is "fts_autoindex=yes" in /etc/dovecot/conf.d/90-fts.conf Then, I have mailboxes like bellow: a a/lot a/lot/of There are some mails is in "a/lot" folder, then create sub like: a/lot/of/apples And move the mails from "a/lot" to "a/lot/of/apples" by MOVE command. In this case, FTS function fts_backend_xx_update_expunge is called. But fts_backend_xx_update_set_build_key is not called. Another case, follow functions are called and mails will be indexed. fts_backend_xx_update_expunge() fts_backend_xx_update_set_build_key() By the way, in the first case, I tried a command as bellow, then the mails ware indexed correctly: # doveadm index -u user1(a)example.com \* I think MOVE is better way to move mails than COPY+FLAG DEL+EXPUNGE. My settings problem? Any hints? Regards, -- Astro.M

1 0

make check failing in CentOS 6
by Peter Ajamian 03 Mar '17

03 Mar '17

Dovecot builds just fine, but fails the tests in src/lib-index. Note that reverting this commit fixes the issue: https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70… $ make check for bin in test-mail-index-map test-mail-index-modseq test-mail-index-sync-ext test-mail-index-transaction-finish test-mail-index-transaction-update test-mail-transaction-log-append test-mail-transaction-log-view; do \ if ! ./$bin; then exit 1; fi; \ done mail index map lookup seq range ...................................... : ok 0 / 1 tests failed mail_transaction_log_file_get_modseq_next_offset() ................... : ok 0 / 1 tests failed mail index sync ext atomic inc ....................................... : ok 0 / 1 tests failed mail index transaction finish flag updates n_so_far=0 ................ : ok mail index transaction finish flag updates n_so_far=1 ................ : ok mail index transaction finish flag updates n_so_far=2 ................ : ok mail index transaction finish check conflicts n_so_far=0 ............. : ok mail index transaction finish check conflicts n_so_far=1 ............. : ok mail index transaction finish check conflicts n_so_far=2 ............. : ok mail index transaction finish modseq updates n_so_far=0 .............. : ok mail index transaction finish modseq updates n_so_far=1 .............. : ok mail index transaction finish modseq updates n_so_far=2 .............. : ok mail index transaction finish expunges n_so_far=0 .................... : ok mail index transaction finish expunges n_so_far=1 .................... : ok mail index transaction finish expunges n_so_far=2 .................... : ok 0 / 12 tests failed mail index append .................................................... : ok mail index append with uids .......................................... : ok mail index flag update fast paths .................................... : ok mail index flag update simple merges ................................. : ok mail index flag update complex merges ................................ : ok mail index flag update random ........................................ : ok mail index flag update appends ....................................... : ok mail index cancel flag updates ....................................... : ok mail index transaction get flag update pos ........................... : ok mail index modseq update ............................................. : ok mail index expunge ................................................... : ok test-mail-index-transaction-update.c:649: Assert(#1) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#1) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#3) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#3) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#4) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:649: Assert(#5) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#5) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#6) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#6) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#7) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#7) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#8) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#8) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#9) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#9) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#10) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:652: Assert(#10) failed: memcmp(new_hdr.day_first_uid, tests[i].new_day_first_uid, sizeof(uint32_t) * 8) == 0 test-mail-index-transaction-update.c:649: Assert(#11) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone test-mail-index-transaction-update.c:649: Assert(#12) failed: new_hdr.day_stamp == tests[i].new_day_stamp + timezone mail index update day first uid ...................................... : FAILED test: random seed #1 was 1488809888 1 / 12 tests failed make: *** [check-test] Error 1

3 2

dovecot lda bouncing postfix aliases
by Ian Evans 02 Mar '17

02 Mar '17

Recently configured postfix to use the dovecot lda as I wanted to use sieve. Got that working a few days ago but noticed that I wasn't getting any emails to aliases. Checked the logs and saw messages like: Mar 1 08:19:59 carson postfix/lmtp[16949]: 0DCD22016BE: to=< sales(a)example.com>, relay=carson.example.com[private/dovecot-lmtp], delay=0.07, delays=0.01/0.01/0/0.04, dsn=5.1.1, status=bounced (host carson.example.com[private/dovecot-lmtp] said: 550 5.1.1 <sales(a)example.com> User doesn't exist: sales(a)example.com (in reply to RCPT TO command)) Aliases were working previously and are in /etc/postfix/vmaps Anything I need to check on the dovecot end of things to get dovecot to recognize postfix aliases? Thanks...reaching for my morning coffee. Info below: Dovecot 2.2.9 # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.11.0-19-generic x86_64 Ubuntu 14.04.5 LTS ext4 auth_mechanisms = plain login cram-md5 mail_debug = yes mail_location = maildir:/home/vmail/%d/%n/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = username_format=%u /etc/dovecot/shadow driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/example.com/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/letsencrypt/live/example.com/privkey.pem userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = sieve postmaster_address = postmaster(a)example.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh }

2 3

Sieve subaddress matching
by Peter Chiochetti 02 Mar '17

02 Mar '17

Hello Stephan, Maybe this is not an issue at all and nothing but a curiosity; maybe though you do care: When there is only a local part in "To", the "subaddress" extension does not match on the "detail" part. This happened when I made a device on the LAN send to "name+foo", where "name" is a system account on the computer used as smtp. Such mail gets filed into INBOX. Matching the whole address against "name+foo" works. This is with dovecot-sieve 2.2.13, postfix here obviously does not alter the To header. -- peter

2 1

Search problems after activating fts/solr
by azurit＠pobox.sk 02 Mar '17

02 Mar '17

Hi, after activating fts/solr, we can see a changed behavior of standard (not fulltext) searches. For example, when searching the 'From' field for something(a)example.com, before activating solr it was ok to start search for word 'some' and the result was correct and complete (all messages from that user was found). After activating fts/solr, searches like this are returning none or only part of messages - i need to search for 'something' to get correct and complete result. Any hints? azur

1 0

Fwd: Some mails do not get replicated anymore after memory-exhaust
by Christoph Kluge 02 Mar '17

02 Mar '17

Hey guys, overall I have an working dovecot replication between 2 servers running on amazon cloud. Sadly I had some messages that my server ran out of memory. After investigating a little bit further I realized that some mails didn't got replicated, but I'm not sure if this was related to the memory exhaust. I was expecting that the full-sync would catch them up but sadly it's not. Attached I'm adding: * /etc/dovecot/dovecot.conf from both servers * one sample of my memory-exhaust exception * maildir directory listing of one mailbox on both servers * commands + outpot of manual attempt for full-replication * grep information of missing mail inside Maildir on both servers Here is my configuration from both servers. The configugration is 1:1 the same except the mail_replica server. Please note one server runs on debian 8.7 and the other one on 7.11. ---- SERVER A > # dovecot -n > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 8.7 > ---- SERVER B > # dovecot -n > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-34-pve i686 Debian 7.11 > auth_mechanisms = plain login > disable_plaintext_auth = no > doveadm_password = **** > doveadm_port = 12345 > listen = *,[::] > log_timestamp = "%Y-%m-%d %H:%M:%S " > mail_max_userip_connections = 100 > mail_plugins = notify replication quota > mail_privileged_group = vmail > passdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > plugin { > mail_replica = tcp:*.****.de > quota = dict:user::file:/var/vmail/%d/%n/.quotausage > replication_full_sync_interval = 1 hours > sieve = /var/vmail/%d/%n/.sieve > sieve_max_redirects = 25 > } > protocols = imap > replication_max_conns = 2 > service aggregator { > fifo_listener replication-notify-fifo { > mode = 0666 > user = vmail > } > unix_listener replication-notify { > mode = 0666 > user = vmail > } > } > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > unix_listener auth-userdb { > group = vmail > mode = 0600 > user = vmail > } > user = root > } > service config { > unix_listener config { > user = vmail > } > } > service doveadm { > inet_listener { > port = 12345 > } > user = vmail > } > service imap-login { > client_limit = 1000 > process_limit = 512 > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > } > service replicator { > process_min_avail = 1 > unix_listener replicator-doveadm { > mode = 0666 > } > } > ssl_cert = </etc/postfix/smtpd.cert > ssl_key = </etc/postfix/smtpd.key > ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = prefetch > } > userdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > protocol imap { > mail_plugins = notify replication quota imap_quota > } > protocol pop3 { > mail_plugins = quota > pop3_uidl_format = %08Xu%08Xv > } > protocol lda { > mail_plugins = notify replication quota sieve > postmaster_address = webmaster@localhost > } > protocol lmtp { > mail_plugins = notify replication quota sieve > postmaster_address = webmaster@localhost > } This is the exception which I got several times: Feb 26 16:16:39 mx dovecot: replicator: Panic: data stack: Out of memory > when allocating 268435496 bytes > Feb 26 16:16:39 mx dovecot: replicator: Error: Raw backtrace: > /usr/lib/dovecot/libdovecot.so.0(+0x6b6fe) [0x7f7ca2b0a6fe] -> > /usr/lib/dovecot/libdovecot.so.0(+0x6b7ec) [0x7f7ca2b0a7ec] -> > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7ca2ac18fb] -> > /usr/lib/dovecot/libdovecot.so.0(+0x6977e) [0x7f7ca2b0877e] -> > /usr/lib/dovecot/libdovecot.so.0(+0x699db) [0x7f7ca2b089db] -> > /usr/lib/dovecot/libdovecot.so.0(+0x82198) [0x7f7ca2b21198] -> > /usr/lib/dovecot/libdovecot.so.0(+0x6776d) [0x7f7ca2b0676d] -> > /usr/lib/dovecot/libdovecot.so.0(buffer_write+0x6c) [0x7f7ca2b069dc] -> > dovecot/replicator(replicator_queue_push+0x14e) [0x7f7ca2fa17ae] -> > dovecot/replicator(+0x4f9e) [0x7f7ca2fa0f9e] -> dovecot/replicator(+0x4618) > [0x7f7ca2fa0618] -> dovecot/replicator(+0x4805) [0x7f7ca2fa0805] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7f7ca2b1bd0f] > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xf9) > [0x7f7ca2b1cd09] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) > [0x7f7ca2b1bd79] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) > [0x7f7ca2b1bdf8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) > [0x7f7ca2ac6dc3] -> dovecot/replicator(main+0x195) [0x7f7ca2f9f8b5] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f7ca2715b45] > -> dovecot/replicator(+0x395d) [0x7f7ca2f9f95d] > Feb 26 16:16:39 mx dovecot: imap(***.com): Warning: replication(***.com): > Sync failure: > Feb 26 16:16:39 mx dovecot: replicator: Fatal: master: > service(replicator): child 24012 killed with signal 6 (core dumps disabled) This is the current maildir listing on Server A # ls -la /var/vmail/*.eu/*h/Maildir/new/ > total 24 > drwx------ 2 vmail vmail 4096 Feb 27 18:12 . > drwx------ 15 vmail vmail 4096 Feb 27 21:47 .. > -rw------- 1 vmail vmail 3600 Feb 27 14:49 1488206976.M277562P25620.mail, > S=3600,W=3671 > -rw------- 1 vmail vmail 4390 Feb 27 15:17 1488208642.M513542P27111.mail, > S=4390,W=4478:2,S > -rw------- 1 vmail vmail 3577 Feb 27 16:32 1488213157.M307300P30773.mail, > S=3577,W=3648:2,S This is the current maildir listing on Server B # ls -la /var/vmail/*.eu/*h/Maildir/new/ > total 16 > drwx------ 2 vmail vmail 12288 Feb 27 16:45 . > drwx------ 15 vmail vmail 4096 Feb 27 21:47 .. This is how I tried to manually sync it doveadm -v sync -u *h(a)*.eu -f tcp:mx.***.de:12345 This is the users sync status # doveadm replicator status 'cheecoh(a)ragequit.eu' > username priority fast sync full sync failed > *h(a)*.eu none 00:24:47 10:57:04 - Then I tried to lookup for the mail-id which is also the same on both servers # grep -ri "M277562P25620" /var/vmail/*.eu/*h/ > /var/vmail/*.eu/*h/Maildir/dovecot-uidlist:493 :1488206976.M277562P25620. > mail,S=3600,W=3671 I have no idea what else I could do. I could also pass a "doveadm -Dv sync" output but this one is really huge.. Best Regards Christoph Kluge

1 1

dovecot-lda crash after upgrade to 2.2.28
by Max Kostikov 01 Mar '17

01 Mar '17

Hi! I posted this problem few days ago in FreeBSD bugtracker https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217364 So, the problem is in crash of dovecot-lda client while local mailbox delivery with this message in log > dovecot: lda(my@email): Panic: file mail-namespace.c: line 709 > (mail_namespace_find): assertion failed: (ns != NULL) My Dovecot config stills the same from previous 2.2.27 installation to I believe that problem in new Dovecot code related namespace. System: > # uname -v > FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Options: > root@beta:/usr/ports/mail/dovecot2 # make showconfig | grep =on > DOCS=on: Build and/or install documentation > EXAMPLES=on: Build and/or install examples > KQUEUE=on: kqueue(2) support > LIBWRAP=on: TCP wrapper support > LZ4=on: LZ4 compression support > MYSQL=on: MySQL database support > GSSAPI_BASE=on: Use GSSAPI from base Config: # doveconf -n # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p8 amd64 ufs auth_mechanisms = plain login default_login_user = dovecot dict { sqluserquota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql-user.conf } disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 25 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_access_sockets = tcpwrap login_greeting = Dovecot ready! login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_access_groups = mail mail_gid = 6 mail_location = maildir:/var/mail/%d/%n mail_plugins = acl quota trash mail_privileged_group = mail mail_uid = 26 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 { location = maildir:/var/mail/%d/.public:INDEXPVT=/var/mail/%d/%n/public prefix = public. separator = . subscriptions = no type = public } 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 Trash { auto = subscribe special_use = \Trash } prefix = separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile::cache_secs=300 antispam_backend = mailtrain antispam_mail_notspam = %u-revoke antispam_mail_sendmail = /usr/local/etc/dovecot/move-cmd.sh antispam_mail_sendmail_args = antispam_mail_spam = %u-report antispam_spam = Junk antispam_trash = Trash quota = dict:user_quota::proxy::sqluserquota quota_grace = 10%% quota_rule2 = Trash:storage=+10%% quota_rule3 = Junk:storage=+10%% quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=75%% quota-warning 75 %u sieve = ~/dovecot.sieve sieve_before = /usr/local/etc/dovecot/default.sieve sieve_dir = ~/sieve sieve_global_path = /usr/local/etc/dovecot/default.sieve trash = /usr/local/etc/dovecot/dovecot-trash.conf } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-client { mode = 0660 user = mailnull } unix_listener auth-master { mode = 0660 user = mailnull } user = root } service dict { unix_listener dict { mode = 0660 user = mailnull } } service imap-login { chroot = login client_limit = 64 executable = /usr/local/libexec/dovecot/imap-login inet_listener imap { port = 143 } inet_listener imaps { port = 993 } process_limit = 32 process_min_avail = 8 service_count = 1 user = $default_login_user vsz_limit = 64 M } service imap { executable = /usr/local/libexec/dovecot/imap } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 1 user = $default_login_user vsz_limit = 64 M } service managesieve { process_limit = 10 } service pop3-login { chroot = login client_limit = 64 executable = /usr/local/libexec/dovecot/pop3-login inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 } process_limit = 32 process_min_avail = 8 service_count = 1 user = $default_login_user vsz_limit = 64 M } service pop3 { executable = /usr/local/libexec/dovecot/pop3 } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { mode = 0660 user = mailnull } } service tcpwrap { unix_listener login/tcpwrap { mode = 0600 user = $default_login_user } } ssl_ca = </usr/local/etc/letsencrypt/live/peek.ru/chain.pem ssl_cert = </usr/local/etc/letsencrypt/live/peek.ru/cert.pem ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol sieve { managesieve_implementation_string = dovecot managesieve_max_line_length = 65536 } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_plugins = acl quota trash antispam imap_acl imap_quota } protocol lmtp { mail_plugins = acl quota trash sieve } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = acl quota trash sieve postmaster_address = postmaster(a)peek.ru sendmail_path = /usr/sbin/sendmail } local_name *.domain.ru { ssl_ca = </usr/local/etc/letsencrypt/live/domain.ru/chain.pem ssl_cert = </usr/local/etc/letsencrypt/live/domain.ru/cert.pem ssl_key = # hidden, use -P to show it } -- With best regards, Max Kostikov BBM: 24CA5DF8 | W: https://kostikov.co

3 11

Exclude namespace from replication
by George Kontostanos 01 Mar '17

01 Mar '17

Hello list, I am using replication with dsync and I am facing some issues with shared folders. More particularly expunged message reappearing. I have searched a bit and it was suggested that shared folders should not be synced. My namespace looks like that: namespace { inbox = no list = children location = maildir:/usr/local/vhosts/mail/%%d/%%n:LAYOUT=fs:INDEX=/usr/local/vhosts/indexes/%d/%n/shared/%%u:INDEXPVT=/usr/local/vhosts/indexes/%d/%n/shared/%%u prefix = shared/%%d/%%n/ separator = / subscriptions = no type = shared } I was wondering if defining: replication_dsync_parameters = -d -N -l 30 -U -x shared Is enough. Or do I need to change the syntax of the namespace like that: namespace shared { .... .... type = shared } Thanks for your help

1 0

Replacement for antispam plugin
by Aki Tuomi 01 Mar '17

01 Mar '17

Hi! Since antispam plugin is deprecated and we would really prefer people not to use it, we wrote instructions on how to replace it with IMAPSieve. Comments and suggestions are most welcome. https://wiki.dovecot.org/HowTo/AntispamWithSieve --- Aki Tuomi Dovecot oy

18 42

Expunged message reappeared, giving a new UID
by Γιώργος Δημακόπουλος 01 Mar '17

01 Mar '17

Dovecot 2.2.27 dsync-server(account_name): Warning: Maildir /usr/local/vhosts/mail/*******/info/Sent: Expunged message reappeared, giving a new UID (old uid=29787, file=*******) What triggers this replication for ever ?? Thank you George

2 1

Preserve environment variables for doveadm
by Teodor Milkov 01 Mar '17

01 Mar '17

Hello, I noticed there are ways to instruct various dovecot processes to preserve particular environment variables. One way is to use import_environment in dovecot.conf and yet another is to export DOVECOT_PRESERVE_ENVS variable – both can contain space delimited list of variables to preserve. I found report that this is supposed to work for dsync: http://www.dovecot.org/list/dovecot/2012-October/138659.html Unfortunately I can't it to work for "doveadm quota recalc". Is it supposed to work or am I doing something wrong? I did strace on the doveadm process and noticed it does exec() doveconf which in turn does exec() doveadm again. If I replace doveconf with a shell script which exports my environment variables then they become available to doveadm: # cat /dovecot/bin/doveconf.wrapper #!/bin/sh export LD_PRELOAD='dovecot-preload.so' exec /dovecot/bin/doveconf.orig "$@"

1 0

Expunged message reappeared, giving a new UID
by Γιώργος Δημακόπουλος 01 Mar '17

01 Mar '17

Please help. How to stop email replication is on going. dsync-server : Warning Expunged message reappeared, giving a new UID

1 0

Query about list policy?
by Andy R 01 Mar '17

01 Mar '17

Greetings for a second time today, As a quick query, what is the policy about linking to user-scripts and small addons ? I've used a couple of perl scripts to help me with dspam training from dovecot-antispam and imapsieve triggering for sorting and feeding messages to dspam in the background. They are most likely not the greatest but seem to work at least. I've posted them to github, but just wanted to ask whether it was an issue if i linked them here, or if they would need any review before posting or any other answer? Many thanks, and to Aki Tuomi and the dovecot team also. Andy R.

1 0

Quota usage value shows 140% of actual disk usage
by Umut Erol Kaçar 28 Feb '17

28 Feb '17

Hello everyone, Our server has these installed: dovecot-2.0.21-2.el6.x86_64 dovecot-pigeonhole-2.0.21-2.el6.x86_64 dovecot-mysql-2.0.21-2.el6.x86_64 ...and has been running for quite a long time, with several hundred domains and thousands of accounts on it. My colleagues reported that it's been showing quota usage values that are more than actual disk usage, so I investigated and found that Dovecot shows a quota usage value roughly around 140% of actual disk usage. It's also valid on newly created accounts. My test account for example: doveadm quota get -u test(a)example.local Quota name Type Value Limit % User quota STORAGE 4359 512000 0 User quota MESSAGE 7 - 0 du -sc /home/vmail/example.local/test/Maildir/{*,.[!.]*} 1044 /home/vmail/example.local/test/Maildir/cur 28 /home/vmail/example.local/test/Maildir/dovecot.index.cache 8 /home/vmail/example.local/test/Maildir/dovecot.index.log 4 /home/vmail/example.local/test/Maildir/dovecot.mailbox.log 4 /home/vmail/example.local/test/Maildir/dovecot-uidlist 4 /home/vmail/example.local/test/Maildir/dovecot-uidvalidity 0 /home/vmail/example.local/test/Maildir/dovecot-uidvalidity.56a4dc8e 4 /home/vmail/example.local/test/Maildir/new 4 /home/vmail/example.local/test/Maildir/subscriptions 4 /home/vmail/example.local/test/Maildir/tmp 24 /home/vmail/example.local/test/Maildir/.Junk 1932 /home/vmail/example.local/test/Maildir/.Sent 44 /home/vmail/example.local/test/Maildir/.Trash 3104 total 4359/3104=1,40431701 So it shows roughly around 1,4*actualDiskUsage. The ratio is mostly the same for almost all the other accounts. It can vary between like 1,3-1,6. So, the gap gets insane when more disk space is used, say like with 2GB disk usage, Dovecot thinks 3,5GB quota is used... dovecot quota recalc does not fix the issue, it only sets the same value again (I've checked with tcpdump and saw the query with the same quota usage value). The method is Dictionary quota with SQL. I'm attaching the dovecot -n output with some other config files. I've tried setting messages and bytes value to -1 on the MariaDB database to force recalculation. But as soon as I run doveadm quota recalc, it gets the same wrong value again. What can I do to fix this? Thanks in advance.

3 3

Index queue
by azurit＠pobox.sk 28 Feb '17

28 Feb '17

Hi, can i, somehow, list mailboxes which are to be indexed by indexer-worker (=index queue?) ? How can i know what part of all mailboxes was indexed so far? Are there any statistics about Solr data dir size based on emails amount? For example, we have about 5TB of emails, what should i except about index size in Solr? Thank you. azur

1 0

Re: Solr 6.4.1 config
by Daniel Miller 28 Feb '17

28 Feb '17

Since I was recently asked off-list - thought I'd make this available if it will help anyone else. Attached is my (I hope) working 6.4.1 config. Also some instructions: First, you have to decide if you're running in standalone or cloud mode. Standalone is simpler, but I seem to be having better luck running in cloud mode - even though I'm only using a single server/core/shard/collection/whatever. I've attached my config. Unzip this somewhere convenient - I will assume "/tmp/solr-dovecot". You may want to tweak it - this is adapted from my version 4 config and is set for English. If you look in solrbasedir/example/files/conf/lang or /solrbasedir/server/solr/configsets/basic_configs/conf/lang you'll find alternatives for "stopwords.txt" - I simply copied the "stopwords_en.txt" file directly to "conf/stopwords.txt". Assuming you extracted the Solr distribution to a base folder, such as /opt/solr-6.4.1, change to that folder. Then execute (again, /tmp/solr-dovecot is the path you extracted my config into): bin/solr create_collection -c dovecot -d /tmp/solr-dovecot That should create a minimal cloud instance. Then start it: bin/solr start -c And hopefully...you'll have a running Solr server. Assuming that's the case - since you've now created a "named" collection you have to specify that for Dovecot. So the fts_solr parameter in 90-plugin.conf needs to be something like: fts_solr = break-imap-search url=http://ser.ver.ip:8983/solr/dovecot/ Restart Dovecot...and with luck you're searching now. Hope this helps somebody! Daniel On 2/10/2017 3:15 PM, Daniel Miller wrote: > 2.2.18 > > On 2/9/2017 11:13 PM, Aki Tuomi wrote: >> What dovecot version are you using? >> >> >> On 10.02.2017 09:12, Aki Tuomi wrote: >>> Yeah, thanks. >>> >>> It seems that there indeed is content-type header (there should not >>> be). >>> We'll look into it. >>> >>> Aki >>> >>> On 10.02.2017 01:44, Daniel Miller wrote: >>>> Does this work (pcap attached)? >>>> >>>> Daniel >>>> >>>> On 2/8/2017 10:57 PM, Aki Tuomi wrote: >>>>> On 09.02.2017 07:54, Daniel Miller wrote: >>>>>> I've been running Solr for a while (4.10.3) - wanted to make the >>>>>> jump >>>>>> to the latest & greatest. I installed 6.4.1, copied over my >>>>>> schema.xml - and after a couple false starts where I needed to tweak >>>>>> it work with the new version...it works! I did not copy the >>>>>> database, >>>>>> started from scratch, and executed a "doveadm fts rescan -A". >>>>>> But... >>>>>> >>>>>> Judging solely from at least one client - it's fine. But looking in >>>>>> the logs I see: >>>>>> 1. The first scan of a mailbox dovecot's error log gives: >>>>>> dovecot: imap(dmiller(a)amfes.com): Error: fts_solr: Lookup >>>>>> failed: >>>>>> Bad Request >>>>>> >>>>>> 2. Subsequent scans do not appear to generate any dovecot error >>>>>> logs >>>>>> - but I'm not certain. Each new mailbox/subfolder scanned will each >>>>>> have one error on the initial scan. >>>>>> >>>>>> 3. Solr's log gives me the following - on every search. >>>>>> 2017-02-09 05:50:12.412 ERROR (qtp205125520-15) [ x:dovecot] >>>>>> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad >>>>>> contentType for search handler :text/xml >>>>>> request={q=from:"test"+OR+to:"test"+OR+cc:"test"+OR+subject:"test"+OR+body:"test"&fl=uid,score&sort=uid+asc&fq=%2Bbox:c1af150abfc9df4d7f7a00003bc41c5f+%2Buser:"dmiller(a)amfes.com"&rows=67135} >>>>>> >>>>>> >>>>> Hi! >>>>> >>>>> can you please use tcpdump or wireshark to capture the actual HTTP >>>>> request causing this exception? >>>>> >>>>> Aki

1 0

Archive key for the Dovecot Automatic Debian Package Archive (Xi) updated
by Stephan Bosch 28 Feb '17

28 Feb '17

Hi, I've updated the archive key for the Xi archive. So, when updating, you will initially get a key error. To fix this, either upgrade the debian-dovecot-auto-keyring package (preferred), or update your key manually from the archive.key located in the repository root. Regards, Stephan.

1 0

indexer-worker assert in v2.2.28 (fts-lucene)
by Daniel J. Luke 27 Feb '17

27 Feb '17

I upgraded to 2.2.28 and started seeing this logged: indexer-worker(dluke): Panic: file mailbox-list.c: line 1158 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) indexer-worker(dluke): Error: Raw backtrace: 2 libdovecot.0.dylib 0x000000010ec63d24 default_fatal_finish + 36 -> 3 libdovecot.0.dylib 0x000000010ec64b5b i_internal_fatal_handler + 43 -> 4 libdovecot.0.dylib 0x000000010ec64039 i_panic + 169 -> 5 libdovecot-storage.0.dylib 0x000000010eac0950 mailbox_list_try_mkdir_root + 1248 -> 6 libdovecot-storage.0.dylib 0x000000010eac0a39 mailbox_list_mkdir_root + 25 -> 7 lib21_fts_lucene_plugin.so 0x0000000110adc949 fts_backend_lucene_update_set_build_key + 73 -> 8 lib20_fts_plugin.so 0x000000010ee736cf fts_backend_update_set_build_key + 79 -> 9 lib20_fts_plugin.so 0x000000010ee74317 fts_build_mail + 599 -> 10 lib20_fts_plugin.so 0x000000010ee7981a fts_mail_precache + 794 -> 11 libdovecot-storage.0.dylib 0x000000010eaa71e9 mail_precache + 25 -> 12 indexer-worker 0x000000010ea9e503 master_connection_input + 1523 -> 13 libdovecot.0.dylib 0x000000010ec78b89 io_loop_call_io + 89 -> 14 libdovecot.0.dylib 0x000000010ec7a96d io_loop_handler_run_internal + 269 -> 15 libdovecot.0.dylib 0x000000010ec7907f io_loop_handler_run + 303 -> 16 libdovecot.0.dylib 0x000000010ec78e58 io_loop_run + 88 -> 17 libdovecot.0.dylib 0x000000010ec03458 master_service_run + 24 -> 18 indexer-worker 0x000000010ea9ddb4 main + 340 -> 19 libdyld.dylib 0x00007fffba7df255 start + 1 Anyone else? -- Daniel J. Luke

1 0

Released Pigeonhole v0.4.17 for Dovecot v2.2.28.
by Stephan Bosch 27 Feb '17

27 Feb '17

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the message to be forgotten or that headers modified by the "editheader" extension would revert to their original state. - file script storage: Amended the up-to-date time stamp comparison for on-disk binaries to include nanoseconds. This will fix problems occurring when both binary and script are saved within the same second. This fix is ineffective on older systems that have no support for nanoseconds in stat() timestamps, which should be pretty rare nowadays. - file script storage: Improve saving and listing permission error to include more details. - imapsieve plugin: Make sure "INBOX" is upper case in static mailbox rules. Otherwise, the mailbox name would never match, since matching is performed case-sensitively and Dovecot only returns the upper-cased "INBOX". - imapsieve plugin: Fixed assert failure occurring when used with virtual mailboxes. - doveadm sieve plugin: Fixed crash when setting Sieve script via attribute's string value. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.17.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.17.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Re: Sieve removeflag Action
by Stephan Bosch 26 Feb '17

26 Feb '17

Op 2/26/2017 om 4:02 PM schreef Thomas Leuxner: >> Am 26.02.2017 um 15:52 schrieb Thomas Leuxner <tlx(a)leuxner.net>: >> >>> So, I cannot reproduce your problem. >>> >>> Could you try this at your end? >> Hi Stephan, >> >> Tried with: >> >> $ /usr/lib/dovecot/dovecot-lda -d tlx(a)leuxner.net -p ./message.eml >> >> From: User <user(a)example.com> >> To: lists(a)example.org >> Subject: Frop! >> List-Id: <debian-security-announce.lists.debian.org> >> >> Frop! >> >> It goes right to the INBOX with no flags: >> > This time *with sieve* enabled in mail_plugins for LDA. (I’m using LMTP). The mail gets processed correctly. Does it make a difference for LMTP from the code? That should not matter normally. I tested this at my end, but I saw no different behavior. I created the following file in ~/message-lmtp.eml (substitute MAIL FROM/RCPT TO with whatever you need): LHLO frop MAIL FROM:<stephan(a)rename-it.nl> RCPT TO:<stephan> DATA From: User <user(a)example.com> To: stephan(a)rename-it.nl Subject: Frop! List-Id: <debian-security-announce.lists.debian.org> Frop! . Then I invoked LMTP through its unix socket (using socat tool): stephan@drieka:~$ cat ~/message-lmtp.eml | socat gopen:/var/run/dovecot/lmtp stdio 220 drieka.tds Dovecot ready. 250-drieka.tds 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 250 2.1.0 OK 250 2.1.5 OK 354 OK 250 2.0.0 <stephan> 1D/3FPsfs1ge/QAASZWA2w Saved Evaluating the results shows that there is still no problem here, since the last delivery is fine (I initially forgot to enable Sieve for LMTP): stephan@drieka:~$ doveadm -f table fetch "uid flags" mailbox "INBOX" uid flags 14 \Flagged \Recent $MailFlagBit1 15 \Flagged \Recent $MailFlagBit1 16 \Flagged \Recent $MailFlagBit1 17 \Flagged \Recent $MailFlagBit1 18 \Flagged \Recent $MailFlagBit1 19 \Recent 20 \Flagged \Recent $MailFlagBit1 stephan@drieka:~$ doveadm -f table fetch "uid flags" mailbox ":public/Newsletters/Debian/Security" uid flags 1 \Recent 2 \Recent 3 \Recent 4 \Recent 5 \Recent 6 \Recent Regards, Stephan.

2 1

Re: Dict quota calculation errors "remote disconnected"/"broken pipe" on 2.22.
by ygrishin-lists＠mail2.ca 26 Feb '17

26 Feb '17

Solved the problem, reporting back to the community. /etc/dovecot/dovecot-dict-sql-user.conf had been lacking dovecot group permissions. It was 700/root:root. However why it wasn't reported by Dovecot explicitly in the log -- the greatest mystery to me. Now, after deleting dovecot and all its packages via 'apt' and installing afresh makes "lacking permissions for the file" entry to appear in the log. I can confirm that Dict-quota works perfectly well with Dovecot 2.2.22.

1 0

Sieve removeflag Action
by Thomas Leuxner 26 Feb '17

26 Feb '17

Hi, I recently noticed that some of my automatically processed mails do no longer show flags with current Dovecot builds. This used to work before, not sure what broke it or whether I used it in the wrong way. When the removeflag line is dropped *both* messages get flagged in the client, one in INBOX and one in Trash. With removeflag in place, *both* messages are unflagged, the one in INBOX and the one in Trash. This used to work differently before if memory doesn't fail me. #Test if address :is "From" "user(a)example.com" { addflag "\\Flagged $MailFlagBit1"; keep; removeflag "\\Flagged $MailFlagBit1"; fileinto "Trash"; } # 2.2.devel (01867a4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (3c071a4) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 Regards Thomas

4 18

Sieve Script Replication Gliches (Report #2)
by Reuben Farrelly 26 Feb '17

26 Feb '17

Hi, I've observed some odd behaviour with dsync replication between two hosts, specifically to do with sieve script replication. In short, I have two hosts which replicate in a master-master type setup where almost all of the reads and writes happen to just one of the two hosts. They are both running 2.2.devel (9dc6403), which is close to the latest 2.2 -git . Pigeonhole is running master-0.4 . This is on x86_64 Gentoo. Normal mail replication between Maildir's for all users works fine, however it appears that something recently committed to the code has broken sieve script replication between the two. I am sure this did once work. Replication is via tcps: . Sieve scripts on the lesser-used host are not up to date by an order of days/weeks with the main host and they don't seem to re-replicate - even if the rules don't exist at all on the replica. The symptoms and effects look to be the same as this (unanswered) post from December: http://dovecot.org/list/dovecot/2015-December/102690.html I am not sure how to view the transaction log files, but I am seeing the same symptoms, ie no live replication, and on the lesser-used host almost all the scripts were old and some had the 1970 date on them. Even after forcing a [dsync replication replicate '*'] the scripts are not replicated. As it stands now there are no sieve scripts on one of the two members and the system seems unable to replicate by itself. Secondly, I am also seeing some doubled up outputs if I run 'doveadm sieve list -A': thunderstorm reuben # doveadm sieve list -A reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE reuben rules ACTIVE liam rules ACTIVE kaylene rules ACTIVE ... Has anyone else experienced the replication problem? Are sieve scripts actually replicating in live time for other 2.2.24/2.2.25 users as well? For me I didn't notice this till I went looking so I wonder if other people are experiencing this but just not aware of it yet...? Reuben

4 9

Replication sieve scripts.
by Luescher Claude 26 Feb '17

26 Feb '17

Hello, Following up on old thread: http://www.dovecot.org/pipermail/dovecot/2014-December/099003.html I have the exact same issue with 2.2.10: ii dovecot-antispam 2.0+20130822-2 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.10-1 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 1:2.2.10-1 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-1 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-1 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-1 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-1 amd64 secure POP3/IMAP server - Sieve filters support As even his version should already support sieve replication through dsync mine would have to support it for sure but I would like to hear a confirmation from the developers. The mail sync just works perfectly between the 2 nodes, it is only the sieve scripts which don't get replicated. I have tried to add additional sieve related options to the replicator: service replicator { process_min_avail = 1 } plugin { mail_replica = tcp:1.2.3.4 replication_full_sync_interval = 1 hours #Added (makes no difference) sieve = ~/.dovecot.sieve sieve_dir = ~/sieve_after sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 1h #Added (makes no difference) } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } It did not help. If there is one way I would like to get this work without upgrading dovecot. Thank you.

4 12

v2.2.28: var-expand.c
by Ruga 26 Feb '17

26 Feb '17

var-expand.c:687:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] va_start(args, key2); ^ var-expand.c:674:58: note: parameter of type 'char' is declared here var_expand_table_build(char key, const char *value, char key2, ...) ^

2 1

v2.2.28: patches (to use libressl 2.4.5) and test error (strftime)
by Ruga 26 Feb '17

26 Feb '17

t_strftime and variants now .......................................... : ok test-time-util.c:123: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 test-time-util.c:124: Assert failed: strcmp(t_strfgmtime(RFC2822_FMT, ts), exp) == 0 t_strftime and variants fixed timestamp .............................. : FAILED timings 0 ............................................................ : ok

4 7

sieve_imapsieve centos 7
by Matthew Broadhead 25 Feb '17

25 Feb '17

i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam with IMAPSieve but the package seems to be lacking sieve_imapsieve. is there anything i can do? i am not really interested in compiling from source because i like to receive security updates automatically. 2017-02-24 21:57:00auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied 2017-02-24 21:57:00master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2017-02-24 21:57:00managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve 2017-02-24 21:57:00config: Error: managesieve-login: dump-capability process returned 89 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:05imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:08imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:10imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot 2017-02-24 21:57:10imap: Fatal: Plugin 'imap_sieve' not found from directory /usr/lib64/dovecot

3 3

Re: sieve_imapsieve centos 7
by Aki Tuomi 25 Feb '17

25 Feb '17

imapsieve needs much newer dovecot and sieve. ---Aki TuomiDovecot oy -------- Original message --------From: Ben <ben+dovecot(a)list-subs.com> Date: 25/02/2017 12:33 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Re: sieve_imapsieve centos 7 >> i am using CentOS 7 centos-release-7-3.1611.el7.centos.x86_64 with >> dovecot dovecot-2.2.10-7.el7.x86_64. i am trying to set up AntiSpam >> with IMAPSieve but the package seems to be lacking sieve_imapsieve. is >> there anything i can do? i am not really interested in compiling from >> source because i like to receive security updates automatically. > The imapsieve plugin for pigeonhole was introduced in version 0.4.14 > for dovecot 2.2.24, with your current packages i'd say there is > nothing you can do except to find some sort of extra packages (i'm not > familiar with centos...) I have dovecot and sieve working on CentOS 7 Only using two packages dovecot.x86_64 1:2.2.10-7.el7 @base dovecot-pigeonhole.x86_64 1:2.2.10-7.el7 @base

2 1

sieve file backend: invalid option `active=~/.dovecot.sieve'
by Ben 25 Feb '17

25 Feb '17

Hi, I am seeing the followin error in my logs (doveconf -n at the bottom of this mail): Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp(a)example.com) Error: cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp(a)example.com) Error: cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script file:~/sieve;active=~/.dovecot.sieve (temporary failure) Looking at http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration, the syntax "sieve = file:~/sieve;active=~/.dovecot.sieve" in my config is correct ? Is this a false error that is only appearing because this is a newly created user with no sieve file ? If this is the case, how do I tell dovecot not to error out and allow the mail ? Thanks ! # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body environment mailbox date ihave enotify mbox_write_locks = fcntl 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 } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = its_virtmail mode = 0660 user = its_virtmail } } service imap-login { process_min_avail = 3 } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = its_virtmail } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieves { address = port = 5190 ssl = yes } } ssl = required ssl_cert = <REMOVED ssl_cipher_list = REMOVED ssl_dh_parameters_length = 2048 ssl_key = </REMOVED ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = sieve postmaster_address = me(a)example.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 20 }

2 4

Users with multiple password
by Eirik Rye 24 Feb '17

24 Feb '17

Hi! ~ dovecot --version 2.2.22 (fe789d2) I am wondering if there is a way to set up virtual users with multiple valid passwords. We want to be able to provide users with device/app-specific passwords for their email accounts, as well as being able to create temporary "access tokens" for technical support when required. I quickly found out that passdb using passwd-file or an sql-backend does not support returning multiple entries ("Error: passwd-file /etc/dovecot/virtual.passwd: User rye exists more than once"). The documentation mentions that you can pass the plain-text password on to the MySQL-server for verification, and I suppose multiple passwords could could work, given a query like this (pseudo-SQL): `SELECT password FROM account WHERE user = '%u' AND domain = '%d' AND password = TO_BASE64((SHA2('%w', 512));` However, having Dovecot pass the plain-text password and letting the database deal with the hashing and encoding doesn't seem like a very "clean" solution. Preferably, dovecot should be the only piece of software touching the plain-text. Ideally, I would like the following behavior: 1. passdb results multiple possible hashed passwords for the user 2. dovecot attempts the passwords in order 3. login fails normally if none of the passdb results match Does anyone have any experience, or tips for setting up this type of behavior? Other ideas we have touched upon are: 1. Different usernames (eg. 'user_device' or 'user_application') 2. Multiple passdbs(?) Best regards, Eirik Rye

2 2

doveadm "-v" optoin doesn't do anything ?
by Ben 24 Feb '17

24 Feb '17

Hi, On 2.2.10, running the following doveadm -v -o mail_fsync=never backup -R -u my(a)example.com imapc: There is zero output ? Running -D instead of -v it spews out debug messages. Any ideas ? Ben

1 0

Re: Problem with Let's Encrypt Certificate
by Joseph Tam 23 Feb '17

23 Feb '17

yacinechaouche(a)yahoo.com writes: > Interesting. Is there any particular benefit in having only one file > for both certificate and private key ? I find that putting private key > in a separate file feels more secure. It's convenient to have key and cert in one place if you don't need the certificate to be publically readable. Keeping it in separate files would add slightly more security (defense in depth), that would protect from, for example, an admin fumble or bug in the SSL library. "Michael A. Peters" <mpeters(a)domblogger.net> writes: >> I use dehydrated (with Cloudflare DNS challenges) and as far as I know, >> it seems to generate a new private key every time. > > Yeah that would be a problem for me because I implement DANE. It's on my to-do list, but I think you can use dehydrated in signing mode. --signcsr (-s) path/to/csr.pem Sign a given CSR, output CRT on stdout (advanced usage) In this way, you can reuse private key, as well as making it more secure by removing a privileged operations (private key acces) allowing dehydrated to be run as a non-privilged/separate user. Joseph Tam <jtam.home(a)gmail.com>

2 2

Pigeonhole External pipe script going zombie?
by Matt Simpson 23 Feb '17

23 Feb '17

I’m running dovecot 2.2.27 and pigeonhole 0.4.16 on FreeBSD 11. I’m using the pigeonhole/sieve external pipe plugin to run a Perl program to send a Pushover notification when certain messages are received. The Perl script is executed, and the notification is sent. But then the script task seems to go zombie until it is killed after a timeout. In the user’s sieve log, I get a message like error: msgid=<20170112191921.66140.qmail(a)v1.redhorse.me>: pipe action: failed to pipe message to program `sievepush.pl': refer to server log for more information. [2017-01-12 14:19:36]. (even though the message really was piped to the program successfully) In the dovecot server log, I see Jan 12 14:19:21 v1 dovecot: lda(matt): Debug: sieve: Executing script from `/usr/home/matt/maildoms/.dovecot.svbin' Jan 12 14:19:21 v1 dovecot: lda(matt): Debug: sieve: action pipe: running program: sievepush.pl Jan 12 14:19:21 v1 dovecot: lda(matt): Debug: Mailbox stdin: Opened mail UID=1 because: mail stream Jan 12 14:19:21 v1 dovecot: lda(matt): Debug: waiting for program `/usr/local/lib/dovecot/sieve-pipe/sievepush.pl' to finish after 0 msecs Jan 12 14:19:31 v1 dovecot: lda(matt): Debug: program `/usr/local/lib/dovecot/sieve-pipe/sievepush.pl'(66145) execution timed out after 10000 milliseconds: sending TERM signal Jan 12 14:19:36 v1 dovecot: lda(matt): Debug: program `/usr/local/lib/dovecot/sieve-pipe/sievepush.pl' (66145) did not die after 5000 milliseconds: sending KILL signal In the process list during that 10 second interval, I see matt 66142 29972 801 801 0 S - 0:00.00 bin/qmail-local -- matt /home/matt/maildoms jmn-matt - jmn-m matt 66143 66142 801 801 0 S - 0:00.00 /var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot matt 66144 66143 801 801 0 S - 0:00.01 /usr/local/libexec/dovecot/dovecot-lda matt 66145 66144 801 801 0 Z - 0:00.65 <defunct> I’m not a Unix programming ace, but from what I’ve been able to find out, this seems to mean that the lda process is forking another process to run the pipe script, and not getting the proper notification when it finishes (not issuing a wait?). So after 10 seconds, it sends a TERM to the task which is no longer running, and when that doesn’t work, it sends a KILL. Anybody know what’s happening here? doveconf -n # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p2 amd64 auth_verbose = yes default_vsz_limit = 128 M lock_method = flock mail_debug = yes mail_location = maildir:~/Maildir mail_privileged_group = mail 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 vnd.dovecot.pipe vnd.dovecot.execute namespace inbox { inbox = yes location = prefix = } passdb { args = imap driver = pam } plugin { recipient_delimiter = - sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/local/lib/dovecot/sieve-pipe sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/lib/dovecot/sieve-pipe sieve_pipe_exec_timeout = 10s sieve_plugins = sieve_extprograms } protocols = imap service auth { unix_listener auth-master { group = qnofiles mode = 0660 user = alias } user = root } service imap-login { process_min_avail = 3 vsz_limit = 94 M } ssl_cert = </usr/local/etc/letsencrypt/live/dummy.redhorse.me/cert.pem ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol lda { mail_plugins = " sieve" }

2 3

How to add Ubuntu 16.04.2 server to join and authenticate with domain controller windows2012r2
by Basdove 23 Feb '17

23 Feb '17

Hi, 1. I have Ubuntu 16.0.4.2 server edition 2. I have windows server 2012R2 domain controller (Active directory installed) 3. I want to join and Authenticate Ubuntu with windows server 2012 domain controller 4. Please provide the clean document Thank you, Baskaranand

3 2

imap/pop3-login assertion failed in dovecot 2.2.27 (c0f36b0)
by Edgaras Lukoševičius 23 Feb '17

23 Feb '17

Hello, I have noticed few errors like this. I don't recall seeing that with version 2.2.10 Feb 23 05:20:03 mail21 dovecot[6569]: imap-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 05:50:03 mail21 dovecot[15044]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 05:50:03 mail21 dovecot[15044]: imap-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 06:30:04 mail21 dovecot[13266]: imap-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 06:30:04 mail21 dovecot[13266]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 07:10:04 mail21 dovecot[14298]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 07:10:04 mail21 dovecot[14298]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 07:10:04 mail21 dovecot[14298]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 08:00:04 mail21 dovecot[13138]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 08:00:04 mail21 dovecot[13138]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 08:00:04 mail21 dovecot[13138]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 08:00:04 mail21 dovecot[13138]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0) Feb 23 08:00:04 mail21 dovecot[13138]: pop3-login: Panic: file login-proxy-state.c: line 77 (login_proxy_state_deinit): assertion failed: (rec->num_waiting_connections == 0)

1 0

Problem with Let's Encrypt Certificate
by Bastian Sebode 23 Feb '17

23 Feb '17

Hello Folks, my StartCom SSL-Certificate expires soon and so I wanted to switch to Let's Encrypt Certificates instead. Unfortunatelly Thunderbird seems not to like it, although all -tested- other Clients work without any problems. When I connect with Thunderbird it sends an "Encrypted Alert" directly after the TLS handshake although Dovecot wants to continue the session. In the Dovecot Log it says: Feb 17 17:27:17 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [82.100.242.26] Feb 17 17:27:17 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [82.100.242.26] Feb 17 17:27:17 imap-login: Warning: SSL alert: where=0x4004, ret=554: fatal bad certificate [82.100.242.26] But the certificate is okay, cause it works with other Mailclients and openssl also says so. What certificate is Thunderbird complaining about? Thunderbird says something like "There's no supported authentication method". I don't use any Certificates for Client Authentication, neither in Dovecot nor in Thunderbird. When I do, it fails the same way. Weirdly my friend uses the same Dovecot Version with Let's Encrypt on his Server and it works with Thunderbird without any flaws. Mine fails the same way in his Thunderbird and also in a fresh installation. After two weeks of investigating I still have no clue why it behaves like this. I uploaded two Wireshark tracefiles, further logs and dovecot -n, may be someone sees any possible reasons for this weird behavior or has any further tips on solving this issue. https://sebode-online.de/dovecot-letsencrypt/ Every hint is highly appreciated! Best Regards Bastian -- Bastian Sebode Fachinformatiker Systemintegration LINET Services GmbH | Cyriaksring 10a | 38118 Braunschweig Tel. 0531-180508-0 | Fax 0531-180508-29 | http://www.linet-services.de LINET in den sozialen Netzwerken: www.twitter.com/linetservices | www.facebook.com/linetservices Wissenswertes aus der IT-Welt: www.linet-services.de/blog/ Geschäftsführung: Timo Springmann, Mirko Savic und Moritz Bunkus HR B 9170 Amtsgericht Braunschweig USt-IdNr. DE 259 526 516

15 27

Scaling to 10 Million IMAP sessions on a single server
by KT Walrus 22 Feb '17

22 Feb '17

I just read this blog: https://mrotaru.wordpress.com/2013/10/10/scaling-to-12-million-concurrent-c… <https://mrotaru.wordpress.com/2013/10/10/scaling-to-12-million-concurrent-c…> about scaling to 12 Million Concurrent Connections on a single server and it got me thinking. Would it be possible to scale Dovecot IMAP server to 10 Million IMAP sessions on a single server? I think the current implementation of having a separate process manage each active IMAP session (w/ the possibility of moving idling sessions to a single hibernate process) will never be able to deploy a single server managing 10 Million IMAP sessions. But, would it be possible to implement a new IMAP server plugin that uses a fixed configurable pool of “worker” processes, much like NGINX or PHP-FPM does. These servers can probably scale to 10 Million TCP connections, if the server is carefully tuned and has enough cores/memory to support that many active sessions. I’m thinking that the new IMAP server could use some external database (e.g., Redis or Memcached) to save all the sessions state and have the “worker” processes poll the TCP sockets for new IMAP commands to process (fetching the session state from the external database when it has a command that is waiting on a response). The Dovecot IMAP proxies could even queue incoming commands to proxy many incoming requests to a smaller number of backend connections (like ProxySQL does for MySQL requests). That might allow each Dovecot proxy to support 10 Million IMAP sessions and a single backend could support multiple front end Dovecot proxies (to scale to 100 Million concurrent IMAP connections using 10 proxies for 100 Million connections and 1 backend server for 10 Million connections). Of course, the backend server may need to be beefy and have very fast NVMe SSDs for local storage, but changing the IMAP server to manage a pool of workers instead of requiring a process per active session, would allow bigger scale up and could save large sites a lot of money. Is this a good idea? Or, am I missing something? Kevin

8 15

v2.2.28 release candidate 2 released
by Timo Sirainen 22 Feb '17

22 Feb '17

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two. Changes since rc1: * Reverted [UNKNOWN-CTE] -> [PARSE] change + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension even though it's advertised. - lmtp_user_concurrency_limit didn't work if userdb changed username - Fixed various bugs that were introduced in rc1 Here's the full list of changes again: * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache caching decisions. * Expunging mails writes GUID to dovecot.index.log now only if the GUID is quickly available from index/cache. * pop3c: Increase timeout for PASS command to 5 minutes. * Mail access errors are no longer ignored when searching or sorting. With IMAP the untagged SEARCH/SORT reply is still sent the same as before, but NO reply is returned instead of OK. + Make dovecot.list.index's filename configurable. This is needed when there are multiple namespaces pointing to the same mail root (e.g. lazy_expunge namespace for mdbox). + Add size.virtual to dovecot.index when folder vsizes are accessed (e.g. quota=count). This is mainly a workaround to avoid slow quota recalculation performance when message sizes get lost from dovecot.index.cache due to corruption or some other reason. + auth: Support OAUTHBEARER and XOAUTH2 mechanisms. Also support them in lib-dsasl for client side. + auth: Support filtering by SASL mechanism: passdb { mechanisms } + Shrink the mail processes' memory usage by not storing settings duplicated unnecessarily many times. + imap: Add imap_fetch_failure setting to control what happens when FETCH fails for some mails (see example-config). + imap: Include info about last command in disconnection log line. + imap: Created new SEARCH=X-MIMEPART extension. It's currently not advertised by default, since it's not fully implemented. + fts-solr: Add support for basic authentication. + Cassandra: Support automatically retrying failed queries if execution_retry_interval and execution_retry_times are set. + doveadm: Added "mailbox path" command. + mail_log plugin: If plugin { mail_log_cached_only=yes }, log the wanted fields only if it doesn't require opening the email. + mail_vsize_bg_after_count setting added (see example-config). + mail_sort_max_read_count setting added (see example-config). + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension even though it's advertised. - Index files: day_first_uid wasn't updated correctly since v2.2.26. This caused dovecot.index.cache to be non-optimal. - imap: SEARCH/SORT may have assert-crashed in client_check_command_hangs - imap: FETCH X-MAILBOX may have assert-crashed in virtual mailboxes. - imap: Running time in tagged command reply was often wrongly 0. - search: Using NOT n:* or NOT UID n:* wasn't handled correctly - director: doveadm director kick was broken - director: Fix crash when using director_flush_socket - director: Fix some bugs when moving users between backends - imapc: Various error handling fixes and improvements - master: doveadm process status output had a lot of duplicates. - autoexpunge: If mailbox's rename timestamp is newer than mail's save-timestamp, use it instead. This is useful when autoexpunging e.g. Trash/* and an entire mailbox is deleted by renaming it under Trash to prevent it from being autoexpunged too early. - autoexpunge: Multiple processes may have been trying to expunge the same mails simultaneously. This was problematic especially with lazy_expunge plugin. - auth: %{passdb:*} was empty in auth-worker processes - auth-policy: hashed_password was always sent empty. - dict-sql: Merge multiple UPDATEs to a single statement if possible. - fts-solr: Escape {} chars when sending queries - fts: fts_autoindex_exclude = \Special-use caused crashes - doveadm-server: Fix leaks and other problems when process is reused for multiple requests (service_count != 1) - sdbox: Fix assert-crash on mailbox create race - lda/lmtp: deliver_log_format values weren't entirely correct if Sieve was used. especially %{storage_id} was broken. - lmtp_user_concurrency_limit didn't work if userdb changed username

1 0

Re: How to dsync mdbox compressed to maildir uncompressed
by Daniel Betz 22 Feb '17

22 Feb '17

Hi Thomas, thank you for your help. This is very strange that it wont work here. can you doveconf -n the relevant parts especially mail_plugins= and plugin { } i think i have misconfigured something :( Regards, Daniel

2 1

Re: How to dsync mdbox compressed to maildir uncompressed
by Daniel Betz 22 Feb '17

22 Feb '17

Hi Thomas, this doesnt work: doveadm -o plugin/quota= -o plugin/zlib_save= backup -u imap at test.de maildir:~/Maildir file Maildir/cur/1487752497.M128284P11684.mail,S=7691,W=7887:2,S Maildir/cur/1487752497.M128284P11684.mail,S=7691,W=7887:2,S: gzip compressed data, from Unix Regards, Daniel

2 1

Sieve and multi-auth databases
by dovecot＠avv.solutions 21 Feb '17

21 Feb '17

Hello Community, I am currently facing the following: - dovecot+postfix+sieve are running smoothly using passwd-file authentication - if a add a second authentication scheme (let's say mysql), I face a problem with sieve: -- receiving thru postfix is ok on both passwd-file and mysql entries and correctly stored -- I am able to send from the server as before ** BUT sieve == does not authenticate anymore from a client (using the same configuration as before ie using imap credentials) == does not process the messages anymore Digging in the sieve logs, it reports not finding the scripts anymore for existing accounts found in the passwd-file Any idea? Thank you! - - - - + - - - - # Here is the 90-sieve.conf: plugin { sieve = file:/sd/MAIL_IMAP_POP/%d/%n/_dovecot-sieve;active=/sd/MAIL_IMAP_POP/%d/%n/_dovecot-sieve-active sieve_default = /sd/myhost/var/lib/dovecot/sieve/default.sieve sieve = /sd/MAIL_IMAP_POP/%d/%n/__Sieve sieve_global_dir = /sd/myhost/var/lib/dovecot/sieve/global/ sieve_before = /sd/MAIL_IMAP_POP/SieveBefore sieve_after = /sd/MAIL_IMAP_POP/%d/SieveAfter/ sieve_after2 = /sd/MAIL_IMAP_POP/SieveAfter/ sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.filter sieve_filter_bin_dir = /etc/dovecot/sieve-filters } - - - - + - - - - # Authentication for SQL users. Included from 10-auth.conf. passdb sql { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext # Associated query: # password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; } userdb sql { driver = static args = uid=vmail gid=vmail home=/sd/MAIL_IMAP_POP/%d/%n:LAYOUT=fs }

2 2

segfault in lib20_expire_plugin
by Mario Arnold 21 Feb '17

21 Feb '17

Hello, after upgrade from [2.2.devel (34f7cc3)] to [2.2.devel (b3443fc)] dovecot stops with a segfault: Fatal: master: service(imap): child 21179 killed with signal 11 (core dumped) imap[21179]: segfault at 0 ip 00000000f726eef1 sp 00000000ffa3b050 error 4 in lib20_expire_plugin.so[f726d000+3000] gdb /usr/lib/dovecot/imap /var/_core/core_imap-11-5000-5000-21179 GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug/.build-id/99/6f1cf1a262cf5738f075ec046d9a7d344d9693.debug...done. done. [New LWP 21179] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/imap imap-postlogin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 expire_mail_namespaces_created (ns=0xf814db90) at expire-plugin.c:428 428 expire-plugin.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt full #0 expire_mail_namespaces_created (ns=0xf814db90) at expire-plugin.c:428 user = 0xf814d028 v = 0x0 db = 0xf815b960 error = 0xf81522c0 "Trash" #1 0xf75f9b21 in hook_mail_namespaces_created (namespaces=0xf8151008) at mail-storage-hooks.c:304 _data_stack_cur_id = 4 hooks__foreach_end = 0xf814dae8 hooks = 0xf814dad4 #2 0xf75ebf9f in mail_namespaces_init_finish (namespaces=0xf8151008, error_r=0xffa3b23c) at mail-namespace.c:383 _data_stack_cur_id = 3 ns = 0x0 prefixless_found = false __FUNCTION__ = "mail_namespaces_init_finish" #3 0xf75ec1bb in mail_namespaces_init (user=0xf814d028, error_r=0xffa3b23c) at mail-namespace.c:438 mail_set = 0xf814d118 ns_set = <optimized out> unexpanded_ns_set = <optimized out> namespaces = 0xf8151008 ns_p = <optimized out> i = <optimized out> count = <optimized out> count2 = <optimized out> __FUNCTION__ = "mail_namespaces_init" #4 0xf75fcd30 in mail_storage_service_init_post (ctx=<optimized out>, error_r=<optimized out>, mail_user_r=<optimized out>, priv=<optimized out>, user=<optimized out>) at mail-storage-service.c:728 mail_set = 0xf814d118 mail_user = 0xf814d028 #5 mail_storage_service_next_real (mail_user_r=<optimized out>, user=<optimized out>, ctx=<optimized out>) at mail-storage-service.c:1426 len = 4162116496 priv = {uid = 5000, gid = 5000, uid_source = 0xf76afeb4 "userdb lookup", gid_source = 0xf76afeb4 "userdb lookup", home = 0xf813ea71 "/srv/vmail/xtlv.de/1000", chroot = 0xf8130a20 ""} error = 0xf75b9934 "4\210\024" #6 mail_storage_service_next (ctx=0xf814d118, user=0xf813da90, mail_user_r=0xffa3b304) at mail-storage-service.c:1444 No locals. #7 0xf75fd0ff in mail_storage_service_lookup_next (ctx=0xf81399b0, input=0xffa3b368, user_r=0xffa3b300, mail_user_r=0xffa3b304, error_r=0xffa3b360) at mail-storage-service.c:1477 user = 0xf813da90 ret = <optimized out> #8 0xf77832c9 in client_create_from_input (input=0xffa3b368, fd_in=15, fd_out=15, client_r=0xffa3b35c, error_r=0xffa3b360) at main.c:228 user = 0x81a4 mail_user = 0xc34a5 ns = 0xf814d000 client = 0xffa3b304 imap_set = 0xffa3b360 lda_set = 0xffa3b304 errstr = 0xf814db90 "" mail_error = 49663 #9 0xf77834ea in login_client_connected (login_client=0xf813b450, username=0xf81300c8 "1000(a)xtlv.de", extra_fields=0xf81300ac) at main.c:316 input = {module = 0xf778b616 "imap", service = 0xf778b616 "imap", username = 0xf81300c8 "1000(a)xtlv.de", session_id = 0xf813b4c0 "doleKgxJ3s8l6zee", session_id_prefix = 0x0, session_create_time = 0, local_ip = { family = 2, u = {ip6 = {__in6_u = {__u6_addr8 = "T&K\217", '\000' <repeats 11 times>, __u6_addr16 = {9812, 36683, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {2404066900, 0, 0, 0}}}, ip4 = {s_addr = 2404066900}}}, remote_ip = { family = 2, u = {ip6 = {__in6_u = {__u6_addr8 = "%\353\067\236", '\000' <repeats 11 times>, __u6_addr16 = {60197, 40503, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {2654464805, 0, 0, 0}}}, ip4 = {s_addr = 2654464805}}}, local_port = 0, remote_port = 0, userdb_fields = 0xf81300ac, flags_override_add = (unknown: 0), flags_override_remove = (unknown: 0), no_userdb_lookup = 0, debug = 0} client = 0xf750331c <t_malloc0+44> flags = <optimized out> error = 0xf8130130 "auth_token=3763fd48bfdfeea2a3617cbda148915c19e125fa" __FUNCTION__ = "login_client_connected" #10 0xf749b0d1 in master_login_auth_finish (client=0xf813b450, auth_args=0xf814d000, auth_args@entry=0xf81300a8) at master-login.c:210 login = 0xf813ab88 service = 0xf81383e8 __FUNCTION__ = "master_login_auth_finish" #11 0xf749b6a9 in master_login_postlogin_input (pl=0xf813d720) at master-login.c:284 login = 0xf813ab88 buf = "1000@xtlv.de\tquota_rule=*:storage=5M\tuid=5000\tgid=5000\thome=/srv/vmail/xtlv.de/1000\tauth_token=3763fd48bfdfeea2a3617cbda148915c19e125fa\nQ\345td", '\000' <repeats 20 times>, "\006\000\000\000\020\000\000\000R\345td\260.\000\000\260>\000\000\260>\000\000P\001\000\000P\001\000\000\004\000\000\000\001\000\000\000"... auth_args = 0xf81300a8 p = 0xf81300c0 ret = -1 fd = -1 ---Type <return> to continue, or q <return> to quit--- #12 0xf751b73e in io_loop_call_io (io=0xf813b358) at ioloop.c:599 ioloop = 0xf81384b8 t_id = 2 __FUNCTION__ = "io_loop_call_io" #13 0xf751cece in io_loop_handler_run_internal (ioloop=0xf81384b8) at ioloop-epoll.c:223 ctx = 0xf813a210 list = 0xf813b390 io = <optimized out> tv = {tv_sec = 59, tv_usec = 999219} events_count = <optimized out> msecs = <optimized out> ret = 1 i = <optimized out> j = 0 call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #14 0xf751b7ef in io_loop_handler_run (ioloop=0xf81384b8) at ioloop.c:648 No locals. #15 0xf751b999 in io_loop_run (ioloop=0xf81384b8) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #16 0xf749d985 in master_service_run (service=0xf81383e8, callback=0xf7782b60 <client_connected>) at master-service.c:641 No locals. #17 0xf7766ece in main (argc=2, argv=0xffa3bab4) at main.c:460 set_roots = {0xf779d2a0 <imap_setting_parser_info>, 0xf7732ac0 <lda_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0xf8130030 "ta_rule=*:storage=5M", postlogin_socket_path = 0xf8130060 "/vmail/xtlv.de/1000", postlogin_timeout_secs = 60, callback = 0xf7783430 <login_client_connected>, failure_callback = 0xf7782cc0 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = <optimized out> auth_socket_path = <optimized out> c = <optimized out> doveconf -n # 2.2.devel (b3443fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (0d78a30) # OS: Linux 3.2.64.stk32 x86_64 Debian 9.0 auth_debug = yes auth_debug_passwords = yes auth_failure_delay = 5 secs auth_master_user_separator = * auth_mechanisms = digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dov_debug.log deliver_log_format = msgid=%m: %$: DeliveryTime=%{delivery_time}: LMTPSessionTime=%{session_time} dict { expire = db:/var/lib/dovecot/expire.db } doveadm_password = # hidden, use -P to show it doveadm_port = 1090 imap_logout_format = in=%i out=%o MailHeaderR=%{fetch_hdr_count} MailBodyR=%{fetch_body_count} MailDel=%{deleted} MailExpung=%{expunged} MailTrash=%{trashed} lmtp_rcpt_check_quota = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_debug = yes mail_gid = vmail mail_location = sdbox:%h/sdbox mail_plugins = " quota mail_log notify expire zlib acl notify replication" mail_privileged_group = vmail mail_uid = vmail 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 { ignore_on_failure = no inbox = no list = children location = sdbox:%%h/sdbox prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = scheme=PLAIN username_format=%Lu /etc/dovecot/user_pw/passwd driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/srv/vmail/shared-db/shared-mailboxes expire = Trash 2h expire_cache = yes expire_dict = proxy::expire mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename save mailbox_create mail_log_fields = uid box msgid size subject mail_replica = tcps:mx00.vtlx.cn quota = dict:User quota::file:%h/dovecot-quota quota_exceeded_message = Die Mailbox des Empfaengers ist voll -- Quota exceeded -- Please contact <postmaster(a)xtlv.cn> quota_grace = 12%% quota_rule = *:storage=350M quota_rule2 = Trash:storage=+15%% quota_status_nouser = DUNNO quota_status_overquota = "552 5.5.2 Die Mailbox des Empfaengers ist voll ## Mailbox is full ## Please contact <postmaster(a)xtlv.cn>" quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=80%% quota-warning 80 %u quota_warning4 = storage=70%% quota-warning 70 %u sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m/%{deleted_bytes}, size=%s postmaster_address = postmaster(a)xtlv.cn protocols = " imap lmtp sieve pop3" service aggregator { fifo_listener replication-notify-fifo { mode = 0660 user = vmail } unix_listener replication-notify { mode = 0660 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service config { unix_listener config { mode = 0600 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service doveadm { inet_listener { address = 84.38.75.143, 2a00:5080:1:16::8 port = 1090 ssl = yes } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = 84.38.75.143 port = 993 ssl = yes } } service imap-postlogin { executable = script-login -d /usr/local/sbin/dov-last-login-imap.sh user = $default_internal_user } 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 { address = 84.38.75.143 port = 4190 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = 84.38.75.143 port = 995 ssl = yes } } service pop3-postlogin { executable = script-login -d /usr/local/sbin/dov-last-login-pop3.sh user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_ca = </etc/dovecot/certs/sub.class2.server.ca.pem ssl_cert = </etc/dovecot/keys/vtlx.cn-wc-2015.crt ssl_cipher_list = ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:DHE-RSA-AES256-SHA:!RC4:!aNULL:!eNULL:!LOW:!EXPORT:!DES:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!NULL:!DH:!EDH:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_file = /etc/dovecot/certs/ca-bundle-2016.pem ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 ssl_verify_client_cert = yes userdb { args = username_format=%Lu /etc/dovecot/user_pw/passwd driver = passwd-file } protocol lmtp { mail_plugins = " quota mail_log notify expire zlib acl notify replication quota sieve" } protocol imap { mail_max_userip_connections = 12 mail_plugins = " quota mail_log notify expire zlib acl notify replication imap_quota imap_zlib imap_acl" } protocol pop3 { mail_plugins = " quota mail_log notify expire zlib acl notify replication quota" } -- Persönlich IS0-Zertifiziert in angewandter Kompetenzsimulation.

2 1

Could not login as root or other Linux user account
by Basdove 21 Feb '17

21 Feb '17

Ubuntu server 16.04.2samba has upgraded from As per repository (latest version)I was configuring samba as per document from wiki "ActivedirectoryWINbindHowto"After editing the common-account and common-auth I rebooted the server.I could notlogin as root or any Linux user. Server says "Incorrect login" But I tried with all otherLinux user login which  are all logged well before inducing  root.How to login nowBelow is part of document :------------------------------------------------------------------------------------------------------------------------------- Note: You can use pam-auth-update to add the necessary entries for winbind authentication. If you installed libpam-winbind above, this step is all you need to do to configure pam. You may want to add the line to automatically create the home directory.sudo pam-auth-updateThis PAM configuration does not acquire a Kerberos TGT at login. To acquire a ticket, use kinit after logging in, and consider using kdestroy in a logout script.file: /etc/pam.d/common-accountaccount sufficient       pam_winbind.soaccount required         pam_unix.sofile: /etc/pam.d/common-authauth sufficient pam_winbind.soauth sufficient pam_unix.so nullok_secure use_first_passauth required   pam_deny.so-------------------------------------------------------------------------------------------------------------------- 

2 1

doveadm: Fatal: All your namespaces have a location setting
by Ben 21 Feb '17

21 Feb '17

Hi, I am trying to migrate mail from an old server and am receiving the following error : doveadm(user(a)example.com): Fatal: All your namespaces have a location setting. Only namespaces with empty location settings are converted. (One namespace should default to mail_location setting) I found an old thread (http://www.dovecot.org/list/dovecot/2012-September/068269.html) that referred to "location" being set. However this is not the case with me, my config reads: 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 = } My dsync conf looks as follows : imapc_host = old-server.example.com imapc_user = %u imapc_features = rfc822.size imapc_features = $imapc_features fetch-headers mail_prefetch_count = 20 imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = yes The command I'm calling is: sudo -u my_dovecot_user doveadm -c /etc/dovecot/dsync_config.conf -o mail_fsync=never backup -R -u user(a)example.com imapc:

3 3

Re: How to dsync mdbox compressed to maildir uncompressed
by Daniel Betz 21 Feb '17

21 Feb '17

Hi Timo, thank you for the hint, but it doesnt seems to work. doveadm sync -u imap(a)test.de 'doveadm -o mail="maildir:~/Maildir" -o "mail_plugins=quota" dsync-server -u imap(a)test.de' Also tried -o mail=~/Maildir .. -o maildir:~/Maildir .. The log throws an error: Feb 21 13:05:35 doveadm: Error: Panic: io_add(0x1) called twice fd=9, callback=0x7f49baa06840 -> 0x7f49ba991e30 Feb 21 13:05:35 doveadm: Error: Error: Raw backtrace: /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(+0x92d70) [0x7f49ba9efd70] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f49ba9efdda] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f49ba98b4e0] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(ioloop_iolist_add+0x83) [0x7f49baa03dc3] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(io_loop_handle_add+0x3b) [0x7f49baa046db] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(+0xa599f) [0x7f49baa0299f] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(io_add+0xd) [0x7f49baa02a4d] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(master_service_io_listeners_add+0x65) [0x7f49ba9916d5] -> /usr/local/dovecot2/lib/dovecot/libdovecot.so.0(master_service_init_finish+0xb7) [0x7f49ba9917a7] -> /usr/local/dovecot2/bin/doveadm(main+0x189) [0x4143a9] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f49ba5bcb15] -> /usr/local/dovecot2/bin/doveadm() [0x414785] Feb 21 13:05:35 dsync-local(imap(a)test.de): Error: read(remote) failed: EOF (version not received) Feb 21 13:05:35 dsync-local(imap(a)test.de): Error: Remote command died with signal 6: doveadm -o mail="maildir:~/Maildir" -o "mail_plugins=quota" dsync-server -u imap(a)test.de dsync-server Regards, Daniel Von: Timo Sirainen [mailto:tss@iki.fi] Gesendet: Dienstag, 21. Februar 2017 12:01 An: Daniel Betz <dbetz(a)df.eu> Cc: dovecot(a)dovecot.org Betreff: Re: How to dsync mdbox compressed to maildir uncompressed On 21 Feb 2017, at 12.49, Daniel Betz <dbetz(a)df.eu> wrote: Hello, we are using doveadm sync to export mdbox to maildir format, so we can use an external tool to convert into an pst file. Since we have enabled zlib compression doveadm sync always exports the maildir gzip compressed. Are there any ways to prevent the doveadm sync to export the maildir compressed ? Have tried this: doveadm -o "maildir_copy_with_hardlinks=no" sync -u imap(a)test.de maildir:~/Maildir >From Wiki: If you want to use dsync to convert to a compressed Maildir you may need -o maildir_copy_with_hardlinks=no (this is set to yes by default and will prevent compression). Run it via two processes so you can give separate settings for them, something like: doveadm sync -u imap(a)test.d 'doveadm -o mail=~/Maildir -o mail_plugins=everything-but-zlib dsync-server'

1 0

How to dsync mdbox compressed to maildir uncompressed
by Daniel Betz 21 Feb '17

21 Feb '17

Hello, we are using doveadm sync to export mdbox to maildir format, so we can use an external tool to convert into an pst file. Since we have enabled zlib compression doveadm sync always exports the maildir gzip compressed. Are there any ways to prevent the doveadm sync to export the maildir compressed ? Have tried this: doveadm -o "maildir_copy_with_hardlinks=no" sync -u imap(a)test.de maildir:~/Maildir >From Wiki: If you want to use dsync to convert to a compressed Maildir you may need -o maildir_copy_with_hardlinks=no (this is set to yes by default and will prevent compression). Regards, Daniel # 2.2.27 (c0f36b0): /usr/local/dovecot2/etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=60000 } is lower than required under max. load (500500) # OS: Linux 3.10.0-327.36.3.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_cache_negative_ttl = 1 mins auth_cache_size = 64 M auth_cache_ttl = 2 hours auth_mechanisms = plain login auth_username_chars = base_dir = /var/run/dovecot/ debug_log_path = /dev/null default_login_user = dovecot default_vsz_limit = 750 M disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 1001 first_valid_uid = 1001 info_log_path = /var/log/dovecot/messages lda_mailbox_autocreate = yes lda_original_recipient_header = X-Envelope-To log_path = /dev/stderr login_log_format_elements = user=[%u] method=%m rip=%r lip=%l %c mail_gid = 1001 mail_location = mdbox:~:INDEX=%h/INDEX mail_plugins = quota notify mail_log zlib mail_uid = 1001 mbox_write_locks = fcntl namespace { inbox = yes location = mailbox Drafts { auto = no special_use = \Drafts } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox "Infizierte Objekte" { auto = no special_use = \Junk } mailbox Sent { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = no special_use = \Trash } prefix = separator = . type = private } namespace inbox { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap2.conf driver = ldap } plugin { quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_rule1 = Trash:storage=+100M quota_rule2 = INBOX.Trash:storage=+100M quota_warning = storage=85%% quota-warning 85 %u quota_warning1 = storage=95%% quota-warning 95 %u quota_warning2 = storage=99%% quota-warning 99 %u zlib_save = gz zlib_save_level = 6 } replication_max_conns = 30 sendmail_path = /usr/local/exim/bin/exim service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = popuser } unix_listener replication-notify { mode = 0666 user = popuser } } service anvil { client_limit = 60000 } service auth { client_limit = 60000 unix_listener auth-userdb { mode = 0666 user = popuser } unix_listener auth { mode = 0666 user = popuser } } service config { unix_listener config { user = popuser } } service dict { unix_listener dict { mode = 0666 user = popuser } } service dns_client { process_limit = 6000 process_min_avail = 12 unix_listener dns-client { mode = 0666 user = popuser } } service doveadm { inet_listener { port = 12345 } user = popuser } service imap-login { chroot = login client_limit = 6000 process_limit = 100 process_min_avail = 16 service_count = 0 } service imap { executable = /usr/local/dovecot2/libexec/dovecot/imap process_limit = 250000 process_min_avail = 50 service_count = 250 } service ipc { client_limit = 60000 unix_listener ipc { mode = 0650 user = dovecot } unix_listener login/ipc-proxy { mode = 0650 user = dovecot } } service lmtp { unix_listener lmtp { mode = 0666 user = popuser } } service pop3-login { chroot = login client_limit = 6000 process_limit = 100 process_min_avail = 16 service_count = 0 } service pop3 { executable = /usr/local/dovecot2/libexec/dovecot/pop3 process_limit = 250000 process_min_avail = 50 service_count = 250 } service quota-warning { executable = script /usr/local/dovecot2/bin/quota-warning.sh unix_listener quota-warning { mode = 0600 user = popuser } user = popuser } service replicator { unix_listener replicator-doveadm { mode = 0600 user = popuser } } ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = TLSv1.2 TLSv1.1 TLSv1 !SSLv3 !SSLv2 userdb { driver = prefetch } userdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol doveadm { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-doveadm.conf driver = ldap name = } userdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-doveadm.conf driver = ldap name = } } protocol lda { info_log_path = /var/log/dovecot-lda log_path = /var/log/dovecot-lda log_timestamp = "%b %d %H:%M:%S " mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ postmaster_address = %u } protocol imap { imap_client_workarounds = mail_max_userip_connections = 100 mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota notify mail_log zlib imap_quota imap_zlib } protocol pop3 { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_fast_size_lookups = yes pop3_reuse_xuidl = no pop3_uidl_format = %g }

3 2

IMAP directory structure.
by C5ace 21 Feb '17

21 Feb '17

Hello, I use Dovecot 2.1.7. and like to know how to force the IMAP directory structure to be: The IMAP server's desired directory structure is: root@server-2:/var/vmail/c5ace.com/test/Maildir# /.INBOX /.INBOX.Archives /.INBOX.Drafts /.INBOX.Junk /.INBOX.Sent /.INBOX.Templates /.INBOX.Trash and to prevent the mail clients like Thunderbird, Claws Mail, etc. to add additional out of tree directories. Thanks in advance. Elmar

2 1

v2.2.28 release candidate released
by Timo Sirainen 21 Feb '17

21 Feb '17

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig Pretty large release. Please test before the final v2.2.28, which should be out in a few days. BTW. Our plan is to start making new releases approximately every month from now on. * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache caching decisions. * Expunging mails writes GUID to dovecot.index.log now only if the GUID is quickly available from index/cache. * imap: When BINARY FETCH sees invalid content, return NO [PARSE] reply instead of [UNKNOWNCTE] (which is now used only for actually unknown Content-Transfer-Encoding headers). * pop3c: Increase timeout for PASS command to 5 minutes. * Mail access errors are no longer ignored when searching or sorting. With IMAP the untagged SEARCH/SORT reply is still sent the same as before, but NO reply is returned instead of OK. + Make dovecot.list.index's filename configurable. This is needed when there are multiple namespaces pointing to the same mail root (e.g. lazy_expunge namespace for mdbox). + Add size.virtual to dovecot.index when folder vsizes are accessed (e.g. quota=count). This is mainly a workaround to avoid slow quota recalculation performance when message sizes get lost from dovecot.index.cache due to corruption or some other reason. + auth: Support OAUTHBEARER and XOAUTH2 mechanisms. Also support them in lib-dsasl for client side. + auth: Support filtering by SASL mechanism: passdb { mechanisms } + Shrink the mail processes' memory usage by not storing settings duplicated unnecessarily many times. + imap: Add imap_fetch_failure setting to control what happens when FETCH fails for some mails (see example-config). + imap: Include info about last command in disconnection log line. + imap: Created new SEARCH=X-MIMEPART extension. It's currently not advertised by default, since it's not fully implemented. + fts-solr: Add support for basic authentication. + Cassandra: Support automatically retrying failed queries if execution_retry_interval and execution_retry_times are set. + doveadm: Added "mailbox path" command. + mail_log plugin: If plugin { mail_log_cached_only=yes }, log the wanted fields only if it doesn't require opening the email. + mail_vsize_bg_after_count setting added (see example-config). + mail_sort_max_read_count setting added (see example-config). - Index files: day_first_uid wasn't updated correctly since v2.2.26. This caused dovecot.index.cache to be non-optimal. - imap: SEARCH/SORT may have assert-crashed in client_check_command_hangs - imap: FETCH X-MAILBOX may have assert-crashed in virtual mailboxes. - imap: Running time in tagged command reply was often wrongly 0. - search: Using NOT n:* or NOT UID n:* wasn't handled correctly - director: doveadm director kick was broken - director: Fix crash when using director_flush_socket - director: Fix some bugs when moving users between backends - imapc: Various error handling fixes and improvements - master: doveadm process status output had a lot of duplicates. - autoexpunge: If mailbox's rename timestamp is newer than mail's save-timestamp, use it instead. This is useful when autoexpunging e.g. Trash/* and an entire mailbox is deleted by renaming it under Trash to prevent it from being autoexpunged too early. - autoexpunge: Multiple processes may have been trying to expunge the same mails simultaneously. This was problematic especially with lazy_expunge plugin. - auth: %{passdb:*} was empty in auth-worker processes - auth-policy: hashed_password was always sent empty. - dict-sql: Merge multiple UPDATEs to a single statement if possible. - fts-solr: Escape {} chars when sending queries - fts: fts_autoexpunge_exclude = \Special-use caused crashes - doveadm-server: Fix leaks and other problems when process is reused for multiple requests (service_count != 1) - sdbox: Fix assert-crash on mailbox create race - lda/lmtp: deliver_log_format values weren't entirely correct if Sieve was used. especially %{storage_id} was broken.

8 10

Released Pigeonhole v0.4.17.rc1 for Dovecot v2.2.28.rc1.
by Stephan Bosch 21 Feb '17

21 Feb '17

Hello Dovecot users, Several bugs were found in the course of the last few months, but no new features were created. So, this will be strictly a bug-fixing release. The previous Pigeonhole release should still work with the new Dovecot release, which means you are not required to upgrade. However, my advice would be to upgrade once this release candidate matures into a final release, since at least the first bug listed below is pretty severe. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the message to be forgotten or that headers modified by the "editheader" extension would revert to their original state. - file script storage: Amended the up-to-date time stamp comparison for on-disk binaries to include nanoseconds. This will fix problems occurring when both binary and script are saved within the same second. This fix is ineffective on older systems that have no support for nanoseconds in stat() timestamps, which should be pretty rare nowadays. - file script storage: Improve saving and listing permission error to include more details. - imapsieve plugin: Make sure "INBOX" is upper case in static mailbox rules. Otherwise, the mailbox name would never match, since matching is performed case-sensitively and Dovecot only returns the upper-cased "INBOX". - imapsieve plugin: Fixed assert failure occurring when used with virtual mailboxes. - doveadm sieve plugin: Fixed crash when setting Sieve script via attribute's string value. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.17… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.17… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 2

Sieve not filtering
by Ben 20 Feb '17

20 Feb '17

Hi, I have copied accross a known-good sieve file from a working server and its not filtering. Everything just gets chucked into INBOX. doveconf-n at the bottom of this mail Feb 17 16:05:20 server postfix/smtpd[51562]: 7FA5E12CBBC: client=unknown[192.168.167.57] Feb 17 16:05:23 server postfix/cleanup[51565]: 7FA5E12CBBC: message-id=<> Feb 17 16:05:23 server postfix/qmgr[45471]: 7FA5E12CBBC: from=<sender(a)example.com>, size=182, nrcpt=1 (queue active) Feb 17 16:05:23 server dovecot: lmtp(51467): Connect from local Feb 17 16:05:23 server dovecot: auth-worker(51568): passwd(recipient(a)example.com): unknown user Feb 17 16:05:23 server dovecot: lmtp(51467, recipient(a)example.com) 1JK2B0Mfp1gLyQAAHLpRfg: sieve: msgid=unspecified: stored mail into mailbox 'INBOX' Feb 17 16:05:23 server dovecot: lmtp(51467): Disconnect from local: Successful quit Feb 17 16:05:23 server postfix/lmtp[51566]: 7FA5E12CBBC: to=<recipient+something(a)example.com>, orig_to=<recipient+something(a)example.com>, relay=server.example.com[private/dovecot-lmtp], delay=4.9, delays=4.9/0.01/0/0.05, dsn=2.0.0, status=sent (250 2.0.0 <bp+nanog(a)example.com> 1JK2B0Mfp1gLyQAAHLpRfg Saved) Feb 17 16:05:23 server postfix/qmgr[45471]: 7FA5E12CBBC: removed This is the syntax I'm using in my sieve file: require ["fileinto","envelope"]; if anyof (address :is :all "to" ["recipient+something@example.com”,”mailing_list@example.com”], header :contains ["Cc", "Delivered-To"] ["recipient+something@example.com”,”mailing_list@example.com”]) { fileinto “THIS_FOLDER”; stop; } # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body environment mailbox date ihave enotify mbox_write_locks = fcntl 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 } passdb { driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = ~/.dovecot.sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = its_virtmail mode = 0660 user = its_virtmail } } service imap-login { process_min_avail = 3 } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = its_virtmail } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieves { address = port = 5190 ssl = yes } } ssl = required ssl_cert = <REMOVED ssl_cipher_list = REMOVED ssl_dh_parameters_length = 2048 ssl_key = </REMOVED ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = sieve postmaster_address = me(a)example.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 20 }

5 5

Issue connecting to dovecot from remote machine
by Antoine Sirven 20 Feb '17

20 Feb '17

Hi, I've set up a postfix +dovecot configuration on my debian jessie. But I have a connection issue. When I try to connect from thunderbird it doesn not work. When I check out my debug logs I get : auth-worker(22252): Info: pam(myuser,hostIP): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: correctPassword) Running doveadm auth test tells me I can authenticate with the same password. So I tried connecting via openssl. When I connect from my local host, everything goes fine : * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5] Dovecot ready. a login myUser myPassword a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE] Logged in But when I run the same thing from my remote laptop, I never get any reply from the imap server. It's as if the request wasn't reaching the server. Although I do get a first reply from the server, I just can't log in. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5] Dovecot ready. a login myUser myPassword (... and then nothing...) The port is properly open when I run nmap. I really don't get what's wrong. Any of you has any idea? Here are my versions & conf : # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab120.16 x86_64 Debian 8.7 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = yes disable_plaintext_auth = no info_log_path = /var/log/maildebug.log mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail 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 = failure_show_msg=yes session=yes dovecot driver = pam } passdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } ssl = required ssl_cert = </etc/ssl/certs/mailcert.pem ssl_key = </etc/ssl/private/mail.key userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_ssl = yes Thanks a lot

2 2

Re: Upgrade from 1.2 to 2.2
by Joseph Tam 16 Feb '17

16 Feb '17

Eduardo M KALINOWSKI writes in reesponse to Gandalf Corvotempesta post: >> I've already read that, and as wrote previously, everything broke down. >> dovecont -n wasn't able to convert the configuration file and dovecot >> wasn't started properly. >> The only way to fix was to downgrade. >> >> As this is a production server, I would like to avoid this kind of issue..... > > Set up a server replicating exactly the configuration you have at > present. Doesn't need to be anything fancy, a virtual machine is > enough. Actually, a virtual machine is a great tool if you can make > snapshots and then rollback to known states if any attempt at a change > fails. If you absolutely can't test on a VM or another test host, you can run the new version along side your current version in another installation directory. Configure your new installation to run on alternate ports. You can work off copies of mail data as well if you really want to isolate your test. Then you can gradually phase in your new version by swapping alternate port/data with production port/data. Joseph Tam <jtam.home(a)gmail.com>

1 0

doveadm backup and quota
by florent＠coppint.com 15 Feb '17

15 Feb '17

Hi, I'm looking to convert all mailboxes from Maildir format to mdbox. When I try my procedure on a user having ~45GB of messages, its quota is growing very fast and is now up to 66GB. I run this command : doveadm -v backup -u user(a)domain.com mdbox:/mnt/maildata1/domain.com/user/mdbox I expected this command to make a copy of user mailbox, it does not make sense to count the backup in its quota. Maybe quota is simply recalculated ? But running a "du -sh" on its home directory is showing a 46G disk usage ! (backup is not stored in home dir) Can someone tell me what happens on my setup ? I use Dovecot 2.2.24. Thank you. Florent

1 1

Upgrade from 1.2 to 2.2
by Gandalf Corvotempesta 15 Feb '17

15 Feb '17

Hi, I have a production server running Debian Squeeze with Dovecot 1.2 I would like to upgrade everything to Jessie, running 2.2 Last time I did something similiar, but from Lenny to Squeeze, the whole dovecot installation broke. Any suggestion on how to upgrade everything ? Can I test our current configuration with a newer dovecot version to be sure that everything would be converted properly with "doveconf -n -c /etc/dovecot/dovecot.conf > dovecot-2.conf" ? Thank you

4 6

Re: dovecot config for 1500 simultaneous connection
by Rajesh M 15 Feb '17

15 Feb '17

christian the servers i currently own are dell servers. The servers i plan to buy are Dell R530, 2U rack servers with 8 x 3.5 inch drives, with 64 gb ram each, Hardware raid. I am thinking of 2 X 300 gb ssds raid1 and 6 x 2 tb drives in raid10 for data. I do not have any experience in setting up drdb (that would be my next step) ... primarily using standalone servers with hardware level redundancy. For backup-ups i rsync data to backup servers, also use qmail taps for backing up sent/recd emails on a per user basis. i am using mysql authentication backend my mail server is qmailtoaster, ie with vpopmail, spamdyke, simscan. you had mentioned as follows ############## With 4000 users and 5 logins/s I can't imagine anything that wouldn't be able to: a) put all of the relevant data into RAM and b) thus handle auth requests in very timely manner. The example I gave earlier about my servers with 140 logins/s authenticates against LDAP and isn't very busy doing so while also fitting all 2.7GB of data for about 1 million users into RAM. ############## >>>>>>>>>>>>>>>>>>how do i put all relevant data into the RAM ? thanks rajesh ----- Original Message ----- From: Christian Balzer [mailto:chibi@gol.com] To: dovecot(a)dovecot.org Sent: Tue, 14 Feb 2017 16:40:01 +0900 Subject: Hello, On Mon, 13 Feb 2017 22:53:23 +0530 Rajesh M wrote: > thanks for your help > > happy to say that the performance dramatically improved after i use the high performance settings from here > http://wiki.dovecot.org/LoginProcess > That's why that page is there. > grep Login: /var/log/mail.log.1 |wc -l > with the mail.log being of a typical, busy day. > 412992 > So about 5 login/s, not that busy, but that of course also depends on your HW and authentication backend. > i also picked up the imap and pop3 connections during peak hours > [root@ns1 domains]# doveadm who | awk '/imap/{m+=$2}/pop3/{n+=$2}END{print m,n}' > username # proto (pids) (ips) > > max figures i got was 535 for imap and 97 for pop > > > Question 1 > i wish to improve the performance further by caching the logins. current the same is kept disable because when user's change passwords then they are not able to immediately login with the new password for some time. How to solve this issue. > There is no solution, caching auth data is by default fraught with that sort of peril. And how did you determine that caching auth data would actually improve things? What is your authentication backend? With 4000 users and 5 logins/s I can't imagine anything that wouldn't be able to: a) put all of the relevant data into RAM and b) thus handle auth requests in very timely manner. The example I gave earlier about my servers with 140 logins/s authenticates against LDAP and isn't very busy doing so while also fitting all 2.7GB of data for about 1 million users into RAM. > > > further to the above. > i am planning to put up a large mail server with one of the following options > Don't plan 1, always plan a pair and then use whatever you're comfortable with to turn them into a HA cluster, like Pacemaker with DRBD. > option 1 > OS and mailqueue : 2 X 600 gb 15k rpm raid 1 What kind of RAID, HW or MD? > data : 4 X 2000 gb raid 10 for data > backup : 2 X 2000 gb raid 10 for backup While with Linux MD a 2 disk RAID10 would be possible, it wouldn't be particular helpful (slower than a RAID 1 with writes). > 32 gb ram > > > option 2 > os and mail queue : 4 X 600 gb 15k rpm raid 10 Those 15k HDDs tend to be expensive. Estimate your expected writes per day (iostat on an existing server can give you some hints) and get 2 SSDs instead, DC S3520s if 1 DWPD is sufficient, DC S3610s if you need 3 DWPD (doubtful), S3710 if you need 10 DWPD (very doubtful). Similar for Samsung DC level SSDs, check their specs. For example, my busiest mailbox servers only write about 250KB/s averaged, which mean about 50GB/day and thus would be a fit even for a small S3520. I'm still using 200GB S3710s because I can afford them, like the speed and never ever want to worry about wearout. > data : 4 X 2000 gb raid 10 for data > 32 gb ram > > i am having the OS and mail queue on primary drives > > i understand that Raid10 give a faster write and read whereas Raid 1 will have slow writes and fast reads > While that is true, you're missing the real difference here, the number of HDDs. With 4 of them in the RAID10 they will be twice as fast as the 2 disk RAID1. This can be tweaked even further with the various RAID 10 layout options, "man md". > the question is will there be huge performance difference between Raid1 and Raid 10 when it comes small files like mail queue ? > Again as explained above, double the IOPS, so yes. Christian > > thanks > rajesh > ----- Original Message ----- > From: Christian Balzer [mailto:chibi@gol.com] > To: dovecot(a)dovecot.org > Cc: kevin(a)my.walr.us > Sent: Mon, 13 Feb 2017 10:46:13 +0900 > Subject: > > > Hello, > > On Sun, 12 Feb 2017 08:27:21 -0500 KT Walrus wrote: > > > Thanks for the info. I do have one further question for you. On your servers that are currently handling 50k IMAP sessions, how many users does that correspond to? Since many users will have multiple IMAP sessions on multiple devices, I’d like to hear about some real-world numbers that could be used for budgeting a new project like mine. > > > > Those servers would actually be the wrong ones to look at, as they are > primarily accessed by the aforementioned broken client, so the numbers are > somewhat skewed. > However looking at other servers with a more "normal" user spread things > aren't actually too different. > > The average number of sessions per user tends to be 2. > The clear majority (over 50%) only has one session open (people with well > behaved and configured clients watching the INBOX mostly). > Another 30% has 2 sessions open, again the typical state of this would be > clients watching another mailbox besides INBOX, typically SENT. > The rest has 3 and more sessions open. > > The number of sessions could of course be drastically reduced if any > client would support IMAP NOTIFY, alas none that I'm aware of do. > > Lastly no more than 60% of the session seem to be in IDLE at any given > time, so my comments about RAM and IMAP hibernation effectiveness stand. > > > Also, do you use Dovecot IMAP proxies in front of your backend servers? If so, how many IMAP sessions can one proxy server handle (assuming the proxy does authorization using MySQL running on a separate server)? And, could the proxy server be tuned to help in optimizing mostly IDLE backend sessions? > > > > Yes to Dovecot Proxying, of course. > > No idea about MySQL, with (Open)LDAP nothing is breaking a sweat at an > average of 140 logins per second (IMAP and POP) on the 2 proxy servers. > If you can fit your entire dataset into RAM it should be fine, my LDAP > servers fall into that category and take about 10% of a slow (1.2GHz, 34%, > power-save mode) core only to handle the that load (also 2 servers). > And the rate of logins/s is what you need to worry about most and optimize > for. > > The proxies will of course have to do the shuffling of data and SSL > en/de-coding, but again they're not particular busy with that. > > The number of sessions comes into play when looking at the number of login > processes on the proxies and their memory footprint. > An IMAP login process on the proxies in performance mode with a client > limit of 1000 will consume about 55MB at most. > So assume at least 55KB RAM per session. > > Read Timo's mail I linked to about IMAP hibernation, AFAIK nothing has > happened to make proxies more supportive for this though. > > Christian > > > On Feb 12, 2017, at 1:58 AM, Christian Balzer <chibi(a)gol.com> wrote: > > > > > > > > > Hello, > > > > > > On Fri, 10 Feb 2017 14:50:03 -0500 KT Walrus wrote: > > > > > >>> 1. 256GB of real RAM, swap is for chums. > > >> > > >> Are you sure that 100,000 IMAP sessions wouldn’t work well with SWAP, especially with fast SSD storage (which is a lot cheaper than RAM)? > > >> > > > > > > I'm sure about tax and death, not much else. > > > > > > But as a rule of thumb I'd avoid swapping out stuff on production servers, > > > even if it were to SSDs. > > > Incidentally the servers I'm talking about here have their OS and swap on > > > Intel DC S3710s (200GB) and the actual storage on plenty of 1.6TB DC > > > S3610s. > > > > > > Relying on the kernel to make swap decisions is likely to result in much > > > reduced performance even with fast SWAP when you're overcommitting things > > > on that scale. > > > > > > > > > But read on. > > > > > >> Seems that these IMAP processes are long lived processes (idling most of the time) that don’t need that much of the contents of real memory available for much of the life of the process. I use a database proxy in front of MySQL (for my web apps) so that there can be a large number of TCP connections to the proxy where the frontend requests are queued for execution using a small number of backend connections. > > >> > > >> Could Dovecot IMAP be re-written to be more efficient so it works more like MySQL (or other scalable data servers) that could handle a million or more IMAP sessions on a server with 32GBs or less of RAM? Those IMAP sessions aren’t doing much most of the time and shouldn’t really average 2MB of active data per session that needs to be resident in main memory at all times. > > >> > > > See IMAP hibernation: > > > https://www.mail-archive.com/dovecot@dovecot.org/msg63429.html <https://www.mail-archive.com/dovecot@dovecot.org/msg63429.html> > > > > > > I'm going to deploy/test this in production in about 2 months from now, > > > but if you look at the link and the consequent changelog entries you'll see > > > that it has certain shortcomings and bug fixes in pretty much each release > > > after it was introduced. > > > > > > But this is the correct way to tackle things, not SWAP. > > > > > > Alas I'm not expecting miracles and if more than 20% of the IMAP sessions > > > here will be hibernated at any given time I'd be pleasantly surprised. > > > > > > Because between: > > > > > > 1. Finding a sensible imap_hibernate_timeout. > > > > > > 2. Having well behaved clients that keep idling instead of restarting the > > > sequence (https://joshdata.wordpress.com/2014/08/09/how-bad-is-imap-idle/ <https://joshdata.wordpress.com/2014/08/09/how-bad-is-imap-idle/>) > > > > > > 3. Having lots of mobile clients who either get disconnected (invisible to > > > Dovecot) or have aggressive IDLE timers to overcome carrier NAT timeouts > > > (a large mobile carrier here times out idle TCP sessions after 2 minutes, > > > forcing people to use 1 minute IDLE renewals, making 1. up there a > > > nightmare). > > > > > > 4. Having really broken clients (don't ask, I can't tell) which open IMAP > > > sessions, don't put them into IDLE and thus having them expire after 30 > > > minutes. > > > > > > the pool of eligible IDLE sessions isn't as big as it could be, in my case > > > at least. > > > > > >> My mail server isn’t that large yet as I haven’t fully deployed Dovecot outside my own small group yet, but it would be nice if scaling Dovecot IMAP to millions of users wasn’t limited to 50,000 IMAP sessions on a server... > > >> > > > > > > Scaling up is nice and desirable from a cost (rack space, HW) perspective, > > > but the scalability of things OTHER than Dovecot as I pointed out plus > > > that little detail of failure domains (do you really want half of your > > > eggs in one basket?) argue for scaling out after a certain density. > > > > > > I'm feeling my way there at this time, but expect more than 100k sessions > > > per server to be tricky. > > > > > > Lastly, when I asked about 500k sessions per server here not so long ago, > > > ( http://www.dovecot.org/list/dovecot/2016-November/106284.html <http://www.dovecot.org/list/dovecot/2016-November/106284.html> ) > > > Timo mentioned that he's not aware of anybody doing more than 50k per > > > server, something I got licked already and definitely will go to 100k > > > eventually. > > > > > > Regards, > > > > > > Christian > > >>> On Feb 10, 2017, at 11:07 AM, Christian Balzer <chibi(a)gol.com> wrote: > > >>> > > >>> On Fri, 10 Feb 2017 07:59:52 -0500 KT Walrus wrote: > > >>> > > >>>>> 1500 IMAP sessions will eat up about 3GB alone. > > >>>> > > >>>> Are you saying that Dovecot needs 2MB of physical memory per IMAP session? > > >>>> > > >>> That depends on the IMAP session, read the mailbox size and index size, > > >>> etc. > > >>> Some are significantly larger: > > >>> --- > > >>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > >>> 1033864 mail 20 0 97600 67m 54m S 0 0.1 0:01.15 imap > > >>> --- > > >>> > > >>> But yes, as somebody who has mailbox servers with 55k+ session the average > > >>> is around 1.6MB. > > >>> > > >>>> If I want to support a max 100,000 IMAP sessions per server, I should configure the server to have at least 200GBs of SWAP? > > >>>> > > >>> You will want: > > >> > > >>> 2. Understanding how to tune Dovecot and more importantly the overall > > >>> system to such a task (see that PID up there?). > > >>> 3. Be willing to deal with stuff like top and ps taking ages to start/run > > >>> and others like atop actually killing dovecot (performance wise, not > > >>> literally) when doing their obviously flawed cleanup on exit. Some things > > >>> clearly do NOT scale well. > > >>> > > >>> My current goal is to have 100k capable servers that work well, 200k in a > > >>> failover scenario, but that won't be particular enjoyable. > > >>> > > >>> Christian > > >>> > > >>>>> On Feb 10, 2017, at 3:58 AM, Christian Balzer <chibi(a)gol.com> wrote: > > >>>>> > > >>>>> On Fri, 10 Feb 2017 01:13:20 +0530 Rajesh M wrote: > > >>>>> > > >>>>>> hello > > >>>>>> > > >>>>>> could somebody with experience let me know the dovecot config file settings to handle around 1500 simultaneous connections over pop3 and 1500 connection over imap simultaneously. > > >>>>>> > > >>>>> > > >>>>> Be very precise here, you expect to see 1500 as the result of > > >>>>> "doveadm who |grep pop3 |wc -l"? > > >>>>> > > >>>>> Because that implies an ungodly number of POP3 connects per second, given > > >>>>> the typically short duration of these. > > >>>>> > > >>>>> 1500 IMAP connections (note that frequently a client will have more than > > >>>>> the INBOX open and thus have more than one session and thus process on the > > >>>>> server) are a much easier proposition, provided they are of the typical > > >>>>> long lasting type. > > >>>>> > > >>>>> So can you put a number to your expected logins per second (both protocols)? > > >>>>> > > >>>>>> my server > > >>>>>> > > >>>>>> server configuration > > >>>>>> hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 > > >>>>>> gb hdd for data (No raid) > > >>>>>> > > >>>>> No RAID and no other replication like DRBD? > > >>>>> Why would you even bother? > > >>>>> > > >>>>> How many users/mailboxes in total with what quota? > > >>>>> > > >>>>> 1500 IMAP sessions will eat up about 3GB alone. > > >>>>> You will want more memory, simply to keep all relevant SLAB bits (inodes, > > >>>>> dentries) in RAM. > > >>>>> > > >>>>> If you really have several hundreds logins/s, you're facing several > > >>>>> bottlenecks: > > >>>>> 1. Login processes themselves (easily fixed by high performance mode) > > >>>>> 2. Auth processes (that will depend on your backends, method mostly) > > >>>>> 3. Dovecot master process (spawning mail processes) > > >>>>> > > >>>>> The later is a single-threaded process, so it will benefit from a faster > > >>>>> CPU core. > > >>>>> It can be dramatically improved by enabling process re-usage, see: > > >>>>> http://wiki.dovecot.org/PerformanceTuning > > >>>>> > > >>>>> However that also means more memory usage. > > >>>>> > > >>>>> > > >>>>> > > >>>>> Christian > > >>>>> > > >>>>>> > > >>>>>> thanks > > >>>>>> rajesh > > >>>>>> > > >>>>> > > >>>>> [snip] > > >>>>> -- > > >>>>> Christian Balzer Network/Systems Engineer > > >>>>> chibi(a)gol.com Global OnLine Japan/Rakuten Communications > > >>>>> http://www.gol.com/ > > >>>> > > >>> > > >>> > > >>> -- > > >>> Christian Balzer Network/Systems Engineer > > >>> chibi(a)gol.com <mailto:chibi@gol.com> <mailto:chibi@gol.com <mailto:chibi@gol.com>> Global OnLine Japan/Rakuten Communications > > >>> http://www.gol.com/ <http://www.gol.com/> <http://www.gol.com/ <http://www.gol.com/>> > > > > > > > > > -- > > > Christian Balzer Network/Systems Engineer > > > chibi(a)gol.com <mailto:chibi@gol.com> Global OnLine Japan/Rakuten Communications > > > http://www.gol.com/ <http://www.gol.com/> > > > > -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

2 1

Re: dovecot config for 1500 simultaneous connection
by Joseph Tam 15 Feb '17

15 Feb '17

Rajesh M wrote: > i wish to improve the performance further by caching the logins. > current the same is kept disable because when user's change passwords > then they are not able to immediately login with the new password for > some time. How to solve this issue. Dovecot shouldn't be doing that. According to https://wiki2.dovecot.org/Authentication/Caching Data is used from the cache if it's not expired (auth_cache_ttl setting) - If authentication fails this time, but it didn't fail last time, it's assumed that the password has changed and a database lookup is done. As I read it, an authentication failure will cause an update of cache credentials. The problem I encountered is the converse -- a user changes their password, but forgets to update their mail reader's or web browser's stored password, which continues to work until the TTL expires. Another related security situation I've encountered is when a fraudster has phished a user's password. A user/admin changes the password, but forgets to invalidate dovecot's cached entry, allowing the fraudster contunuing access to the mail account until the TTL expires or user logs in with new credentials. I've been burnt by this one. Joseph Tam <jtam.home(a)gmail.com>

2 2

pop3 login core dump
by Luciano Mannucci 14 Feb '17

14 Feb '17

Hello! Sorry for my newbie question, I've notied some lines in my logfile like this: Feb 13 16:05:54 pop3-login: Fatal: master: service(pop3-login): child 10660 killed with signal 11 (core not dumped - add -D parameter to service pop3-login { executable } ... where am I supposed to add the -D option in order to get the core file dumped so I can examine it? Thanks to all, luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

1 2

Mailbox suddenly inaccessible
by Sven Strickroth 14 Feb '17

14 Feb '17

Hi, out of the sudden I've an inaccessible folder with Dovecot 2.2.27 (c0f36b0) from Debian Jessy backports. $ doveadm mailbox list -u mail(a)example.com INBOX/Erledigt INBOX/Erledigt/Erledigt INBOX/Versicherung gesendet Sent INBOX However, it is not accessible any more, my IMAP client tells me: "STATUS: Mailbox doesn't exist: INBOX/Erledigt" Also: $ doveadm search -u mail(a)example.com mailbox INBOX/Erledigt doveadm(mail(a)example.com): Error: Couldn't get mailbox 'INBOX/Erledigt' GUID: Mailbox doesn't exist: INBOX/Erledigt Other mailboxes (especially INBOX/Erledigt/Erledigt) are accessible: $ doveadm search -u mail(a)example.com mailbox INBOX/Erledigt/Erledigt 60af0f1964d68d574a480000f94cf17a 346 60af0f1964d68d574a480000f94cf17a 367 ... $ doveadm -f table mailbox status -u mail(a)example.com "messages vsize" "INBOX*" mailbox messages vsize INBOX/Erledigt2 15 25868676 INBOX/Erledigt/Erledigt 4344 6107238270 INBOX 24 36081472 I'm using mdbox and see no errors in syslog from dovecot. Any ideas on what's going on and how I can recover the mails in that folder? -- Best regards, Sven Strickroth PGP key id F5A9D4C4 @ any key-server

2 2

openssl 1.1.0d breaks Android7 TLS connects
by Tributh 14 Feb '17

14 Feb '17

Hi, the actual OpenSSL version detection in dovecot is insufficient. The implementation only checks for SSL_CTRL_SET_ECDH_AUTO. That was effective for OpenSSL 1.0.2, but in 1.1.0 it is removed. Thats the code part: #ifdef SSL_CTRL_SET_ECDH_AUTO /* OpenSSL >= 1.0.2 automatically handles ECDH temporary key parameter selection. */ SSL_CTX_set_ecdh_auto(ssl_ctx, 1); #else /* For OpenSSL < 1.0.2, ECDH temporary key parameter selection must be performed manually. Attempt to select the same curve as that used in the server's private EC key file. Otherwise fall back to the NIST P-384 (secp384r1) curve to be compliant with RFC 6460 when AES-256 TLS cipher suites are in use. This fall back option does however make Dovecot non-compliant with RFC 6460 which requires curve NIST P-256 (prime256v1) be used when AES-128 TLS cipher suites are in use. At least the non-compliance is in the form of providing too much security rather than too little. */ nid = ssl_proxy_ctx_get_pkey_ec_curve_name(set); ecdh = EC_KEY_new_by_curve_name(nid); if (ecdh == NULL) { /* Fall back option */ nid = NID_secp384r1; ecdh = EC_KEY_new_by_curve_name(nid); } if ((curve_name = OBJ_nid2sn(nid)) != NULL && set->verbose_ssl) i_debug("SSL: elliptic curve %s will be used for ECDH and" " ECDHE key exchanges", curve_name); if (ecdh != NULL) { SSL_CTX_set_tmp_ecdh(ssl_ctx, ecdh); EC_KEY_free(ecdh); } #endif The OpenSSL CHANGES file says for version 1.1.0: Changes between 1.0.2h and 1.1.0 [25 Aug 2016] ... ... *) SSL_{CTX_}set_ecdh_auto() has been removed and ECDH is support is always enabled now. If you want to disable the support you should exclude it using the list of supported ciphers. This also means that the "-no_ecdhe" option has been removed from s_server. [Kurt Roeckx] So when the check for OpenSSL 1.1.0 fails, the curve selection will be forced to use secp384r1 like it would be on older versions. This curve change during negotiation breaks the connect for Android7 devices. They are not able to negotiate any ECDHE cipher. The dovecot log shows: ...SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher... but here it is not a cipher problem. Instead it is a curve problem. This is most relevant if the server is suited with an ECDSA-Certificate. Than no TLS negotiation is possible. There should be added a more sufficient check for the OpenSSL version. If using OpenSSL 1.1.0*, the easiest way the have auto curve selection again is to remove the whole check for testing purpose which results in a working auto curve offering installation and allows also Android7 devices again to connect with TLS & ECDHE ciphers. Regards Torsten

1 0

Re: dovecot config for 1500 simultaneous connection
by Rajesh M 14 Feb '17

14 Feb '17

thanks for your help happy to say that the performance dramatically improved after i use the high performance settings from here http://wiki.dovecot.org/LoginProcess grep Login: /var/log/mail.log.1 |wc -l with the mail.log being of a typical, busy day. 412992 i also picked up the imap and pop3 connections during peak hours [root@ns1 domains]# doveadm who | awk '/imap/{m+=$2}/pop3/{n+=$2}END{print m,n}' username # proto (pids) (ips) max figures i got was 535 for imap and 97 for pop Question 1 i wish to improve the performance further by caching the logins. current the same is kept disable because when user's change passwords then they are not able to immediately login with the new password for some time. How to solve this issue. further to the above. i am planning to put up a large mail server with one of the following options option 1 OS and mailqueue : 2 X 600 gb 15k rpm raid 1 data : 4 X 2000 gb raid 10 for data backup : 2 X 2000 gb raid 10 for backup 32 gb ram option 2 os and mail queue : 4 X 600 gb 15k rpm raid 10 data : 4 X 2000 gb raid 10 for data 32 gb ram i am having the OS and mail queue on primary drives i understand that Raid10 give a faster write and read whereas Raid 1 will have slow writes and fast reads the question is will there be huge performance difference between Raid1 and Raid 10 when it comes small files like mail queue ? thanks rajesh ----- Original Message ----- From: Christian Balzer [mailto:chibi@gol.com] To: dovecot(a)dovecot.org Cc: kevin(a)my.walr.us Sent: Mon, 13 Feb 2017 10:46:13 +0900 Subject: Hello, On Sun, 12 Feb 2017 08:27:21 -0500 KT Walrus wrote: > Thanks for the info. I do have one further question for you. On your servers that are currently handling 50k IMAP sessions, how many users does that correspond to? Since many users will have multiple IMAP sessions on multiple devices, I’d like to hear about some real-world numbers that could be used for budgeting a new project like mine. > Those servers would actually be the wrong ones to look at, as they are primarily accessed by the aforementioned broken client, so the numbers are somewhat skewed. However looking at other servers with a more "normal" user spread things aren't actually too different. The average number of sessions per user tends to be 2. The clear majority (over 50%) only has one session open (people with well behaved and configured clients watching the INBOX mostly). Another 30% has 2 sessions open, again the typical state of this would be clients watching another mailbox besides INBOX, typically SENT. The rest has 3 and more sessions open. The number of sessions could of course be drastically reduced if any client would support IMAP NOTIFY, alas none that I'm aware of do. Lastly no more than 60% of the session seem to be in IDLE at any given time, so my comments about RAM and IMAP hibernation effectiveness stand. > Also, do you use Dovecot IMAP proxies in front of your backend servers? If so, how many IMAP sessions can one proxy server handle (assuming the proxy does authorization using MySQL running on a separate server)? And, could the proxy server be tuned to help in optimizing mostly IDLE backend sessions? > Yes to Dovecot Proxying, of course. No idea about MySQL, with (Open)LDAP nothing is breaking a sweat at an average of 140 logins per second (IMAP and POP) on the 2 proxy servers. If you can fit your entire dataset into RAM it should be fine, my LDAP servers fall into that category and take about 10% of a slow (1.2GHz, 34%, power-save mode) core only to handle the that load (also 2 servers). And the rate of logins/s is what you need to worry about most and optimize for. The proxies will of course have to do the shuffling of data and SSL en/de-coding, but again they're not particular busy with that. The number of sessions comes into play when looking at the number of login processes on the proxies and their memory footprint. An IMAP login process on the proxies in performance mode with a client limit of 1000 will consume about 55MB at most. So assume at least 55KB RAM per session. Read Timo's mail I linked to about IMAP hibernation, AFAIK nothing has happened to make proxies more supportive for this though. Christian > > On Feb 12, 2017, at 1:58 AM, Christian Balzer <chibi(a)gol.com> wrote: > > > > > > Hello, > > > > On Fri, 10 Feb 2017 14:50:03 -0500 KT Walrus wrote: > > > >>> 1. 256GB of real RAM, swap is for chums. > >> > >> Are you sure that 100,000 IMAP sessions wouldn’t work well with SWAP, especially with fast SSD storage (which is a lot cheaper than RAM)? > >> > > > > I'm sure about tax and death, not much else. > > > > But as a rule of thumb I'd avoid swapping out stuff on production servers, > > even if it were to SSDs. > > Incidentally the servers I'm talking about here have their OS and swap on > > Intel DC S3710s (200GB) and the actual storage on plenty of 1.6TB DC > > S3610s. > > > > Relying on the kernel to make swap decisions is likely to result in much > > reduced performance even with fast SWAP when you're overcommitting things > > on that scale. > > > > > > But read on. > > > >> Seems that these IMAP processes are long lived processes (idling most of the time) that don’t need that much of the contents of real memory available for much of the life of the process. I use a database proxy in front of MySQL (for my web apps) so that there can be a large number of TCP connections to the proxy where the frontend requests are queued for execution using a small number of backend connections. > >> > >> Could Dovecot IMAP be re-written to be more efficient so it works more like MySQL (or other scalable data servers) that could handle a million or more IMAP sessions on a server with 32GBs or less of RAM? Those IMAP sessions aren’t doing much most of the time and shouldn’t really average 2MB of active data per session that needs to be resident in main memory at all times. > >> > > See IMAP hibernation: > > https://www.mail-archive.com/dovecot@dovecot.org/msg63429.html <https://www.mail-archive.com/dovecot@dovecot.org/msg63429.html> > > > > I'm going to deploy/test this in production in about 2 months from now, > > but if you look at the link and the consequent changelog entries you'll see > > that it has certain shortcomings and bug fixes in pretty much each release > > after it was introduced. > > > > But this is the correct way to tackle things, not SWAP. > > > > Alas I'm not expecting miracles and if more than 20% of the IMAP sessions > > here will be hibernated at any given time I'd be pleasantly surprised. > > > > Because between: > > > > 1. Finding a sensible imap_hibernate_timeout. > > > > 2. Having well behaved clients that keep idling instead of restarting the > > sequence (https://joshdata.wordpress.com/2014/08/09/how-bad-is-imap-idle/ <https://joshdata.wordpress.com/2014/08/09/how-bad-is-imap-idle/>) > > > > 3. Having lots of mobile clients who either get disconnected (invisible to > > Dovecot) or have aggressive IDLE timers to overcome carrier NAT timeouts > > (a large mobile carrier here times out idle TCP sessions after 2 minutes, > > forcing people to use 1 minute IDLE renewals, making 1. up there a > > nightmare). > > > > 4. Having really broken clients (don't ask, I can't tell) which open IMAP > > sessions, don't put them into IDLE and thus having them expire after 30 > > minutes. > > > > the pool of eligible IDLE sessions isn't as big as it could be, in my case > > at least. > > > >> My mail server isn’t that large yet as I haven’t fully deployed Dovecot outside my own small group yet, but it would be nice if scaling Dovecot IMAP to millions of users wasn’t limited to 50,000 IMAP sessions on a server... > >> > > > > Scaling up is nice and desirable from a cost (rack space, HW) perspective, > > but the scalability of things OTHER than Dovecot as I pointed out plus > > that little detail of failure domains (do you really want half of your > > eggs in one basket?) argue for scaling out after a certain density. > > > > I'm feeling my way there at this time, but expect more than 100k sessions > > per server to be tricky. > > > > Lastly, when I asked about 500k sessions per server here not so long ago, > > ( http://www.dovecot.org/list/dovecot/2016-November/106284.html <http://www.dovecot.org/list/dovecot/2016-November/106284.html> ) > > Timo mentioned that he's not aware of anybody doing more than 50k per > > server, something I got licked already and definitely will go to 100k > > eventually. > > > > Regards, > > > > Christian > >>> On Feb 10, 2017, at 11:07 AM, Christian Balzer <chibi(a)gol.com> wrote: > >>> > >>> On Fri, 10 Feb 2017 07:59:52 -0500 KT Walrus wrote: > >>> > >>>>> 1500 IMAP sessions will eat up about 3GB alone. > >>>> > >>>> Are you saying that Dovecot needs 2MB of physical memory per IMAP session? > >>>> > >>> That depends on the IMAP session, read the mailbox size and index size, > >>> etc. > >>> Some are significantly larger: > >>> --- > >>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > >>> 1033864 mail 20 0 97600 67m 54m S 0 0.1 0:01.15 imap > >>> --- > >>> > >>> But yes, as somebody who has mailbox servers with 55k+ session the average > >>> is around 1.6MB. > >>> > >>>> If I want to support a max 100,000 IMAP sessions per server, I should configure the server to have at least 200GBs of SWAP? > >>>> > >>> You will want: > >> > >>> 2. Understanding how to tune Dovecot and more importantly the overall > >>> system to such a task (see that PID up there?). > >>> 3. Be willing to deal with stuff like top and ps taking ages to start/run > >>> and others like atop actually killing dovecot (performance wise, not > >>> literally) when doing their obviously flawed cleanup on exit. Some things > >>> clearly do NOT scale well. > >>> > >>> My current goal is to have 100k capable servers that work well, 200k in a > >>> failover scenario, but that won't be particular enjoyable. > >>> > >>> Christian > >>> > >>>>> On Feb 10, 2017, at 3:58 AM, Christian Balzer <chibi(a)gol.com> wrote: > >>>>> > >>>>> On Fri, 10 Feb 2017 01:13:20 +0530 Rajesh M wrote: > >>>>> > >>>>>> hello > >>>>>> > >>>>>> could somebody with experience let me know the dovecot config file settings to handle around 1500 simultaneous connections over pop3 and 1500 connection over imap simultaneously. > >>>>>> > >>>>> > >>>>> Be very precise here, you expect to see 1500 as the result of > >>>>> "doveadm who |grep pop3 |wc -l"? > >>>>> > >>>>> Because that implies an ungodly number of POP3 connects per second, given > >>>>> the typically short duration of these. > >>>>> > >>>>> 1500 IMAP connections (note that frequently a client will have more than > >>>>> the INBOX open and thus have more than one session and thus process on the > >>>>> server) are a much easier proposition, provided they are of the typical > >>>>> long lasting type. > >>>>> > >>>>> So can you put a number to your expected logins per second (both protocols)? > >>>>> > >>>>>> my server > >>>>>> > >>>>>> server configuration > >>>>>> hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 > >>>>>> gb hdd for data (No raid) > >>>>>> > >>>>> No RAID and no other replication like DRBD? > >>>>> Why would you even bother? > >>>>> > >>>>> How many users/mailboxes in total with what quota? > >>>>> > >>>>> 1500 IMAP sessions will eat up about 3GB alone. > >>>>> You will want more memory, simply to keep all relevant SLAB bits (inodes, > >>>>> dentries) in RAM. > >>>>> > >>>>> If you really have several hundreds logins/s, you're facing several > >>>>> bottlenecks: > >>>>> 1. Login processes themselves (easily fixed by high performance mode) > >>>>> 2. Auth processes (that will depend on your backends, method mostly) > >>>>> 3. Dovecot master process (spawning mail processes) > >>>>> > >>>>> The later is a single-threaded process, so it will benefit from a faster > >>>>> CPU core. > >>>>> It can be dramatically improved by enabling process re-usage, see: > >>>>> http://wiki.dovecot.org/PerformanceTuning > >>>>> > >>>>> However that also means more memory usage. > >>>>> > >>>>> > >>>>> > >>>>> Christian > >>>>> > >>>>>> > >>>>>> thanks > >>>>>> rajesh > >>>>>> > >>>>> > >>>>> [snip] > >>>>> -- > >>>>> Christian Balzer Network/Systems Engineer > >>>>> chibi(a)gol.com Global OnLine Japan/Rakuten Communications > >>>>> http://www.gol.com/ > >>>> > >>> > >>> > >>> -- > >>> Christian Balzer Network/Systems Engineer > >>> chibi(a)gol.com <mailto:chibi@gol.com> <mailto:chibi@gol.com <mailto:chibi@gol.com>> Global OnLine Japan/Rakuten Communications > >>> http://www.gol.com/ <http://www.gol.com/> <http://www.gol.com/ <http://www.gol.com/>> > > > > > > -- > > Christian Balzer Network/Systems Engineer > > chibi(a)gol.com <mailto:chibi@gol.com> Global OnLine Japan/Rakuten Communications > > http://www.gol.com/ <http://www.gol.com/> > -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

2 1

pop3 and dsync master-master replication issue causing duplicate delivery (resolved)
by Burak Seydioglu 14 Feb '17

14 Feb '17

I had opened a thread a while ago in regards to dsync duplicate delivery issues. Here is an update in case anybody else is suffering from this: https://dovecot.org/list/dovecot/2016-April/103973.html We are using an LDAP backend for userdb and passdb lookups and this is causing multiple replication users to be created. Here is the broken setup: ############################################### userdb ############################################### hosts = localhost dn = cn=dovecot,dc... dnpass = PASSWORD ldap_version = 3 base = ou=instances,dc... deref = never scope = subtree user_attrs = \ =home=/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:uid}, \ =mail=maildir:/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:maildrop} user_filter = (&(objectClass=mailUser)(uid=%n)) iterate_attrs = uid=user iterate_filter = (objectClass=mailUser) ############################################### passdsb ############################################### hosts = localhost dn = cn=dovecot,dc=dc... dnpass = PASSWORD ldap_version = 3 base = ou=instances,dc=dc... deref = never scope = subtree pass_attrs = uid=user,userPassword=password, \ =userdb_home=/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:uid}, \ =userdb_mail=maildir:/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:maildrop} pass_filter = (&(objectClass=mailUser)(uid=%n)) ############################################### If you don't specify a user attribute in the userdb configuration, dovecot uses the destination email address to create the replication user in addition to users based on the definitions from iterate_attr and pass_attr entries. At the end, multiple replication users are created for the same mailbox causing deleted messages to re-appear and get delivered multiple times. ############################################### username priority fast sync full sync failed buraktest1 none 02:07:02 02:07:02 - buraktest1(a)buraktest1.domain.com none 02:57:13 02:57:13 - ############################################### One thing to note here is that the behavior does not manifest itself during the first delivery/retrieval/delete cycle. You need to repeat the cycle again to expose the issue. The fix is to define and override the "user" attribute in the userdb configuration: ############################################### userdb ############################################### hosts = localhost dn = cn=dovecot,dc... dnpass = PASSWORD ldap_version = 3 base = ou=instances,dc... deref = never scope = subtree user_attrs = \ =user=%{ldap:uid}, \ =home=/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:uid}, \ =mail=maildir:/mail/spool/hash-%0.2M{ldap:uid}/%{ldap:maildrop} user_filter = (&(objectClass=mailUser)(uid=%n)) iterate_attrs = uid=user iterate_filter = (objectClass=mailUser) ###############################################

1 0

unsubscribe
by jean francois pion 13 Feb '17

13 Feb '17

unsubscribe -- -- JF Pion /*Marisol Touraine, Ministre de la Santé à propos du virus Zika:*/ *"Quand on a un projet de grossesse, il faut avoir des relations sexuelles protégées parce que le virus peut se transmettre par la voie sexuelle. "* Oui, mais…enfin, sérieusement quoi ? ?? elle réfléchit parfois ?? --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

1 0

Unable to use encrypted password for imap and pop3
by Davide Marchi 13 Feb '17

13 Feb '17

Hi friends, Following the Workaround tutorial for Jessie (https://workaround.org/ispmail/jessie ) I've set up six month ago my first Postfix email server and all works very fine, except for the ability from the user to encrypt login password. I can use the encrypted login password with smtp (Postfix), but not with pop3 and imap (Dovecot). The certificates are from Letsencrypt. I've read "http://wiki2.dovecot.org/Authentication/Mechanisms#Non-plaintext_authentica…" and set auth_mechanisms = plain login cram-md5 But with no luck, If I try to connect to Dovecot from openssl obtain an error: "Verify return code: 20 (unable to get local issuer certificate)" And now, if I enable on the client (Tunderbird) the encrypted password obtain a message to reinsert the password Here my Dovecot configuration: doveconf -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 ext4 auth_mechanisms = plain login cram-md5 apop mail_location = maildir:/var/vmail/%d/%n/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX.Junk { auto = subscribe special_use = \Junk } mailbox INBOX.Trash { auto = subscribe special_use = \Trash } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_dir = ~/sieve } protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/server.sio4.org/fullchain.pem ssl_key = </etc/letsencrypt/live/server.sio4.org/privkey.pem userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol lmtp { mail_plugins = " sieve" } Could you suggest me where I should look into? Many many thanks! davide

2 1

Problem with Horde "Mailbox does not support mod-sequences"
by Luca Bertoncello 13 Feb '17

13 Feb '17

Hi list! I already asked about this problem about two years ago, but I couldn't solve my problem... Now I have a new Server, with Debian 8 and Dovecot 2.2.13-12 (from Debian repositories) and Horde 5.2.13. When I delete an E-Mail, I always get the error "Mailbox does not support mod-sequences". It results in having the E-Mail not moved to Trash and I must update more times the folder to see the E-Mail moved to Trash... Could someone help me to add this support for mod-sequences? Thanks a lot! Luca Bertoncello (lucabert(a)lucabert.de)

2 2

Dict quota calculation errors "remote disconnected"/"broken pipe" on 2.22.
by ygrishin-lists＠mail2.ca 13 Feb '17

13 Feb '17

Keywords: dovecot, dict, quota, postgre sql, broken pipe, remote disconnected Having Dovecot 2.2.22 (fe789d2) with Postgre SQL 9.5 (9.5.5-0ubuntu0.16.04) as the backend. I do not understand why quota service is not working, not seeing it as a configuration error at least. My quotas are DICT/SQL based. OS: Ubuntu 16.0.4.1 32-bit (Linux XXX 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:36:54 UTC 2017 i686 i686 i686 GNU/Linux) dovecot --build-options: *********************** Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql /etc/dovecot/conf.d/10-master.conf: *********************************** service quota-warning { executable = script /etc/dovecot/some-script.sh unix_listener quota-warning { user = Debian-exim mode = 0660 } } service dict { unix_listener dict { mode = 0660 user = Debian-exim group = Debian-exim } } /etc/dovecot/conf.d/90-quota.conf: ********************************** plugin { quota = dict:user_quota::proxy::sqlquota quota_rule2 = Trash:storage=+10%% quota_rule3 = Junk:storage=+10%% quota_grace = 10%% quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=75%% quota-warning 75 %u } dict { sqlquota = pgsql:/etc/dovecot/dovecot-dict-sql-user.conf } /etc/dovecot/dovecot-dict-sql-user.conf: **************************************** connect = host=A.B.C.D dbname=db user=DDD password=YYY map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } I will not be able to provide full "doveconf -n" output unfortunately. Logging ALL incoming DB queries: ******************************** ... 2017-02-04 12:03:12 MST [29500-10] DDD@db LOG: statement: SELECT password FROM mailbox WHERE local_part = 'YYY' AND domain = 'XXX' AND active ='t' LIMIT 1; 2017-02-04 12:03:12 MST [29501-10] DDD@db LOG: statement: SELECT 111 AS uid, 222 AS gid, '/var/mail/AAA/' || 'BBB' || '/' || 'YYY' AS home, '*:bytes=' || mailbox.quota AS quota_rule FROM mailbox WHERE local_part = 'YYY' AND active ='t' LIMIT 1; <END OF FILE HERE> And seeing that BOTH dict statements are missing: SELECT and UPDATE. dovecot-lda-erros.log: ********************** Feb 04 14:23:33 lda(testuser@XXX): Error: read(/var/run/dovecot/dict) failed: Remote disconnected Feb 04 14:23:33 lda(testuser@XXX): Error: Internal quota calculation error Feb 04 14:23:33 lda(testuser@XXX): Error: Internal quota calculation error dovecot.log: ************ Feb 04 13:57:06 imap(YYY@XXX): Error: write(/var/run/dovecot/dict) failed: Broken pipe Feb 04 13:57:06 imap(YYY@XXX): Error: write(/var/run/dovecot/dict) failed: Broken pipe ... Feb 04 13:57:07 imap(YYY@XXX): Error: write(/var/run/dovecot/dict) failed: Broken pipe ... Feb 04 13:57:10 imap(YYY@XXX): Error: write(/var/run/dovecot/dict) failed: Broken pipe I have tried stopping dovecot, removing /var/run/dovecot/dict manually and starting dovecot. This has not changed the behavior. dovecot-debug.log: ****************** Feb 04 13:18:12 lda(YYY@XXX): Error: read(/var/run/dovecot/dict) failed: Remote disconnected Feb 04 13:18:12 lda(YYY@XXX): Error: dict quota: Quota update failed, it's now desynced Feb 04 13:57:07 lda(testuser@XXX): Error: write(/var/run/dovecot/dict) failed: Broken pipe Feb 04 13:57:07 lda(testuser@XXX): Error: Internal quota calculation error Feb 04 13:57:07 lda(testuser@XXX): Error: Internal quota calculation error Running 'user_query' manually on the server: ******************************************** db=> SELECT 111 AS uid, 222 AS gid, '/var/mail/AAA/' || 'XXX' || '/' || 'testuser' AS home, '*:bytes=' || mailbox.quota AS quota_rule FROM mailbox WHERE local_part = 'testuser' AND active ='t' LIMIT 1; uid | gid | home | quota_rule -----+-----+-----------------------------------+------------------ 111 | 222 | /var/mail/AAA/BBB/testuser | *:bytes=10485760 (1 row) The identity had been granted 'all' privilege for 'quota2' table: ***************************************************************** db=> SELECT table_catalog, table_schema, table_name, privilege_type db-> FROM information_schema.table_privileges db-> WHERE grantee='DDD'; table_catalog | table_schema | table_name | privilege_type ---------------+--------------+------------+---------------- mail | public | quota2 | INSERT mail | public | quota2 | SELECT mail | public | quota2 | UPDATE mail | public | quota2 | DELETE mail | public | quota2 | TRUNCATE mail | public | quota2 | REFERENCES mail | public | quota2 | TRIGGER mail | public | mailbox | SELECT mail | public | quota | INSERT mail | public | quota | SELECT mail | public | quota | UPDATE mail | public | quota | DELETE mail | public | quota | TRUNCATE mail | public | quota | REFERENCES mail | public | quota | TRIGGER (15 rows) Rows are obviously not getting inserted: *************************************** db=> select * from quota2; username | bytes | messages ----------+-------+---------- (0 rows) I have checked logs for any crash-related messages, there's none. Also, I have tried to deploy 2.27-release version on the server to see whether the behavior is gone. I set-up a testing environment which consists of ubuntu-16.0.4-i386 server, installed build-essential package and unpacked the dovecot-2.2.27.tar.gz there. Getting exactly same issue as Ricardo Machini was having in his post to "v2.2.27 released" thread on Sat Dec 3 21:20:05 UTC 2016: **************************************** checking that generated files are newer than configure... done configure: error: conditional "SSL_VERSION_GE_102" was never defined. Usually this means the macro was only invoked conditionally. All I ran was ./configure 'openssl' package is installed as well.

2 2

dovecot config for 1500 simultaneous connection
by Rajesh M 13 Feb '17

13 Feb '17

hello could somebody with experience let me know the dovecot config file settings to handle around 1500 simultaneous connections over pop3 and 1500 connection over imap simultaneously. my server server configuration hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 gb hdd for data (No raid) thanks rajesh my current config file settings as such # 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) # NOTE: Send doveconf -n output instead when asking for help. auth_anonymous_username = anonymous auth_cache_negative_ttl = 0 auth_cache_size = 0 auth_cache_ttl = 0 auth_debug = no auth_debug_passwords = yes auth_default_realm = auth_failure_delay = 2 secs auth_gssapi_hostname = auth_krb5_keytab = auth_master_user_separator = auth_mechanisms = plain login digest-md5 cram-md5 auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_username_translation = auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth auth_worker_max_count = 30 base_dir = /var/run/dovecot config_cache_size = 1 M debug_log_path = default_client_limit = 1000 default_idle_kill = 1 mins default_internal_user = dovecot default_login_user = vpopmail default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%m: %$ dict_db_config = director_doveadm_port = 0 director_mail_servers = director_servers = director_user_expire = 15 mins director_username_hash = %u disable_plaintext_auth = no dotlock_use_excl = yes doveadm_allowed_commands = doveadm_password = doveadm_port = 0 doveadm_socket_path = doveadm-server doveadm_worker_count = 0 dsync_alt_char = _ dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U first_valid_gid = 89 first_valid_uid = 89 hostname = imap_capability = imap_client_workarounds = imap_id_log = imap_id_send = name * imap_idle_notify_interval = 2 mins imap_logout_format = in=%i out=%o imap_max_line_length = 64 k imap_metadata = no imap_urlauth_host = imap_urlauth_logout_format = in=%i out=%o imap_urlauth_port = 143 imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_verify = yes imapc_user = import_environment = TZ DEBUG_OUTOFMEM info_log_path = instance_name = dovecot last_valid_gid = 0 last_valid_uid = 0 lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header = libexec_dir = /usr/libexec/dovecot listen = *, :: lmtp_address_translate = lmtp_proxy = no lmtp_rcpt_check_quota = no lmtp_save_to_detail_mailbox = no lock_method = fcntl log_path = /var/log/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_access_sockets = login_greeting = ready. login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = mail_access_groups = mail_always_cache_fields = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_attribute_dict = mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = mail_home = mail_location = mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib64/dovecot mail_plugins = " quota" mail_prefetch_count = 0 mail_privileged_group = mail_save_crlf = no mail_shared_explicit_inbox = no mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = mailbox_idle_check_interval = 30 secs mailbox_list_index = no maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 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 master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_md5 = apop3d mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = prefix = separator = . subscriptions = yes type = private } passdb { args = cache_key=%u webmail=127.0.0.1 default_fields = deny = no driver = vpopmail master = no override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } plugin { quota = maildir:ignore=Trash quota_rule = ?:storage=0 } pop3_client_workarounds = pop3_deleted_flag = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %08Xu%08Xv pop3c_host = pop3c_master_user = pop3c_password = pop3c_port = 110 pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_verify = yes pop3c_user = %u postmaster_address = protocols = imap pop3 quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s replication_full_sync_interval = 1 days replication_max_conns = 10 replicator_host = replicator replicator_port = 0 sendmail_path = /usr/sbin/sendmail service aggregator { chroot = . client_limit = 0 drop_priv_before_exec = no executable = aggregator extra_groups = fifo_listener replication-notify-fifo { group = mode = 0600 user = } group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replication-notify { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = $default_internal_user } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0666 user = $default_internal_user } unix_listener login/login { group = mode = 0666 user = } unix_listener token-login/tokenlogin { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 reuse_port = no ssl = no } inet_listener imaps { address = port = 993 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 50 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-login { chroot = token-login client_limit = 0 drop_priv_before_exec = no executable = imap-urlauth-login extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login unix_listener imap-urlauth { group = mode = 0666 user = } user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener imap-urlauth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service imap-urlauth { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener token-login/imap-urlauth { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 2048 process_min_avail = 50 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 512 M } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service managesieve-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = managesieve-login extra_groups = group = idle_kill = 0 inet_listener sieve { address = port = 4190 reuse_port = no ssl = no } privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service managesieve { chroot = client_limit = 1 drop_priv_before_exec = no executable = managesieve extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = unix_listener login/sieve { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 reuse_port = no ssl = no } inet_listener pop3s { address = port = 995 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service replicator { chroot = client_limit = 0 drop_priv_before_exec = no executable = replicator extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replicator-doveadm { group = mode = 00 user = $default_internal_user } unix_listener replicator { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } unix_listener ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = yes ssl_ca = ssl_cert = </var/qmail/control/servercert.pem ssl_cert_username_field = commonName ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = ssl_client_ca_file = ssl_client_cert = ssl_client_key = ssl_crypto_device = ssl_dh_parameters_length = 2048 ssl_key = </var/qmail/control/servercert.pem ssl_key_password = ssl_parameters_regenerate = 0 ssl_prefer_server_ciphers = no ssl_protocols = !SSLv2 ssl_require_crl = yes ssl_verify_client_cert = no state_dir = /var/lib/dovecot stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_session_min_time = 15 mins stats_user_min_time = 1 hours submission_host = syslog_facility = mail userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q default_fields = driver = vpopmail override_fields = } valid_chroot_dirs = verbose_proctitle = no verbose_ssl = no version_ignore = no protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 200 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 40 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_lock_session = no pop3_no_flag_updates = yes }

3 7

Plugin sieve vs. imap_sieve
by Matthias Fechner 12 Feb '17

12 Feb '17

Dear all, I just saw that a "new" plugin imap_sieve is available: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I configured everything using the plugin sieve. Was the plugin sieve just renamed to imap_sieve or is it completely different? Thanks a lot for explaining what had been changed here, I cannot find anything in the wiki. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

2 1

antispam plugin pipe backend error when moving multiple emails
by Stéphane Cottin 12 Feb '17

12 Feb '17

Hi, I've got some trouble with the dovecot antispam plugin and the pipe backend. I'm using dovecot 2.2.18 with maildirs and zlib compression enabled. When moving 2 or more emails at once from the Junk folder to another one, I always have the following error : "Failed to copy to temporary file" In the server logs : imap(vvv(a)vvv.vvv): Error: read(zlib(/data/Maildir/.test/tmp/1446974366.M123890P936.vvv)) failed: Cached message size smaller than expected (13553 < 13562, box=test, UID=0) The same operation with one email at a time, on the same emails, works as expected. Stéphane

2 2

no Authnticationmethode from outlook to Imap
by Maurizio Caloro 11 Feb '17

11 Feb '17

Hello Debian, with postfix and Dovecot Imap "2.2.13" running. If I want connect from Outlook or Thunderbird I will become this error: Plaintext disalowd on non secure SSL/TLS Connection. but I will that this run with secure connection, I don't have any intention to use Plaintext auth. Also I don't know why, dovecot will switch from IMAP --> POP3-Login. Or it's this Outlook that will ask for it. 10-ssl.conf SSL = yes 10-auth.conf disable_plaintext_auth = yes Mail.log pop3-login: Info: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=IP, lip=ip, session=<bnmZNB1AUZ+Blw> Regards

2 3

Re: dovecot config for 1500 simultaneous connection
by Joseph Tam 11 Feb '17

11 Feb '17

"Rajesh M" <24x7server(a)24x7server.net> writes: > during peak times here are the results for connections > > [root@ns1 domains]# doveadm who |grep imap |wc -l > username # proto (pids) (ips) > 631 > [root@ns1 domains]# doveadm who |grep pop3 |wc -l > username # proto (pids) (ips) > 233 Thare are user counts, not connections. Ae a user can launch multiple IMAP connections, and if they have some MaxOSX reader, that can peak to several dozens during searches. This counts connections doveadm who | awk '/imap/{m+=$2}/pop3/{n+=$2}END{print m,n}' Or you can parse the output of netstat. I'm suprised you have so many POP3 connections though -- they tend to be connect/process/disconnect. n=0 most of the time on my modest server. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: dovecot config for 1500 simultaneous connection
by Rajesh M 11 Feb '17

11 Feb '17

----- Original Message ----- From: Christian Balzer [mailto:chibi@gol.com] To: dovecot(a)dovecot.org Cc: 24x7server(a)24x7server.net Sent: Fri, 10 Feb 2017 17:58:58 +0900 Subject: On Fri, 10 Feb 2017 01:13:20 +0530 Rajesh M wrote: > hello > > could somebody with experience let me know the dovecot config file settings to handle around 1500 simultaneous connections over pop3 and 1500 connection over imap simultaneously. > Be very precise here, you expect to see 1500 as the result of "doveadm who |grep pop3 |wc -l"? Because that implies an ungodly number of POP3 connects per second, given the typically short duration of these. 1500 IMAP connections (note that frequently a client will have more than the INBOX open and thus have more than one session and thus process on the server) are a much easier proposition, provided they are of the typical long lasting type. So can you put a number to your expected logins per second (both protocols)? > my server > > server configuration > hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 > gb hdd for data (No raid) > No RAID and no other replication like DRBD? Why would you even bother? How many users/mailboxes in total with what quota? 1500 IMAP sessions will eat up about 3GB alone. You will want more memory, simply to keep all relevant SLAB bits (inodes, dentries) in RAM. If you really have several hundreds logins/s, you're facing several bottlenecks: 1. Login processes themselves (easily fixed by high performance mode) 2. Auth processes (that will depend on your backends, method mostly) 3. Dovecot master process (spawning mail processes) The later is a single-threaded process, so it will benefit from a faster CPU core. It can be dramatically improved by enabling process re-usage, see: http://wiki.dovecot.org/PerformanceTuning However that also means more memory usage. Christian > > thanks > rajesh > [snip] -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/ thanks christian during peak times here are the results for connections [root@ns1 domains]# doveadm who |grep imap |wc -l username # proto (pids) (ips) 631 [root@ns1 domains]# doveadm who |grep pop3 |wc -l username # proto (pids) (ips) 233 could you please guide me concerning the dovecot config files settings to handle the above 631 imap and 233 pop connections. number of mailboxes is around 4000 -- some users would consume 25 GB while others would be just around 10 MB this is a hex core machine with hyperthreading -- so 12 cores [root@ns1 domains]# iostat Linux 2.6.32-431.29.2.el6.x86_64 (ns1.bizmailserver.net) 02/10/2017 _x86_64_ (12 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 2.67 0.00 0.65 3.43 0.00 93.25 Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn sdd 44.95 1094.25 765.10 720884842 504041712 sdc 1.92 32.15 0.03 21178186 21248 sdb 34.71 1377.37 625.54 907398402 412102224 sda 49.88 124.29 2587.32 81879548 1704506408 thanks rajesh

2 1

Solr 6.4.1
by Daniel Miller 11 Feb '17

11 Feb '17

I've been running Solr for a while (4.10.3) - wanted to make the jump to the latest & greatest. I installed 6.4.1, copied over my schema.xml - and after a couple false starts where I needed to tweak it work with the new version...it works! I did not copy the database, started from scratch, and executed a "doveadm fts rescan -A". But... Judging solely from at least one client - it's fine. But looking in the logs I see: 1. The first scan of a mailbox dovecot's error log gives: dovecot: imap(dmiller(a)amfes.com): Error: fts_solr: Lookup failed: Bad Request 2. Subsequent scans do not appear to generate any dovecot error logs - but I'm not certain. Each new mailbox/subfolder scanned will each have one error on the initial scan. 3. Solr's log gives me the following - on every search. 2017-02-09 05:50:12.412 ERROR (qtp205125520-15) [ x:dovecot] o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad contentType for search handler :text/xml request={q=from:"test"+OR+to:"test"+OR+cc:"test"+OR+subject:"test"+OR+body:"test"&fl=uid,score&sort=uid+asc&fq=%2Bbox:c1af150abfc9df4d7f7a00003bc41c5f+%2Buser:"dmiller(a)amfes.com"&rows=67135} at org.apache.solr.request.json.RequestUtil.processParams(RequestUtil.java:72) at org.apache.solr.util.SolrPluginUtils.setDefaults(SolrPluginUtils.java:180) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:163) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2306) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:658) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:464) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:345) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:296) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1691) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:534) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) at java.lang.Thread.run(Thread.java:745) 2017-02-09 05:50:12.412 INFO (qtp205125520-15) [ x:dovecot] o.a.s.c.S.Request [dovecot] webapp=/solr path=/select params={q=from:"test"+OR+to:"test"+OR+cc:"test"+OR+subject:"test"+OR+body:"test"&fl=uid,score&sort=uid+asc&fq=%2Bbox:c1af150abfc9df4d7f7a00003bc41c5f+%2Buser:"dmiller(a)amfes.com"&rows=67135} status=400 QTime=1 My managed-schema file is: <?xml version="1.0" encoding="UTF-8"?>  <schema name="dovecot" version="1.5"> <uniqueKey>id</uniqueKey> <fieldType name="long" class="solr.TrieLongField" positionIncrementGap="0" precisionStep="0"/> <fieldType name="phonetic" class="solr.TextField" indexed="true" stored="false"> <analyzer> <tokenizer class="solr.StandardTokenizerFactory"/> <filter class="solr.DoubleMetaphoneFilterFactory" inject="true"/> </analyzer> </fieldType> <fieldType name="string" class="solr.StrField" omitNorms="true" sortMissingLast="true"/> <fieldType name="boolean" class="solr.BoolField" sortMissingLast="true"/> <fieldType name="booleans" class="solr.BoolField" sortMissingLast="true" multiValued="true"/> <fieldType name="tlongs" class="solr.TrieLongField" docValues="true" precisionStep="8" positionIncrementGap="0" multiValued="true"/> <fieldType name="tdoubles" class="solr.TrieDoubleField" docValues="true" precisionStep="8" positionIncrementGap="0" multiValued="true"/> <fieldType name="tdate" class="solr.TrieDateField" docValues="true" precisionStep="6" positionIncrementGap="0"/> <fieldType name="tdates" class="solr.TrieDateField" docValues="true" precisionStep="6" positionIncrementGap="0" multiValued="true"/> <fieldType name="text_en_splitting" class="solr.TextField" autoGeneratePhraseQueries="true" positionIncrementGap="100"> <analyzer type="index"> <charFilter class="solr.MappingCharFilterFactory" mapping="mapping-FoldToASCII.txt"/> <charFilter class="solr.MappingCharFilterFactory" mapping="mapping-ISOLatin1Accent.txt"/> <charFilter class="solr.HTMLStripCharFilterFactory"/> <tokenizer class="solr.StandardTokenizerFactory"/> <filter class="solr.StopFilterFactory" words="stopwords.txt" ignoreCase="true"/> <filter class="solr.WordDelimiterFilterFactory" catenateNumbers="1" generateNumberParts="1" splitOnCaseChange="1" generateWordParts="1" catenateAll="0" catenateWords="1"/> <filter class="solr.LowerCaseFilterFactory"/> <filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt"/> <filter class="solr.PorterStemFilterFactory"/> </analyzer> <analyzer type="query"> <tokenizer class="solr.StandardTokenizerFactory"/> <filter class="solr.SynonymFilterFactory" expand="true" ignoreCase="true" synonyms="synonyms.txt"/> <filter class="solr.StopFilterFactory" words="stopwords.txt" ignoreCase="true"/> <filter class="solr.WordDelimiterFilterFactory" catenateNumbers="0" generateNumberParts="1" splitOnCaseChange="1" generateWordParts="1" catenateAll="0" catenateWords="0"/> <filter class="solr.LowerCaseFilterFactory"/> <filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt"/> <filter class="solr.PorterStemFilterFactory"/> </analyzer> </fieldType> <field name="_version_" type="long" indexed="true" stored="true"/> <field name="bcc" type="text_en_splitting" indexed="true" stored="false"/> <field name="body" type="text_en_splitting" indexed="true" stored="false"/> <field name="box" type="string" indexed="true" required="true" stored="true"/> <field name="cc" type="text_en_splitting" indexed="true" stored="false"/> <field name="from" type="text_en_splitting" indexed="true" stored="false"/> <field name="hdr" type="text_en_splitting" indexed="true" stored="false"/> <field name="id" type="string" indexed="true" required="true" stored="true"/> <field name="subject" type="text_en_splitting" indexed="true" stored="false"/> <field name="text" type="text_en_splitting" multiValued="true" indexed="true" stored="false"/> <field name="to" type="text_en_splitting" indexed="true" stored="false"/> <field name="uid" type="long" indexed="true" required="true" stored="true"/> <field name="user" type="string" indexed="true" required="true" stored="true"/> </schema> -- Daniel

2 5

Safely piping to a shell script
by Adam Shostack 10 Feb '17

10 Feb '17

Thanks for the previous answer on :execute. In thinking about malicious input, I am worried about the possibility that mail will be sent with a clever from line. (Section 7 of http://www.ietf.org/rfc/rfc5229.txt is great, btw) To address this, I'm considering the following, and would appreciate feedback. I'm aware that this doesn't capture all emails, those with non-alphanum are legit, and badly handled. I think that this restricts the input of the grepfrom script to be a single string, matching "a-zA-Z09@." if not address :regex "from" "^[:alnum]*@[:alnum]*([:alnum].)*$" { fileinto :create "wierd"; stop ; } elsif address :regex "from" "*" { set "sender" ${1}; if execute "grepfrom" "${sender}" { keep ; stop; } else {fileinto :create "neversent"} As an aside, https://www.joachim-breitner.de/blog/441-Goodbye_procmail,_Hello_Sieve contains a nice pattern, creating an include file to test, and that addresses many, but not all of my use cases. Should I worry if the match there is 5000+ strings? Adam

1 0

Prohibit dots in folder names
by Marek Grondecki 10 Feb '17

10 Feb '17

Hello Dovecot Community, I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). separator = / listescape plugin is NOT active LAYOUT=fs is NOT active I would like to prohibit a creation of folders with dot "." in the names - so creation of a folder "foo.bar" should NOT be possible. Currently, when I create "foo.bar" in Outlook 2013 it will be created but won't be synchronised with the mail server - Outlook shows it as "foo.bar (Only this computer)". Ideally the user should receive an error message informing that "the folder foo.bar could not be created." Thank you for your help. Regards, Marek Grondecki

3 4

please help this newbie get started
by drbobllc＠yahoo.com 10 Feb '17

10 Feb '17

Hi, everyone, I'm trying to get email working on a server. Web servers I have some experience with, but this is new for me. On FreeBSD, with dovecot2 (2.2.27), when I try to check email, Thunderbird says: Sending of password for user xxx did not succeed.Mail server xxxresponded: Authentication failed. And on the server, in the mail log, there's a message: dovecot: pop3-login: Disconnected (user disabled) Any idea what I'm doing wrong? I didn't mean to disable any users. Thanks! Bob

3 11

Re: dovecot Digest, Vol 166, Issue 22
by Aki Tuomi 10 Feb '17

10 Feb '17

I have not tried it at all. Was just an suggestion. You can try something like protocol lda { namespace archive { ... } } On 10.02.2017 14:12, Nick Lekkas wrote: > > Hi Aki > > > > Thanks for your answer .... > > What version of dovecot have you tried it ? Mine is 2.2.10 > > > > > > > > > > *From:*Aki Tuomi [mailto:aki.tuomi@dovecot.fi] > *Sent:* Friday, February 10, 2017 2:06 PM > *To:* nlekkas(a)gmail.com; dovecot(a)dovecot.org > *Subject:* Re: dovecot Digest, Vol 166, Issue 22 > > > > You could enable it for LDA/LMTP? > > Aki > > On 09.02.2017 17:45, Nick Lekkas wrote: > > Hello to all > > > > > > After a lot of tries using dovecot 2.2.10 on centos 7 latest ...i could not > > > manage make dovecot dsync work ... > > > i have tried a lot of scenarios using mysql as backend , custom user file. > > > Using by command line the dsync it works fine > > > > > > Has anyone managed to use 2.2.10 ..? > > > > > > > > > -----Original Message----- > > > From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of > > > dovecot-request(a)dovecot.org <mailto:dovecot-request@dovecot.org> > > > Sent: Thursday, February 09, 2017 1:05 PM > > > To: dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > > > Subject: dovecot Digest, Vol 166, Issue 22 > > > > > > Send dovecot mailing list submissions to > > > dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > > > > > > To subscribe or unsubscribe via the World Wide Web, visit > > > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > > or, via email, send a message with subject or body 'help' to > > > dovecot-request(a)dovecot.org <mailto:dovecot-request@dovecot.org> > > > > > > You can reach the person managing the list at > > > dovecot-owner(a)dovecot.org <mailto:dovecot-owner@dovecot.org> > > > > > > When replying, please edit your Subject line so it is more specific > > > than "Re: Contents of dovecot digest..." > > > > > > > > > Today's Topics: > > > > > > 1. Re: Solr 6.4.1 (Aki Tuomi) > > > 2. dovecot logout issues (Rajesh M) > > > 3. Re: Messages on this list are often marked as spam. > > > (Steven Mainor) > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Thu, 9 Feb 2017 08:57:50 +0200 > > > From: Aki Tuomi <aki.tuomi(a)dovecot.fi> <mailto:aki.tuomi@dovecot.fi> > > > To: dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > > > Subject: Re: Solr 6.4.1 > > > Message-ID: <aba919c2-cffe-ed91-23f4-2e57d967b83b(a)dovecot.fi> > <mailto:aba919c2-cffe-ed91-23f4-2e57d967b83b@dovecot.fi> > > > Content-Type: text/plain; charset=utf-8 > > > > > > > > > > > > On 09.02.2017 07:54, Daniel Miller wrote: > > >> I've been running Solr for a while (4.10.3) - wanted to make the jump > > >> to the latest & greatest. I installed 6.4.1, copied over my > > >> schema.xml - and after a couple false starts where I needed to tweak > > >> it work with the new version...it works! I did not copy the database, > > >> started from scratch, and executed a "doveadm fts rescan -A". But... > > >> > > >> Judging solely from at least one client - it's fine. But looking in > > >> the logs I see: > > >> 1. The first scan of a mailbox dovecot's error log gives: > > >> dovecot: imap(dmiller(a)amfes.com <mailto:dmiller@amfes.com>): Error: > fts_solr: Lookup failed: > > >> Bad Request > > >> > > >> 2. Subsequent scans do not appear to generate any dovecot error logs > > >> - but I'm not certain. Each new mailbox/subfolder scanned will each > > >> have one error on the initial scan. > > >> > > >> 3. Solr's log gives me the following - on every search. > > >> 2017-02-09 05:50:12.412 ERROR (qtp205125520-15) [ x:dovecot] > > >> o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad > > >> contentType for search handler :text/xml > > >> > > > request={q=from:"test"+OR+to:"test"+OR+cc:"test"+OR+subject:"test"+OR+body:" > > > test"&fl=uid,score&sort=uid+asc&fq=%2Bbox:c1af150abfc9df4d7f7a00003bc41c5f+% > > > 2Buser:"dmiller(a)amfes.com" <mailto:dmiller@amfes.com>&rows=67135} > > > > > > Hi! > > > > > > can you please use tcpdump or wireshark to capture the actual HTTP > > > request causing this exception? > > > > > > Aki > > > > > > > > > ------------------------------ > > > > > > Message: 2 > > > Date: Thu, 9 Feb 2017 16:00:22 +0530 > > > From: "Rajesh M" <24x7server(a)24x7server.net> <mailto:24x7server@24x7server.net> > > > To: <dovecot(a)dovecot.org> <mailto:dovecot@dovecot.org> > > > Subject: dovecot logout issues > > > Message-ID: <3112B2DB02AA4C97871A9E3C19D6C9B8.MAI(a)ns1.24x7server.net> > <mailto:3112B2DB02AA4C97871A9E3C19D6C9B8.MAI@ns1.24x7server.net> > > > Content-Type: text/plain; charset="UTF-8" > > > > > > hi > > > > > > we are using dovecot version 2.2.7 (config file given below) > > > centos 6, qmail, vpopmail, mysql > > > > > > server configuration > > > hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X > > > 2000 gb hdd for data (No raid) > > > > > > busy server with around 4000 email ids --- load is around 2 to 10 > > > > > > the issue is that SQUIRRELMAIL webmail users suddenly lose connection while > > > they are working on the webmail. > > > > > > after logging in, if the user tries to open a mail then the interface gives > > > error invalid user id or password. > > > > > > this happens on an extremely random basis. > > > > > > also htop always shows a few delayed processes of dovecot (shown as D) on > > > top -- pop3 and imap > > > > > > dovecot logs do not show any login error when such a logout takes place. > > > > > > the said mailbox contained just around 30 emails > > > > > > and it is not related to the timeout plugin of squirrelmail either since the > > > same webmail folders works on other servers of ours without any issues. > > > > > > webmail load slowly in general > > > > > > however when it works normally webmail is very fast and able to handle > > > several 10 s of thousands of emails in the inbox. > > > > > > ram consumed is 2 - 5 gb during peak hours. > > > > > > rebooted server but issue not solved > > > > > > issue is present for the last around 1 month and was not present earlier. > > > > > > help required please. > > > > > > thanks > > > rajesh > > > > > > > > > settings as such > > > # 2.2.7: /etc/dovecot/dovecot.conf > > > # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) > > > # NOTE: Send doveconf -n output instead when asking for help. > > > auth_anonymous_username = anonymous > > > auth_cache_negative_ttl = 0 > > > auth_cache_size = 0 > > > auth_cache_ttl = 0 > > > auth_debug = no > > > auth_debug_passwords = yes > > > auth_default_realm = > > > auth_failure_delay = 2 secs > > > auth_gssapi_hostname = > > > auth_krb5_keytab = > > > auth_master_user_separator = > > > auth_mechanisms = plain login digest-md5 cram-md5 > > > auth_proxy_self = > > > auth_realms = > > > auth_socket_path = auth-userdb > > > auth_ssl_require_client_cert = no > > > auth_ssl_username_from_cert = no > > > auth_use_winbind = no > > > auth_username_chars = > > > abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ > > > auth_username_format = %Lu > > > auth_username_translation = > > > auth_verbose = no > > > auth_verbose_passwords = no > > > auth_winbind_helper_path = /usr/bin/ntlm_auth > > > auth_worker_max_count = 30 > > > base_dir = /var/run/dovecot > > > config_cache_size = 1 M > > > debug_log_path = > > > default_client_limit = 1000 > > > default_idle_kill = 1 mins > > > default_internal_user = dovecot > > > default_login_user = vpopmail > > > default_process_limit = 100 > > > default_vsz_limit = 256 M > > > deliver_log_format = msgid=%m: %$ > > > dict_db_config = > > > director_doveadm_port = 0 > > > director_mail_servers = > > > director_servers = > > > director_user_expire = 15 mins > > > director_username_hash = %u > > > disable_plaintext_auth = no > > > dotlock_use_excl = yes > > > doveadm_allowed_commands = > > > doveadm_password = > > > doveadm_port = 0 > > > doveadm_socket_path = doveadm-server > > > doveadm_worker_count = 0 > > > dsync_alt_char = _ > > > dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U > > > first_valid_gid = 89 > > > first_valid_uid = 89 > > > hostname = > > > imap_capability = > > > imap_client_workarounds = > > > imap_id_log = > > > imap_id_send = name * > > > imap_idle_notify_interval = 2 mins > > > imap_logout_format = in=%i out=%o > > > imap_max_line_length = 64 k > > > imap_metadata = no > > > imap_urlauth_host = > > > imap_urlauth_logout_format = in=%i out=%o > > > imap_urlauth_port = 143 > > > imapc_features = > > > imapc_host = > > > imapc_list_prefix = > > > imapc_master_user = > > > imapc_max_idle_time = 29 mins > > > imapc_password = > > > imapc_port = 143 > > > imapc_rawlog_dir = > > > imapc_ssl = no > > > imapc_ssl_verify = yes > > > imapc_user = > > > import_environment = TZ DEBUG_OUTOFMEM > > > info_log_path = > > > instance_name = dovecot > > > last_valid_gid = 0 > > > last_valid_uid = 0 > > > lda_mailbox_autocreate = no > > > lda_mailbox_autosubscribe = no > > > lda_original_recipient_header = > > > libexec_dir = /usr/libexec/dovecot > > > listen = *, :: > > > lmtp_address_translate = > > > lmtp_proxy = no > > > lmtp_rcpt_check_quota = no > > > lmtp_save_to_detail_mailbox = no > > > lock_method = fcntl > > > log_path = /var/log/dovecot.log > > > log_timestamp = "%b %d %H:%M:%S " > > > login_access_sockets = > > > login_greeting = ready. > > > login_log_format = %$: %s > > > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c > > > session=<%{session}> > > > login_trusted_networks = > > > mail_access_groups = > > > mail_always_cache_fields = > > > mail_attachment_dir = > > > mail_attachment_fs = sis posix > > > mail_attachment_hash = %{sha1} > > > mail_attachment_min_size = 128 k > > > mail_attribute_dict = > > > mail_cache_fields = flags > > > mail_cache_min_mail_count = 0 > > > mail_chroot = > > > mail_debug = no > > > mail_fsync = optimized > > > mail_full_filesystem_access = no > > > mail_gid = > > > mail_home = > > > mail_location = > > > mail_log_prefix = "%s(%u): " > > > mail_max_keyword_length = 50 > > > mail_max_lock_timeout = 0 > > > mail_max_userip_connections = 10 > > > mail_never_cache_fields = imap.envelope > > > mail_nfs_index = no > > > mail_nfs_storage = no > > > mail_plugin_dir = /usr/lib64/dovecot > > > mail_plugins = " quota" > > > mail_prefetch_count = 0 > > > mail_privileged_group = > > > mail_save_crlf = no > > > mail_shared_explicit_inbox = no > > > mail_temp_dir = /tmp > > > mail_temp_scan_interval = 1 weeks > > > mail_uid = > > > mailbox_idle_check_interval = 30 secs > > > mailbox_list_index = no > > > maildir_broken_filename_sizes = no > > > maildir_copy_with_hardlinks = yes > > > maildir_stat_dirs = no > > > maildir_very_dirty_syncs = no > > > managesieve_client_workarounds = > > > managesieve_implementation_string = Dovecot Pigeonhole > > > managesieve_logout_format = bytes=%i/%o > > > managesieve_max_compile_errors = 5 > > > managesieve_max_line_length = 65536 > > > 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 > > > master_user_separator = > > > mbox_dirty_syncs = yes > > > mbox_dotlock_change_timeout = 2 mins > > > mbox_lazy_writes = yes > > > mbox_lock_timeout = 5 mins > > > mbox_md5 = apop3d > > > mbox_min_index_size = 0 > > > mbox_read_locks = fcntl > > > mbox_very_dirty_syncs = no > > > mbox_write_locks = dotlock fcntl > > > mdbox_preallocate_space = no > > > mdbox_rotate_interval = 0 > > > mdbox_rotate_size = 2 M > > > mmap_disable = no > > > namespace { > > > disabled = no > > > hidden = no > > > ignore_on_failure = no > > > inbox = yes > > > list = yes > > > location = > > > prefix = > > > separator = . > > > subscriptions = yes > > > type = private > > > } > > > passdb { > > > args = cache_key=%u webmail=127.0.0.1 > > > default_fields = > > > deny = no > > > driver = vpopmail > > > master = no > > > override_fields = > > > pass = no > > > result_failure = continue > > > result_internalfail = continue > > > result_success = return-ok > > > skip = never > > > } > > > plugin { > > > quota = maildir:ignore=Trash > > > quota_rule = ?:storage=0 > > > } > > > pop3_client_workarounds = > > > pop3_deleted_flag = > > > pop3_enable_last = no > > > pop3_fast_size_lookups = no > > > pop3_lock_session = no > > > pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s > > > pop3_no_flag_updates = no > > > pop3_reuse_xuidl = no > > > pop3_save_uidl = no > > > pop3_uidl_duplicates = allow > > > pop3_uidl_format = %08Xu%08Xv > > > pop3c_host = > > > pop3c_master_user = > > > pop3c_password = > > > pop3c_port = 110 > > > pop3c_rawlog_dir = > > > pop3c_ssl = no > > > pop3c_ssl_verify = yes > > > pop3c_user = %u > > > postmaster_address = > > > protocols = imap pop3 > > > quota_full_tempfail = no > > > recipient_delimiter = + > > > rejection_reason = Your message to <%t> was automatically rejected:%n%r > > > rejection_subject = Rejected: %s > > > replication_full_sync_interval = 1 days > > > replication_max_conns = 10 > > > replicator_host = replicator > > > replicator_port = 0 > > > sendmail_path = /usr/sbin/sendmail > > > service aggregator { > > > chroot = . > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = aggregator > > > extra_groups = > > > fifo_listener replication-notify-fifo { > > > group = > > > mode = 0600 > > > user = > > > } > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener replication-notify { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service anvil { > > > chroot = empty > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = anvil > > > extra_groups = > > > group = > > > idle_kill = 4294967295 secs > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 1 > > > protocol = > > > service_count = 0 > > > type = anvil > > > unix_listener anvil-auth-penalty { > > > group = > > > mode = 0600 > > > user = > > > } > > > unix_listener anvil { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service auth-worker { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = auth -w > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 1 > > > type = > > > unix_listener auth-worker { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service auth { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = auth > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener auth-client { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > unix_listener auth-login { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > unix_listener auth-master { > > > group = > > > mode = 0600 > > > user = > > > } > > > unix_listener auth-userdb { > > > group = > > > mode = 0666 > > > user = $default_internal_user > > > } > > > unix_listener login/login { > > > group = > > > mode = 0666 > > > user = > > > } > > > unix_listener token-login/tokenlogin { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service config { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = config > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = config > > > unix_listener config { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service dict { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = dict > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener dict { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service director { > > > chroot = . > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = director > > > extra_groups = > > > fifo_listener login/proxy-notify { > > > group = > > > mode = 00 > > > user = > > > } > > > group = > > > idle_kill = 4294967295 secs > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener director-admin { > > > group = > > > mode = 0600 > > > user = > > > } > > > unix_listener login/director { > > > group = > > > mode = 00 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service dns_client { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = dns-client > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener dns-client { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service doveadm { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = doveadm-server > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 1 > > > type = > > > unix_listener doveadm-server { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service imap-login { > > > chroot = login > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = imap-login > > > extra_groups = > > > group = > > > idle_kill = 0 > > > inet_listener imap { > > > address = > > > port = 143 > > > reuse_port = no > > > ssl = no > > > } > > > inet_listener imaps { > > > address = > > > port = 993 > > > reuse_port = no > > > ssl = yes > > > } > > > privileged_group = > > > process_limit = 256 > > > process_min_avail = 50 > > > protocol = imap > > > service_count = 1 > > > type = login > > > user = $default_login_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service imap-urlauth-login { > > > chroot = token-login > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = imap-urlauth-login > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = imap > > > service_count = 1 > > > type = login > > > unix_listener imap-urlauth { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = $default_login_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service imap-urlauth-worker { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = imap-urlauth-worker > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 1024 > > > process_min_avail = 0 > > > protocol = imap > > > service_count = 1 > > > type = > > > unix_listener imap-urlauth-worker { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service imap-urlauth { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = imap-urlauth > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 1024 > > > process_min_avail = 0 > > > protocol = imap > > > service_count = 1 > > > type = > > > unix_listener token-login/imap-urlauth { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service imap { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = imap > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 2048 > > > process_min_avail = 50 > > > protocol = imap > > > service_count = 1 > > > type = > > > unix_listener login/imap { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = > > > vsz_limit = 512 M > > > } > > > service indexer-worker { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = indexer-worker > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 10 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener indexer-worker { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service indexer { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = indexer > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener indexer { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service ipc { > > > chroot = empty > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = ipc > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener ipc { > > > group = > > > mode = 0600 > > > user = > > > } > > > unix_listener login/ipc-proxy { > > > group = > > > mode = 0600 > > > user = $default_login_user > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service lmtp { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = lmtp > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = lmtp > > > service_count = 0 > > > type = > > > unix_listener lmtp { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service log { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = log > > > extra_groups = > > > group = > > > idle_kill = 4294967295 secs > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = log > > > unix_listener log-errors { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service managesieve-login { > > > chroot = login > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = managesieve-login > > > extra_groups = > > > group = > > > idle_kill = 0 > > > inet_listener sieve { > > > address = > > > port = 4190 > > > reuse_port = no > > > ssl = no > > > } > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = sieve > > > service_count = 1 > > > type = login > > > user = $default_login_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service managesieve { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = managesieve > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = sieve > > > service_count = 1 > > > type = > > > unix_listener login/sieve { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service pop3-login { > > > chroot = login > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = pop3-login > > > extra_groups = > > > group = > > > idle_kill = 0 > > > inet_listener pop3 { > > > address = > > > port = 110 > > > reuse_port = no > > > ssl = no > > > } > > > inet_listener pop3s { > > > address = > > > port = 995 > > > reuse_port = no > > > ssl = yes > > > } > > > privileged_group = > > > process_limit = 256 > > > process_min_avail = 25 > > > protocol = pop3 > > > service_count = 1 > > > type = login > > > user = $default_login_user > > > vsz_limit = 18446744073709551615 B > > > } > > > service pop3 { > > > chroot = > > > client_limit = 1 > > > drop_priv_before_exec = no > > > executable = pop3 > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 256 > > > process_min_avail = 25 > > > protocol = pop3 > > > service_count = 1 > > > type = > > > unix_listener login/pop3 { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service replicator { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = replicator > > > extra_groups = > > > group = > > > idle_kill = 4294967295 secs > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener replicator-doveadm { > > > group = > > > mode = 00 > > > user = $default_internal_user > > > } > > > unix_listener replicator { > > > group = > > > mode = 0600 > > > user = $default_internal_user > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service ssl-params { > > > chroot = > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = ssl-params > > > extra_groups = > > > group = > > > idle_kill = 0 > > > privileged_group = > > > process_limit = 0 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = startup > > > unix_listener login/ssl-params { > > > group = > > > mode = 0666 > > > user = > > > } > > > unix_listener ssl-params { > > > group = > > > mode = 0666 > > > user = > > > } > > > user = > > > vsz_limit = 18446744073709551615 B > > > } > > > service stats { > > > chroot = empty > > > client_limit = 0 > > > drop_priv_before_exec = no > > > executable = stats > > > extra_groups = > > > fifo_listener stats-mail { > > > group = > > > mode = 0600 > > > user = > > > } > > > group = > > > idle_kill = 4294967295 secs > > > privileged_group = > > > process_limit = 1 > > > process_min_avail = 0 > > > protocol = > > > service_count = 0 > > > type = > > > unix_listener stats { > > > group = > > > mode = 0600 > > > user = > > > } > > > user = $default_internal_user > > > vsz_limit = 18446744073709551615 B > > > } > > > shutdown_clients = yes > > > ssl = yes > > > ssl_ca = > > > ssl_cert = </var/qmail/control/servercert.pem > > > ssl_cert_username_field = commonName > > > ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL > > > ssl_client_ca_dir = > > > ssl_client_ca_file = > > > ssl_client_cert = > > > ssl_client_key = > > > ssl_crypto_device = > > > ssl_dh_parameters_length = 2048 > > > ssl_key = </var/qmail/control/servercert.pem > > > ssl_key_password = > > > ssl_parameters_regenerate = 0 > > > ssl_prefer_server_ciphers = no > > > ssl_protocols = !SSLv2 > > > ssl_require_crl = yes > > > ssl_verify_client_cert = no > > > state_dir = /var/lib/dovecot > > > stats_command_min_time = 1 mins > > > stats_domain_min_time = 12 hours > > > stats_ip_min_time = 12 hours > > > stats_memory_limit = 16 M > > > stats_session_min_time = 15 mins > > > stats_user_min_time = 1 hours > > > submission_host = > > > syslog_facility = mail > > > userdb { > > > args = cache_key=%u quota_template=quota_rule=*:backend=%q > > > default_fields = > > > driver = vpopmail > > > override_fields = > > > } > > > valid_chroot_dirs = > > > verbose_proctitle = no > > > verbose_ssl = no > > > version_ignore = no > > > protocol imap { > > > imap_client_workarounds = delay-newmail > > > mail_max_userip_connections = 200 > > > mail_plugins = " quota imap_quota" > > > } > > > protocol pop3 { > > > mail_max_userip_connections = 40 > > > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > > > pop3_fast_size_lookups = yes > > > pop3_lock_session = no > > > pop3_no_flag_updates = yes > > > } > > > > > > > > > > > > > > > ------------------------------ > > > > > > Message: 3 > > > Date: Thu, 09 Feb 2017 06:13:37 -0500 > > > From: Steven Mainor <steve(a)degga.net> <mailto:steve@degga.net> > > > To: Bj?rn T Johansen <btj(a)havleik.no> > <mailto:btj@havleik.no>,dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > > > Subject: Re: Messages on this list are often marked as spam. > > > Message-ID: <00905D2C-F645-424B-AA31-92E36318AC5F(a)degga.net> > <mailto:00905D2C-F645-424B-AA31-92E36318AC5F@degga.net> > > > Content-Type: text/plain; charset=UTF-8 > > > > > Well for other mailing lists I have noticed that a lot of lists add > text to > the body or subject saying what list the email is from which would > cause the > signature not to match. > > But the dovecot list doesn't do that so that's why I found it strange that > so many emails fail dkim. > > > > > > > > > > > > ------------------------------ > > > > > > Subject: Digest Footer > > > > > > _______________________________________________ > > > dovecot mailing list > > > dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > > > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > > > > > > ------------------------------ > > > > > > End of dovecot Digest, Vol 166, Issue 22 > > > **************************************** > > > > > > > > > __________ Information from ESET Endpoint Antivirus, version of virus > > > signature database 14908 (20170209) __________ > > > > > > The message was checked by ESET Endpoint Antivirus. > > > > > > part000.txt - is OK > > > > > > http://www.eset.com > > > > > > > > > > > > > > > __________ Information from ESET Endpoint Antivirus, version of virus > > > signature database 14909 (20170209) __________ > > > > > > The message was checked by ESET Endpoint Antivirus. > > > > > > Email message - is OK > > > > > > http://www.eset.com > > > > > __________ Information from ESET Endpoint Antivirus, version of virus > signature database 14914 (20170210) __________ > > The message was checked by ESET Endpoint Antivirus. > > part000.txt - is OK > part001.htm - is OK > > http://www.eset.com > > > > __________ Information from ESET Endpoint Antivirus, version of virus > signature database 14914 (20170210) __________ > > The message was checked by ESET Endpoint Antivirus. > > Email message - is OK > > http://www.eset.com >

1 0

dovecot logout issues
by Rajesh M 10 Feb '17

10 Feb '17

hi we are using dovecot version 2.2.7 (config file given below) centos 6, qmail, vpopmail, mysql server configuration hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 gb hdd for data (No raid) busy server with around 4000 email ids --- load is around 2 to 10 the issue is that SQUIRRELMAIL webmail users suddenly lose connection while they are working on the webmail. after logging in, if the user tries to open a mail then the interface gives error invalid user id or password. this happens on an extremely random basis. also htop always shows a few delayed processes of dovecot (shown as D) on top -- pop3 and imap dovecot logs do not show any login error when such a logout takes place. the said mailbox contained just around 30 emails and it is not related to the timeout plugin of squirrelmail either since the same webmail folders works on other servers of ours without any issues. webmail load slowly in general however when it works normally webmail is very fast and able to handle several 10 s of thousands of emails in the inbox. ram consumed is 2 - 5 gb during peak hours. rebooted server but issue not solved issue is present for the last around 1 month and was not present earlier. help required please. thanks rajesh settings as such # 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) # NOTE: Send doveconf -n output instead when asking for help. auth_anonymous_username = anonymous auth_cache_negative_ttl = 0 auth_cache_size = 0 auth_cache_ttl = 0 auth_debug = no auth_debug_passwords = yes auth_default_realm = auth_failure_delay = 2 secs auth_gssapi_hostname = auth_krb5_keytab = auth_master_user_separator = auth_mechanisms = plain login digest-md5 cram-md5 auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_username_translation = auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth auth_worker_max_count = 30 base_dir = /var/run/dovecot config_cache_size = 1 M debug_log_path = default_client_limit = 1000 default_idle_kill = 1 mins default_internal_user = dovecot default_login_user = vpopmail default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%m: %$ dict_db_config = director_doveadm_port = 0 director_mail_servers = director_servers = director_user_expire = 15 mins director_username_hash = %u disable_plaintext_auth = no dotlock_use_excl = yes doveadm_allowed_commands = doveadm_password = doveadm_port = 0 doveadm_socket_path = doveadm-server doveadm_worker_count = 0 dsync_alt_char = _ dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U first_valid_gid = 89 first_valid_uid = 89 hostname = imap_capability = imap_client_workarounds = imap_id_log = imap_id_send = name * imap_idle_notify_interval = 2 mins imap_logout_format = in=%i out=%o imap_max_line_length = 64 k imap_metadata = no imap_urlauth_host = imap_urlauth_logout_format = in=%i out=%o imap_urlauth_port = 143 imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_verify = yes imapc_user = import_environment = TZ DEBUG_OUTOFMEM info_log_path = instance_name = dovecot last_valid_gid = 0 last_valid_uid = 0 lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header = libexec_dir = /usr/libexec/dovecot listen = *, :: lmtp_address_translate = lmtp_proxy = no lmtp_rcpt_check_quota = no lmtp_save_to_detail_mailbox = no lock_method = fcntl log_path = /var/log/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_access_sockets = login_greeting = ready. login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = mail_access_groups = mail_always_cache_fields = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_attribute_dict = mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = mail_home = mail_location = mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib64/dovecot mail_plugins = " quota" mail_prefetch_count = 0 mail_privileged_group = mail_save_crlf = no mail_shared_explicit_inbox = no mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = mailbox_idle_check_interval = 30 secs mailbox_list_index = no maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 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 master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_md5 = apop3d mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = prefix = separator = . subscriptions = yes type = private } passdb { args = cache_key=%u webmail=127.0.0.1 default_fields = deny = no driver = vpopmail master = no override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } plugin { quota = maildir:ignore=Trash quota_rule = ?:storage=0 } pop3_client_workarounds = pop3_deleted_flag = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %08Xu%08Xv pop3c_host = pop3c_master_user = pop3c_password = pop3c_port = 110 pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_verify = yes pop3c_user = %u postmaster_address = protocols = imap pop3 quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s replication_full_sync_interval = 1 days replication_max_conns = 10 replicator_host = replicator replicator_port = 0 sendmail_path = /usr/sbin/sendmail service aggregator { chroot = . client_limit = 0 drop_priv_before_exec = no executable = aggregator extra_groups = fifo_listener replication-notify-fifo { group = mode = 0600 user = } group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replication-notify { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = $default_internal_user } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0666 user = $default_internal_user } unix_listener login/login { group = mode = 0666 user = } unix_listener token-login/tokenlogin { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 reuse_port = no ssl = no } inet_listener imaps { address = port = 993 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 50 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-login { chroot = token-login client_limit = 0 drop_priv_before_exec = no executable = imap-urlauth-login extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login unix_listener imap-urlauth { group = mode = 0666 user = } user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener imap-urlauth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service imap-urlauth { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener token-login/imap-urlauth { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 2048 process_min_avail = 50 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 512 M } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service managesieve-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = managesieve-login extra_groups = group = idle_kill = 0 inet_listener sieve { address = port = 4190 reuse_port = no ssl = no } privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service managesieve { chroot = client_limit = 1 drop_priv_before_exec = no executable = managesieve extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = unix_listener login/sieve { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 reuse_port = no ssl = no } inet_listener pop3s { address = port = 995 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service replicator { chroot = client_limit = 0 drop_priv_before_exec = no executable = replicator extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replicator-doveadm { group = mode = 00 user = $default_internal_user } unix_listener replicator { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } unix_listener ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = yes ssl_ca = ssl_cert = </var/qmail/control/servercert.pem ssl_cert_username_field = commonName ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = ssl_client_ca_file = ssl_client_cert = ssl_client_key = ssl_crypto_device = ssl_dh_parameters_length = 2048 ssl_key = </var/qmail/control/servercert.pem ssl_key_password = ssl_parameters_regenerate = 0 ssl_prefer_server_ciphers = no ssl_protocols = !SSLv2 ssl_require_crl = yes ssl_verify_client_cert = no state_dir = /var/lib/dovecot stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_session_min_time = 15 mins stats_user_min_time = 1 hours submission_host = syslog_facility = mail userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q default_fields = driver = vpopmail override_fields = } valid_chroot_dirs = verbose_proctitle = no verbose_ssl = no version_ignore = no protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 200 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 40 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_lock_session = no pop3_no_flag_updates = yes }

2 1

Messages on this list are often marked as spam.
by Steven Mainor 09 Feb '17

09 Feb '17

Hello, It seems that I get several emails a week from this list in my spam folder. Usually because the DKIM signature fails. Has anyone else noticed this problem or is it just me? -- Steven mainor steve(a)degga.net

4 5

RE: dovecot Digest, Vol 166, Issue 22
by Nick Lekkas 09 Feb '17

09 Feb '17

Hello to all After a lot of tries using dovecot 2.2.10 on centos 7 latest ...i could not manage make dovecot dsync work ... i have tried a lot of scenarios using mysql as backend , custom user file. Using by command line the dsync it works fine Has anyone managed to use 2.2.10 ..? -----Original Message----- From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of dovecot-request(a)dovecot.org Sent: Thursday, February 09, 2017 1:05 PM To: dovecot(a)dovecot.org Subject: dovecot Digest, Vol 166, Issue 22 Send dovecot mailing list submissions to dovecot(a)dovecot.org To subscribe or unsubscribe via the World Wide Web, visit http://dovecot.org/cgi-bin/mailman/listinfo/dovecot or, via email, send a message with subject or body 'help' to dovecot-request(a)dovecot.org You can reach the person managing the list at dovecot-owner(a)dovecot.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dovecot digest..." Today's Topics: 1. Re: Solr 6.4.1 (Aki Tuomi) 2. dovecot logout issues (Rajesh M) 3. Re: Messages on this list are often marked as spam. (Steven Mainor) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Feb 2017 08:57:50 +0200 From: Aki Tuomi <aki.tuomi(a)dovecot.fi> To: dovecot(a)dovecot.org Subject: Re: Solr 6.4.1 Message-ID: <aba919c2-cffe-ed91-23f4-2e57d967b83b(a)dovecot.fi> Content-Type: text/plain; charset=utf-8 On 09.02.2017 07:54, Daniel Miller wrote: > I've been running Solr for a while (4.10.3) - wanted to make the jump > to the latest & greatest. I installed 6.4.1, copied over my > schema.xml - and after a couple false starts where I needed to tweak > it work with the new version...it works! I did not copy the database, > started from scratch, and executed a "doveadm fts rescan -A". But... > > Judging solely from at least one client - it's fine. But looking in > the logs I see: > 1. The first scan of a mailbox dovecot's error log gives: > dovecot: imap(dmiller(a)amfes.com): Error: fts_solr: Lookup failed: > Bad Request > > 2. Subsequent scans do not appear to generate any dovecot error logs > - but I'm not certain. Each new mailbox/subfolder scanned will each > have one error on the initial scan. > > 3. Solr's log gives me the following - on every search. > 2017-02-09 05:50:12.412 ERROR (qtp205125520-15) [ x:dovecot] > o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: Bad > contentType for search handler :text/xml > request={q=from:"test"+OR+to:"test"+OR+cc:"test"+OR+subject:"test"+OR+body:" test"&fl=uid,score&sort=uid+asc&fq=%2Bbox:c1af150abfc9df4d7f7a00003bc41c5f+% 2Buser:"dmiller(a)amfes.com"&rows=67135} Hi! can you please use tcpdump or wireshark to capture the actual HTTP request causing this exception? Aki ------------------------------ Message: 2 Date: Thu, 9 Feb 2017 16:00:22 +0530 From: "Rajesh M" <24x7server(a)24x7server.net> To: <dovecot(a)dovecot.org> Subject: dovecot logout issues Message-ID: <3112B2DB02AA4C97871A9E3C19D6C9B8.MAI(a)ns1.24x7server.net> Content-Type: text/plain; charset="UTF-8" hi we are using dovecot version 2.2.7 (config file given below) centos 6, qmail, vpopmail, mysql server configuration hex core processor, 16 gb ram 1 X 600 gb 15 k rpm for main drive and 2 X 2000 gb hdd for data (No raid) busy server with around 4000 email ids --- load is around 2 to 10 the issue is that SQUIRRELMAIL webmail users suddenly lose connection while they are working on the webmail. after logging in, if the user tries to open a mail then the interface gives error invalid user id or password. this happens on an extremely random basis. also htop always shows a few delayed processes of dovecot (shown as D) on top -- pop3 and imap dovecot logs do not show any login error when such a logout takes place. the said mailbox contained just around 30 emails and it is not related to the timeout plugin of squirrelmail either since the same webmail folders works on other servers of ours without any issues. webmail load slowly in general however when it works normally webmail is very fast and able to handle several 10 s of thousands of emails in the inbox. ram consumed is 2 - 5 gb during peak hours. rebooted server but issue not solved issue is present for the last around 1 month and was not present earlier. help required please. thanks rajesh settings as such # 2.2.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) # NOTE: Send doveconf -n output instead when asking for help. auth_anonymous_username = anonymous auth_cache_negative_ttl = 0 auth_cache_size = 0 auth_cache_ttl = 0 auth_debug = no auth_debug_passwords = yes auth_default_realm = auth_failure_delay = 2 secs auth_gssapi_hostname = auth_krb5_keytab = auth_master_user_separator = auth_mechanisms = plain login digest-md5 cram-md5 auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_username_translation = auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth auth_worker_max_count = 30 base_dir = /var/run/dovecot config_cache_size = 1 M debug_log_path = default_client_limit = 1000 default_idle_kill = 1 mins default_internal_user = dovecot default_login_user = vpopmail default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%m: %$ dict_db_config = director_doveadm_port = 0 director_mail_servers = director_servers = director_user_expire = 15 mins director_username_hash = %u disable_plaintext_auth = no dotlock_use_excl = yes doveadm_allowed_commands = doveadm_password = doveadm_port = 0 doveadm_socket_path = doveadm-server doveadm_worker_count = 0 dsync_alt_char = _ dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U first_valid_gid = 89 first_valid_uid = 89 hostname = imap_capability = imap_client_workarounds = imap_id_log = imap_id_send = name * imap_idle_notify_interval = 2 mins imap_logout_format = in=%i out=%o imap_max_line_length = 64 k imap_metadata = no imap_urlauth_host = imap_urlauth_logout_format = in=%i out=%o imap_urlauth_port = 143 imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_verify = yes imapc_user = import_environment = TZ DEBUG_OUTOFMEM info_log_path = instance_name = dovecot last_valid_gid = 0 last_valid_uid = 0 lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header = libexec_dir = /usr/libexec/dovecot listen = *, :: lmtp_address_translate = lmtp_proxy = no lmtp_rcpt_check_quota = no lmtp_save_to_detail_mailbox = no lock_method = fcntl log_path = /var/log/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_access_sockets = login_greeting = ready. login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = mail_access_groups = mail_always_cache_fields = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_attribute_dict = mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = mail_home = mail_location = mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib64/dovecot mail_plugins = " quota" mail_prefetch_count = 0 mail_privileged_group = mail_save_crlf = no mail_shared_explicit_inbox = no mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = mailbox_idle_check_interval = 30 secs mailbox_list_index = no maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 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 master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_md5 = apop3d mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = prefix = separator = . subscriptions = yes type = private } passdb { args = cache_key=%u webmail=127.0.0.1 default_fields = deny = no driver = vpopmail master = no override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } plugin { quota = maildir:ignore=Trash quota_rule = ?:storage=0 } pop3_client_workarounds = pop3_deleted_flag = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %08Xu%08Xv pop3c_host = pop3c_master_user = pop3c_password = pop3c_port = 110 pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_verify = yes pop3c_user = %u postmaster_address = protocols = imap pop3 quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s replication_full_sync_interval = 1 days replication_max_conns = 10 replicator_host = replicator replicator_port = 0 sendmail_path = /usr/sbin/sendmail service aggregator { chroot = . client_limit = 0 drop_priv_before_exec = no executable = aggregator extra_groups = fifo_listener replication-notify-fifo { group = mode = 0600 user = } group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replication-notify { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = $default_internal_user } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0666 user = $default_internal_user } unix_listener login/login { group = mode = 0666 user = } unix_listener token-login/tokenlogin { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 reuse_port = no ssl = no } inet_listener imaps { address = port = 993 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 50 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-login { chroot = token-login client_limit = 0 drop_priv_before_exec = no executable = imap-urlauth-login extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = imap service_count = 1 type = login unix_listener imap-urlauth { group = mode = 0666 user = } user = $default_login_user vsz_limit = 18446744073709551615 B } service imap-urlauth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener imap-urlauth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service imap-urlauth { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap-urlauth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener token-login/imap-urlauth { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 2048 process_min_avail = 50 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 512 M } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = lmtp service_count = 0 type = unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service managesieve-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = managesieve-login extra_groups = group = idle_kill = 0 inet_listener sieve { address = port = 4190 reuse_port = no ssl = no } privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service managesieve { chroot = client_limit = 1 drop_priv_before_exec = no executable = managesieve extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = unix_listener login/sieve { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 reuse_port = no ssl = no } inet_listener pop3s { address = port = 995 reuse_port = no ssl = yes } privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 256 process_min_avail = 25 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service replicator { chroot = client_limit = 0 drop_priv_before_exec = no executable = replicator extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replicator-doveadm { group = mode = 00 user = $default_internal_user } unix_listener replicator { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } unix_listener ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = yes ssl_ca = ssl_cert = </var/qmail/control/servercert.pem ssl_cert_username_field = commonName ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = ssl_client_ca_file = ssl_client_cert = ssl_client_key = ssl_crypto_device = ssl_dh_parameters_length = 2048 ssl_key = </var/qmail/control/servercert.pem ssl_key_password = ssl_parameters_regenerate = 0 ssl_prefer_server_ciphers = no ssl_protocols = !SSLv2 ssl_require_crl = yes ssl_verify_client_cert = no state_dir = /var/lib/dovecot stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_session_min_time = 15 mins stats_user_min_time = 1 hours submission_host = syslog_facility = mail userdb { args = cache_key=%u quota_template=quota_rule=*:backend=%q default_fields = driver = vpopmail override_fields = } valid_chroot_dirs = verbose_proctitle = no verbose_ssl = no version_ignore = no protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 200 mail_plugins = " quota imap_quota" } protocol pop3 { mail_max_userip_connections = 40 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_lock_session = no pop3_no_flag_updates = yes } ------------------------------ Message: 3 Date: Thu, 09 Feb 2017 06:13:37 -0500 From: Steven Mainor <steve(a)degga.net> To: Bj?rn T Johansen <btj(a)havleik.no>,dovecot(a)dovecot.org Subject: Re: Messages on this list are often marked as spam. Message-ID: <00905D2C-F645-424B-AA31-92E36318AC5F(a)degga.net> Content-Type: text/plain; charset=UTF-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Well for other mailing lists I have noticed that a lot of lists add text to the body or subject saying what list the email is from which would cause the signature not to match. But the dovecot list doesn't do that so that's why I found it strange that so many emails fail dkim. - -- Steven Mainor On February 7, 2017 2:22:59 AM EST, "Bj?rn T Johansen" <btj(a)havleik.no> wrote: >On Mon, 06 Feb 2017 17:39:07 -0500 >Steven Mainor <steve(a)degga.net> wrote: > >> Hello, >> >> It seems that I get several emails a week from this list in my spam >> folder. Usually because the DKIM signature fails. Has anyone else >> noticed this problem or is it just me? >> >> -- >> Steven mainor >> steve(a)degga.net > >Yes, same here... Having the same problem on other maillists as well, >not sure why. > >BTJ -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQI9BAEBCgAnBQJYnE7hIBxTdGV2ZW4gTWFpbm9yIDxzdGV2ZUBkZWdnYS5uZXQ+ AAoJEHEwUCz4iIxrOVcP/A6eW2CqDs6wl53cPRgBszBVCJeoiWPesdR2ZTBEK/k3 agFgeBoknDLxlsAqnqDpi8vAVOjc1DvUTAFDs0btp8e5qirFjwzSMy74PpdBAWWJ m7B/8g69TnhDwYi9RQITJ1Ev5gUX/S5BqpV7zFjsr5BP1fhPEEwDYlnZLWrFXe+e Z3N/skPKvr9Obyd+dREiL9OVjrU+2SNLnbLjPn69JKDQZxarCq2wqz6DTJ+YAtRs ompbEgjAFTQ2p/618KQeOKRy59BIDWKp0TB797FiWYCjwVS0M9+vuecro2otplj6 xHWPhkF9paoZzxi5YXpFH/M5rXwg52jaUJWLVEiPszANHVgkZcolPkf71JcLOU01 H5LG66qXdy7spDjKvbXA0vYRzB/BaviJi4TIk/gK2qQpalXcz00G1EDmSQA7XqA1 uXf2TOpfIOQYjzN2YajtNM1+fnQUHw65SWC/vVEuN3nbjaNsmNSrTwximG5J5JZK ffYzr934TCXw65l+WIJS4nUafJKyuX7BKmz6kBcBQOr8Rw3udxiMzyC4ZelTLBw+ akj88JlHbYA2H2nA8xAsqwVxGOfJnvxb9IDiGwJyI0WoL4CRIcpZVyNelsrJMRZg v7U4wRKX7J485PSB9NDpQTGpDkUJCjtmWZx7cJpYQbiTHZiCJ4cMJyNO/T/nywvR =XJnU -----END PGP SIGNATURE----- ------------------------------ Subject: Digest Footer _______________________________________________ dovecot mailing list dovecot(a)dovecot.org http://dovecot.org/cgi-bin/mailman/listinfo/dovecot ------------------------------ End of dovecot Digest, Vol 166, Issue 22 **************************************** __________ Information from ESET Endpoint Antivirus, version of virus signature database 14908 (20170209) __________ The message was checked by ESET Endpoint Antivirus. part000.txt - is OK http://www.eset.com __________ Information from ESET Endpoint Antivirus, version of virus signature database 14909 (20170209) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

1 0

Quota error for disabled namespace
by Riecken Jens 09 Feb '17

09 Feb '17

Hello, Some of our users use a dedicated archive mailbox, so we've setup an archive namespace for it, which is by default disabled. This namespace has its own quota which is defined by quota2* settings. Every time a user without archive authenticates, dsync kicks in, lmtp delivers a message or imap is used an Error message gets recorded: "imap(user1): Error: quota: Unknown namespace: Archive/" This happens about 441,756 times per hour - putting heavy load on the whole logging chain. In my opinion it makes sense suppressing quota error messages for disabled namespaces or flag it as debug messages. I'm thankful for every solution for this problem! Best regards Jens Environment: Dovecot Version 2.2.27 (c0f36b0) Red Hat Enterprise Linux Server release 7.3 (Maipo) Linux 3.10.0-514.6.1.el7.x86_64 doveadm user '*' |wc -l: 15946 Relevant configuration sections: namespace archive { disabled = yes hidden = no inbox = no list = yes location = maildir:/archive/%h/Archive mailbox "Auto Archive" { auto = subscribe special_use = \Archive } prefix = Archive/ separator = / subscriptions = no type = private } The archive gets enabled by the authentication backend: user_attrs = ou=home=/mail/%U$/%u,=uid=500,=gid=500,quota=quota_rule=*:bytes=%{ldap:quota},archiveDisabled=namespace/archive/disabled=%{ldap:archiveDisabled:yes} To ensure that the archive storage stays within sane boundaries there is a quota defined for the archive: plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = proxy::acl mail_replica = tcp:mail-replica:12345 quota = maildir:User_quota quota2 = maildir:Archive_quota:ns=Archive/ quota2_rule = *:storage=10G quota_rule = *:storage=2G quota_rule2 = INBOX/Trash:storage=+10%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=85%% quota-warning 85 %u quota_warning4 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve }

1 0

How to add User in MSSQL DB - error unknown user
by Maurizio Caloro 08 Feb '17

08 Feb '17

Hello Please I need to add "Maurizio" to this MSSQL DB, but I don't now how to add this step in my opinion I'think that the user can't be found, so I will have the "unknown user" Can give here any little help to fix this? Feb 8 12:09:56 caloro dovecot: auth: Debug: auth client connected (pid=13300) Feb 8 12:09:56 caloro dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011session=dfsfdsdsJITACX+KIh#011lip=37.1 20.190.188#011rip=151.248.162.33#011lport=110#011rport=54604#011resp=<hidden > Feb 8 12:09:56 caloro dovecot: auth-worker(13303): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Feb 8 12:09:56 caloro dovecot: auth-worker(13303): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Feb 8 12:09:56 caloro dovecot: auth-worker(13303): Debug: sql(maurizio(a)caloro.ch,151.248.162.33): query: SELECT username AS user, password_enc AS password, CONCAT(homedir, maildir) AS userdb_home, uid AS userdb_uid, gid AS userdb_gid, CONCAT('maildir:', homedir, maildir) AS userdb_mail, CONCAT('maildir:storage=', (quota*1024)) as userdb_quota FROM mail_users WHERE (username = 'maurizio(a)caloro.ch' OR email = 'maurizio(a)caloro.ch') AND ((imap = 1 AND 'pop3' = 'imap') OR (pop3 = 1 AND 'pop3' = 'pop3') OR 'pop3' = 'smtp' OR 'pop3' = 'sieve') Feb 8 12:09:56 caloro dovecot: auth-worker(13303): sql(maurizio(a)caloro.ch,151.248.162.33): unknown user Feb 8 12:09:58 caloro dovecot: auth: Debug: client passdb out: FAIL#0111#011user=maurizio(a)caloro.ch Feb 8 12:09:58 caloro dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<maurizio(a)caloro.ch>, method=PLAIN, rip=151.248.162.33, lip=37.120.190.188, session=<DPyY5wJITACX+KIh> Regards and thank for any hint or help mauri

3 3

define auth timeout
by Daniel Betz 08 Feb '17

08 Feb '17

Hello list, when reloading dovecot via "doveadm reload" it throws me tons of errors like this: Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 imap: Error: net_connect_unix(/run/dovecot/auth-master) failed: Resource temporarily unavailable Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 imap: Error: net_connect_unix(/run/dovecot/auth-master) failed: Resource temporarily unavailable Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 imap: Error: net_connect_unix(/run/dovecot/auth-master) failed: Resource temporarily unavailable Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 imap: Error: net_connect_unix(/run/dovecot/auth-master) failed: Resource temporarily unavailable Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 imap: Error: net_connect_unix(/run/dovecot/auth-master) failed: Resource temporarily unavailable this is so long, till all client logins time out: Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8576.416 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8574.736 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 13163.1758 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 13163.1760 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 13163.1761 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 13163.1762 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8566.121 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8583.1702 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: login(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8582.1834 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: plain(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8576.340 timed out after 150 secs, state=3 Feb 08 10:57:30 server1 dovecot[18243]: Feb 08 10:57:30 auth: Error: login(mail(a)adress,xx.xx.xx.xx.<xxxxxxxxxxxx>): Request 8576.335 timed out after 150 secs, state=3 I have searched for this timeout in dovecot config, but havent found something. Can you tell me how to define this timeout, or is this an LDAP timeout in userdb/passdb and dovecot-ldap.conf ? Or better, how to prevent this failures? I can see them sometimes in the log too w/o reloading. Regards, Daniel dovecot-ldap.conf: uris = ldapi://%2Fvar%2Frun%2Fldapi dn = cn=xxxxxxx,o=domain,c=com dnpass = xxxxxxxxxxxxx auth_bind = no ldap_version = 3 base = o=domain,c=com user_attrs = mail=user,mailMessageStore=home,\ mailQuota=quota_rule=*:storage=%$ iterate_filter= (|(mailHost=server1.domain.com)(mailHost=popserver1.domain.com)) user_filter = (&(accountstatus=active)(|(uid=%u)(mail=%u))) pass_attrs = mail=user,userPassword=password,=proxy_maybe=y,mailHost=host,=destuser=%u[%r] pass_filter = (&(accountstatus=active)(|(uid=%u)(mail=%u))) dovecot.conf: # 2.2.25 (7be1766): /usr/local/dovecot2/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.36.3.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_cache_negative_ttl = 1 mins auth_cache_size = 64 M auth_cache_ttl = 2 hours auth_mechanisms = plain login auth_username_chars = auth_verbose = yes base_dir = /var/run/dovecot/ debug_log_path = /dev/null default_login_user = dovecot disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 1001 first_valid_uid = 1001 info_log_path = /var/log/dovecot/messages lda_mailbox_autocreate = yes lda_original_recipient_header = X-Envelope-To log_path = /dev/stderr login_log_format_elements = user=[%u] method=%m rip=%r lip=%l %c mail_gid = 1001 mail_location = mdbox:~:INDEX=%h/INDEX mail_plugins = " notify replication stats" mail_uid = 1001 mbox_write_locks = fcntl namespace { inbox = yes location = mailbox Drafts { auto = no special_use = \Drafts } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox "Infizierte Objekte" { auto = no special_use = \Junk } mailbox Sent { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = no special_use = \Trash } prefix = separator = . type = private } namespace inbox { hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap2.conf driver = ldap } plugin { quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_warning = storage=85%% quota-warning 85 %u stats_refresh = 30 secs stats_track_cmds = yes } replication_max_conns = 30 sendmail_path = /usr/local/exim/bin/exim service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = popuser } unix_listener replication-notify { mode = 0666 user = popuser } } service anvil { client_limit = 60000 } service auth { client_limit = 60000 unix_listener auth-userdb { mode = 0666 user = popuser } unix_listener auth { mode = 0666 user = popuser } } service config { unix_listener config { user = popuser } } service dict { unix_listener dict { mode = 0666 user = popuser } } service doveadm { inet_listener { port = 12345 } user = popuser } service imap-login { chroot = login client_limit = 600 process_limit = 100 process_min_avail = 16 service_count = 0 } service imap { executable = /usr/local/dovecot2/libexec/dovecot/imap process_limit = 250000 } service ipc { client_limit = 60000 unix_listener ipc { mode = 0650 user = dovecot } unix_listener login/ipc-proxy { mode = 0650 user = dovecot } } service lmtp { unix_listener lmtp { mode = 0666 user = popuser } } service pop3-login { chroot = login client_limit = 600 process_limit = 100 process_min_avail = 16 service_count = 0 } service pop3 { executable = /usr/local/dovecot2/libexec/dovecot/pop3 process_limit = 250000 } service replicator { unix_listener replicator-doveadm { mode = 0600 user = popuser } } service stats { fifo_listener stats-mail { mode = 0600 user = popuser } } ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key ssl_protocols = TLSv1.2 TLSv1.1 TLSv1 !SSLv3 !SSLv2 userdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol doveadm { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-doveadm.conf driver = ldap name = } userdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-doveadm.conf driver = ldap name = } } protocol lda { info_log_path = /var/log/dovecot-lda log_path = /var/log/dovecot-lda log_timestamp = "%b %d %H:%M:%S " mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota postmaster_address = %u } protocol imap { imap_client_workarounds = mail_max_userip_connections = 100 mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota imap_quota stats imap_stats } protocol pop3 { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota stats pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_fast_size_lookups = yes pop3_reuse_xuidl = no pop3_uidl_format = %g } local xx.xx.xx.54 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xx.xx.xx.54 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xx.xx.xx.55 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xx.xx.xx.55 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xx.xx.xx.56 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xx.xx.xx.56 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xxx:xxx:xxx::::fa { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxx:xxx:xxx::::fa { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxx:xxx:xxx::::fb { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxx:xxx:xxx::::fb { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxx:xxx:xxx::::fc { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xxx:xxx:xxx::::fc { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } }

1 0

Changes to userdb not picked up
by Tom Sommer 08 Feb '17

08 Feb '17

I have my quota limits stored in userdb and auth_cache enabled (default settings). When I change the quota limit the old limit is still cached for the user for another hour. Is there any way to prevent this from happening? Thanks -- Tom

3 3

Filenames and flags
by Carsten Czichos 08 Feb '17

08 Feb '17

Hi list, where can I find the meaning of lowercase file flags ? I found this information: http://cr.yp.to/proto/maildir.html <http://cr.yp.to/proto/maildir.html> But what does the lowercase a & d mean as in ...,S=2364,W=2411:2,Sad ? Thanx for your help !

2 1

Re: Dovecot dsync 'ssl_client_ca'
by Aki Tuomi 08 Feb '17

08 Feb '17

Please keep responses in list. rm -f /var/lib/dovecot/ssl-parameters.dat, i think it was in that dir. On 2017-02-03 17:00, Thierry wrote: > Hi, > > I have removed the '<' : > > ssl_client_ca_file = /etc/ssl/certs/GandiCA2.pem > > But now: > > doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 > doveadm: Error: Couldn't initialize SSL parameters, disabling SSL > doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 > doveadm: Error: Couldn't initialize SSL parameters, disabling SSL > > Any idea ? > > Thx > >> Yes. The ssl_client_ca_file is not actually expecting <, just file name. >> Aki > >> On 2017-02-03 15:13, Thierry wrote: >>> Hi, >>> >>> I have made change: >>> >>> ssl_protocols = !SSLv2 !SSLv3 >>> ssl = required >>> verbose_ssl = no >>> ssl_key = </etc/ssl/private/private.key >>> ssl_cert = </etc/ssl/certs/key.crt >>> ssl_client_ca_file = </etc/ssl/certs/GandiCA2.pem >>> >>> >>> # Create a listener for doveadm-server >>> service doveadm { >>> user = vmail >>> inet_listener { >>> port = 12345 >>> ssl= yes >>> } >>> } >>> >>> and doveadm_port = 12345 // mail_replica = tcps:server2.domain.ltd # use doveadm_port >>> >>> And now: >>> >>> Feb 03 14:11:16 doveadm(user1(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't load CA certs from directory : error:02001024:system library:fopen:File name too long >>> Feb 03 14:11:17 doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 >>> Feb 03 14:11:17 doveadm: Error: Couldn't initialize SSL parameters, disabling SSL >>> >>> Thx for your support >>> >>> >>> >>> >>> Le vendredi 3 février 2017 à 11:34:43, vous écriviez : >>> >>>> Hello, >>>> On 02/03/2017 08:51 AM, Thierry wrote: >>>>> Hello, >>>>> >>>>> Still working with my dsync pb. >>>>> I have done a clone (vmware) of my email server. >>>>> Today I have two strictly identical emails servers (server1 >>>>> (main) and server2 (bck) (except IP, hostname and mail_replica). >>>>> >>>>> The ssl config on my both server: >>>>> >>>>> ssl_protocols = !SSLv2 !SSLv3 >>>>> ssl = required >>>>> verbose_ssl = no >>>>> ssl_key = </etc/ssl/private/private.key >>>>> ssl_cert = </etc/ssl/certs/key.crt >>>>> ssl_ca = </etc/ssl/certs/GandiStandardSSLCA2.pem >>>> I think it should be ssl_client_ca_file = >>>> </etc/ssl/certs/GandiStandardSSLCA2.pem for you. >>>>> This config is working for my email client and my email web >>>>> interface ... >>>>> >>>>> Are they on the right order ? >>>>> >>>>> mail_replica = tcps:server1@domain.ltd and tcps:server2@domain.ltd >>>>> >>>>> There is trafic on my iptables rules on my both servers: >>>>> >>>>> 60 3600 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:4711 >>>>> >>>>> >>>>> >>>>> My error message from server1 (main server): >>>>> >>>>> Feb 03 08:38:08 doveadm(user1(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) >>>>> Feb 03 08:42:35 doveadm(user2(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) >>>>> Feb 03 08:42:35 doveadm(user3(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) >>>>> Feb 03 08:42:35 doveadm(user4(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) >>>>> >>>>> No logs from server2 >>>>> >>>>> Any ideas ? >>>>> >>>>> Thx for your support >>>>> >>>>> >>>

3 6

Sieve LDA Errors (Improper Saving?)
by Richard Laager 08 Feb '17

08 Feb '17

I'm getting lots of errors like this (possibly on every message delivery): imap2 dovecot: lmtp(rlaager(a)wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ : sieve: binary save: failed to create temporary file: open(/var/lib/dovecot/sieve/junk-mail.svbin.ima p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +w perm: /var/lib/dovecot/ sieve, dir owned by 0:0 mode=0755) imap2 dovecot: lmtp(rlaager(a)wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ: sieve: The LDA Sieve plugin does not have permission to save global Sieve script binaries; global Sieve scripts like `/var/lib/dovecot/sieve/junk-mail.sieve' need to be pre-compiled using the sievec tool It's intentional in my setup that the vmail user can't write to the global sieve script directory. But it shouldn't need to, as those are already pre-compiled: rlaager@imap2:/var/lib/dovecot/sieve$ ls -la total 12 drwxr-xr-x 2 root root 4096 Nov 29 22:27 . drwxr-xr-x 3 root root 4096 Feb 6 20:39 .. lrwxrwxrwx 1 root root 53 Sep 12 01:35 junk-mail.sieve -> /usr/share/wiktel-server-mail-backend/junk-mail.sieve -rw-r--r-- 1 root root 254 Nov 29 22:27 junk-mail.svbin rlaager@imap2:/var/lib/dovecot/sieve$ ls -la /usr/share/wiktel-server-mail-backend/junk-mail.sieve -rw-r--r-- 1 root root 124 Oct 31 09:34 /usr/share/wiktel-server-mail-backend/junk-mail.sieve Note that the .svbin is from November, while the text version is from October. Even if something is looking at the date of the symlink, that's from September. So the first question is... why is Dovecot trying to write the binary file? I dug into the Pigeonhole code... I think, but am certainly not sure, that lda_sieve_open() in pigeonhole/src/plugins/lda-sieve/lda-sieve-plugin.c is the relevant function calling lda_sieve_binary_save(). At the end of the function, it has: if (!recompile) lda_sieve_binary_save(srctx, sbin, script); This seems odd to me. Why is it trying to save in the "!recompile" case? It seems like it should be saving in the "recompile" case. If I'm reading this code right, recompile is set when it loads a corrupt sieve binary script and needs to recompile from text. I could be completely off, though. Any thoughts? -- Richard

2 2

Migrating to sieve
by Adam Shostack 08 Feb '17

08 Feb '17

Hi, As I migrate to sieve, I would like to carry over the logic I had in procmail rules, which let me take all mail where I'd never sent email to that address into a final spam catchall, which I called "neversent." I see that sieve can't run external programs, and I wonder if that means I'm SOL, or is there an alternate approach that does roughly the same thing? (I understand the general security logic for that decision. I have root access on the server in question if that helps.) Thank you for any help you can provide! Adam The procmail code was: # a bunch of complex shell script to extract From: into a variable of that # name. :0: * ^TO_$ME * !? fgrep -q --ignore-case -e "$FROM" $HOME/.lbdb/m_inmail.list neversent along with a procmail-outbound setup of: :0hc | lbdb-fetchaddr -a :0 ! "$@"

2 2

Dovecot with dsync
by Nick Lekkas 07 Feb '17

07 Feb '17

Hello to all !!! I am trying to setup dsync on CentOS latest with dovecot 2.2.10 ...but does not seem to work !! I have tried to follow many guides i have found but none seem to work ! Before i mention my issues please clear me something: 1. dsynch to work needs for sure mysql ..? or can work with the default linux user scheme ..? 2. if mysql is required please where can i a working working user schema ? thanks in advance for your time ... __________ Information from ESET Endpoint Antivirus, version of virus signature database 14893 (20170206) __________ The message was checked by ESET Endpoint Antivirus. Email message - is OK http://www.eset.com

1 0

Dsync migration with shared folders
by George Dimakopoulos 06 Feb '17

06 Feb '17

Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both machines then dsync could not replicate the domains that contained shared folders. What is the right migration process for domains with shared folders ? Regards, George dovecot -n ------------------------- # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p2 amd64 zfs auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2560 default_process_limit = 512 dict { acl = mysql:/usr/local/etc/dovecot/dovecot-shared-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } doveadm_password = # hidden, use -P to show it doveadm_port = 12345 log_path = /var/log/dovecot.log mail_debug = yes mail_home = /usr/local/vhosts/mail/%d/%n mail_location = maildir:/usr/local/vhosts/mail/%d/%n:LAYOUT=fs mail_max_userip_connections = 70 mail_plugins = quota acl notify replication mail_privileged_group = vmail mail_shared_explicit_inbox = 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 mbox_write_locks = fcntl namespace { inbox = no list = children location = maildir:/usr/local/vhosts/mail/%%d/%%n:LAYOUT=fs:INDEX=/usr/local/vhosts/indexes/%d/%n/shared/%%u:INDEXPVT=/usr/local/vhosts/indexes/%d/%n/shared/%%u prefix = shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl mail_replica = tcp:mx1 quota = dict:User quota::proxy::quota quota_rule2 = Trash:storage=+100M sieve = /usr/local/vhosts/mail/%d/%n/.dovecot.sieve sieve_before = /usr/local/vhosts/sieve/before.d/ sieve_dir = /usr/local/vhosts/mail/%d/%n sieve_global_dir = /usr/local/vhosts/sieve/%d sieve_global_path = /usr/local/vhosts/sieve/%d/default.sieve } protocols = imap lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service config { unix_listener config { user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service replicator { unix_listener replicator-doveadm { mode = 0666 } } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota acl notify replication sieve } protocol lda { mail_plugins = quota acl notify replication sieve acl postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota acl notify replication imap_quota imap_acl } ssl_cert = ssl_key =

1 0

Dsync migration with shared folders
by Γιώργος Δημακόπουλος 06 Feb '17

06 Feb '17

Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both machines then dsync could not replicate the domains that contained shared folders. What is the right migration process for domains with shared folders ? Regards, George g.dimakopoulos(a)sophimail.com dovecot -n ------------------------- # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p2 amd64 zfs auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2560 default_process_limit = 512 dict { acl = mysql:/usr/local/etc/dovecot/dovecot-shared-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } doveadm_password = # hidden, use -P to show it doveadm_port = 12345 log_path = /var/log/dovecot.log mail_debug = yes mail_home = /usr/local/vhosts/mail/%d/%n mail_location = maildir:/usr/local/vhosts/mail/%d/%n:LAYOUT=fs mail_max_userip_connections = 70 mail_plugins = quota acl notify replication mail_privileged_group = vmail mail_shared_explicit_inbox = 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 mbox_write_locks = fcntl namespace { inbox = no list = children location = maildir:/usr/local/vhosts/mail/%%d/%%n:LAYOUT=fs:INDEX=/ usr/local/vhosts/indexes/%d/%n/shared/%%u:INDEXPVT=/usr/ local/vhosts/indexes/%d/%n/shared/%%u prefix = shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl mail_replica = tcp:mx1 quota = dict:User quota::proxy::quota quota_rule2 = Trash:storage=+100M sieve = /usr/local/vhosts/mail/%d/%n/.dovecot.sieve sieve_before = /usr/local/vhosts/sieve/before.d/ sieve_dir = /usr/local/vhosts/mail/%d/%n sieve_global_dir = /usr/local/vhosts/sieve/%d sieve_global_path = /usr/local/vhosts/sieve/%d/default.sieve } protocols = imap lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service config { unix_listener config { user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service replicator { unix_listener replicator-doveadm { mode = 0666 } } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota acl notify replication sieve } protocol lda { mail_plugins = quota acl notify replication sieve acl postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota acl notify replication imap_quota imap_acl } ssl_cert = ssl_key =

1 0

Compiling Dovecot on Solaris 10
by Mantas Gegužis 06 Feb '17

06 Feb '17

Hello, I am tying to compile Dovecot 2.2.27 on Solaris 10, and I get this error: test-ioloop.c: In function `test_ioloop_pending_io': test-ioloop.c:188: error: size of array `type name' is negative My configuration is like this: Install prefix . : /usr/local File offsets ... : 64bit I/O polling .... : poll I/O notifys .... : none SSL ............ : yes (OpenSSL) GSSAPI ......... : no passdbs ........ : static passwd passwd-file shadow pam checkpassword dcrypt ..........: yes : -bsdauth -sia -ldap -sql -vpopmail userdbs ........ : static prefetch passwd passwd-file checkpassword : -ldap -sql -vpopmail -nss SQL drivers .... : : -pgsql -mysql -sqlite -cassandra Full text search : squat : -lucene -solr Last version that I have compiled was 2.2.24, version 2.2.25 failed with error: In file included from guid.c:6: sha1.h:80: error: static or type qualifiers in abstract declarator Is there anyone who can help me? -- Pagarbiai Mantas Gegužis VU Informacinių technologijų taikymo centras tel. 8 5 236 6208

6 10

Dsync migration with shared folders
by George Dimakopoulos 06 Feb '17

06 Feb '17

Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both machines then dsync could not replicate the domains that contained shared folders. What is the right migration process for domains with shared folders ? Regards, George dovecot -n ------------------------- # 2.2.27 (c0f36b0): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: FreeBSD 11.0-RELEASE-p2 amd64 zfs auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2560 default_process_limit = 512 dict { acl = mysql:/usr/local/etc/dovecot/dovecot-shared-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } doveadm_password = # hidden, use -P to show it doveadm_port = 12345 log_path = /var/log/dovecot.log mail_debug = yes mail_home = /usr/local/vhosts/mail/%d/%n mail_location = maildir:/usr/local/vhosts/mail/%d/%n:LAYOUT=fs mail_max_userip_connections = 70 mail_plugins = quota acl notify replication mail_privileged_group = vmail mail_shared_explicit_inbox = 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 mbox_write_locks = fcntl namespace { inbox = no list = children location = maildir:/usr/local/vhosts/mail/%%d/%%n:LAYOUT=fs:INDEX=/usr/local/vhosts/indexes/%d/%n/shared/%%u:INDEXPVT=/usr/local/vhosts/indexes/%d/%n/shared/%%u prefix = shared/%%d/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl mail_replica = tcp:mx1 quota = dict:User quota::proxy::quota quota_rule2 = Trash:storage=+100M sieve = /usr/local/vhosts/mail/%d/%n/.dovecot.sieve sieve_before = /usr/local/vhosts/sieve/before.d/ sieve_dir = /usr/local/vhosts/mail/%d/%n sieve_global_dir = /usr/local/vhosts/sieve/%d sieve_global_path = /usr/local/vhosts/sieve/%d/default.sieve } protocols = imap lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service config { unix_listener config { user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service replicator { unix_listener replicator-doveadm { mode = 0666 } } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota acl notify replication sieve } protocol lda { mail_plugins = quota acl notify replication sieve acl postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota acl notify replication imap_quota imap_acl } ssl_cert = ssl_key =

1 0

dovecot/auth CPU spikes
by nicolas＠andrillon.net 05 Feb '17

05 Feb '17

Hi All, I have recently moved by webmail server from a VPS to a hosted dedicated server running Ubuntu 16.04. Everything is fine except that login is particularly and consistently long (around 4-5 seconds). I have noticed that the process dovecot/auth seems to eat all of the resources of one of the cores available on the host during login. The authentication backend is a postgres database which is running absolutely fine. I have been scavenging on the dovecot mailing list for some time but I have not been able to find a solution to my problem so decided to send this bottle to the sea. Here is my config: $ sudo dovecot -n # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 3.14.32-xxxx-grs-ipv6-64 x86_64 Ubuntu 16.04.1 LTS ext4 auth_cache_size = 10 M auth_mechanisms = plain login default_internal_user = vmail first_valid_uid = 0 mail_location = maildir:/home/data/vmail/%d/%n mail_plugins = " fts fts_solr" mail_privileged_group = vmail maildir_stat_dirs = 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 Archive { auto = subscribe special_use = Archive } mailbox Drafts { auto = subscribe special_use = Drafts } mailbox Junk { auto = subscribe special_use = Junk } mailbox Sent { auto = subscribe special_use = Sent } mailbox "Sent Messages" { special_use = Sent } mailbox Trash { auto = subscribe special_use = Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_sendmail_args = -h;localhost:11334;-P;q1 antispam_mail_spam = learn_spam antispam_spam = Junk antispam_trash = Trash fts = solr fts_solr = break-imap-search url=http://localhost:8080/solr/ sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ } postmaster_address = postmaster(a)domain.net protocols = imap lmtp sieve pop3 service auth-worker { unix_listener auth-worker { user = vmail } user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = vmail } service imap-login { inet_listener imap { port = 0 } service_count = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service pop3-login { inet_listener pop3 { port = 0 } } ssl = required ssl_cert =

1 2

Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Aki Tuomi 05 Feb '17

05 Feb '17

Sorry for finnish. I think it might also work with libtool flag -static in Makefile.am LDADD flags.---Aki TuomiDovecot oy -------- Original message --------From: Aki Tuomi <aki.tuomi(a)dovecot.fi> Date: 05/02/2017 20:21 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) jos ldflags laittaa -static vivun niin se preferoi .a filedn linkkausta. ---Aki TuomiDovecot oy -------- Original message --------From: Timo Sirainen <tss(a)iki.fi> Date: 05/02/2017 20:19 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) On 5 Feb 2017, at 19.58, Timo Sirainen <tss(a)iki.fi> wrote: > > On 5 Feb 2017, at 19.49, Timo Sirainen <tss(a)iki.fi> wrote: >> >> On 4 Feb 2017, at 20.03, Ruga <ruga(a)protonmail.com> wrote: >>> >>> https://github.com/libressl-portable/portable/issues/278 >> >> I've no idea why that would happen. The only idea I had got rejected by someone. > > Oh, that's with OSX. I think that's the reason. Nothing to do with libressl. I'll see if I can reproduce it, as soon as I can figure out how to get a newer OpenSSL installed to my OSX.. Attached patch seems to work.

1 0

Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Aki Tuomi 05 Feb '17

05 Feb '17

jos ldflags laittaa -static vivun niin se preferoi .a filedn linkkausta. ---Aki TuomiDovecot oy -------- Original message --------From: Timo Sirainen <tss(a)iki.fi> Date: 05/02/2017 20:19 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub) On 5 Feb 2017, at 19.58, Timo Sirainen <tss(a)iki.fi> wrote: > > On 5 Feb 2017, at 19.49, Timo Sirainen <tss(a)iki.fi> wrote: >> >> On 4 Feb 2017, at 20.03, Ruga <ruga(a)protonmail.com> wrote: >>> >>> https://github.com/libressl-portable/portable/issues/278 >> >> I've no idea why that would happen. The only idea I had got rejected by someone. > > Oh, that's with OSX. I think that's the reason. Nothing to do with libressl. I'll see if I can reproduce it, as soon as I can figure out how to get a newer OpenSSL installed to my OSX.. Attached patch seems to work.

1 0

Panic error from dovecot 2.2.27 using libressl 2.4.5 (cross-posting at GitHub)
by Ruga 05 Feb '17

05 Feb '17

https://github.com/libressl-portable/portable/issues/278

2 3

Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled)
by baskar anand 05 Feb '17

05 Feb '17

Always I have the following lines in my mail.log (at startup and service restart) dovecot: master: Warning: Killed with signal 15 (by pid=3156 uid=0 code=kill) dovecot: log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) dovecot: master: Dovecot v2.2.22 (fe789d2) starting up for imap, pop3 (core dumps disabled) dovecot -n output is below: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-31-generic x86_64 Ubuntu 16.04.1 LTS auth_mechanisms = plain login mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap pop3" service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert =

2 1

Re: Compiling Dovecot on Solaris 10
by Joseph Tam 03 Feb '17

03 Feb '17

> I don't have problems building 2.2.27 on Solaris 10 > (using Sun Workshop compiler 5.11). ... and I don't have problems with Solaris10/gcc, but I don't have as many options as you do. Joseph Tam <jtam.home(a)gmail.com>

1 0

Crash while reading compressed mbox: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1)
by Anton Yuzhaninov 03 Feb '17

03 Feb '17

Hello, I use mbox compressed by gzip as read-only folder (using zlib plugin). This setup worked for a while, but doesn't work with latest dovecot version (2.2.27). I have error in logs: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) I can see list of messages in MUA but can't ready body of any message. I've tried to delete indexes, but it doesn't help. Backtrace looks like: (gdb) bt #0 0x0000000011266a4a in thr_kill () from /lib/libc.so.7 #1 0x0000000011266a1b in raise () from /lib/libc.so.7 #2 0x0000000011266989 in abort () from /lib/libc.so.7 #3 0x0000000010ef3850 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:201 #4 0x0000000010ef5167 in i_internal_fatal_handler (ctx=0x7fffffffe010, format=0x1222cf93 "file %s: line %d (%s): assertion failed: (%s)", args=0x7fffffffdff0) at failures.c:670 #5 0x0000000010ef3e5f in i_panic (format=0x1222cf93 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 #6 0x0000000012229238 in i_stream_zlib_seek (stream=0x118dd300, v_offset=56248, mark=false) at istream-zlib.c:416 #7 0x0000000010f05e48 in i_stream_skip (stream=0x118dd370, count=32489) at istream.c:278 #8 0x0000000010f057ba in i_stream_seek (stream=0x118dd370, v_offset=56248) at istream.c:300 #9 0x0000000010b17702 in istream_raw_mbox_get_body_size (stream=0x118ec870, expected_body_size=36695, body_size_r=0x7fffffffe2a0) at istream-raw-mbox.c:612 #10 0x0000000010b2b0aa in mbox_sync_read_next_mail (sync_ctx=0x7fffffffe418, mail_ctx=0x7fffffffe270) at mbox-sync.c:162 #11 0x0000000010b2964a in mbox_sync_loop (sync_ctx=0x7fffffffe418, mail_ctx=0x7fffffffe270, partial=false) at mbox-sync.c:1057 #12 0x0000000010b290cb in mbox_sync_do (sync_ctx=0x7fffffffe418, flags=MBOX_SYNC_UNDIRTY) at mbox-sync.c:1642 #13 0x0000000010b28999 in mbox_sync_int (mbox=0x118ee040, flags=MBOX_SYNC_UNDIRTY, lock_id=0x7fffffffe640) at mbox-sync.c:1969 #14 0x0000000010b280ea in mbox_sync (mbox=0x118ee040, flags=MBOX_SYNC_UNDIRTY) at mbox-sync.c:2022 #15 0x0000000010b28c9e in mbox_storage_sync_init (box=0x118ee040, flags=65) at mbox-sync.c:2071 #16 0x0000000010acc280 in mailbox_sync_init (box=0x118ee040, flags=65) at mail-storage.c:1740 #17 0x0000000010acb45d in mailbox_sync (box=0x118ee040, flags=65) at mail-storage.c:1788 #18 0x0000000000418cf5 in select_open (ctx=0x1184a1a8, mailbox=0x11816f50 "old/Example/INBOX.gz", readonly=false) at cmd-select.c:303 #19 0x0000000000418937 in cmd_select_full (cmd=0x1184a040, readonly=false) at cmd-select.c:426 #20 0x00000000004190f7 in cmd_select (cmd=0x1184a040) at cmd-select.c:435 #21 0x0000000000423b00 in command_exec (cmd=0x1184a040) at imap-commands.c:181 #22 0x00000000004220c0 in client_command_input (cmd=0x1184a040) at imap-client.c:986 -- Best Regards, Anton Yuzhaninov

1 0

Revision-proof archiving
by Paul Atreides 03 Feb '17

03 Feb '17

Hi, I am interested in the "Dovecot Email Archive" solution. Does anyone know if it is suitable revision-proof archiving? Is it available for smaller companies? I tried to contact people at dovecot.fi but I haven’t gotten any response yet. Thanks Regards,

2 1

dsync backup public namespace - how?
by Tobias Kirchhofer 03 Feb '17

03 Feb '17

Hello, We just celebrated the launch of our new mailserver setup (Dovecot and Postfix). Really nice! Now we want to change our quickfix backup with rsync to dsync. For mailder backup of users this was an easy task: dsync -v -f -u "${user}" backup "maildir:${destination}" (local file path destination) We use many public folder with ACL and now we are wondering how we can backup these folder in a similar manner: a) dsync -u doveadm(a)domain.com backup -n Namespacename "maildir:/var/vmail-backup/backup/public" or b) dsync -v -u doveadm(a)domain.com -N backup "maildir:${destination} But this is not working. a) does nothing, no error b) Error message: doveadm(doveadm(a)domain.com): Fatal: -N parameter requires syncing with remote host Any ideas? # dovecot --version 2.2.13 -- Tobias Kirchhofer tobias(a)kirchhofer.net

1 0

Dovecot auth-worker error after cram-md5 auth
by Poliman - Serwis 03 Feb '17

03 Feb '17

I set up cram-md5 using this tutorial https://wiki2.dovecot.org/HowTo/CRAM-MD5 in /etc/dovecot/dovecot.conf in passdb code block: listen = *,[::] protocols = imap pop3 #auth_mechanisms = plain login cram-md5 auth_mechanisms = cram-md5 plain login #dodana nizej linia ssl = required disable_plaintext_auth = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_privileged_group = vmail postmaster_address = postmaster(a)vps342401.ovh.net ssl_cert = </etc/postfix/smtpd.cert ssl_key = </etc/postfix/smtpd.key ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384[image: :D]HE-RSA-AES128-GCM-SHA256[image: :D]HE-DSS-AES$ ssl_prefer_server_ciphers = yes ssl_dh_parameters_length = 2048 mail_max_userip_connections = 100 passdb { # args = /etc/dovecot/dovecot-sql.conf # driver = sql driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } Of course I created cram-md5.pwd file. All mails go out and come nicely. But after I want to do default settings by commented out these two lines: driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd and uncomment # args = /etc/dovecot/dovecot-sql.conf # driver = sql I can't send emails - I use Thunderbird - get error "logging on server mail.example.com not work out". Error in logs: dovecot: auth-worker(22698): Error: Auth worker sees different passdbs/userdbs than auth server. dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF Is it possible that hashed password from cram-md5.pwd file was written to database (if yes then where - I have ISPconfig)? I wasn't change any userdb {} block and this second userdb block has this same lines like default settings in passdb block. -- *Pozdrawiam / Best Regards* *Piotr Bracha* *tel. 534 555 877* *serwis(a)poliman.pl <serwis(a)poliman.pl>*

4 25

Dovecot dsync 'ssl_client_ca'
by Thierry 03 Feb '17

03 Feb '17

Hello, Still working with my dsync pb. I have done a clone (vmware) of my email server. Today I have two strictly identical emails servers (server1 (main) and server2 (bck) (except IP, hostname and mail_replica). The ssl config on my both server: ssl_protocols = !SSLv2 !SSLv3 ssl = required verbose_ssl = no ssl_key = </etc/ssl/private/private.key ssl_cert = </etc/ssl/certs/key.crt ssl_ca = </etc/ssl/certs/GandiStandardSSLCA2.pem This config is working for my email client and my email web interface ... Are they on the right order ? mail_replica = tcps:server1@domain.ltd and tcps:server2@domain.ltd There is trafic on my iptables rules on my both servers: 60 3600 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:4711 My error message from server1 (main server): Feb 03 08:38:08 doveadm(user1(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user2(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user3(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Feb 03 08:42:35 doveadm(user4(a)domain.ltd): Error: sync: Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) No logs from server2 Any ideas ? Thx for your support -- Cordialement, Thierry e-mail : lenaigst(a)maelenn.org PGP Key: 0xB7E3B9CD

3 4

Re: Dovecot performance and proxy loops with IPv6
by Daniel Betz 03 Feb '17

03 Feb '17

Ok, got it. change imap-login and pop-login to these like showed in dovocot wiki for high-performance login mode. service imap-login { chroot = login service_count = 0 client_limit = 600 process_limit = 100 process_min_avail = 16 } service pop3-login { chroot = login service_count = 0 client_limit = 600 process_limit = 100 process_min_avail = 16 }

1 0

postfix/smtpd[725]: fatal: no SASL authentication mechanisms
by Poliman - Serwis 03 Feb '17

03 Feb '17

I haven't doveadm logs in /var/log/. Are they default in another place or maybe should I turn on something? My config (default passdb block and auth_mechanisms, nothing more changed): root@vps342401:/etc/dovecot# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_max_userip_connections = 100 mail_plugins = " quota" mail_privileged_group = vmail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = /var/vmail/%d/%n/.sieve sieve_max_redirects = 25 } postmaster_address = postmaster(a)vps342401.ovh.net protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/postfix/smtpd.cert ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:EC DHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDH E-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS- AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE- ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE- RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128- SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA- AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128- GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256: AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:! eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3- SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/postfix/smtpd.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = webmaster@localhost } protocol lmtp { mail_plugins = quota sieve postmaster_address = webmaster@localhost } And my logs: Error from mail.err: Feb 1 09:50:01 vps342401 postfix/smtpd[699]: fatal: no SASL authentication mechanisms Feb 1 09:51:02 vps342401 postfix/smtpd[724]: fatal: no SASL authentication mechanisms Feb 1 09:51:02 vps342401 postfix/smtpd[725]: fatal: no SASL authentication mechanisms Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: fatal: no SASL authentication mechanisms Error from syslog: Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: connect from host9323131.internet.3s.com[12.34.45.56] Feb 1 09:52:21 vps342401 postfix/smtps/smtpd[773]: fatal: no SASL authentication mechanisms Feb 1 09:52:22 vps342401 postfix/master[29133]: warning: process /usr/lib/postfix/smtpd pid 773 exit status 1 Feb 1 09:52:22 vps342401 postfix/master[29133]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling Feb 1 09:53:01 vps342401 CRON[777]: (root) CMD (/usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; do ne) Feb 1 09:53:01 vps342401 CRON[778]: (root) CMD (/usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done ) Is there any strange thing in these config lines? -- *Pozdrawiam / Best Regards* *Piotr Bracha* *tel. 534 555 877* *serwis(a)poliman.pl <serwis(a)poliman.pl>*

1 0

Dovecot, Postfix, and SASL AUTH EXTERNAL
by Matt Horan 03 Feb '17

03 Feb '17

Hey folks, I've been using the ever popular Dovecot and Postfix combo for years. A while back I also introduced mutual TLS for mail clients to Dovecot and Postfix. I achieved this by a custom checkpassword script and SASL AUTH EXTERNAL for IMAP. This all worked great with clients like Thunderbird, which can be configured to use mutual TLS and SASL EXTERNAL for IMAP, and mutual TLS with no additional authentication for SMTP. However, I found that other mail clients, in particular K-9 mail on Android, [1] are not compatible with this configuration. I've been patching K-9 mail to work around this issue for some time now. If I configure K-9 to behave like Thunderbird when sending messages via SMTP, all is well. However, there's been some activity on an issue [2] which suggests some changes may be upcoming which will be incompatible with my patch. Without my patch, K-9 tries to auth with Postfix via AUTH EXTERNAL after presenting its client certificate. Despite configuring Postfix to prefer certificates before SASL, Postfix forwards the authentication request to Dovecot, which rejects it without even trying my checkpassword script. With my patch, K-9 simply initiates an SMTP connection without any additional authentication when mutual TLS is used. This behavior is similar to Thunderbird. The K-9 maintainers do not seem interested in merging this behavior into mainline. I can't seem to get Postfix to ignore the SASL failures in the case of successful mutual TLS. I want to use SASL authentication as a fallback from untrusted clients, where I use a combination of password and one time code. Even if Dovecot did not reject the AUTH EXTERNAL request from Postfix, I'm not sure how it could determine whether a valid client certificate were presented to Postfix, unless some additional information were passed along in the SASL request. I'd love to hear any thoughts from the community on how to move forward here. Should I pressure the K-9 maintainers to behave more like other clients? Would it make sense to extend the SASL interface in some way such that Dovecot could handle an EXTERNAL request from Postfix? Or should Postfix simply ignore SASL EXTERNAL based on the configured authentication mechanism order? Thanks, Matt [1] https://github.com/k9mail/k-9/ [2] https://github.com/k9mail/k-9/issues/793 -- Matt Horan matt(a)matthoran.com http://matthoran.com/

1 0

Moving to new password scheme
by ＠lbutlr 02 Feb '17

02 Feb '17

dovecot is setup on a system with MD5-CRYPT password scheme for all users, and I would like to update this to something that is secure, probably SSHA256-CRYPT, but I want to do this seamlessly without the users having to jump through any hoops. The users are in mySQL (managed via postfixadmin) and the mailbox record simply stores the hash in the password field. Users access their accounts though IMAP MUAs or Roundcube. How would I setup my system so that if a user logs in and still has a $1$ password (MD5-CRYPT) their password will be encoded to the new SHCEME and then the SQL row updated with the $5$ password instead? Something where they are redirected after authentication to a page that forces them to renter their password (or choose a new one) is acceptable. And, while I am here, is it worthwhile to set the -r flag to a large number (like something over 100,000 which sets takes about 0.25 seconds to do on my machine)? -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

4 8

quota-status returns quota_status_success when email would put user over quota
by Kristian Pedersen 02 Feb '17

02 Feb '17

Hi list, I am attempting to get quota-status service working, so I can deny email at the initial smtp dialog instead of generating bounces with lda. I can't seem to get quota-status to return quota_status_overquota, even when an email would put an account over quota. Quota in general works fine: Jan 22 06:39:23 mail dovecot: lda(xx(a)yy.dk): msgid=<25c5bdb20d58fc4f649f716a947613dc(a)zz.org>: save failed to INBOX: Quota exceeded (mailbox for user is full) Jan 22 06:39:23 mail dovecot: lda(xx(a)yy.dk): msgid=<25c5bdb20d58fc4f649f716a947613dc(a)zz.org>: rejected: Quota exceeded (mailbox for user is full) The system is a pretty standard debian 8 box running virtually on a kvm/ovirt cluster: root@mail:~# dpkg --list | grep dovec ii dovecot-core 1:2.2.13-12~deb8u1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.13-12~deb8u1 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 1:2.2.13-12~deb8u1 amd64 secure POP3/IMAP server - LMTP server ii dovecot-mysql 1:2.2.13-12~deb8u1 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.13-12~deb8u1 amd64 secure POP3/IMAP server - POP3 daemon Mail storage is local XFS partitions as far as the dovecot server knows. Behind the scene its actually raw disk images on NFS shares from a SAN towards the kvm/ovirt cluster. I test by using nc towards the quota-status instance: root@mail:~# printf "recipient=kptest(a)asom-net.dk\nsize=1000000000\n\n" | nc -q1 localhost 12340 action=DUNNO User has 500MB quota: mysql> SELECT CONCAT('/data/vmail/',CONCAT(SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1))) AS home, 110 AS uid, 110 AS gid, CONCAT('*:storage=',mailquota,'M') AS quota_rule FROM virtual_users WHERE email='kptest(a)asom-net.dk'; +--------------------------------+-----+-----+----------------+ | home | uid | gid | quota_rule | +--------------------------------+-----+-----+----------------+ | /data/vmail/asom-net.dk/kptest | 110 | 110 | *:storage=500M | +--------------------------------+-----+-----+----------------+ 1 row in set (0.00 sec) maildirsize seems ok: root@mail:~# cat /data/vmail/asom-net.dk/kptest/maildirsize 524288000S 685 1 690 1 Quota-status will return unknown user if that is the case: root@mail:~# printf "recipient=kptest2(a)asom-net.dk\nsize=1000000000\n\n" | nc -q1 localhost 12340 action=551 5.5.1 User not found Log file (with mail_debug = yes): Jan 12 16:52:21 mail dovecot: quota-status: Debug: auth input: kptest(a)asom-net.dk home=/data/vmail/asom-net.dk/kptest uid=110 gid=110 quota_rule=*:storage=500M Jan 12 16:52:21 mail dovecot: quota-status: Debug: Added userdb setting: plugin/quota_rule=*:storage=500M Jan 12 16:52:21 mail dovecot: quota-status(kptest(a)asom-net.dk): Debug: Effective uid=110, gid=110, home=/data/vmail/asom-net.dk/kptest Jan 12 16:52:21 mail dovecot: quota-status(kptest(a)asom-net.dk): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/data/vmail/asom-net.dk/kptest/ Jan 12 16:52:21 mail dovecot: quota-status(kptest(a)asom-net.dk): Debug: maildir++: root=/data/vmail/asom-net.dk/kptest, index=, indexpvt=, control=, inbox=/data/vmail/asom-net.dk/kptest, alt= dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ext4 auth_default_realm = vejen-net.dk auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no first_valid_uid = 110 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = maildir:/data/vmail/%d/%n/ mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/local-sql.conf driver = sql } plugin { quota = maildir:User quota quota_rule = *:storage=200M quota_status_nouser = 551 5.5.1 User not found quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1024 process_limit = 256 process_min_avail = 8 service_count = 0 vsz_limit = 512 M } service imap { process_limit = 10240 } service pop3-login { client_limit = 512 process_limit = 256 process_min_avail = 8 service_count = 0 vsz_limit = 512 M } service pop3 { process_limit = 10240 } service quota-status { client_limit = 1 executable = /usr/lib/dovecot/quota-status -p postfix inet_listener { port = 12340 } } ssl_cert = </etc/letsencrypt/live/mail.asom-net.dk/fullchain.pem ssl_key = </etc/letsencrypt/live/mail.asom-net.dk/privkey.pem ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/local-sql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota postmaster_address = postmaster(a)asom-net.dk } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } local-sql.conf: driver = mysql connect = host=xyz dbname=xyz user=xyz password=xyz default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; user_query = SELECT CONCAT('/data/vmail/',CONCAT(SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1))) AS home, 110 AS uid, 110 AS gid, CONCAT('*:storage=',mailquota,'M') AS quota_rule FROM virtual_users WHERE email='%u'; If I do a strace on the quota-status PID, it seems to do a stat on the directory and then give up? Not sure Im interpreting it correct (only including the last few lines): ... lseek(14, 833, SEEK_SET) = 833 munmap(0x7f165d32a000, 833) = 0 close(14) = 0 geteuid() = 0 getegid() = 110 getgid() = 110 getegid() = 110 setgroups(1, [110]) = 0 setresuid(-1, 110, -1) = 0 prctl(PR_SET_DUMPABLE, 1) = 0 stat("/data/vmail/asom-net.dk/kptest", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 prctl(PR_SET_DUMPABLE, 1) = 0 setsockopt(12, SOL_TCP, TCP_CORK, [1], 4) = 0 write(12, "action=DUNNO\n\n", 14) = 14 setsockopt(12, SOL_TCP, TCP_CORK, [0], 4) = 0 epoll_wait(11, {{EPOLLIN, {u32=1593554016, u64=139734059562080}}}, 5, 59999) = 1 read(12, "", 8146) = 0 epoll_ctl(11, EPOLL_CTL_DEL, 12, 7fff0be817a0) = 0 close(12) = 0 epoll_wait(11, {}, 5, 1000) = 0 write(5, "\35q\1\0007\10\0\0\1\0\0\0", 12) = 12 epoll_wait(11, ... It seems like sort of permission issue? root@mail:~# su - vmail No directory, logging in with HOME=/ $ id -a uid=110(vmail) gid=110(vmail) groups=110(vmail) $ cat /data/vmail/asom-net.dk/kptest/maildirsize 524288000S 685 1 690 1 /data/vmail/asom-net.dk is actually a symlink, maybe that could be of importance?: root@mail:~# ls -ld /data/vmail/asom-net.dk lrwxrwxrwx 1 root root 19 Jan 9 11:18 /data/vmail/asom-net.dk -> ../mnt1/asom-net.dk root@mail:~# ls -ld /data/mnt1/asom-net.dk/ drwxrwx--- 45 vmail vmail 4096 Dec 15 10:54 /data/mnt1/asom-net.dk/ root@mail:~# ls -ld /data/mnt1/asom-net.dk/kptest/ drwx------ 9 vmail vmail 4096 Jan 23 08:55 /data/mnt1/asom-net.dk/kptest/ root@mail:~# ls -ld /data/mnt1/asom-net.dk/kptest/maildirsize -rw------- 1 vmail vmail 23 Jan 12 16:50 /data/mnt1/asom-net.dk/kptest/maildirsize Anyone have any idea what might be wrong here? Regards, -- Kristian Pedersen ASOM-Net Systemadministrator www.asom-net.dk Telefon: 44 400 970

3 5

Dovecot performance and proxy loops with IPv6
by Daniel Betz 02 Feb '17

02 Feb '17

Hello list, i run here an large mailsetup with some million mailboxes and got strange performance problems, cause i think i have overseen or forgotten an simple setting. Here are some details: 21 CentOS 7 Servers with dovecot 2.2.25 and ldap userdb/passdb via socket behind an hardware loadbalancer. The storage behind is an ISCSI Storage with 4 10Gbit/s multipath paths, splitted up to 10 TB volumes for each server with LVM and xfs filesystem. No Cluster FS Each server has about 60.000 to 75.000 mailboxes on it. mailboxes can have up to 10Gbyte space. The Log says this sometimes and complete random: Feb 1 10:42:49 server1 dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Feb 1 10:42:50 server1 dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Feb 1 10:42:50 server1 dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Feb 1 10:42:50 server1 dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Feb 1 10:42:50 server1 dovecot: imap-login: Error: net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Feb 1 10:42:50 server1 dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable Sure i have read the SocketUnavailabe wiki page and changed some settings, but the errors are not gone. Could you please look over my dovecot config and give me some tips or hints what to change. The next this is, when adding IPv6 via DNS to the hosts and login with IPv6 i will become an proxy loop. Settings in nameserver: server1.domain.com IN A 123.123.123.123 server1.domain.com IN AAAA 2001:123::1 The host entry comes from the ldap and says: mailHost: server1.domain.com Imap Login with IPv6 to server1.domain.com tries to proxy from server1.domain.com ( IPv6 ) to server1.domain.com ( IPv6 ) and loops then. I have removed the IPv6 AAAA entries in the dns to stop this loops. Sorry, but i have no logs for this anymore. Thanks in advise, Daniel And here system configs and dovecot configs: sysctl: fs.inotify.max_user_instances = 65535 fs.inotify.max_user_watches = 16384 systemd startup with ulimit settings: [Unit] Description=Dovecot Mailservice IMAP/POP [Service] Type=simple LimitCORE=0 LimitNPROC=5000000 LimitNOFILE=65535 LimitSTACK=81920 LimitDATA=infinity LimitMEMLOCK=infinity LimitRSS=infinity LimitAS=infinity ExecStart=/usr/local/dovecot2/sbin/dovecot -F -c /usr/local/dovecot2/etc/dovecot/dovecot.conf [Install] WantedBy=multi-user.target dovecot-ldap.conf: uris = ldapi://%2Fvar%2Frun%2Fldapi dn = cn=xxxxxxx,o=domain,c=com dnpass = xxxxxxxxxxxxx auth_bind = no ldap_version = 3 base = o=domain,c=com user_attrs = mail=user,mailMessageStore=home,\ mailQuota=quota_rule=*:storage=%$ iterate_filter= (|(mailHost=server1.domain.com)(mailHost=popserver1.domain.com)) user_filter = (&(accountstatus=active)(|(uid=%u)(mail=%u))) pass_attrs = mail=user,userPassword=password,=proxy_maybe=y,mailHost=host,=destuser=%u[%r] pass_filter = (&(accountstatus=active)(|(uid=%u)(mail=%u))) dovecot.conf: # 2.2.25 (7be1766): /usr/local/dovecot2/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.36.3.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_cache_negative_ttl = 1 mins auth_cache_size = 64 M auth_cache_ttl = 2 hours auth_mechanisms = plain login auth_username_chars = auth_verbose = yes base_dir = /var/run/dovecot/ debug_log_path = /dev/null default_login_user = dovecot disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 1001 first_valid_uid = 1001 info_log_path = /dev/stderr lda_mailbox_autocreate = yes lda_original_recipient_header = X-Envelope-To log_path = /dev/stderr log_timestamp = login_log_format_elements = user=[%u] method=%m rip=%r lip=%l %c mail_gid = 1001 mail_location = mdbox:~:INDEX=%h/INDEX mail_plugins = "notify replication stats" mail_uid = 1001 mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_warning = storage=85%% quota-warning 85 %u stats_refresh = 30 secs stats_track_cmds = yes } replication_max_conns = 30 sendmail_path = /usr/local/exim/bin/exim service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = popuser } unix_listener replication-notify { mode = 0666 user = popuser } } service anvil { client_limit = 60000 } service auth { client_limit = 60000 unix_listener auth-userdb { mode = 0666 user = popuser } unix_listener auth { mode = 0666 user = popuser } } service config { unix_listener config { user = popuser } } service dict { unix_listener dict { mode = 0666 user = popuser } } service doveadm { inet_listener { port = 12345 } user = popuser } service imap-login { chroot = login process_limit = 60000 process_min_avail = 16 } service imap { executable = /usr/local/dovecot2/libexec/dovecot/imap process_limit = 250000 } service ipc { client_limit = 60000 unix_listener ipc { mode = 0650 user = dovecot } unix_listener login/ipc-proxy { mode = 0650 user = dovecot } } service lmtp { unix_listener lmtp { mode = 0666 user = popuser } } service pop3-login { chroot = login process_limit = 60000 process_min_avail = 16 } service pop3 { executable = /usr/local/dovecot2/libexec/dovecot/pop3 process_limit = 250000 } service replicator { unix_listener replicator-doveadm { mode = 0600 user = popuser } } service stats { fifo_listener stats-mail { mode = 0600 user = popuser } } ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key ssl_protocols = TLSv1.2 TLSv1.1 TLSv1 !SSLv3 !SSLv2 userdb { args = /usr/local/dovecot2/etc/dovecot/dovecot-ldap.conf driver = ldap } verbose_proctitle = yes protocol doveadm { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota } protocol lda { info_log_path = /var/log/dovecot-lda log_path = /var/log/dovecot-lda log_timestamp = "%b %d %H:%M:%S " mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota postmaster_address = %u } protocol imap { imap_client_workarounds = mail_max_userip_connections = 100 mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota imap_quota stats imap_stats } protocol pop3 { mail_plugin_dir = /usr/local/dovecot2/lib/dovecot/ mail_plugins = quota stats pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes pop3_fast_size_lookups = yes pop3_reuse_xuidl = no pop3_uidl_format = %g } local xxx.xxx.xxx.54 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxx.xxx.xxx.54 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxx.xxx.xxx.55 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxx.xxx.xxx.55 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxx.xxx.xxx.56 { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xxx.xxx.xxx.56 { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xxxx:xxxx::fa { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxxx:xxxx::fa { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert1.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert1.key } } local xxxx:xxxx::fb { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxxx:xxxx::fb { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert2.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert2.key } } local xxxx:xxxx::fc { protocol imap { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } } local xxxx:xxxx::fc { protocol pop3 { ssl_cert = </usr/local/dovecot2/etc/dovecot/certs/cert3.crt ssl_key = </usr/local/dovecot2/etc/dovecot/certs/cert3.key } }

1 0

SNI with mixed certs
by Ruga 02 Feb '17

02 Feb '17

Dovecot SNI is failing hard today. Server with n domains, each with a startssl certificate of its own, all certificates expired this morning. Decision: move to Letsencrypt. Firsr certificate issued and installed. Other domains in the pipeline. Dovecot server rebooted. Expected result: one domain returning the new cert, and the n-1 domains returning the expiration notification. Actual result: the domain with LE is returning startssl expired notifications. Manual check of the key and pem files is OK...

1 0

Doveadm option for a non-wildcard single-user with userdb
by Ivan Zahariev 02 Feb '17

02 Feb '17

Hello, Most "doveadm" commands accept "[-A|-u user|-F file]" for user selection, or the environment "USER". I'm testing with "doveadm quota recalc". The problem is that there is no way to ask "doveadm" to work in (1) single-user mode with (2) no wildcard support, and at the same time to (3) make a lookup in "userdb", in order to get the user's specific configuration. We have mailboxes which contain "?" and "*" symbols, and we can't work with them using "doveadm" now. * If we use "-A", this works with all users. Not our case at all. * If we use "-F" and provide just one user in the file, this works for a single user + lookup in "userdb", does not interpret wildcard, but "doveadm" works in a "users list" mode and the output is different. What's more problematic is that errors for an mbox do not end up in "doveadm" exiting with a non-zero exit code. * If we use "-u", this works for a single user + lookup in "userdb", but interprets wildcards. Does not work for mailboxes which contain "?" and "*". * If we use the USER environment, this works for a single users and does not interpret wildcards but does not do a lookup in "userdb". Should we add another user-selection argument, for example "-U", which (1) selects a single-user like "-u", does a "userdb" lookup like "-u" does, but does not interpret wildcards unlike "-u" ? Best regards. --Ivan

1 0

Restoring a deleted imap folder from backup to user Maildir
by Kepa Lyman 02 Feb '17

02 Feb '17

Hi, A user accidentally delete a folder from their Maildir (probably while using Thunderbird). The folder was at Archives/Sent/2015 (/.Archives.Sent.2015 in the Maildir format). I attempted to copy the folder from a tar backup into the Maildir folder but the new folder does not show up in Thunderbird or in the Subscribe option. I also copied the .Archives.Sent. folder as well. A "Sent" folder shows up after this in Thunderbird's Subscribe menu but not the 2015 subfolder. Is there some other additional step(s) to undertake when moving Maildir folders around so they show up in Dovecot (or Thunderbird- though I did try deleting Thunderbird's local mail tmp folder). Re: this message about SELinux on CentOS, SELinux is set to permissive: https://dovecot.org/list/dovecot/2009-January/036257.html Thanks! Kepa

2 1

what do you think about that?
by dovecot 02 Feb '17

02 Feb '17

Dear! I just wanted to show you my last article and to ask your opinion about it, please read it here http://gianluigi.bigshowonline.net/0607 dovecot

1 0

dovecot 2.2.27 welcome plugins script
by Carlos R Laguna 01 Feb '17

01 Feb '17

Hello everyone, I am trying to send a mail to newly autocreated users, using the welcome plugins, however, i am get unable to pipe user information correctly to the script, acording to the wiki the scripts are called just as the quota warnig scripts. Also, every time that a try something new i have created a new user...... is a pain. what can i do to test this without to create a new user after any little change? # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.0-59-generic x86_64 Ubuntu 14.04.5 LTS nfs auth_mechanisms = plain login mail_debug = yes mail_gid = vmail mail_location = maildir:/var/nfsvmail/%d/%Ln/ mail_plugins = " quota welcome" mail_uid = vmail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=2M quota_rule2 = Trash:storage=+1M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 El buzón esta lleno quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u welcome_script = welcome %u welcome_wait = yes } postmaster_address = postmaster(a)cubava.cu protocols = " imap lmtp pop3" inet_listener pop3s { port = 0 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service welcome { executable = script /usr/local/bin/welcome.sh unix_listener welcome { user = vmail } user = dovecot } ssl_cert = </etc/ssl/certs/mailcubava.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_plugins = " quota welcome imap_quota" } -rwxr-xr-x 1 dovecot vmail 397 Jan 31 16:11 welcome.sh #!/bin/sh USER=$1 cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER From: postmaster(a)example.com Subject: Welcome Message EOF -- Carlos R Laguna Mendoza Esp. Principal NDC TINORED Joven Club de Computación y Electrónica Tel: 52793189, 7863-3174, 7868-4230

1 0

Vacation Sending To Root
by Shaun Forsyth 31 Jan '17

31 Jan '17

Dovecot Version 2.0.9 I am having an issue where all vacation messages are being sent to root. Is any one able to advise. Dovecot Log Shows :- Sieve: msgid=< CAMD5TViw0sSigGm8JY5WOv0ROs1UdCJFnvb9vo-RzcNN74E92Q(a)mail.xxxxxx.com>: sent vacation response to <root> The emails are handed off to dovecot from sendmail using procmail :0 w | $DELIVER The variable $DELIVER is set as DELIVER="/usr/libexec/dovecot/deliver" I do have DROPPRIVS=YES in procmail, however I don't think deliver works without this. Any advice would greatly help. Shaun

2 2

mail_location in userdb inconsistent with imap and pigeonhole
by Ladislav Laska 31 Jan '17

31 Jan '17

Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to do an override via userdb. I already have a passwd-file authdb, so I uncommented those few lines in configuration, and added this to my passwd-file: krakonos:{SHA256}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=:1000:100::/home/krakonos:/bin/bash:userdb_mail=maildir:/home/krakonos/Mail Now, I'm not really sure why it has to be prefixed with userdb_, but the example in docs has it, and it seems to work. I've attached the relevant part of a logfile, with some debugging enabled, but in short: Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Added userdb setting: mail=maildir:/home/krakonos/Mail [...] Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: maildir++: root=/home/krakonos/Mail, index=, indexpvt=, control=, inbox=/home/krakonos/Mail, alt= [...] Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox I'm confused why the last line chooses my old mbox over the new location. I'm even more confused by the fact the IMAP works fine, and as I connect from mutt over imap, I can see empty mailboxes (the ~/Mail has only the basic cur/new/tmp structure). However, pigeonhole delivers into the .mbox, and not only if it's for INBOX, but also for spam and others. I read somewhere in the docs that the order is first try userdb, then mail_location and namespaces override the rest. This might be the problem, as I have: mail_location = mbox:~/.mbox 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 = } Due to inbox=yes this would explain why inbox is using the default path in mail_location. But why even the spam is delivered into the old mbox? And how do I solve the problem anyway, should I just remove the namespace? Anyway, it doesn't explain why the IMAP part and pigeonhole apply different rules and show me different inboxes, which is probably a bug. Thanks! ----------------------------------------------------------------------- Here is the rest of my configuration for reference, the log is attached: ----------------------------------------------------------------------- # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.26-gentoo x86_64 Gentoo Base System release 2.2 auth_username_format = %n hostname = ibex.krakonos.org login_greeting = Dovecot(a)krakonos.org ready. mail_debug = yes mail_location = mbox:~/.mbox mbox_read_locks = dotlock fcntl 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 = * driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = sieve-execute sieve_extensions = +vnd.dovecot.filter +editheader sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_filter_socket_dir = sieve-filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)krakonos.org protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { mail_plugins = sieve } -- S pozdravem Ladislav "Krakonoš" Láska http://www.krakonos.org/

2 2