- dovecot - dovecot.org

[Dovecot] Using MailDir but local messages still save in mbox format
by Mike Edwards 30 Sep '13

30 Sep '13

I am using MailDir format for all my virtual users and it is working well. However, if email comes in to a unix system user, it delivers in Mbox format. This is mostly cron jobs that do this. Mail addressed to my virtual users goes to the MailDir locations just fine. None of these mailboxes have ever been created, they are just incorrect assumed addresses. There should NEVER be any email to username(a)my.host.name because everything is virtual. Does anyone know how to fix this? Here is my config. # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.18.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) auth_debug = yes auth_mechanisms = plain login cram-md5 ntlm auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no listen = * 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 mbox_write_locks = fcntl passdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { autocreate = Trash autocreate2 = Spam autocreate3 = Drafts autocreate4 = Sent autocreate5 = Archives autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Drafts autosubscribe4 = Sent autosubscrube5 = Archives sieve = ~/.dovecot.sieve sieve_before = /home/vmail/movespam.sieve sieve_dir = ~/sieve } 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 } } ssl_ca = /etc/pki/dovecot/ca/dovecot.pem ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem ssl_cipher_list = HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n driver = static } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = /home/vmail/dovecot-deliver.log mail_plugins = " sieve sieve" postmaster_address = postmaster(a)zeus.deltatechnicalservices.com } protocol lmtp { mail_plugins = " sieve" } protocol imap { mail_plugins = autocreate } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

4 9

[Dovecot] pop3-login problem
by Oleksii Krykun 30 Sep '13

30 Sep '13

Hi! I have dovecot-2.2.5 installed as part of postfix+dovecot+mysql+amavisd. My server has two NICs (Internet and local). /etc/resolv.conf point to ISP DNS. Local names are not resolved. If ISP link goes to down state I see (after about 1minute) a following error: Sep 26 15:44:29 pop3-login: Error: master(pop3): Auth request timed out (received 0/12 bytes) and following informational message: Sep 26 15:44:29 pop3-login: Info: Internal login failure (pid=12809 id=17815) (internal failure, 1 successful auths): user=<xxx(a)xxx.xxx> ..... If link is restored (even for a short time) all works fine again. After next down errors are repeated. I suppose that this is dns issue. Am I wrong? And I have a following question. Is it possible to disable dns requests? I haven't external clients. Or I must fix a name resolution e.g. to use a caching dns server? Thanks.

3 4

[Dovecot] proxy: can I use the password returned from passdb to log in to the back-end?
by Justin McAleer 30 Sep '13

30 Sep '13

I am hoping to support encrypted passwords, which I know is generally not allowed in a proxy setup. However, I can return the password in clear-text out of the password database, so I was hoping for something similar to the destuser field. I have successfully used the master password functionality to support encrypted passwords (users impersonating themselves), as long as the back-end server supports that. However, I need to proxy POP3 to Gmail, which does not.

2 2

[Dovecot] Processing sent items
by Bruce Markey 29 Sep '13

29 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How does dovecot handle sent items and is it possible to "process" them befor they get saved in the sent item folder? My scenario is that I'm running postifx + dovecot with all incoming and outgoing mail passed to a script that encrypts the mail with the public key of the recipient. The only place now that has unencrypted mail sitting on the server is the sent items, I'd like to fix that. What would be the best way to proceed here? - -- Encrypt everything. Public key: https://www.secryption.com/BruceMarkey.asc I believe that any violation of privacy is nothing good. Lech Walesa -----BEGIN PGP SIGNATURE----- Version: OpenPGP.js v.1.20130420 Comment: http://openpgpjs.org wsFcBAEBCAAQBQJSR+odCRDIVcS4Lgc6WAAAIOYP/AqT3HWNbZZnoRXgeq27 n8id40wWemf+IgXGEe1fCTX7d/x+Zinj7bZw5EVq8WlLDxwpOhJGDNUAfA2+ 2z+6J7H0dAHk8rSJZqZfNaGWQQhY3ZehwJnojGJnM5ORuHHH/9WsY91jq26u 4Bzg54tUo+aIoWJHLWlVdqiDjJsW4n536UaHcKlVQx0JCe1byt4eXAmJP9dh Dc9YkP3lKUdW9oxgusJRLOxGfaN++nIFHSBDV6wGp0gEdCuzkgphdEFMnUX9 mD1dwPrDMlEmqHkiyHFH9RGGFvHRaTmdREW8eX9vnHp2PBXthbqd3RKWs7Q4 FmnfoS18inSbTM9Cp79HgQBMKBu66/qtdI6q5q45An9lmQAGf2ElvApSj8b+ ZI5GklVGSyrkxwRTOSRij57SDcRexNhlHg1jsDwSFvNjW5CzH0cB+mVU98eB TqfbIPKvGuqKzpdgf7SNJhZXmmkRrtsL/pI3xCheaZVh34Jxx6N/mP01pDEv d4IrajaTS+0mv6cM4z5f6k62YypHNB9fSTTjIKIqAvLgWMyQIFdjd9BQ1PQK pPiu+btbhhb4RgKa3LFSTp2xJVZlKXd2bqTaRkv63eUgF9NUIr3RYM98I75z mMnxfR5QDZIS6s5tlmZXF7zvCzXoRj30xEp8IsTMrfA4GzLpfAVsJaSUZlSo j5I3 =5Tw/ -----END PGP SIGNATURE-----

2 2

[Dovecot] How to authenticate against SQL DB with custom-ciphered passwords?
by Nicolay Vizovitin 29 Sep '13

29 Sep '13

Hello, I'm about to start developing authentication/password-scheme module for Dovecot. So I would like to get some advice before actually committing to doing things in particular way. Hope somebody will be able to help me :) For the record, I am currently targeting latest stable Dovecot version 2.2.5. I have an SQL DB with mail users' authentication data. Passwords are stored either encrypted via system crypt(3) or ciphered with some custom algorithm (think something symmetrical like AES, so passwords can be decrypted into plain form). I want to use this DB as both userdb and passdb backend. The issue, of course, is with ciphered passwords support. 1) Is it feasible to just implement a new password scheme for ciphered passwords support and still use stock passdb driver in Dovecot for SQL DB access? So that passwords in this scheme would be treated as PLAIN (in a sense that both cleartext and shared secret authentication methods would work). 2) Provided I implement custom password scheme for ciphered passwords, what is the best way to be capable to perform authentication against both ciphered and encrypted passwords? Ciphered and encrypted passwords are stored in different fields of SQL table (one of them is NULL when the other one is set). a) Do I define two passdb clauses with their own default_pass_scheme (equal to my new scheme or CRYPT for encrypted passwords) and use fallback to effectively check both of them? b) Do I modify SQL query so that it prefixes existing password with correct scheme (I'm not sure this will be easy enough to do)? 3) Is it mandatory to provide password generation routine for custom password scheme? When it will be used? 4) Maybe it's better to just implement a plugin that serves as both userdb and passdb driver (in other words a kind of generic authentication module)? What are advantages and disadvantages of each method - custom password scheme + stock SQL driver VS. custom userdb and passdb driver? Fortunately, I already have all the required credentials lookup and verification code. So in any case the question is only in figuring out suitable Dovecot APIs and integrating the existing code. 5) I have previously implemented similar custom authentication module for Courier-IMAP (Courier-Authlib to be precise) to use the same SQL DB. And I will need to support both IMAP servers for some time. So it is only natural to expect some generic solution to be possible. I'd like to remind that I need to be able to supply either encrypted password or deciphered plain password, or just check against them. Is it possible to do so in a common way? If so, what method should I use? I would expect SASL helping me out here, but AFAIK, both Dovecot and Courier-IMAP can only serve as SASL servers (providing authentication services), not clients. 6) I obviously care about providing enhanced security, especially against stealing mail passwords. So any additional advice or related guidelines are welcome. 7) Somewhat unrelated question: what is the best way to test IMAP (and maybe POP3 as well) server performance and compare it to another server? I'm interested in both login performance (the part I will influence) and performance with many mails in mailbox. I heard imaptest is suitable for this task. Are there any recipes or example testing scenarios you might share? ;) I would be grateful for any insight in these issues. If I chose a wrong mailing list to post to, please feel free to correct me. Thanks for your time! :) -- Best regards, Nick

2 2

[Dovecot] Conditional jump or move depends on uninitialised value(s)
by Tamsy 28 Sep '13

28 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Timo, Dovecot 2.2.6 compiled on Ubuntu 10.04 fails on "make check" with the following errors. "make install" is finishing just fine and Dovecot itself works flawlessly so far. - ----- 8< ----- http header invalid [0]: parse failure ............................... : ok: Expected ':' after header field name 'Server', but found ' ' http header invalid [0] .............................................. : ok http header invalid [1]: parse failure ............................... : ok: Expected ':' after header field name 'X', but found ' ' http header invalid [1] .............................................. : ok http header invalid [2]: parse failure ............................... : ok: Expected LF after CR at end of header, but found 'A' http header invalid [2] .............................................. : ok http header invalid [3]: parse failure ............................... : ok: Expected line end after header field 'Accept', but found 0x7f http header invalid [3] .............................................. : ok http header invalid [4]: parse failure ............................... : ok: Expected ':' after header field name 'Suhosin-Patch', but found ' ' http header invalid [4] .............................................. : ok http header invalid [5]: parse failure ............................... : ok: Excessive header size http header invalid [5] .............................................. : ok http header invalid [6]: parse failure ............................... : ok: Excessive header field size http header invalid [6] .............................................. : ok http header invalid [7]: parse failure ............................... : ok: Excessive number of header fields http header invalid [7] .............................................. : ok 0 / 66 tests failed ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B0: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FC92: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B2: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B0: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FC92: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B2: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FCDF: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2.2.6/src/lib-http' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2.2.6/src' make: *** [check-recursive] Error 1 - ----- >8 ----- Is it just me? Cheers, Tamsy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJSQ9FeAAoJEKYXVM1dyOfZVsoIAOM1z1aULWvVqGJScmd8uNXz EG1gRnG6vlrjdUa+8mYQq7RPZZbZ2Cvxd73rkWtptPFAQX+gKsHsh53HS2GKohle W6dJWnEdR7cvUk1UC7FHK3KR5+Z2pdbxhwGB0G26jHKf2OM7dyNcrmtXgkvb3Mwp 4AHrRHVYnPDkcF4Mc9mCnlGdHGsG1bA2BMtI6eR1vbAMKlUy9v11EfunDJHwqkwf 9A5vWAqCnNT9QewJctrHubnN+Rzz5ZLA0cc5ngTL+hsSknIKzH/bj1R99Orca7VN AzBYkWRQ2GqKWxdSBs8RSGv/bVojW1SLjp04xEea+zUeV6sg3RMGkou/pK+lfj4= =o8pw -----END PGP SIGNATURE-----

2 3

Re: [Dovecot] New install not working.
by Joseph Tam 28 Sep '13

28 Sep '13

"Rhorer, Leslie" <Leslie.Rhorer(a)twtelecom.com> writes: > At first things were looking much better, except that most of my > folders, other than the Inbox, were not showing up. I started changing > both the dovecot configuration and the folder structure of my mail > files, but now I can't even get the Inbox to populate. Outlooks says > it is there, along with any folders I create new in Outlook, plus the > Trash folder, which is the only non-local folder with anything in it. > Try what I might, I can't get my Inbox to populate or any of the > existing folders to show up at all. Here is the current output from > dovecot -n: > .... > mail_location = mbox:/RAID/home/%u/mail Maybe try mail_location = mbox:/RAID/home/%n/mail:INBOX=/RAID/home/%n/mail/inbox (%n does not include the domain part, but it might be the same as %u). Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] service anvil and ssl-params not starts with dovecot started
by Dewey Du 28 Sep '13

28 Sep '13

Hi My dovecot started with the error below. What's the most possible reason for the error? “2013-08-28 11:41:40 ”master: Info: Dovecot v2.2.5 starting up (core dumps disabled) “2013-08-28 11:42:00 ”anvil: Fatal: Error reading configuration: Timeout reading config from /var/run/dovecot/config “2013-08-28 11:42:00 ”master: Error: service(anvil): command startup failed, throttling for 2 secs “2013-08-28 11:42:00 ”ssl-params: Fatal: Error reading configuration: Timeout reading config from /var/run/dovecot/config “2013-08-28 11:42:00 ”master: Error: service(ssl-params): command startup failed, throttling for 2 secs Actually, After dovecot starts, I can telnet 110, but it takes 30seconds or so to get through the authentication. I suspect whether the error above cause the issue or not. Other information: dovecot version v2.2.5 use posfix, dovecot sasl, and mysql Attached my dovecot.conf: #auth_debug = yes auth_mechanisms = plain login #debug_log_path = /var/log/dovecot.debug default_internal_user = postfix default_login_user = postfix disable_plaintext_auth = no first_valid_uid = 1000 last_valid_uid = 1000 mail_gid = 1000 mail_uid = 1000 log_path = /var/log/dovecot.log mail_location = maildir:/var/vmail/%d/%u mail_privileged_group = vmail protocols = imap pop3 listen = * base_dir = /var/run/dovecot/ service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } user = root } ssl = no userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

2 2

Re: [Dovecot] recipient_delimiter
by voytek＠sbt.net.au 28 Sep '13

28 Sep '13

>> $recipient_delimiter = ‘+’ ahem, dumb question coming: //I often read various threads here, and, look at my own setup, with a view of optimizing or understanding things I should...// I have working dovecot 2.1.1 with postfix, only have virtual domains, all users in mysql; '+' delimiter is enabled in postfix, and, works OK postfix]# grep _delimiter main.cf # The recipient_delimiter parameter specifies the separator between recipient_delimiter = + BUT, I seem to have nothing in dovecot.conf: postfix]# cd /etc/dovecot dovecot]# grep delimiter * dovecot]# cd conf.d conf.d]# grep delimiter * 15-lda.conf:#recipient_delimiter = + 20-lmtp.conf:# the mail to the detail mailbox. See also recipient_delimiter and 20-lmtp.c_org:# the mail to the detail mailbox. See also recipient_delimiter and should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ? what will it add to this working setup, what am I missing? thanks for all pointers

6 10

[Dovecot] Truncated emails
by David LEROUX 27 Sep '13

27 Sep '13

Hi, I'm running Dovecot IMAP and some times receive truncated emails. Don't understand why. Here are my settings: /dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-48-server x86_64 Ubuntu 10.04.4 LTS log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.log log_timestamp: Â« %Y-%m-%d %H:%M:%S Â» login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_max_userip_connections: 11 mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock imap_client_workarounds: tb-extra-mailbox-sep auth default: passdb: driver: pam userdb: driver: passwd/ Hop you can help. Thanks, David

2 3