- dovecot - dovecot.org

[Dovecot] dsync backup questions
by Joe Beaubien 06 Feb '13

06 Feb '13

Hi, I'm currently trying to setup remote backups of my emails but i'm running into issues (mdbox format, indexes and storage in the same folder hierarchy). Local backup command: dsync -u "my_user" backup /backups/my_user (1) Recently, I noticed that the local backup takes up twice the size as the original mail location (8gb vs. 4gb). I purged alot of emails from the original location, so the size shrunk, but the local backup just keeps on getting bigger. I couldn't find any dsync option that would delete extra emails. - Question: Why isn't the local backup synced properly and remove the extra emails? (2) What is the best why to copy this local backup to a remote location that does NOT have the possibility to run dsync. - Question 1: is rsync safe to use and will this data work for restore? - Question 2: Would it be safe to simply rsync the original mail_location to the remote server? I searched the net, but it seems that mdbox is tricky to backup. Thanks in advance, -Joe

3 4

[Dovecot] Out of memory after upgrading to dovecot 2.0.21
by Arnaud Abélard 05 Feb '13

05 Feb '13

Hello, I've upgraded our servers and now dovecot seems to be running out of memory when accessing my own mailbox (and only mine, which is in a way pretty fortunate): dovecot: imap(abelard-a): Error: mmap() failed with file /vmail/a/b/abelard-a/dovecot.index.cache: Cannot allocate memory imap(abelard-a): Fatal: pool_system_realloc(131072): Out of memory /vmail/a/b/abelard-a/dovecot.index.cache is 224MB big and my mailbox is 72% full of 8GB. any idea of what is happening? Thanks in advance, Arnaud -- Arnaud Abélard jabber: arnaud.abelard(a)univ-nantes.fr / twitter: ArnY Administrateur Système DSI Université de Nantes -

3 5

[Dovecot] Using Mutt - folder atime/mtime etc
by David Woodfall 05 Feb '13

05 Feb '13

Version 2.1.10 For some reason Mutt doesn't list any info about IMAP folders and seems to ignore folder_format. My questions is does anyone have any workarounds for this?

3 4

[Dovecot] Upgrade from 2.1.13 to 2.1.14 and load doubled
by Alessio Cecchi 05 Feb '13

05 Feb '13

Hi, during the weekend I upgrade my mail servers from dovecot 2.1.13 to dovecot 2.1.14 (and rebuild dovecot-2.1-pigeonhole-0.3.3). After upgrade all works fine, but today the load avarage un MXs is doubled. Mailboxes are in Maildir/ on NFS and I'm using dovecot as LDA and dict quota only for quota usage. May be a problem with the new version? This is my configuration: $ ./configure --prefix=/usr/local/dovecot-2.1 --with-vpopmail --with-mysql --with-bzlib --with-zlib # cat /usr/local/dovecot-2.1/etc/dovecot/sieve/default.sieve require ["vnd.dovecot.duplicate", "fileinto", "mailbox"]; if header :contains "X-Spam-Status" "Yes" { fileinto "Spam"; } if header :contains "Subject" "TEST 123" { fileinto "Spam"; } if duplicate { fileinto "Trash"; } ##################### # 2.1.14: /usr/local/dovecot-2.1/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 auth_cache_size = 512 k auth_worker_max_count = 60 default_login_user = nobody dict { acl = mysql:/usr/local/dovecot-2.1/etc/dovecot/dovecot-share-folder.conf expire = mysql:/usr/local/dovecot-2.1/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/usr/local/dovecot-2.1/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no dotlock_use_excl = no first_valid_gid = 89 first_valid_uid = 89 last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /var/log/dovecot/dovecot.log mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota acl zlib expire maildir_very_dirty_syncs = yes 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 vnd.dovecot.duplicate mmap_disable = yes namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = cache_key=%s%u webmail=192.168.113.215 driver = vpopmail } plugin { acl = vfile:/usr/local/dovecot-2.1/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = proxy::acl expire = Trash expire2 = Spam expire_dict = proxy::expire quota = maildir:UserQuota quota2 = dict:User quota::noenforcing:proxy::quota quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_default = /usr/local/dovecot-2.1/etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.duplicate } protocols = imap pop3 sieve service auth { unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { unix_listener dict { group = vchkpw mode = 0660 user = vpopmail } } service imap-login { service_count = 0 } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { service_count = 0 } service quota-warning { executable = script /usr/local/dovecot-2.1/etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { user = vpopmail } user = vpopmail } ssl_cert = </etc/ssl/certs/wildcard.pem ssl_key = </etc/ssl/private/wildcard.key submission_host = localhost userdb { args = quota_template=quota_rule=*:backend=%q driver = vpopmail } protocol lda { log_path = /var/log/dovecot/lda.log mail_plugins = quota acl zlib expire sieve } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins mail_max_userip_connections = 18 mail_plugins = quota acl zlib expire imap_quota imap_acl } protocol sieve { mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 5 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } Thanks -- Alessio Cecchi is: @ ILS -> http://www.linux.it/~alessice/ on LinkedIn -> http://www.linkedin.com/in/alessice Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it

3 11

[Dovecot] lmtp-proxying in 2.1 slower than in 2.0.14 ?
by Jan-Frode Myklebust 05 Feb '13

05 Feb '13

We upgraded our two dovecot directors from v2.0.14 to dovecot-ee 2.1.10.3 this week, and after that mail seems to be flowing a lot slower than before. The backend mailstores are untouched, on v2.0.14 still. After the upgrade we've been hitting process_limit for lmtp a lot, and we're struggeling with large queues in the incoming mailservers that are using LMTP virtual transport towards our two directors. I seem to remember 2.1 should have a new lmtp-proxying code. Is there anything in this that maybe needs to be tuned that's different from v2.0 ? I'm a bit scheptical to just increasing the process_limit for LMTP proxying, as I doubt running many hundreds of simultaneous deliveries should work that much better against the backend storage.. ###### doveconf -n ########## # 2.1.10.3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.32.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.5 (Tikanga) default_client_limit = 4000 director_mail_servers = 192.168.42.7 192.168.42.8 192.168.42.9 192.168.42.10 192.168.42.28 192.168.42.29 director_servers = 192.168.42.15 192.168.42.17 disable_plaintext_auth = no listen = * lmtp_proxy = yes 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 passdb { args = proxy=y nopassword=y driver = static } protocols = imap pop3 lmtp sieve service anvil { client_limit = 6247 } service auth { client_limit = 8292 unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 5515 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_limit = 4096 process_min_avail = 4 service_count = 0 vsz_limit = 256 M } service lmtp { inet_listener lmtp { address = * port = 24 } process_limit = 100 } service managesieve-login { executable = managesieve-login director inet_listener sieve { address = * port = 4190 } process_limit = 50 } service pop3-login { executable = pop3-login director process_limit = 2048 process_min_avail = 4 service_count = 0 vsz_limit = 256 M } ssl_cert = </etc/pki/tls/certs/pop.example.com.cert.ca-bundle ssl_key = </etc/pki/tls/private/pop.example.com.key protocol lmtp { auth_socket_path = director-userdb } ################ -jf

2 5

[Dovecot] dsync-local(user): Error: proxy client timed out
by Metro Domain Admin 05 Feb '13

05 Feb '13

Hello, I have an intermittent but frequent problem using dsync backup. The command outputs: dsync-local(user): Error: proxy client timed out Then dies with exit code 75. Any subsequent attempts to re-run the backup invariably fail like this: dsync-local(user): Warning: Destination mailbox INBOX has been modified, need to recreate it before we can continue syncing dsync-local(user): Error: read() from worker server failed: EOF dsync-local(user): Error: msg-copy returned invalid input: dsync-local(user): Error: remote: dsync-remote(user(a)domain.com): Error: Can't delete mailbox INBOX: INBOX can't be deleted. dsync-remote(l_user(a)domain.com): Error: command MSG-SAVE failed dsync-local(user): Warning: Mailbox changes caused a desync. You may want to run dsync again. The syntax I am using is: dsync -u $user backup \ ssh -i <idfile> <user@host> \ dsync -u l_$user We have this running in a script that loops through all users. The error happens mostly on the larger mailboxes but I've seen it succeed on the largest ones then fail on smaller. One mid-sized account now fails consistently. The backup is running from a Mac OS PPC server running 2.1.12 The target is a Linux Intel box running 2.1.13, but I had the same problem sending to a Mac OS Intel on 2.1.12. Mdbox in all cases. Thanks, Tony

2 1

[Dovecot] METADATA / ANNOTATE extensions
by list＠airstreamcomm.net 05 Feb '13

05 Feb '13

According to the roadmap http://wiki2.dovecot.org/Roadmap implementation of the METADATA / ANNOTATE extensions is fairly high on the list. I was just curious if there is a target release in mind for this functionality?

2 1

[Dovecot] Overloading IMAP Server
by Harford, Ken 04 Feb '13

04 Feb '13

Hi All, I am having an issue with dovecot IMAP reading and writing to one specific mailbox. I have a check email delivery script that sends out a email and then logs into dovecot to check if the mailbox that the message has been delivered to. However, the servers that send these messages send them in bunches depending on how many postfix spools it is checking. So I could get 60 messages all being sent to 1 mailbox and then having to read that same mailbox to check if the message actually got delivered. I am using postfix as the MTA and dovecot is actually delivering the message to the mailbox I am getting a lot of errors such as the following: Could not connect to IMAP server imap failed: IMAP RECEIVE CRITICAL - Could not select INBOX Any ideas as to what I can tweak in dovecot to allow these messages to be verified. Thanks for any information or help you could provide!! Ken

3 5

[Dovecot] cmsg cancel <keh8l6$3c9$1@de-l.enfer-du-nord.net>
by Michael Grimm 01 Feb '13

01 Feb '13

ignore Article cancelled by slrn 1.0.1

1 0

[Dovecot] Reviewing end-user ham/spam submissions before feeding them to sa-learn via Dovecot Antispam plug-in
by Ben Johnson 01 Feb '13

01 Feb '13

Currently, I'm using the Dovecot Antispam plug-in with great success. Everything works as expected. However, I would like to change the plug-in's behavior such that it simply sends a copy of a message that is moved from Inbox -> Junk (or Junk -> Inbox) to an administrator, instead of calling sa-learn (I'm using SpamAssassin) automatically. Basically, I would like to be able to review messages that end-users submit for training before they are actually fed to sa-learn. Has anyone had a similar need? If the Antispam plug-in already supports this, if the necessary commands can simply be added to the shell script that Antispam calls, or if there is a better method altogether, any help is greatly appreciated. Thank you! -Ben

2 4