- dovecot - dovecot.org

Temporary Lookup Failure
by Brad 18 Jan '16

18 Jan '16

Hi All, Have a CentOS 7, dovecot and postfix setup. Can get mail via 995 SSL/TLS Can send mail to virtual users and auto creation works using /etc/dovecot/passwd file via mail command. Using the dovecot lmtp and can login via 465 but the user lookup fails via postfix. in postfix main.cf have virtual_transport = lmtp:unix:private/dovecot-lmtp in dovecot.log I am seeing no errors in dovecot-info.log no errors either in maillog I am seeing: postfix/smtps/smtpd warning hash:/etc/postfix/virtual is unavailable open database /etc/postfix/virtual.db No such file. Note: I did go through creating the virtual.db and associated files but figured that it cant be correct as I want lmtp to handle it and it didn't work anyways, so I removed it. NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 <user@domain> Temporary lookup failure from=<user@domain> to=<user@domain> proto=ESMTP helo=<localhost.localdomain> -- obfuscated Tried every article I could find on the Internet to resolve this with out much luck. Any pointers would be greatly appreciated or if you need specific config details just let me know. Thanks, Brad

4 6

Dovecot doesn't listen on port 143, 993 in SSL
by 남설 18 Jan '16

18 Jan '16

Dear Dovecot Team First of all, I always appreciated your contribution & effort. Dovecot is very good tool for me for a while since my 2 years Linux start. But, 3 days ago, I upgraded my ubuntu 15.04 to 15.10 Then, I realized that my dovecot mail sever didn't work. So I simply terminated all the packages and reinstall it. It means I can't remeber what my previous setting was in my memory. So, dovecot in run is ver 2.2.18 now. Dovecot -n shows below and there is no "SSL" option. then all the port 143, 993 opens(It's not accesible somehow from clients but it's next matter) ----------------------No SSL version------------------------ auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } userdb { driver = passwd } ----------------------------------------------------------- But, If I turn on SSL option with encrypt key and certicate, all port 143, 993 just disappeared. I treaded this issue in ubuntu ASK but still no proper answer so far http://askubuntu.com/questions/722072/dovecot-doesnt-listen-on-993imaps --------------------------SSL option version---------------- auth_mechanisms = plain login mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } *ssl_cert = </etc/dovecot/dovecot.csr>** **ssl_key = </etc/dovecot/private/dovecot.key>* userdb { driver = passwd } -------------------------------------------------------------- Looing forward your reply Thanks in advance

3 2

mmap failed
by ＠lbutlr 18 Jan '16

18 Jan '16

Error: mmap() failed with file /home/user/Maildir/.Archive/dovecot.index.cache: Cannot allocate memory I have default_vsz_limit = 512 M in my conf file. (This error only occurs with a single user’s .Archive index, but that user has over 400,000 files int eh Archive mailbox) -- Let him who desires peace, prepare for war.

2 1

doveconf syntax question
by A. Schulze 18 Jan '16

18 Jan '16

Hello, I have one sieve extension enabled: /etc/dovecot/conf.d/20-sieve.conf: plugin { sieve_extensions = +vacation-seconds } now (months later) we want to enable an other extension. no big deal: /etc/dovecot/local.conf: plugin { sieve_extensions = +editheaders ... } This was wrong. We ASSUMED the plus would add the extension to the list. But at the end only +editheaders was activ. What's the right way to /add/ sieve_extensions from different config files? our guess "sieve_extensions = $sieve_extensions +editheaders" do not work: doveconf -a | grep sieve_extensions doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 22: Unknown variable: $sieve_extensions doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 22: Unknown variable: $sieve_extensions Andreas

2 2

Running without anvil?
by Dave Abrahams 18 Jan '16

18 Jan '16

Hi, I'm using dovecot as a local mail store on my laptop using preauth tunneling. It turns out I almost don't even need to start dovecot at all; the only reason it needs to be running is so that FTS indexing can be invoked. And because I don't want it to run any services, I can run it as an unprivileged user, so long as I turn them all off: # We don't want to serve any protocols, so we don't bind to any ports. # We can run everything as me. protocols = default_login_user = dave default_internal_user = dave The only thing is, I keep getting these in var/log/mail.log: anvil: Fatal: chroot(/Users/dave/brew/var/run/dovecot/empty) failed: Operation not permitted master: Error: service(anvil): command startup failed, throttling for 60 secs auth: Error: read(anvil-auth-penalty) failed: EOF Any suggestions? TIA, Dave

3 5

sieve - configuration problem
by Hajo Locke 18 Jan '16

18 Jan '16

Hello List, first thanks for previous hints, you helped me a lot. Unfortunately i have new problem with sieve and executing multiple scripts sequentially. This is current conf which is complete working : #CONF1 plugin { sieve = ~/sieve/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader sieve_pipe_bin_dir = /usr/local/bin/ sieve_filter_bin_dir = /usr/local/bin/ sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } i also activated managesieve which is working as well. Now iam looking for a way to run individual scripts for users. My idea is to have a system generated script which may run before or after the personal script. Additional the system scripts should not be viewed or changed by mailusers. So i tried with directives sieve_before and sieve_after: #CONF2 plugin { sieve = ~/sieve/.dovecot.sieve sieve_before = ~/sieve_before/.dovecot.sieve sieve_after = ~/sieve_after/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader sieve_pipe_bin_dir = /usr/local/bin/ sieve_filter_bin_dir = /usr/local/bin/ sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } every single script "~/sieve/.dovecot.sieve", "~/sieve_before/.dovecot.sieve" and "~/sieve_after/.dovecot.sieve" contains a small rule to add a new mailheader (X-Before, X-After, X-Middle) so i can watch what happens. The problem is: Every single script is working, but only when this directive is the only one which is activated in conf. As soon as i enable another directive absolut nothing is happen. It does not matter which combination of directives (sieve|sieve_before_sieve_after) is enabled or disabled. Just as a second one is enabled sieve seems to do nothing. Mail is delivered by lda but no songle one headerentry is added. What happens here and how to solve this? Currently i use dovecot 2.2.21 and sieve 0.4.11 Thanks, Hajo

2 2

Dockerfile for building latest github version
by KT Walrus 16 Jan '16

16 Jan '16

Is there a Dockerfile for building/installing the latest Dovecot version in a Docker Image? I don't see Dovecot in the Official Repositories on the Docker Hub like almost all the other popular open source software packages that I use. Why no Official Docker repo for Dovecot? All the user contributed repos containing Dovecot in the Docker Hub seem to just install from a distribution’s repo (like Ubuntu 14.04) but these packages seem to lag the most recent version of Dovecot that I see in GitHub. Kevin

1 0

Corrupted index cache file - migration with zlib
by Leon Kyneur 15 Jan '16

15 Jan '16

Hi I'm migrating some mailboxes from an old dovecot system where mailboxes are stored maildir uncompressed. I enabled zlib on the new system and migrated an account: doveadm -o mail_fsync=never backup -R -u tonyg imapc: when the account connects to the new system after a while i'm seeing the following error and the mailbox is no longer functioning: Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: read(/srv/vmail/532868/tonyg/mdbox/storage/m.1): FETCH BODY[] for mailbox INBOX UID 61 got too little data: 4106341 vs 6054268 Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: unlink(/srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jan 15 13:58:06 S611 dovecot: imap(tonyg): Error: Corrupted index cache file /srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 61 Jan 15 13:58:06 S611 dovecot: imap(tonyg): FETCH failed in=181 out=4109653 Jan 15 13:58:06 S611 dovecot: auth-worker(6130): ldap(tonyg,144.132.1.90): unknown user Jan 15 13:58:06 S611 dovecot: imap-login: Login: user=<tonyg>, method=PLAIN, rip=144.132.1.90, lip=203.134.11.127, mpid=6746, secured, session=<7qqWklYpnGjLhgHK> Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: read(/srv/vmail/532868/tonyg/mdbox/storage/m.1): FETCH BODY[] for mailbox INBOX UID 61 got too little data: 4106341 vs 6054268 Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: unlink(/srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jan 15 13:58:07 S611 dovecot: imap(tonyg): Error: Corrupted index cache file /srv/vmail/532868/tonyg/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 61 Jan 15 13:58:07 S611 dovecot: imap(tonyg): FETCH failed in=181 out=4109653 If i migrate the account without zlib everthing works fine and the error can't be reproduced. I have tried force-resync and index commands to no avail. Any ideas what's going on here? doveconf -n: [root@S611 532868]# doveconf -n # 2.2.21 (5345f22): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (6ddf62b87f60+) # OS: Linux 3.10.0-327.4.4.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_debug = yes auth_verbose = yes imapc_features = rfc822.size fetch-headers imapc_host = removed imapc_master_user = removed imapc_password = # hidden, use -P to show it imapc_user = %u lmtp_proxy = yes login_trusted_networks = 192.168.10.0/24 mail_debug = yes mail_gid = vmail mail_location = mdbox:%h/mdbox:ALT=/altstorage%h/mdbox mail_plugins = quota zlib mail_prefetch_count = 50 mail_uid = vmail 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 mdbox_rotate_size = 10 M namespace inbox { inbox = yes location = mailbox "Deleted Messages" { special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap-m2core.conf.ext driver = ldap } plugin { quota = dict:User quota::file:%h/dovecot-quota sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } pop3c_host = <removed> pop3c_password = # hidden, use -P to show it service lmtp { inet_listener lmtp { address = <removed> port = 24 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem verbose_proctitle = yes protocol imap { mail_plugins = quota imap_quota imap_zlib }

2 2

Courier generates new UIDVALIDITY
by Peer Heinlein 15 Jan '16

15 Jan '16

We just detected, that under some circumstances Courier-IMAP will generate a new UIDVALIDITY for every access to an IMAP-folder, if the folder had been created by a simple "mkdir" and not with maildirmake. Courier doesn't save his uidvalidity-file in this case. Courier DOES generate a sticky UIDVALIDITY after the first "real" access by a User through the IMAP-SELECT-command. That's why this problem isn't a "real" problem in the world. Courier does NOT create this IMAP-UIDVALIDITY if the user just uses POP3-access, because there the UIDVALIDITY isn't used. We have a migration scenario where we have many users with POP3-only access (so that they DO have many mails in der INBOX) and an incremental migration trough doveadm/dsync/imapc fails (caused by consequently changing UIDVALIDITYs). doveadm just uses the IMAP EXAMINE command to open the source IMAP-folder on the Courier's side readonly. Courier DOES handle this access "readonly" and doesn't consequently doesn't generate a UIDVALIDITY-file. Instead Courier uses random UIDVALIDITYS by every access and doveadm always has to copy all mails (and duplicates them if "-1 -R" is used!). To fix this problem and to make a migration and/or doveadm backup/sync much more reliable Dovecot should open the source folder with a SELECT command instead. (Maybe one SELECT and then change to EXAMINE, if you think EXAMINE would be more safe.) Maybe this is also relevant for a real permanent imapc-situation, where Dovecot/imapc is used to fix broken IMAP-implementations from an older backend. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 1

doveadm/dsync/imapc loose folder subscriptions
by Peer Heinlein 15 Jan '16

15 Jan '16

As I already wrote some days ago we're actually running a huge migration using doveadm/dsync-backup/imapc: doveadm -o imapc_user="$UNAME1" -o imapc_password="$PWORD1" -o imapc_host=$SERVER1 -o pop3c_user="$UNAME1" -o pop3c_password="$PWORD1" -o pop3c_host=$SERVER1 -D -v backup -R -u "$UNAME2" imapc: We just noticed that doveadm looses changes in folder subscriptions if a folder is copied again. a) Copy a mdbox-home of a user (using doveadm backup...) b) Change his subscriptions on the source-side OR change his subscripts on the destination-side OR delete his subscriptions-file. c) Copy that mdbox-home from that user again (using doveadm backup...) doveadm will copy & merge his mails, but he does NOT check for changes in folder subscriptions. As you can see in the attached logs, doveadm nitices changes in subscriptions: dsync(p100490p11): Debug: brain S: Local mailbox tree: INBOX.Trash guid=b36f688eae08506001091708006abe5a uid_validity=1368084367 uid_next=1206 subs=yes last_change=0 last_subs=0 dsync(p100490p11): Debug: brain M: Local mailbox tree: INBOX.Trash guid=b36f688eae08506001091708006abe5a uid_validity=1368084367 uid_next=1206 subs=no last_change=1448903088 last_subs=1448177531 but doesn't fix the subscriptions list: dsync(p100490p11): Debug: brain M: Mailbox INBOX.Trash: local=b36f688eae08506001091708006abe5a/1448903088/1, remote=b36f688eae08506001091708006abe5a/0/1: Mailboxes are equal Even a deletion of the subscriptions file doesn't work. doveadm does not create a new subscription file. This bug is heavy, because incremental backups made by doveadm backup aren't complete and reliable any more. Our biggest problem ist, that we changed the folder prefix and doveadm does change the folder names, but not the subscriptions. So we have several hundred thousand users with broken subscriptions (yes, sed can fix this, I know, but also we'd kill changes made by users during migration period). Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 2