- dovecot - dovecot.org

[Dovecot] Connection queue full on 2.0.8
by Patrick McLean 15 Dec '10

15 Dec '10

Hi, I can't find any references to this problem on 2.x. I upgraded to 2.0.8 last night, and now I am getting these errors in the logs (along with the server refusing new connections): > Dec 8 09:46:52 orford dovecot: imap-login: Disconnected: Connection queue full (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS > Dec 8 09:47:16 orford dovecot: imap-login: Disconnected: Connection queue full (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS handshaking I have unsuccessfully tried to tweak my settings to prevent this problem, and any help would be appreciated. The server has plenty of power for increasing process limits, etc. Below is the output of "dovecot -n". We have users with some _very_ large mailboxes (~400 000 messages) so some of the limits might appear excessive.: > # 2.0.8: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.35-gentoo-r5+ x86_64 Gentoo Base System release 2.0.1 > auth_cache_size = 10 M > auth_mechanisms = plain login > auth_worker_max_count = 80 > default_client_limit = 2048 > default_process_limit = 256 > default_vsz_limit = 512 M > first_valid_uid = 125 > last_valid_uid = 20000 > listen = 127.0.0.1 x.x.x.x > login_greeting = IMAP ready. > mail_location = maildir:~/Maildir > 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 > mdbox_rotate_size = 10 M > namespace { > hidden = no > inbox = yes > list = yes > location = > prefix = > subscriptions = yes > type = private > } > namespace { > hidden = yes > list = no > location = > prefix = INBOX. > subscriptions = yes > type = private > } > namespace { > hidden = no > list = yes > location = maildir:/home/shared/Maildir:CONTROL=~/Maildir/control/shared:INDEX=~/Maildir/index/shared > prefix = shared. > subscriptions = no > type = public > } > passdb { > args = failure_show_msg=yes > driver = pam > } > plugin { > quota = fs:User quota:user > quota_warning2 = storage=80%% quota-warning 80 %u > sieve = ~/dovecot.sieve > sieve_dir = ~/sieve > } > protocols = imap pop3 > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > } > service imap-login { > process_min_avail = 5 > } > service imap { > process_limit = 2048 > } > service managesieve-login { > inet_listener sieve_deprecated { > port = 2000 > } > } > service pop3 { > process_limit = 128 > } > ssl_cert = </etc/ssl/dovecot/imap.crt > ssl_key = </etc/ssl/dovecot/imap.key > userdb { > driver = passwd > } > verbose_proctitle = yes > protocol lda { > mail_plugins = sieve quota > } > protocol imap { > mail_max_userip_connections = 10 > mail_plugins = " quota imap_quota acl" > } > protocol sieve { > mail_max_userip_connections = 10 > } > protocol pop3 { > mail_max_userip_connections = 3 > pop3_uidl_format = %u-%v > ssl_cert = </etc/dovecot/certs/pop3.pem > ssl_key = </etc/dovecot/certs/pop3.key > }

3 7

[Dovecot] question about snarf plugin in dovecot 2
by Tom Lieuallen 15 Dec '10

15 Dec '10

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that mail_location be updated to point at ~/mbox for INBOX. However, with the optional snarfing, sometimes inbox will be at /var/mail and for some users, it'll be ~/mbox. What, if anything, do I do to mail_location? Does it matter where (in which config file) the plugin block is placed? I put all of my snarf configuration in 10-mail.conf. It's not working; not snarfing and not reading mail from ~/mbox (how would it, I have yet to tell it to). The following are excerpts from 10-mail.conf mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/a2/imap-index/%u .... namespace { type = private separator = / prefix = inbox = yes } .... namespace snarf { prefix = /snarf separator = / location = mbox:/private/dovecot/var/run/dovecot/empty:INBOX=/var/mail/%u:INDEX=MEMORY list = no hidden = yes } plugin { snarf = /snarf/INBOX mbox_snarf = ~/mbox } Thank you BTW, the dovecot-2.0.7/docs/wiki appear to be from wiki1, not wiki2... :-) Tom Lieuallen Oregon State University

3 5

[Dovecot] After-delivery sieve processing
by Daniel L. Miller 14 Dec '10

14 Dec '10

Is it possible to run sieve against an existing mailbox? My application: I've got a mailbox that stores status messages from multiple sites. It's easier to check up on recent events by having them all in one folder. However, after I've read them, I'd like to have them archived to individual folders per site. I currently have a sieve script that uses "fileinto" to sort the mails - but I'm thinking of removing it from deliver if I can run it as a manual job later. I suppose another method would be to duplicate the mails on delivery into both the main folder and the per site folders, then delete after I've read them - but for whatever reason that strikes me as inelegant. -- Daniel

1 0

[Dovecot] Migration from UW-IMAP
by Daniel Senie 14 Dec '10

14 Dec '10

I am attempting to test out dovecot on a server on a separate IP address from the live, functioning UW-IMAP. I am having mixed results with dovecot. An entirely new account that's never been used with UW-IMAP seems to work fine, but that's really not the point of the exercise. If I try changing over an existing account to use dovecot, I get a variety of issues. Testing with Apple Mail.app, if I synchronize the account, the INBOX stops displaying. So off to plan B, and debug via command line commands. I tried connecting to Dovecot. It was able to list the mailboxes for me. I asked for status on INBOX. Sometimes I get an error back in the IMAP stream, sometimes not. Either way, the log shows complaints about creating mail/.imap and below (we use mbox format, plus /var/mail/%u for inbox). I have active namespace compatibility recommended by the Wiki so that clients specifying "mail/" and clients not specifying an imap path both work. With the test account, I proved this functionality is working. At this point I clearly have some issues, and could use some help figuring out what to ask for help with, i.e. how to proceed to debug this without damaging the existing UW-IMAP setup in the process. The goal is to cut over to dovecot once I can be sure it really is working compatibly, but until then I have a large user base and can't blow everything up. And yes, I really, truly have RTFM (i.e. read the Wiki, the troubleshooting pages, the migration pages).

2 2

[Dovecot] Incorrect W value after filesystem corruption
by Bob 14 Dec '10

14 Dec '10

Dec 14 00:15:54 vm dovecot: IMAP(####@####): Maildir filename has wrong W value: /var/vmail/#####/####/cur/#########.M###########.??.????.??.??,S=4951,W=5057:2,RSa Dear Dovecot elite, This morning I woke up to find my mail server hard disk controller had gone crazy and decided to corrupt my file system. After over eight passes with the fsck and a new machine I have mostly recovered but this being a personal server the backups were a half-job. So for speed I recovered the mail directly off the bad file system. Most of the data was fine but a few files were corrupt and as a result I have found Dovecot to be a real pain when it comes to handling a wrong W value. I am having to separately look at the mail.log and just systematically remove the W value as a quick work-around. But it seems to me that it would be much easier to have this done by Dovecot when it realises it has this wrong value, especially as Dovecot seems to drop the connection of that user after encountering this problem. Can I suggest as an improvement this scenario is handled better? I saw one posting which said "this should never happen" but clearly it can and I think there could be better handing of it perhaps? Regards, Bob ============== I am configured as vmail with MySQL back-end, postfix, policyd-weight and mailscanner. # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.7 ext3 base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_cert_file: xxx ssl_key_file: xxx login_dir: /var/run/dovecot//login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_max_userip_connections(default): 30 mail_max_userip_connections(imap): 30 mail_max_userip_connections(pop3): 10 first_valid_uid: 150 last_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:/var/vmail/%d/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 lda: postmaster_address: postmaster(a)orbit.me.uk sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/auth-master mail_plugins: sieve auth default: user: nobody passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: trash: /etc/dovecot/dovecot-trash.conf sieve: /var/vmail/%d/%u/.sieve sieve_global_path: /var/vmail/globalsieverc

2 1

[Dovecot] Courier-mta with Dovecot LDA
by komodo 14 Dec '10

14 Dec '10

Hi all I have setup dovecot lda instead of maildrop on my courier server. Delivery is working, sieve plugin too, but i can't figure out why lda can't send emails via sendmail (vacation). I always get error Error: Sendmail process terminated abnormally, exit status 67 And i know why, but i don't know how to setup lda to make it work . Here is .courier file where is redirect to lda. | /usr/libexec/dovecot/deliver -a $RECIPIENT -f $SENDER But the deliver does not pass recipient address to sendmail. Here is some output of strace execve("/usr/libexec/dovecot/deliver", ["/usr/libexec/dovecot/deliver", "-a", "komodo@somedomain", "-f", "someuser@somedomain"], [/* 22 vars */]) = 0 So it's clear that deliver have those variables, but then i can see this execve("/usr/sbin/sendmail", ["/usr/sbin/sendmail", "-i", "-f", "<>", "--", "someuser@somedomain"], [/* 2 vars */] <unfinished ...> And there is empty -f , so here is the problem. How should i setup this to make it work correctly ? Here is my config [root(a)OVZ.mail ~]# dovecot -n # 2.0.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.8.1.el5.028stab070.5 x86_64 CentOS release 5.5 (Final) disable_plaintext_auth = no hostname = ovzmail listen = 10.0.10.34 mail_location = maildir:~/Maildir 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 mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace { location = maildir:/home/shared/Maildir prefix = spam_learner. separator = . type = public } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve ssl_cert = </etc/pki/dovecot/certs/server.pem ssl_key = </etc/pki/dovecot/private/server.pem userdb { driver = prefetch } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 40 } Many thanks Martin

1 0

[Dovecot] WLM and dovecot
by Agim Cami 14 Dec '10

14 Dec '10

Windows Live Mail seems to be a nice IMAP client! Do you have good or bad experiences of WLM with dovecot as server? Thanks!

1 0

[Dovecot] FTS and compound searches
by Tony Pyro 13 Dec '10

13 Dec '10

Hello, New subscriber here. I noticed that the FTS index is not used in compound searches. Is this expected? Tested in 2.0.0 and 2.0.8: . search BODY "waldo" * SEARCH . OK Search completed (0.000 secs). . SEARCH CHARSET UTF-8 OR SUBJECT "waldo" FROM "waldo" * SEARCH . OK Search completed (1.768 secs). . SEARCH CHARSET UTF-8 OR SUBJECT "waldo" BODY "waldo" * OK Searched 0% of the mailbox, ETA 9605:25 * OK Searched 4% of the mailbox, ETA 6:39 * OK Searched 6% of the mailbox, ETA 6:58 * OK Searched 8% of the mailbox, ETA 6:54 It's a problem for us because the Afterlogic webmail client does not offer a body-only search. The two search options are From + To + Subject, or "entire messages", which puts together a large OR query: SRCH1069 SEARCH CHARSET UTF-8 OR (OR (OR FROM "waldo" TO "waldo") SUBJECT "waldo") BODY "waldo" I also checked to see whether the header fields are included in the FTS index but it didn't appear so. I got more results from the search "TO gmail.com" than from "BODY gmail.com" plugin { fts = squat } protocol imap { mail_plugins = " fts fts_squat" } Thanks!

3 4

[Dovecot] postfix-dovecot-sasl help
by Ted To 13 Dec '10

13 Dec '10

I'm trying to set up SMTP authentication on my server and am getting an authentication failed error. My client is set up to automatically select authentication method and tries CRAM_MD5. The http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL suggests "passdb pam" and "userdb passwd" -- is it possible to configure sasl authentication using a dovecot.conf like http://pastebin.com/6JWE5jp1? Thanks in advance, Ted To

3 7

[Dovecot] Question about "slow" storage but fast cpus, plenty of ram and dovecot
by javierdemiguel＠us.es 13 Dec '10

13 Dec '10

Hello We are using dovecot 1.2.x. In our setup we will have 1200 concurrent imap users (maildirs) and we have 2xraid5 sas 15k diks mounted by iSCSI. The dovecot server (RHEL 5 x64) is a virtual machine in our vmware esx cluster. We want to minimize disk I/O, what config options should we use. We can "exchange" CPU & RAM to minimize disk i/o. Should we change to dovecot 2.0? Maybe mdbox can help us? Maybe ext4 instead of ext3? Any idea is welcome. Regards Javier

7 9