April 2013 - dovecot - dovecot.org

[Dovecot] Dovecot has no understandable configuration any more
by forum 04 May '13

04 May '13

Hello, for many years i used an mailserver with dovecot V1 very satisfied! http://mailserver.decotrain.de/ One of the reasons to use dovecot was a simply configuration. Dovecot was the best choice for IMAP for me! Now i updated the server to Debian testing with dovecot 2.1.7. It's not possible for me to get a running authentication for virtual mail users! I recently found this mailing and have the same problem: http://www.dovecot.org/list/dovecot/2012-March/064181.html The documentation says *nothing* about my problem how to authenticate with mysql! http://wiki2.dovecot.org/VirtualUsers I can solve the problem only with try and error without a chance in this complex system. It's nice to have all this possibilites but they are not useful if not documented. There should be some clear examples for different scenarios to be found in your wiki. My problem at this time: I don't know how to configure the userdb to work with mysql authentification? All mail is running under the special user mail. dovecot.conf ============ disable_plaintext_auth = yes passdb { driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext args = /etc/dovecot/dovecot-sql.conf } userdb { driver = prefetch } first_valid_uid = 8 last_valid_uid = 8 first_valid_gid = 8 last_valid_gid = 8 mail_location = maildir:/srv/mail/%d/%n dovecot-sql.conf ================ driver = mysql connect = host=/var/run/mysqld/mysqld.sock dbname=... => WORKS! default_pass_scheme = SHA1 password_query = SELECT password, '/srv/mail/%d/%n' AS home, 'mail' AS uid, 'mail' AS gid FROM user WHERE username = '%n' AND domain = '%d' AND IMAP_allowed = 'YES' Errors ====== Apr 30 10:28:22 auth: Debug: client out: OK 1 user=xxxx@yyyy home=/srv/mail/yyyy/xxxx uid=mail gid=mail Apr 30 10:28:22 auth: Debug: master in: REQUEST 3163291649 5347 1 87066c907eef8f4e5ed71319b560dd2a Apr 30 10:28:22 auth: Error: prefetch(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): userdb lookup not possible with only userdb prefetch Apr 30 10:28:22 auth: Error: userdb(xxxx@yyyy,::1,<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB>): user not found from userdb prefetch Apr 30 10:28:22 auth: Debug: master out: NOTFOUND 3163291649 Apr 30 10:28:22 imap: Error: Authenticated user not found from userdb, auth lookup id=3163291649 (client-pid=5347 client-id=1) Apr 30 10:28:22 imap-login: Info: Internal login failure (pid=5347 id=1) (internal failure, 1 succesful auths): user=<karsten(a)dct.mine.nu>, method=PLAIN, rip=::1, lip=::1, mpid=5352, secured, session=<doTKyI/brgAAAAAAAAAAAAAAAAAAAAAB> I have no idea how to solve the problem and up to know i could not find an example with google. Please help. Best regards Karsten

8 11

[Dovecot] CATENATE allows zero parts
by Mike Abbott 03 May '13

03 May '13

I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469 (URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1) and comparing their functionality against Apple's implementation. So far I have discovered a few inconsistencies. I will report each of these, and any more that I may find, in separate threads. The first issue is that using CATENATE with no message parts works but, IMO, shouldn't: a2 append inbox catenate () a2 OK [APPENDUID 1366726248 9] Append completed. For comparison this is how Apple's enhanced dovecot in OS X Server handles this request: a2 append inbox catenate () a2 BAD Invalid arguments. According to RFC 4469 section 3 CATENATE requires "one or more message parts." This is formalized in section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" and in RFC 3501 section 9 which states that "[ABNF] rules MUST be followed strictly." I believe that permitting zero cat-parts is contrary to the RFC, although I can understand permitting it under the general doctrine of "servers should be liberal in what they accept, and clients strict in what they send." Is accepting zero cat-parts an intentional exception to the RFC or an oversight?

2 2

[Dovecot] CATENATE doesn't support literal+ url
by Mike Abbott 03 May '13

03 May '13

Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing literals (RFC 2088 LITERAL+), and also does not read and discard the literal+ input after reporting the error. This results in the literal+ input being interpreted as IMAP commands, which could alter the user's mail store in unexpected ways and/or lead to the abrupt disconnection of the client for exceeding the maximum number of bad IMAP commands. Example using dovecot-2.2.1 (note that the text nonsync literal includes the invisible CRLFs: "foobarCRLFbarbazCRLF"): a3 append inbox catenate (url {9+} /some-url text {16+} foobar barbaz ) a4 noop a3 BAD Error in IMAP command APPEND: Invalid arguments. foobar BAD Error in IMAP command : Unknown command. barbaz BAD Error in IMAP command : Unknown command. ) BAD Error in IMAP command : Unknown command. a4 OK NOOP completed. Example using Apple's enhanced dovecot in OS X Server: a3 append inbox catenate (url {9+} /some-url text {16+} foobar barbaz ) a4 noop a3 NO [BADURL /some-url] missing or invalid uid a4 OK NOOP completed. I believe the RFCs indicate that nonsync literal URLs should be permitted. RFC 4469 section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" cat-part = text-literal / url url = "URL" SP astring RFC 3501 section 9: astring = 1*ASTRING-CHAR / string string = quoted / literal RFC 2088 section 4: literal ::= "{" number ["+"] "}" CRLF *CHAR8

2 4

[Dovecot] Dovecot vs MBox
by Gregory Sloop 02 May '13

02 May '13

I'm still in the "what's wrong" stage of figuring out what's going on. But I've got a mail user who isn't getting new messages. Postfix accepts it and drops it in the users mbox. [This is verified. If I tail the Mbox, I can see the new messages.] "Mail" will see the messages too. But dovecot doesn't seem to know they exist. I don't think the MBox is corrupt, as I've tossed the first few messages in hopes that it would then read the rest, but no luck. Any ideas where to look next, what I might do to force dovecot to forget message ID's etc - that might force it to read the whole mailbox file again? [Or a pointer as to where it might be most productive to poke next?] TIA -Greg -- Gregory Sloop, Principal: Sloop Network & Computer Consulting 503.251.0452 x121 Voice | 503.251.0452 Fax www.sloop.net mailto:gregs@sloop.net

5 7

[Dovecot] CATENATE allows empty messages
by Mike Abbott 02 May '13

02 May '13

Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE: b1 append inbox catenate (text {0+} ) b1 OK [APPENDUID 1366726248 12] Append completed. Contrast this with regular APPEND: b2 append inbox {0+} b2 NO Can't save a zero byte message. Note that zero-size literals are OK but zero-size messages are not. So while "b1" above should fail like "b2", this should continue to succeed: b3 append inbox catenate (text {0+} text {8+} foobar ) b3 OK [APPENDUID 1366726248 13] Append completed.

3 6

[Dovecot] Slow DNS warnings (proxy/auth)
by Christian Balzer 02 May '13

02 May '13

Hello, I've just finished transiting our proxies from perdition to dovecot (2.1.7-7 Debian). Yesterday 12 messages (all within the same second) like this caught my attention: --- Apr 25 17:19:09 pp11 dovecot: auth: Warning: proxy(redacted(a)gol.com,xx.xx.xx.xx,<26hUEivbfQBlMrMS>): DNS lookup for mb04.dentaku.gol.com took 5.002 s --- Now this machine at that time was handling a load of about 2 logins per second, about 20% of what it previously handled with perdition w/o a hiccup. It also runs a local caching nameserver and the A record for the mailbox server in question was most definitely cached at the time (verified via TTL). The machine in question was very bored and certainly capable of handling hundreds if not thousands of DNS queries per second at that moment. In short, I can't see any reason how the lookup could have taken so long, so my guess is there are some issues with the dns-helper (locking, stepping on each others feet, not being spawned fast enough) causing this. Some general remarks, dovecot as proxy feels "heavier" than perdition. In the CPU area that's probably a more subjective impression, because all the little helper processes make it clear what's going on where. Though the "config" process being rather active is something that perdition definitely doesn't do, it reads the config once at start time and that's it. All the IPC and central processes of course also make dovecot rather file handle hungry. Memory wise it's about 35% bigger than perdition and that's not subjective at all. ^o^ About one MB per proxy process/connection for dovecot in my case. Caveat emptor. ^o^ Regards, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Fusion Communications http://www.gol.com/

2 1

[Dovecot] NTLM authentication with Outlook 2010
by Kevin Bridges 01 May '13

01 May '13

All, I have a Ubuntu 12.04.2 box running Dovecot 2.0.19. I have it configured for our active directory. WBinfo and ntlm_auth work great. I am trying to get sso to work with ntlm. Gssapi with thunderbird works like it should. I just cant get ntlm with outlook 2010 to work for sso. I get prompted for my password each time I open outlook. I have attached my config for dovecot. Any help would be much appreciated. # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-39-virtual x86_64 Ubuntu 12.04.2 LTS auth_debug = yes auth_debug_passwords = yes auth_mechanisms = gssapi ntlm auth_use_winbind = yes auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot_debug.log log_path = /var/log/dovecot.log mail_location = mdbox:~/mdbox passdb { driver = pam } plugin { quota_rule = *:storage=2G quota_warning = storage=95%% quota-warning 95 %u } protocols = " imap" service auth-worker { user = root } service auth { user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_plugins = " quota imap_quota" }

2 2

[Dovecot] Antispam r49 breaks Dovecot v2.1
by Steffen Kaiser 30 Apr '13

30 Apr '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Eugene, patch 49 breaks compilation with Dovecot v2.1. Attached patch encloses the change in a #if. To feed the #if the actual Dovecot version, I've introduced an extra variable in extra.mk, but I cannot help with making the GNU configure stuff doing it right away. There will be numerous other ways to get the Dovecot version into the source ... . Maybe, Timo would add a binary version of the Dovecot version in its config.h ? In order to be able to built version-aware plugins. Regards, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUNLvT2oxLS8a3A9mAQIzfwgAvf7zcN9RwKD/kTmFkfx5djKd5H0dRXt8 423csD3bCU6qcOtR2MHR0ApNp07aXK84MPgIazbne41Iekqk0daoOhnPoc0mHy8u kj9EYFGVlQTKa2vcSUEu8Phddc/YHvzQba9m2Dg9P4STuJ6EcRqkhvufspERGphF Y+IY20BQc9/Flu8TIxtt6pSiIioq0WWntCGnyPP9BX90JYYO+5zAm5FnG4GH4Q0Z 44dZSKM7iP0/nMhmsraX/5alxy0mvx3ZfhO/Ktx/wd92WmLROAlicBClIZC9XCH2 6HD/ryr73DrEeEZdmwHcnmZrtWc++EJcAetfv45Fov8XagUtFJ0D4A== =G+d/ -----END PGP SIGNATURE-----

2 1

[Dovecot] Dovecot has no understandable configuration any more
by forum 30 Apr '13

30 Apr '13

Hello, my last problem could be solved now with userdb { driver = static args = uid=mail gid=mail home=/srv/mail/%d/%n } I can connect to dovecot locally with an webmailer. But there is no listener process to be seen outside of the server? Locally this ports are working, but not outside: # netstat -tulpn | grep dove tcp6 0 0 :::110 :::* LISTEN 5741/dovecot tcp6 0 0 :::143 :::* LISTEN 5741/dovecot tcp6 0 0 :::993 :::* LISTEN 5741/dovecot tcp6 0 0 :::995 :::* LISTEN 5741/dovecot Is this a configuration problem inside dovecot? Another problem is the migration from the existant emails from V1 to V2: In the log i can find: Apr 30 11:14:57 imap(xxxx@yyyy): Error: Broken file /srv/mail/yyyy/xxxx/.INBOX.dir.09/dovecot-uidlist line 1: Broken header (uidvalidity = 0, next_uid=697) How can i recover this? Delete all the index files? Has someone an idea how to migrate the emails from charset ISO8859-1 to UTF-8? Best regards Karsten

2 1

[Dovecot] Dovecot Antispam Plugin is not working
by Ravi Kanchan 30 Apr '13

30 Apr '13

Hi All, I am using dovecot version 2.0.9 DSPAM Anti-Spam Suite 3.10.2 (agent/library) ClamAV 0.97.7/17102 and dspam antispam plugin dovecot-antispam-plugin-43880985e3dd and plugin configuration is given below: protocol imap { mail_plugins = " antispam autocreate" } protocol pop3 { mail_plugins = antispam autocreate } plugin { antispam_allow_append_to_spam = YES antispam_backend = dspam antispam_crm_args = --config=/home/vmail antispam_dspam_args = --client;--user vmail antispam_dspam_binary = /usr/bin/dspam antispam_dspam_notspam = --class=innocent antispam_dspam_result_header = X-DSPAM-Result antispam_dspam_spam = --class=spam antispam_mail_tmpdir = /tmp antispam_signature = X-DSPAM-Signature antispam_signature_missing = error antispam_spam = Spam } dspam bin path: [root@sogo ~]# which dspam /usr/bin/dspam and dspam.conf has attached with this mail. but my dspam plugin configuration is not working. and also I am not getting any log from dspam. My dspam server is working prefect. but I guess plugin is not working properly can anyone helpme. and my configuration for this is following:Regard's Ravi Kanchan Sharma Sr. System Administrator Infinite Computer Solutions (I) Ltd. Bglr. Mo. 9997154666

1 0