- dovecot - dovecot.org

Re: Mailbox problem on centos O/S after some "fiddling"
by Joseph Tam 21 Jan '17

21 Jan '17

> I do not understand why dovecot creates this folder as we ONLY ever use pop3 > (currently with plain text auth but going to secure when this sorted) > for mail and also why when it writes the blank folder it "owns" it with the > user accessing it (also the /var/mail/new folder takes the same owner) I think maybe those mailboxes were created because you've mapped all user home directories to the same folder (/var/mail), and thus, the first user to log in created files that subsequent users could not access. > mail_location = mbox:/var/mail/:INBOX=/var/mail/%u See this for the POP3 scenario you want: http://wiki.dovecot.org/MailLocation/mbox (Section: Only /var/mail mboxes) Don't need these > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } Joseph Tam <jtam.home(a)gmail.com>

1 0

Deleting a mailbox recursively
by Malte Schmidt 20 Jan '17

20 Jan '17

This topic was already discussed on this mailinglist: https://www.dovecot.org/list/dovecot/2011-November/079491.html I am also looking for a nice and convenient way of recursively deleting a mailbox which uses the mdbox-Format. Since then - was there any progress?

3 4

Replication between three servers
by James Pharaoh 19 Jan '17

19 Jan '17

Hi, Dovecot version: 2.2.27 I'm a little unsure if I have set up my replication correctly, and also how to set up replication on three servers, if this is possible. My replication works, with exactly the same configuration on both servers, except that the mail_replica contains the other server name in each case, of course. This seems to work fine. As I understand it, both need to be set up as a client and a server, since I have mail arriving on both. Is this a correct and supported configuration? I believe then I should be able to get three-way replication working, by pointing the three servers at each other in a circle. I am hoping this will cause a mail arriving at server 1 to be sent to server 2, which will then send it to server 3. Server 3 will attempt to send it back to server 1 which will already have it, and so this will terminate the loop. This is obviously going to create a bit of extra load, but I don't want to try it without some advice, and I'm not sure if the replication will be triggered properly by an email which is itself arriving via replication. Reading the description of the components, I think it should, since the aggregator service shouldn't care how an email has arrived, since it is simply reading the log, right? If a server fails, or needs to be taken out manually, I'll obviously need to reconfigure the loop, essentially taking it back to a standard two-server configuration. Similarly, I should be able to add a fourth server, and so on, if I wanted. I'm planning to distribute incoming emails over all servers, so that these will arrive and be stored on a working server during an outage without any reconfiguration, and to use something like nginx as a proxy to send each user to a specific server, to distribute the client load. Thanks in advance, James

1 0

Remove empty milder folders
by ＠lbutlr 18 Jan '17

18 Jan '17

Not sure if anyone will find this useful, but this is how I deleted a bunch (several hundred) of empty mail folders from a user account: # doveadm mailbox status -u “user(a)example.com" messages "*" ALL | grep "=0" | awk -F= '{print $1}' | awk '{print "rm -rf ."$1}' > list then I looked over list just to be sure it wasn’t mucked up and in the users root maildir: # sh < list and done. I probably could do some research on how to combine those two awk pipes but this worked, and it was fast. -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.

2 2

Dynamic autoexpunge for IMAP folders
by Thorsten Hater 18 Jan '17

18 Jan '17

Dear all, is there a way to allow users to set up something like autoexpunge on an individual IMAP folder basis? The idea I implemented does not seem to work, namely returning namespace/inbox/mailbox/Bla/autoexpunge=6h from a userdb, which results in Debug: Unknown userdb setting: plugin/namespace/inbox/mailbox/Bla/autoexpunge=6h >From older questions on the mailing list I gather that the mailbox Bla needs to be set up in the config before I can override its fields. If there is a way around this, I would gladly use this. Another solution that comes to mind would be to use a table-driven cron job, but I would prefer the cleanup to be triggered at delivering and/or moving mail. Best regards, Thorsten

3 8

Plugin "mail_crypt" does not work
by Evgeniy Korneechev 18 Jan '17

18 Jan '17

Hi, i have a problem. I sent test e-mail. It is in folder "Sent", but it was not delivered (folder "Inbox" is empty). /var/log/dovecot: ......... lda(mail(a)example.com): Error: User initialization failed: mail_crypt_plugin: mail_crypt_global_public_key: Couldn't parse public key: Unknown key format ......... Try RSA and EC: https://wiki2.dovecot.org/Plugins/MailCrypt#RSA_key https://wiki2.dovecot.org/Plugins/MailCrypt#EC_key Why "Unknown key format"? RSA pubkey: -----BEGIN PUBLIC KEY----- MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC4hfgRDlMJtN9rcV2VGa8gOF1g xiXHwokRkKmKfr64ZbqAhXzLzP8fSLo8ZEtRzfS3f/EyLRvYL9LHxlxYuSnq2LTW lbvSj8jcg3ucpA431Pbnq/OVI8WsXhXhZdipGcBDyzWHZw5Dp3I/am+FB96VlfPW maHO/oKGphXXhXSOXwIDAQAB -----END PUBLIC KEY----- EC pubkey: -----BEGIN PUBLIC KEY----- MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEw96p6hvv/BJi9njHyXq05ZrKA3RR BNFOslljkgv6YUb4de1pln6hTUN69CjMBEB5P3YI7KP8hooozwM8iN/wLQ== -----END PUBLIC KEY----- ------------------------------------------------ # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.39-std-def-alt0.M80P.1 x86_64 ALT 8.1 Server auth_debug = yes auth_debug_passwords = yes auth_default_realm = example.com auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot disable_plaintext_auth = no first_valid_gid = 502 first_valid_uid = 502 last_valid_gid = 502 last_valid_uid = 502 log_path = /var/log/dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_access_groups = vmail mail_debug = yes mail_gid = 502 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = mail_crypt mail_privileged_group = vmail mail_uid = 502 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 { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_crypt_curve = prime256v1 mail_crypt_global_private_key = </etc/dovecot/eckey/ecprivkey.pem mail_crypt_global_public_key = </etc/dovecot/eckey/ecpubkey.pem mail_crypt_save_version = 2 recipient_delimiter = + sieve = /etc/dovecot/sieves/default.sieve sieve_default = /etc/dovecot/sieves/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 8 } protocols = imap pop3 lmtp sieve service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service imap { process_limit = 1024 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } ssl_ca = /var/lib/ssl/cert.pem ssl_cert = </etc/dovecot/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-ldap-user.conf.ext driver = ldap } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = mail_crypt sieve } protocol lda { mail_plugins = mail_crypt sieve quota plugin { quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol imap { mail_plugins = mail_crypt autocreate quota imap_quota plugin { autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } -- WBR, BaseALT/ALTLinux Team

2 6

Reappearing emails
by Ron Cleven 17 Jan '17

17 Jan '17

We have been running Dovecot 2.2.10 with a pair of CentOS 7 boxes with replications for the past year. We have been quite happy with the performance and reliability. Recently we received a report from an Android IMAP user that emails that he deleted without reading would often reappear in his INBOX. At first I thought it might be some quirky incompatibility with his email client, but I found that I could easily reproduce it in Roundcube by dragging an unread email to Trash. I have been monitoring this forum fairly religiously and don't recall seeing any similar reports. I plan to capture the IMAP wire interactions, but before doing that, I thought I would submit this to the IMAP gods to see if anyone had heard of this and/or if there is some newer version that might resolve the problem. This particular customer contacted his email vendor and asked them to analyze the problem. The actual log data is gigantic, so I just pasted in the vendor's narrative below in case it helps. Otherwise, as I said, I will capture a similar interaction at the wire level and follow up here. Vendor's narrative: You had 8 messages in the Inbox, and moved two to Trash. The server notified the app on the push connection (for Inbox) that there are now 6 messages. By the time the app got around to catch up with that (it did the Trash folder first), the server said "oh wait, there are 8 messages, not 6" (in the Inbox), and so the app synced them in, just as reported. app selecting the Inbox, server saying there are 8 messages there app moving UID 729 and 730 to Trash (push) server saying Trash now has 34 messages (push) server saying two messages gone from Inbox, 6 left (push) 6 messages left in Inbox becoming 8 (push) and here they are (the two new ones) Thanks, Ron

3 3

Mail rescue from Dovecot Server
by Joakim Magnussen - MediaLabs AS 17 Jan '17

17 Jan '17

Hi all, I have a mail folder from Dovecot server. Screenshot: https://i.stack.imgur.com/11NHs.jpg Is there any way to import to Outlook, or otherwise convert to readable format? I could setup Dovecot on my own server if there is any point.

2 1

Correct settings for ssl protocols" and "ssl ciphers"
by Jerry 17 Jan '17

17 Jan '17

I have the following two settings in my "10-ssl.conf" file # SSL protocols to use ssl_protocols = !SSLv2 # SSL ciphers to use ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL I have seen different configurations while Googling. I am wondering what the consensus is for the best settings for these two items. What do the developers recommend? Thanks! -- Jerry

4 3

fts-solr: Returning 400 on searches; unescaped braces
by Michael Welsh Duggan 17 Jan '17

17 Jan '17

Using Debian, dovecot-solr 1:2.2.26.0-4, and solr-tomcat 3.6.2+dfsg-9, I am getting 400 errors when doing searches. Here is an example search query from dovecot that failed (captured with wireshark): Frame 23: 338 bytes on wire (2704 bits), 338 bytes captured (2704 bits) on interface 0 Linux cooked capture Internet Protocol Version 6, Src: ::1, Dst: ::1 Transmission Control Protocol, Src Port: 56860, Dst Port: 8080, Seq: 1, Ack: 1, Len: 250 Hypertext Transfer Protocol GET /solr/select?fl=uid,score&rows=2664&sort=uid+asc&q={!lucene+q.op%3dAND}(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i HTTP/1.1\r\n Host: localhost:8080\r\n Date: Mon, 19 Dec 2016 00:25:56 GMT\r\n Connection: Keep-Alive\r\n \r\n [Full request URI: http://localhost:8080/solr/select?fl=uid,score&rows=2664&sort=uid+asc&q={!l…] [HTTP request 1/1] [Response in frame: 25] Here is the same query from firefox, which succeeds: Frame 66: 646 bytes on wire (5168 bits), 646 bytes captured (5168 bits) on interface 0 Linux cooked capture Internet Protocol Version 6, Src: ::1, Dst: ::1 Transmission Control Protocol, Src Port: 56862, Dst Port: 8080, Seq: 1, Ack: 1, Len: 558 Hypertext Transfer Protocol GET /solr/select?fl=uid,score&rows=2664&sort=uid+asc&q=%7B!lucene+q.op%3DAND%7D(hdr:test+OR+body:test)&fq=%2Bbox:6d5de009f991854df726000012cf7b9c+%2Buser:md5i HTTP/1.1\r\n Host: localhost:8080\r\n Connection: keep-alive\r\n Cache-Control: max-age=0\r\n Upgrade-Insecure-Requests: 1\r\n User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36\r\n Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8\r\n DNT: 1\r\n Accept-Encoding: gzip, deflate, sdch, br\r\n Accept-Language: en-US,en;q=0.8\r\n \r\n [Full request URI: http://localhost:8080/solr/select?fl=uid,score&rows=2664&sort=uid+asc&q=%7B…] [HTTP request 1/1] [Response in frame: 86] The salient difference seems to be the encoding of the braces. Indeed in the tomcat 8 logs, I find the following which seems to corroborate my hypothesis: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986 at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:467) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:667) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:789) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1437) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Indeed the braces are listed in fts-backend-solr.c as part of solr_escape_chars, so don't know how the braces are making it through unencoded. -- Michael Welsh Duggan (md5i(a)md5i.com)

2 3