- dovecot - dovecot.org

[Dovecot] LDA and enkive
by Davide 23 May '13

23 May '13

Hi to all is it possible to use dovecot lda to pipe emails into enkive socket? if yes how? -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

[Dovecot] should dovecot store maildir files with CRLF or LF?
by Christoph Anton Mitterer 22 May '13

22 May '13

Hi. I've made a strange observation. When having Dovecot (at least) with maildir and moving (via IMAP) mail received by some client (Evolution 3.4) into it the following happens: Regardless of whether the mail was originally(!) set with CRLF or LF (i.e. when I use netcat to submit the plain SMTP to the relaying MTA). When the client (Evolution) had received the mail via POP3 before moving it via IMAP into Dovecot... then the maildir file within dovecot is all LF. When the client however received it via IMAP, before in turn moving it on via IMAP into Dovecot, then the maildir file is mixed CRLF and LF, i.e. the body is CRLF, the headers are terminated... Well the actually bug here is probably in Evolution (as so many others... o.O)... but I wondered... what is Dovecot expected to write files? Platform end-of-line markers (i.e. LF in case of UNIX) or always network end-of-line markers (CRLF)? Cheers, Chris.

4 5

[Dovecot] dsync Migration Couldn't keep all uids dove 2.1.16
by Robert Schetterer 22 May '13

22 May '13

Hi Timo, using http://wiki2.dovecot.org/Migration/Dsync for migration i am getting this in periods dsync(sys4-test-2(a)example.de): Info: INBOX: Couldn't keep all uids dsync(sys4-test-2(a)example.de): Warning: Mailbox changes caused a desync. You may want to run dsync again. dsync(sys4-test-2(a)example.de): Warning: I/O leak: 0x756547164490 (line 1229, fd 15) dsync(sys4-test-2(a)example.de): Warning: I/O leak: 0x756547164490 (line 1229, fd 10) dsync(sys4-test-2(a)example.de): Warning: Timeout leak: 0x7565471647a0 (line 1316) dsync(sys4-test-2(a)example.de): Warning: Timeout leak: 0x7565471647a0 (line 1316) Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 4

[Dovecot] ACLs - creating new top level folders
by Ingo Rogalsky 22 May '13

22 May '13

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1 /home/mail01/user1/Maildir/.folder1/tmp / ... Assigning an ACL with full access rights for user2 to the folder Inbox works as expected. user2 can create subfolders of Inbox, too. But he can't create a new folder like folder1 parallel to Inbox. Is there a possibility of defining an ACL on the mailbox of user1 itself? Or do we need to create all subfolders beneath Inbox like this is usual with other IMAP servers? Ingo --- /usr/sbin/dovecot -c /etc/dovecot/dovecot-test.conf -n # 1.2.15: /etc/dovecot/dovecot-test.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 base_dir: /var/run/dovecot-test/ log_path(default): /var/log/dovecot-test/error.log log_path(imap): /var/log/dovecot-test/error.log log_path(pop3): /var/log/dovecot-test/error.log log_path(managesieve): /var/log/dovecot-test/managesieve.log info_log_path(default): /var/log/dovecot-test/info.log info_log_path(imap): /var/log/dovecot-test/info.log info_log_path(pop3): /var/log/dovecot-test/info.log info_log_path(managesieve): /var/log/dovecot-test/managesieve.log protocols: imap imaps pop3 pop3s managesieve listen(default): *:10143 listen(imap): *:10143 listen(pop3): *:10110 listen(managesieve): *:12000 ssl_listen(default): *:10943 ssl_listen(imap): *:10943 ssl_listen(pop3): *:10995 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/certs/imap-cert.pem ssl_key_file: /etc/ssl/private/imap-key.pem shutdown_clients: no login_dir: /var/run/dovecot-test//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_max_processes_count: 4096 max_mail_processes: 4096 verbose_proctitle: yes mail_location: maildir:~/Maildir:INDEX=/srv/dovecot/index/%u:CONTROL=/srv/dovecot/control/%u maildir_copy_preserve_filename: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_process_size: 1024 mail_plugins(default): fts fts_squat acl imap_acl mail_plugins(imap): fts fts_squat acl imap_acl mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_lock_session(managesieve): no pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu pop3_uidl_format(managesieve): %08Xu%08Xv namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: Other Users/%%u/ location: maildir:%%h/Maildir:INDEX=/srv/dovecot/index/%%u:CONTROL=/srv/dovecot/control/%%u list: children lda: postmaster_address: postmaster@... mail_plugins: sieve acl quota_full_tempfail: yes auth_socket_path: /var/run/dovecot-test/auth-master log_path: /var/log/dovecot-test/deliver.log info_log_path: /var/log/dovecot-test/deliver.log auth default: cache_size: 1024 cache_negative_ttl: 0 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@~ master_user_separator: * debug: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd.masterusers pass: yes master: yes passdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd passdb: driver: pam userdb: driver: passwd-file args: /etc/dovecot/dovecot-passwd socket: type: listen client: path: /var/run/dovecot-test/auth-client mode: 384 user: vmail master: path: /var/run/dovecot-test/auth-master mode: 384 user: vmail plugin: acl: vfile acl_shared_dict: file:/srv/dovecot/lib/shared-mailboxes sieve: ~/.dovecot.sieve sieve_dir: ~/.pysieved fts: squat fts_squat: partial=4 full=10

3 3

[Dovecot] lda: duplicate prefix?
by Larry Rosenman 22 May '13

22 May '13

I've just started using Dovecot, and can't seem to get the LDA to work. I get the following error: Mar 4 00:47:19 thebighonker dovecot: lda(ler): Error: user ler: Initialization failed: namespace configuration error: Duplicate namespace prefix: "" Mar 4 00:47:19 thebighonker dovecot: lda(ler): Fatal: Invalid user settings. Refer to server log for more information. Mar 4 00:47:19 thebighonker exim[76281]: 1UCPB8-000JqI-L7 == /home/ler/clamav-rules <ler(a)lerctr.org> R=userforward T=address_file_dovecot defer (0): Child process of address_file_dovecot transport returned 75 (could mean temporary error) from command: /usr/local/libexec/dovecot/dovecot-lda dovecot -n attached. the invocation from my exim config for other than inbox: address_file_dovecot: driver = pipe # Use /usr/lib/dovecot/dovecot-lda if using Debian's package. # You may or may not want to add -d $local_part@$domain depending on if you ne ed a userdb lookup done. command = /usr/local/libexec/dovecot/dovecot-lda -f $sender_address -m ~/mail/ ${sg{$address_file}{$home}{}} message_prefix = message_suffix = log_output delivery_date_add envelope_to_add return_path_add #group = mail #mode = 0660 temp_errors = 64 : 69 : 70: 71 : 72 : 73 : 74 : 75 : 78 What am I doing wrong? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 430 Valona Loop, Round Rock, TX 78681-3893

2 9

[Dovecot] dsync-2.2.2 incorrectly synchronizes subscription status of deleted mailbox
by Karol Jurak 22 May '13

22 May '13

Hi, It seems that dsync-2.2.2 doesn't correctly synchronize subscription status of a deleted mailbox. The situation is as follows. There are two servers: A and B, and a test user test_mdbox. Mailboxes (mdbox) of this user on both servers are synchronized. Specifically on both of them there is a Trash/x mailbox. Replication plugin is disabled. I delete Thrash/x mailbox on A with Thunderbird. The relevant IMAP commands issued are: 71 87.068176 10.4.0.13 10.1.107.144 IMAP Request: 9 delete "Trash/x" 72 87.072238 10.1.107.144 10.4.0.13 IMAP Response: 9 OK Delete completed. 73 87.073736 10.4.0.13 10.1.107.144 IMAP Request: 10 unsubscribe "Trash/x" 74 87.085263 10.1.107.144 10.4.0.13 IMAP Response: 10 OK Unsubscribe completed. Inspecting output of 'doveadm mailbox list' and contents of subscriptions file shows that everything is as expected, ie. mailbox was deleted and unsubscribed. Moreover in dovecot.mailbox.log on A the following records appear: #480: delete-mailbox 3f3eb117a51c9a51d8280000f671379f (2013-05-20 14:54:40) #504: delete-dir f91e44cab57821aa456b525c7a2f1d7e (2013-05-20 14:54:40) #528: unsubscribe f91e44cab57821aa456b525c7a2f1d7e (2013-05-20 14:54:40) Subsequently I run 'doveadm sync -u test_mdbox -d'. It causes an entry for Thrash/x to reappear in subscriptions file on both servers and the following records are appended to dovecot.mailbox.log on B: #2112: delete-mailbox 3f3eb117a51c9a51d8280000f671379f (2013-05-20 14:55:49) #2136: delete-dir f91e44cab57821aa456b525c7a2f1d7e (2013-05-20 14:55:49) On A this record is added: #552: subscribe f91e44cab57821aa456b525c7a2f1d7e (2013-05-20 14:55:49) So, in described situation, dsync subscribes a mailbox on a server it was deleted on instead of unsubscribing it on the other one. -- Karol Jurak

2 4

[Dovecot] read only users's mailboxes
by Frank Bonnet 22 May '13

22 May '13

Hello for internal purpose I need to put some users's mailboxes in readonly mode during few days. We use MBOX format and UNIX user mode on a FreeBSD 9.1 box I tried to read-only mount the partition but dovecot does not work this way Any infos welcome

2 2

[Dovecot] Dovecot 2.2.1 LDA and sieve (lack of) errors
by Jim McNamara 22 May '13

22 May '13

Hello again, all. Of course after posting yesterday that all was well with my setup, turns out all is not well. The problem I'm having is with dovecot-lda functioning and making deliveries to my mailbox, but the sieve scripts don't seem to have any effect. Attempts at logging what is/isn't happening have been total failures. Managesieve seems to work fine, port 4190 is open on the server and it allows the tunderbird plugin to function, I can create and edit scripts with the plugin. For some reason it doesn't seem to auto-compile the scripts to binary form, but if I just need to do that manually I can live with it. I only mention the lack of auto-compiling in case that sheds light on what is wrong with the LDA or sieve. I'm running the current dovecot, 2.2.1 along with pigeonhole 0.4.0. Here is the config: root@hostname:/usr/local/dovecot-2.2.1# doveconf -n # 2.2.1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0 auth_cache_size = 10 M auth_default_realm = mail.domain.com auth_mechanisms = plain login auth_socket_path = /usr/local/var/run/dovecot/auth-userdb debug_log_path = /dev/stderr default_internal_user = vpopmail default_login_user = vpopmail first_valid_gid = 89 first_valid_uid = 89 hostname = mail.domain.com last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /dev/stderr mail_access_groups = 89 mail_debug = yes mail_gid = 89 mail_location = maildir:%h/Maildir mail_plugins = " quota" mail_privileged_group = 89 mail_uid = 89 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 spamtest spamtestplus vnd.dovecot.debug namespace inbox { inbox = yes location = prefix = separator = . } passdb { driver = vpopmail } plugin { quota = maildir:User quota quota_rule = *:storage=2G quota_warning = storage=95%% quota-warning 95 %u sieve = ~/.sieve/dovecot.sieve sieve_dir = ~/.sieve sieve_extensions = +spamtest +spamtestplus +relational +comparator-i;ascii-numeric +vnd.dovecot.debug } postmaster_address = postmaster(a)mail.domain.com protocols = imap pop3 lmtp sieve sendmail_path = /var/qmail/bin/sendmail service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { group = vchkpw mode = 0600 user = vpopmail } user = $default_internal_user } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } ssl = required ssl_cert = </var/qmail/control/servercert.pem ssl_key = </var/qmail/control/servercert.priv userdb { args = quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol lda { info_log_path = /dev/stderr log_path = /dev/stderr mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { mail_plugins = " quota quota" } I've set the lda specific logs to /dev/stderr because I'm running dovecot through daemontools, and that is what it logs. Daemontools redirects /dev/stderr to /var/log/qmail/qmail-dovecot/current. I had tried logging to /var/log/dovecot/lda.log, that file exists, the directory is 775 dovecot:dovecot, but the file size remained 0. Very little appears in the dovecot logs with lda - root@hostname:/home/vpopmail/domains/domain.com/jim/.sieve# grep lda /var/log/qmail/qmail-dovecot/current |tai64nlocal 2013-05-16 11:05:49.432026500 May 16 11:05:49 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-16 11:29:32.386361500 May 16 11:29:32 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-16 11:54:03.145741500 May 16 11:54:03 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-16 12:33:40.274543500 May 16 12:33:40 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-16 12:47:07.202036500 May 16 12:47:07 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-16 13:40:44.548948500 May 16 13:40:44 auth: Debug: master in: USER 1jim(a)domain.com service=lda 2013-05-17 11:50:31.073410500 May 17 11:50:31 auth: Debug: master in: USER 1jim(a)domain.com service=lda The sieve issue is as follows: I have a very simple sieve script. the managaesieve utility accepts the script, here is the contents of the $HOME/.sieve directory: root@hostname:/home/vpopmail/domains/domain.com/jim/.sieve# ls -al total 20 drwx------ 3 vpopmail vchkpw 4096 May 18 02:24 . drwx------ 5 vpopmail vchkpw 4096 May 18 09:39 .. lrwxrwxrwx 1 vpopmail vchkpw 16 May 18 02:22 dovecot.sieve -> night-test.sieve -rw------- 1 vpopmail vchkpw 303 May 18 02:22 dovecot.svbin -rw------- 1 vpopmail vchkpw 315 May 18 02:24 night-test.sieve drwx------ 2 vpopmail vchkpw 4096 May 18 02:24 tmp The contents of dovecot.sieve itself are: root@hostname:/home/vpopmail/domains/domain.com/jim/.sieve# cat dovecot.sieve # # 2013-5-17 # require ["fileinto", "envelope", "vnd.dovecot.debug"]; if header :contains ["from"] "sub1.domain.com" { debug_log "match happened and syntax changed for testing purposes"; fileinto "INBOX.folder2"; } else { debug_log "can't catch a cold when wet snowy and cold"; keep; } The compile of the script works fine as user vpopmail: vpopmail@hostname:~/domains/domain.com/jim/.sieve$ sievec dovecot.sieve /tmp/dovecot.svbin sievec(vpopmail): Debug: Loading modules from directory: /usr/local/lib/dovecot sievec(vpopmail): Debug: Module loaded: /usr/local/lib/dovecot/lib10_quota_plugin.so sievec(vpopmail): Debug: Effective uid=89, gid=89, home=/home/vpopmail sievec(vpopmail): Debug: Quota root: name=User quota backend=maildir args= sievec(vpopmail): Debug: Quota rule: root=User quota mailbox=* bytes=2147483648 messages=0 sievec(vpopmail): Debug: Quota warning: bytes=2040109465 (95%) messages=0 reverse=no command=quota-warning 95 vpopmail sievec(vpopmail): Debug: Quota grace: root=User quota bytes=214748364 (10%) A diff between dovecot.svbin and /tmp/dovecot.svbin shows no difference. Neither of the debug lines show up anywhere in the logs. When I send an email from sub1.domain.com to this server, it ends up in the main inbox rather than INBOX.folder2. Interestingly, if I run sieve-test on the mail, it tells me it should have been moved to INBOX.folder2: vpopmail@hostname:~/domains/domain.com/jim/Maildir/cur$ sieve-test ../../.sieve/dovecot.sieve 1368888104.11471.hostname\,S\=1235\:2\,a sieve-test(vpopmail): Debug: Loading modules from directory: /usr/local/lib/dovecot sieve-test(vpopmail): Debug: Module loaded: /usr/local/lib/dovecot/lib10_quota_plugin.so sieve-test(vpopmail): Debug: Effective uid=89, gid=89, home=/home/vpopmail sieve-test(vpopmail): Debug: Quota root: name=User quota backend=maildir args= sieve-test(vpopmail): Debug: Quota rule: root=User quota mailbox=* bytes=2147483648 messages=0 sieve-test(vpopmail): Debug: Quota warning: bytes=2040109465 (95%) messages=0 reverse=no command=quota-warning 95 vpopmail sieve-test(vpopmail): Debug: Quota grace: root=User quota bytes=214748364 (10%) sieve-test(vpopmail): Debug: Quota root: name=User quota backend=maildir args= sieve-test(vpopmail): Debug: Quota rule: root=User quota mailbox=* bytes=2147483648 messages=0 sieve-test(vpopmail): Debug: Quota warning: bytes=2040109465 (95%) messages=0 reverse=no command=quota-warning 95 raw mail user sieve-test(vpopmail): Debug: Quota grace: root=User quota bytes=214748364 (10%) sieve-test(vpopmail): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= dovecot: line 6: info: DEBUG: match happened and syntax changed for testing purposes. Performed actions: * store message in folder: INBOX.folder2 Implicit keep: (none) sieve-test(vpopmail): Info: final result: success And yes, INBOX.folder exists: vpopmail@hostname:~/domains/domain.com/jim/Maildir/cur$ ls -al ../.INBOX.folder2/ total 28 drwx------ 5 vpopmail vchkpw 4096 May 14 10:33 . drwx------ 15 vpopmail vchkpw 4096 May 18 10:42 .. drwx------ 2 vpopmail vchkpw 4096 May 14 10:20 cur -rw------- 1 vpopmail vchkpw 232 May 17 08:07 dovecot.index.log -rw------- 1 vpopmail vchkpw 17 May 14 10:33 dovecot-uidlist -rw------- 1 vpopmail vchkpw 0 May 14 10:20 maildirfolder drwx------ 2 vpopmail vchkpw 4096 May 14 10:20 new drwx------ 2 vpopmail vchkpw 4096 May 14 10:20 tmp Here's the file that calls dovecot-lda for user jim: vpopmail@hostname:~/domains/domain.com/jim$ cat .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot-lda -d $EXT@$USER Both /var/qmail/bin/preline and /usr/local/libexec/dovecot/dovecot-lda exist. Any idea why my sieve doesn't seem to take effect? Thanks for reading.

2 3

Re: [Dovecot] Outlook 2013 - mounting folders with XLIST
by Hajo Locke 21 May '13

21 May '13

Hello, >> i do some tests with dovecot 2.1.7 and activated a default special-use >> config. To get it work with outlook 2013, i also added XLIST to imap >> capability string. basically this is working. >> >> is somebody also using special-use folders successful with outlook 2013? > yes, testet a few times, works fine, without Junk folder , cause > outlook wants this handled by it own, but i ve seen reg patches to > change this My serverside setup now is completed. I did a lot of tests last weeks and experienced some strange behaviour of some clients. Outlook 2013 is only working when adding XLIST manually to imap_capability imap_capability = +XLIST This is because outlook 2013 not supports rfc 6154 but the deprecated XLIST standard invented by google. So the problem with junkfolder is not a bug in Outlook 2013, in rfc 6154 spamfolder is tagged by \Junk, in XLIST standard \Spam is used. I did see that when using a gmailaccount in outlook 2013. Adding XLIST capability to dovecot seems to be a problem for other Clients. k9 is able to work with rfc 6154 servers. But if k9 finds XLIST and SPECIAL-USE together in capabilitystring it seems to prefer XLIST requests. Because of dovecot is accepting XLIST requests, but outputs rfc 6154 details, k9 seems to be confused and dont finds special Folders. rfc 6154 is similar but not identical to XLIST. If you dont test with really individual foldernames, you get tricked by clients behaviour. I looked around and the most imap-servers of hosting companies etc. provide XLIST feature, Special-USE unfortunately only a few. So i did now some changes to dovecot sources on my own. I added \Spam as allowed special-use attribute and created a new function for XLIST Requests. So if XLIST is requested, Clients gets lines of output with XLIST and \Junk is replaced with \Spam. So all is done in the code and i dont need to change my userdb-config. Testing this server with different clients was successful. All of them did find their special folders and worked fine, outlook 2013 also finds spamfolder now. So this changes contribute to consolidate a deprecated standard but i have to find a way where all users can benefit from new features. This is not a request to change something in dovecot, this is a call to decision makers to support one rfc Standard. Hajo

1 0

[Dovecot] Configure dovecot to provide SASL authentication
by Peter Skensved 21 May '13

21 May '13

Hi, I'm trying to get dovecot to provide SASL authentication for postfix My setup appears to be working but I'm not 100% certain I've got it right. I've come across several examples for dovecot version 1 but I'm running 2.0.9. The output of doveconf -n is here : 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.2.1.el6.x86_64 x86_64 CentOS release 6.3 (Final) auth_debug = yes auth_verbose = yes disable_plaintext_auth = no mbox_write_locks = fcntl passdb { driver = pam } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } Specifically : are the "service auth", userdb and passdb sections correct ? And the mode ? Or is it too permissive ? For completeness the postfix setup is here : smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous # smtpd_delay_reject = yes smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, permit # smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain, permit # smtpd_recipient_restrictions = reject_unauth_pipelining, reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, permit # peter ---- Peter Skensved Dept. of Physics, Queen's University, Kingston, Ontario, Canada

3 2