- dovecot - dovecot.org

[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

[Dovecot] How to configure ssl cert chain in dovecot 10-ssl.conf file
by Bu Xiaobing 21 May '13

21 May '13

Hi there, Does anyone know how to do this: "Put all the certificates in the ssl_cert file. For example when using a certificate signed by TDC the correct order is: Dovecot's public certificate TDC SSL Server CA TDC Internet Root CA Globalsign Partners CA " I try to set these parameters in the conf.d/10-ssl.conf as below, but it seems doesn't work. --- ssl_cert = </etc/pki/dovecot/certs/mail.mymailserver.com.crt ssl_cert = </etc/ssl/certs/dovecot/sub.class1.server.ca.pem ssl_cert = </etc/ssl/certs/dovecot/ca.pem ---- I even cat mail.mymailserver.com.crt sub.class1.server.ca.pem certs/dovecot/ca.pem into one singe file, and define ssl_cert = < /path/to/the/singcertfile.pem, but it doesn't work too. In my apache httpd server httpd.conf file I can define: -- SSLCertificateChainFile /etc/pki/dovecot/certs/sub.class1.server.ca.pem SSLCACertificateFile /etc/pki/dovecot/certs/ca.pem -- And it well work fine. Thinks for any suggest. Bu Xiaobing

2 3

[Dovecot] Pigeonhole: extprograms - pipe
by Anes Mukhametov 20 May '13

20 May '13

Hello! I've tried to use extprograms pipe feature but stuck with "Broken pipe" errors in mail log: May 17 15:18:57 backend1 dovecot: lmtp(20338, user(a)domain.tld) Debug: 3VMVFWFKllFyTwAArRg8UA: sieve: action pipe: running program: learn May 17 15:18:57 backend1 dovecot: script: Error: write(response) failed: Broken pipe May 17 15:18:57 backend1 dovecot: lmtp(20338, user(a)domain.tld) 3VMVFWFKllFyTwAArRg8UA: sieve: execution of script /data/mail/storage/domain/user(a)domain.tld/.dovecot.sieve;name=main script failed, but implicit keep was successful (user logfile /data/mail/storage/domain/buser(a)domain.tld/.dovecot.sieve.log should reveal additional details) /data/mail/storage/domain/buser(a)domain.tld/.dovecot.sieve.log: error: msgid=<c7cd36f19be8164addf091a646b8b284(a)domain.tld>: pipe action: failed to pipe message to program `learn': refer to server log for more information. [2013-05-17 15:18:57] ham user(a)domain.tld 50796. Sieve script contents: require ["fileinto","copy","mailbox","vnd.dovecot.pipe"]; if anyof (header :is "Subject" "ham") { pipe :try "learn" ["ham"]; fileinto "INBOX/ham"; stop; } Sieve plugin config uncommented conents: sieve_plugins = sieve_extprograms *sieve_pipe_socket_dir = sieve-pipe* # Define the executed script as parameter to the sieve service executable = script /etc/dovecot/scripts/spam.sh # Use some unprivileged user for executing the program user = nobody # The unix socket located in the sieve_pipe_socket_dir (as defined in the # plugin {} section above) unix_listener sieve-pipe/learn { # LDA/LMTP must have access user = nobody mode = 0777 } } spam.sh is message processing script which interacts with spamassassin. I've tested pipe with spam.sh that redirects stdin to /dev/null and returns 0 but errors were logged anyway. Note that spam.sh runs, getting the message from sieve and processing it to spamassassin without a problem, but "broken pipe" is being logged.

3 4

Re: [Dovecot] Configure dovecot to provide SASL
by Peter Skensved 20 May '13

20 May '13

> > > Am 19.05.2013 17:51, schrieb Peter Skensved: > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > mode = 0666 > > } > > chmod 666 is always a very bad idea > > > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0660 > user = postfix > group = postfix > } > } > Thanks for the reply - - all the other sockets in /var/spool/postfix/private have mode 666 ( and the directory itself mode 700 ) but that is probably a question for the postfix list.... peter

1 0

[Dovecot] v2.2.2 + dsync version incompatibility
by Timo Sirainen 20 May '13

20 May '13

Looks like dsync v2.2.2 isn't fully compatible with earlier dsync versions, unless you add: http://hg.dovecot.org/dovecot-2.2/rev/e0156c479a12

1 0

[Dovecot] Linking mdbox directories
by Alex Crow 20 May '13

20 May '13

Hi Timo/list, We have a scenario in which some email accounts on dovecot (stored in mdbox, separate paths for indexes, email, ALT storage and also using SIS for attachments, LDAP directory) need their names changed. I know we could just change the mail LDAP attribute (and leave mailMessageStore alone) so they keep the same directories on disk, but this would throw a spanner in the works for our backups. Would it be possible to create a hard link of the user's directories under the new name, and change the LDAP mailMessageStore attribute to point to these without stopping and starting dovecot? And after a while unlink the original locations? Or would this mess up dovecot's internal state? Thanks Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).

2 2

[Dovecot] doveadm altmove to gzipped-mdbox
by Claus 20 May '13

20 May '13

Hi, im wondering if it's possible to store old messages in a compressed mdbox on alternate storage. The main storage is uncompressed mdbox. I tried something like: doveadm -Dv -o "plugin/zlib_save=gz" altmove -u testuser sentbefore 8d Could someone tell me if it's possible and give me a hint how this can be done? I tried this with dovecot-2.2 Claus

2 2