- dovecot - dovecot.org

[Dovecot] imap-login process_limit reached
by Don Buchholz 29 Jan '12

29 Jan '12

I've been having some problems with IMAP user connections to the Dovecot (v2.0.8) server. The following message is being logged. Jan 16 10:51:36 postal dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped The server is running Red Hat Enterprise Linux release 4 (update 6). Dovecot is v2.0.8. We have only 29 user accounts in /etc/dovecot/users. There were 196 "dovecot/imap" processes and 6 other dovecot processes, for a total of 202 "dovecot" processes, listed in the 'ps aux' output when problems were being experienced. Stopping and restarting the Dovecot system fixes the problem -- for a while. The 'doveconf -n' output is attached. I have not set any "process_limit" values, and I don't think I'm getting anywhere close to the 1024 default, so I'm pretty confused as to what might be wrong. Any suggestions on what to do next are appreciated. Thanks, - Don ------------------------------------------------------------------------ # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.9-67.0.1.ELsmp i686 Red Hat Enterprise Linux WS release 4 (Nahant Update 6) ext3 auth_username_format = %Lu auth_verbose = yes auth_verbose_passwords = sha1 login_log_format_elements = user=<%u> service=%Us method=%m rip=%r lip=%l mpid=%e %c login_trusted_networks = xx.xx.xx.0/24 mail_location = maildir:/Virtual_Users/%u/Mail passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } passdb { driver = pam } ssl_ca = </etc/dovecot/ssl/iMove_2011_CAcert.pem ssl_cert = </etc/dovecot/ssl/postal_cert.pem ssl_key = </etc/dovecot/ssl/postal_key+req.pem ssl_key_password = ********** ssl_parameters_regenerate = 12 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } userdb { driver = passwd } verbose_proctitle = yes protocol imap { ssl_cert = </etc/dovecot/ssl/imap_cert.pem ssl_key = </etc/dovecot/ssl/imap_key+req.pem ssl_key_password = </etc/dovecot/ssl/imap.pw } protocol pop3 { ssl_cert = </etc/dovecot/ssl/pop3_cert.pem ssl_key = </etc/dovecot/ssl/pop3_key+req.pem ssl_key_password = </etc/dovecot/ssl/pop3.pw }

5 16

[Dovecot] XFS Developer Takes Shots At Btrfs, EXT4
by Adrian Minta 29 Jan '12

29 Jan '12

Nice article about XFS improvements: http://tinyurl.com/7pvr9ju

2 2

[Dovecot] 2.1.rc1 (056934abd2ef): virtual plugin mailbox search pattern
by e-frog 29 Jan '12

29 Jan '12

Hello Timo, With dovecot 2.1.rc1 (056934abd2ef) there seems to be something wrong with virtual plugin mailbox search patterns. I'm using a virtual mailbox 'unread' with the following dovecot-virtual file $ cat dovecot-virtual * unseen For testing propose I created the following folders with each containing one unread message INBOX, INBOX/level1 and INBOX/level1/level2 2.1.rc1 (056934abd2ef) 1 LIST "" "*" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasChildren) "/" "INBOX/level1" * LIST (\HasNoChildren) "/" "INBOX/level1/level2" * LIST (\HasChildren) "/" "virtual" * LIST (\HasNoChildren) "/" "virtual/unread" 1 OK List completed. 2 STATUS "INBOX" (UNSEEN) * STATUS "INBOX" (UNSEEN 1) 2 OK Status completed. 3 STATUS "INBOX/level1" (UNSEEN) * STATUS "INBOX/level1" (UNSEEN 1) 3 OK Status completed. 4 STATUS "INBOX/level1/level2" (UNSEEN) * STATUS "INBOX/level1/level2" (UNSEEN 1) 4 OK Status completed. 5 STATUS "virtual/unread" (UNSEEN) * STATUS "virtual/unread" (UNSEEN 1) 5 OK Status completed. Result: virtual/unread shows only 1 unseen message. Further tests showed it's the one from INBOX. The mails from the deeper levels are not found. Downgrading to 2.0.16 restores the correct behavior: 1 LIST "" "*" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasChildren) "/" "INBOX/level1" * LIST (\HasNoChildren) "/" "INBOX/level1/level2" * LIST (\HasChildren) "/" "virtual" * LIST (\HasNoChildren) "/" "virtual/unread" 1 OK List completed. 2 STATUS "INBOX" (UNSEEN) * STATUS "INBOX" (UNSEEN 1) 2 OK Status completed. 3 STATUS "INBOX/level1" (UNSEEN) * STATUS "INBOX/level1" (UNSEEN 1) 3 OK Status completed. 4 STATUS "INBOX/level1/level2" (UNSEEN) * STATUS "INBOX/level1/level2" (UNSEEN 1) 4 OK Status completed. 5 STATUS "virtual/unread" (UNSEEN) * STATUS "virtual/unread" (UNSEEN 3) 5 OK Status completed. Result: virtual/unread shows 3 unseen messages as it should The namespace configuration is as following namespace { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } namespace { location = virtual:~/virtual prefix = virtual/ separator = / subscriptions = no type = private } I've also tried this with location = virtual:~/virtual:LAYOUT=maildir++ leading to the same result. Thanks, e-frog

2 3

[Dovecot] Migration to multi-dbox and SiS
by Ronald MacDonald 29 Jan '12

29 Jan '12

Dear list, A huge thank-you first of all for all the work that's gone into Dovecot itself. I'm rebuilding a mail server next week and so, taking the rare opportunity to re-consider all the options I've had running over the past couple of years. Around the time of the last re-build (2010), there had been some discussion on single instance storage, which was quite new on Dovecot around then. I chickened out of setting it up though. Now with it having been in the wild for a couple of years, I wonder, how have people found SiS to behave? Additionally, though there was talk of the prospect of it being merged with 2.x am I right in thinking it's not yet in the main project? Couldn't find any 2.x changelogs that could confirm this. With best wishes, Ronald.

2 1

[Dovecot] Attribute Cache flush errors on FreeBSD 8.2
by Phil Kernick 29 Jan '12

29 Jan '12

I'm running dovecot 2.0.16 on FreeBSD 8.2 with the mail spool and indexes on an NFS server. Lines like the following keep appearing in syslog for access to each mailbox: Error: nfs_flush_attr_cache_fd_locked: fchown(/home/philk/Mail/Deleted) failed: Bad file descriptor This is coming from nfs-workarounds.c line 210, which tracing back seems to be coming from the call to mbox_lock on lib-storage/index/mbox/mbox-lock.c line 774. I have /home mounted with options acregmin=0,acregmax=0,acdirmin=0,acdirmax=0 (as FreeBSD doesn't have a noac option), but it throws the same error either way. The output of dovecot -n is below. Phil. # 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE-p3 i386 auth_mechanisms = plain login auth_username_format = %Lu disable_plaintext_auth = no first_valid_gid = 1000 first_valid_uid = 1000 listen = *, [::] mail_fsync = always mail_location = mbox:~/Mail/:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mmap_disable = yes passdb { args = session=yes dovecot driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = blocking=yes driver = passwd } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { postmaster_address = postmaster(a)example.com sendmail_path = /usr/sbin/sendmail }

2 1

[Dovecot] 2.0.17: Index lost -> SAVEDON lost as well?
by Ralf Hildebrandt 29 Jan '12

29 Jan '12

Today I encoundered these errors: Jan 9 08:30:06 mail dovecot: lmtp(31174, backup(a)backup.invalid) Error: Log synchronization error at seq=858,offset=44672 for /home/mailboxname/mdbox/storage/dovecot.map.index: Append with UID 282388, but next_uid = 282389 Jan 9 08:30:06 mail dovecot: lmtp(31819, backup(a)backup.invalid) Error: Log synchronization error at seq=858,offset=44672 for /home/mailboxname/mdbox/storage/dovecot.map.index: Append with UID 282388, but next_uid = 282389 Jan 9 08:30:06 mail dovecot: lmtp(32148, backup(a)backup.invalid) Error: Log synchronization error at seq=858,offset=44672 for /home/mailboxname/mdbox/storage/dovecot.map.index: Append with UID 282388, but next_uid = 282389 After that, the SAVEDON date for all mails was reset to today: mail:~# doveadm search -u backup(a)backup.invalid mailbox INBOX SAVEDON 2012-01-09 | wc -l 75650 mail:~# doveadm search -u backup(a)backup.invalid mailbox INBOX SAVEDON 2012-01-08 | wc -l 0 mail:~# doveadm search -u backup(a)backup.invalid mailbox INBOX SAVEDON 2012-01-07 | wc -l 0 Before, I was running this: vorgestern=`date -d "-2 day" +"%Y-%m-%d"` doveadm expunge -u backup(a)backup.invalid mailbox INBOX SAVEDBEFORE $vorgestern doveadm purge -u backup(a)backup.invalid Is there a way of restoring the SAVEDON info? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 4

[Dovecot] compressed mboxes very slow
by kjonca＠o2.pl 29 Jan '12

29 Jan '12

I have some archive mails in gzipped mboxes. I could use them with dovecot 1.x without problems. But recently I have installed dovecot 2.0.12, and they are slow. very slow. Creating index files takes about 10 minutes for ~20M file with 560 messages for bzipped mbox, for gzipped is little better but still unusable :( Stracing dovecot process shows that every ~ 20 messages it rereads complete mbox file. Am I doing something wrong? KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewsk…

4 13

[Dovecot] maildir vs mdbox
by Jean-Daniel Beaubien 29 Jan '12

29 Jan '12

Hi, I am planning on running on test between maildir and mdbox to see which is a better fit for my use case. And I'm just looking for general advice/recommendation. I will post any results I obtain here. Important question: I have multiple users hitting the same email account at the same time. Can be a problem with mdbox? (either via thunderbird or with custom webmail apps). I remember having huge issues with mbox a decade ago because of this. Maildir fixed this... will mdbox reintroduce this problem? This is a very important point for me. Here is my use case: - Ubuntu server (any specific recommandations on FS to use?) - Standard PC hardware (core i5 or i7, few gigs of ram, hdds at first, probably ssd afterwards, nothing very fancy) - Serving only a hand full of email accounts but some of the accounst have over 3 millions emails in them (with individual mail folders having 100k+ emails) - Will use latest dovecot (2.1 when it comes out) - fts-lucene or fts-solr? -jd

2 5

[Dovecot] sieve under lmtp using wrong homedir ?
by Frank Post 29 Jan '12

29 Jan '12

Hi, i have a problem with dovecot-2.0.15. All is working well except lmtp. Sieve scripts are correctly saved under /var/vmail/test.com/test/sieve, but under lmtp sieve will use /var/vmail//testuser/ Uid testuser has mail=test(a)test.com configured in ldap. As i could see in the debug logs, there is a difference between the auth "master out" lines, but why ? working if managesieve stores scripts: Jan 11 15:02:42 auth: Debug: master in: REQUEST 3533701121 23001 1 7ec31d3c65cb934785e8eb0f33a182ae Jan 11 15:02:42 auth: Debug: ldap(test(a)test.com,10.234.201.4): result: mail(user)=test(a)test.com Jan 11 15:02:42 auth: Debug: master out: USER 3533701121 test(a)test.com home=/var/vmail/test.com/test uid=5000 gid=5000 Jan 11 15:02:42 managesieve(test(a)test.com): Debug: Effective uid=5000, gid=5000, home=/var/vmail/test.com/test but under lmtp not: Jan 11 14:39:53 auth: Debug: master in: USER 1 testuser service=lmtp lip=10.234.201.9 rip=10.234.201.4 Jan 11 14:39:53 auth: Debug: auth(testuser,10.234.201.4): username changed testuser -> test(a)test.com Jan 11 14:39:53 auth: Debug: ldap(test(a)test.com,10.234.201.4): result: mail(user)=test(a)test.com Jan 11 14:39:53 auth: Debug: master out: USER 1 test(a)test.com home=/var/vmail//testuser uid=5000 gid=5000 Jan 11 14:39:53 lmtp(8499): Debug: auth input: test(a)test.com home=/var/vmail//testuser uid=5000 gid=5000 Jan 11 14:39:53 lmtp(8499): Debug: changed username to test(a)test.com Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: Effective uid=5000, gid=5000, home=/var/vmail//testuser Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: Quota root: name=User quota backend=maildir args= Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: Quota rule: root=User quota mailbox=* bytes=2147483648 messages=0 Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: Quota warning: bytes=1932735283 (90%) messages=0 reverse=no command=quota-warning 90 test(a)test.com Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: maildir++: root=/var/vmail/test.com/test/Maildir, index=/var/dovecot/indexes/test.com/test, control=, inbox=/var/vmail/test.com/test/Maildir, alt= Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: trash: No trash setting - plugin disabled Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: pla8CymRDU8zIQAAFrfQGQ: sieve: user's script path /var/vmail//testuser/.dovecot.sieve doesn't exist (using global script path in stead) Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: pla8CymRDU8zIQAAFrfQGQ: sieve: user has no valid personal script Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: pla8CymRDU8zIQAAFrfQGQ: sieve: no scripts to execute: reverting to default delivery. Jan 11 14:39:53 lmtp(8499, test(a)test.com) Debug: Namespace : Using permissions from /var/vmail/test.com/test/Maildir: mode=0700 gid=-1 Thanks, for your help. Frank

2 1

Re: [Dovecot] A small bug and a question about CONTEXT=SEARCH
by Anders 29 Jan '12

29 Jan '12

On Tue, 2012-01-10 at 15:05 +0100, Anders wrote: > > the socket connection being closed without warning: > > UID SEARCH RETURN (SAVE COUNT) CHARSET UTF-8 (UNDELETED TEXT "foo") > > You mean it closes with above also? It works fine with me. No, that also works fine here :-) > > UID SEARCH RETURN (COUNT MIN) CHARSET UTF-8 () $ > > This was fixed in v2.0.17. Great, thanks! > > Then I have question about RFC5267 and the announcement of > > CONTEXT=SEARCH > > in the capabilities. I think this RFC is supported by dovecot, or maybe > > just part of the RFC is supported? > > All of it is supported, as far as I know. > > At least when I include the CONTEXT ADDTO or REMOVEFROM keywords I get > > an error, > These are server notifications. Clients aren't supposed to send them. Sorry, apparently I was a bit too fast there. ADDTO and REMOVEFROM should not be sent by a client, but I think that a client can send CONTEXT as a hint to the server, see http://tools.ietf.org/html/rfc5267#section-4.2 Thanks! Regards Anders

2 1