- dovecot - dovecot.org

Problem: mail moved by thunderbird script is invisible to mail clients, but in cur directory
by David Gessel 18 Apr '15

18 Apr '15

Over the last year I've had a script moving old mail (120 days) into my annual archive folder. This is the first year I've done this with Dovecot, previously it was running against Cyrus. There's nothing particularly clever: a few conditions to match, then "move message to" the appropriate archive folder. There's one for every year from 2000 to 2015. 2015 is just barely ahead of need. 2014 has about a year's mail in the cur directory. The 2000-2013 folders were filled by Cyrus and were migrated over using IMAP Migrate. They're fine, and read normally. The 2014 layout looks normal to me # ls cur dovecot-uidlist dovecot.index.cache dovecot.index.log.2 new dovecot-keywords dovecot.index dovecot.index.log maildirfolder tmp Permissions are the same as every other folder, as is owner: drw-r----- 2 vmail vmail 9.6K Apr 12 21:13 cur and # ls | wc -l 9822 I've checked with Thunderbird, Mulberry, Claws, and Sylpheed - none can read the directory. The files look normal: 2014/cur 1426411329.M123928P26360.host.domain.com,S=3523,W=3591:2,R More or less the same as a working directory: 2013/cur 1405500734.M958596P27867.host.domain.com,S=794,W=819:2,RS I've run # doveadm force-resync -u user .archives.2014 and nothing changed. I'm at a bit of a loss since no client can read them, something like moving them to another folder and back is a little complicated. Any hints?

3 3

ManageSieve Dovecot v2 listen on localhost only
by trash＠skrilnetz.net 17 Apr '15

17 Apr '15

Hi, How can I only listen on localhost for ManageSieve? I tried: port = localhost:4190 still listening *: tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 0 515675 20540/dovecot Would did I not get here? Thanks,

3 5

Replace autocreate after upgrading
by trash＠skrilnetz.net 17 Apr '15

17 Apr '15

Hi, I just upgraded to 2.2.9 and found out that autocreate should not be used any more. I had a look at http://wiki2.dovecot.org/MailboxSettings and I tried to replace my old config but I had no success. Would somebody be so and help me to change my config? Here is my old config: http://pastebin.com/zFUAQmV3 Thanks,

2 1

Potentially breaking dict-proxy (dict-sql) backwards compatibility
by Timo Sirainen 17 Apr '15

17 Apr '15

Looks like the dict-proxy code doesn't currently do escaping newlines properly, but it still accidentally happens to work, because the data is stored in the escaped form. I'm thinking about fixing this, but this might break somebody's existing dict usage. But then again maybe nobody is actually using it now, especially because it hasn't been working exactly as expected. So, can anybody tell me if they're currently using a combination of: - dict proxy (especially to dict sql) - containing values which can contain LFs (or TABs) I guess this mainly means storing Sieve scripts or IMAP METADATA to SQL. Or maybe somebody is using dict (via proxy) for their own purposes?..

1 0

Calendar and address book with Dovecot
by mimicafe＠gmail.com 16 Apr '15

16 Apr '15

Hi guys Thanks for all your input. I'll feedback later... Mimi

1 0

Thunderbird sync time? (reverse quota warning)
by E.B. 16 Apr '15

16 Apr '15

For reverse quota warning, it looks like webmail works nice. quota_warning3 = -storage=100%% quota-warning below %u # user is no longer over quota But using thunderbird I deleted enough messages to go below quota and I deleted them from trash folder too. But mail log does not show thunderbird connecting to imap to actually delete mails and get the trigger below quota warning msg. It's i thinks a thundrbrd behavior but i wonder if anyone on this list knows how it works? Do i just keep waiting for it to sync eventually? or??????? TIA!

2 3

Dovecot and recipient_delimiter
by J. Echter 16 Apr '15

16 Apr '15

Hi, we're using thunderbird as our client, it has the functionality to sort spamassassin tagged mails in a folder called 'Junk'. I have this folder on my dovecot server and i'd like to use the recipient_delimiter feature to get my spam/junk mails directly to this folder. what i have done yet: dovecot.conf: plugin { recipient_delimiter = + } postfix: master.cf dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail null_sender= argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} -e -m ${extension} postfix: main.cf recipient_delimiter = + what i get: Apr 14 13:46:50 mule postfix/pickup[22664]: 71ED53C05EE: uid=0 from=<testuser(a)testdomain.test> Apr 14 13:46:50 mule postfix/cleanup[1408]: 71ED53C05EE: message-id=<552cfe2a.tR3wZK7y16RgA548%testuser(a)testdomain.test> Apr 14 13:46:50 mule postfix/qmgr[12559]: 71ED53C05EE: from=<testuser(a)testdomain.test>, size=465, nrcpt=2 (queue active) Apr 14 13:46:50 mule dovecot: lda(testuser(a)testdomain.test): msgid=<552cfe2a.tR3wZK7y16RgA548%testuser(a)testdomain.test>: save failed to junk: Mailbox doesn't exist: junk Apr 14 13:46:50 mule dovecot: lda(testuser(a)testdomain.test): msgid=<552cfe2a.tR3wZK7y16RgA548%testuser(a)testdomain.test>: saved mail to INBOX Apr 14 13:46:50 mule postfix/pipe[10898]: 71ED53C05EE: to=<testuser+Junk(a)testdomain.test>, relay=dovecot, delay=0.04, delays=0.02/0/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) Apr 14 13:46:50 mule postfix/qmgr[12559]: 71ED53C05EE: removed here is my complete dovecot -n output: dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-504.12.2.el6.x86_64 x86_64 CentOS release 6.6 (Final) ext4 auth_cache_negative_ttl = 0 auth_cache_size = 50 M auth_verbose = yes base_dir = /var/run/dovecot/ imap_id_log = * imap_id_send = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = 5000 mail_home = /DATEN/vmail/%d/%n mail_location = maildir:/DATEN/vmail/%d/%n/mail/ mail_plugins = " zlib" mail_uid = 5000 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 = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { autocreate = Junk autosubscribe = Junk recipient_delimiter = + sieve = /DATEN/vmail/%d/%n/.dovecot.sieve sieve_dir = /DATEN/vmail/%d/%n/sieve zlib_save = gz zlib_save_level = 6 } protocols = sieve imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = root } service imap-login { chroot = login executable = /usr/libexec/dovecot/imap-login inet_listener imap { port = 0 } process_min_avail = 4 user = dovecot } service imap { executable = /usr/libexec/dovecot/imap } service managesieve-login { chroot = login user = dovecot } service pop3-login { chroot = login user = dovecot } ssl = required ssl_cert = </shared/config/dovecot/certs/dovecot.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL:!EXPORT ssl_key = </shared/config/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } valid_chroot_dirs = /var/spool/vmail protocol lda { mail_plugins = sieve postmaster_address = postmaster } any hints on what i do wrong here? thanks juergen

2 4

Disk space usage with mdbox
by Alexandros Soumplis 15 Apr '15

15 Apr '15

Hello, I am using dovecot with mdbox+sis and I notice an ever increasing disk space usage since I converted mailboxes from Maildir to mdboxes. I have checked with a user and while it actually uses only 65K, his mdbox files on disk are more than 6G. The backup of his mailbox is just 64K. Any suggestions ? Below are some relevant commands: [root@mail ~]# doveadm quota get -u test Quota name Type Value Limit % User quota STORAGE 10135 31457280 0 User quota MESSAGE 186 - 0 [root@mail ~]# du -k --max-depth=1 /mdboxes/test/ 220 /mdboxes/test/mailboxes 6029348 /mdboxes/test/storage 6029592 /mdboxes/test/ [root@mail ~]# doveadm purge -u test [root@mail ~]# du -k --max-depth=1 /mdboxes/test/ 220 /mdboxes/test/mailboxes 6029348 /mdboxes/test/storage 6029592 /mdboxes/test/ [root@mail ~]# doveadm backup -u test mdbox:/tmp/MDBOX_TEMP/ [root@mail ~]# du -k --max-depth=1 /tmp/MDBOX_TEMP/ 16 /tmp/MDBOX_TEMP/mailboxes 65540 /tmp/MDBOX_TEMP/storage 65568 /tmp/MDBOX_TEMP/

4 9

setting service_count results in Permission denied
by Micah Anderson 15 Apr '15

15 Apr '15

The load on our machines has gotten too high, so I started to see log messages that directed me to look at this page for config changes: https://pad.riseup.net/redirect#http%3A//wiki2.dovecot.org/SocketUnavailable One of the things I wanted to do on that page was to set the: service imap { service_count = 100 } but when I added that to the service imap block, and restarted dovecot, I see this in the logs: Error: net_connect_unix(/run/dovecot/imap-postlogin) failed: Permission denied I dont understand how this impacts permissions. Its clearly this setting, because when I remove it, things work again. I found nothing else in the logs indicating a configuration problem. This is what the config block looked like: service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = 256M # Max. number of IMAP processes (connections) process_limit = 4096 service_count = 100 executable = imap imap-postlogin } service imap-postlogin { # the script process runs as the user specified here (v2.0.14+): #user = $default_internal_user executable = script-login /usr/local/sbin/postlogin_imap # this UNIX socket listener must use the same name as given to imap executable unix_listener imap-postlogin { } } This is with dovecot 2.2.13, thanks for any help you can provide! micah

4 3

concurrent IMAP connections (plus 2 easy questions)
by Ron Cleven 15 Apr '15

15 Apr '15

I posted a few days back asking about configuration issues with a modestly large number of IMAP connections. Several people were kind enough to respond with various ideas. Armed with those ideas and Google, I was able to determine the underlying configuration issues with CentOS 7 and Dovecot 2.2.10. I did some further benchmarking to ensure that we could properly plan our server configuration requirements as we continue to roll this out, so I thought I would share this, partly to see if anyone has experiences that conflict with my findings. I found that each incremental dovecot IMAP process required about 750k of RAM. Simulations confirmed that 8 gig of RAM was sufficient to support approximately 10,000 concurrent IMAP connections (no POP3). CentOS settings: Added: fs/inotify/max_user_instances = 28000 to: /etc/sysctl.d/99-sysctl.conf Added: * hard nproc 28000 * soft nproc 28000 * hard nofile 28000 * soft nofile 28000 to: /etc/security/limits.d/20-nproc.conf To verify the settings after reboot: cat /proc/sys/fs/inotify/max_user_instances ulimit -Hn ulimit -Sn Dovecot: Added: process_limit = 28000 to service imap{} /etc/dovecot/conf.d/10-master.conf Added (using proxies, would like to just turn off this check): mail_max_userip_connections = 40 to protocol imap {}: /etc/dovecot/conf.d/20-imap.conf Added: process_limit = 28000 to service managesieve {}: /etc/dovecot/conf.d/20-managesieve.conf Hope this helps someone. Feedback would be welcome. It would be great if there was a blessed cookbook for Dovecot scaling. At this point it seems a bit like an art form. Now to my two "easy" questions. 1) TCP replication between our two CentOS boxes has been working great, no complaints. However, I realized I did not know how to check the status of replications, as one might want to do if one of the two boxes was taken offline for maintenance or repair. On the surface, it would appear that the command: doveadm replicator status '*' would likely show me what I want to know. However, when I tried it, I got: doveadm(): Fatal: net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: No such file or directory The documentation says that doveadm assumes the socket /var/run/dovecot/replicator-doveadm and the command format provides a "-a" override. In that directory, there is no "replicator-doveadm" socket, but I do see a "replicator" socket. So, should I be using the command: doveadm replicator status -a /var/run/dovecot/replicator '*' or is the non-existence of the replicator-doveadm socket indicative of something I might have done wrong with the config? I hate experimenting more than I have to with a production box. The 2.2.10 Dovecot I am running was installed via yum, so there are no potential compilation issues. 2) It seems logical to me that: dovecot stop would first lock out any new user connections, then do the equivalent of a: doveadm kick "*" before actually cycling everything else down to ensure the shutdown is as graceful as possible. I suppose I could experiment and find out for certain, but I have the sense that the "stop" command is not quite that elegant, so we have implemented procedures to work around it. Just a point of curiosity. An alternative would be if there was a doveadm command to lock out any new user connections, which could then be followed by kick and stop. I have found that many clients are VERY quick to reconnect after a kick.

2 1