- dovecot - dovecot.org

[Dovecot] Dovecot Inactivity Problem
by vipin＠barc.gov.in 09 Sep '07

09 Sep '07

Hi, We are using dovecot version 1.0.3. We have dovecot-ldap configured to authenticate users using ldap database. We are facing the inactivity problem with dovecot. After some hrs of successful working, dovecot logs shows the connection inactive problem with pop3 & imap server, & it starts rejecting the connection requests from clients. The problem goes away once we restart dovecot. The problem occurs again & again after some random time. Please help us in solving this problem. The output of dovecot -n command is as follows: # 1.0.3: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_max_processes_count: 256 login_max_connections: 512 mail_location: mbox:~/:INBOX=%h/mbox mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf Thanks & Regards Vipin Gupta Scientific Officer Computer Division BARC, Trombay Mumbai

2 1

[Dovecot] Dovecot problem
by Raphael Bittencourt S. Costa 09 Sep '07

09 Sep '07

Helo all, Yesterday dovecot began droping connections and there is nothing conclusive in the log file, just the messagens below: Sep 2 11:43:57 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.152.100.77, lip=10.0.3.1 Sep 2 11:44:02 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.204.69.20, lip=10.0.3.1 Sep 2 11:44:19 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.20.236.248, lip=10.0.3.1 Sep 2 11:44:21 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.83.2.206, lip=10.0.3.1 Sep 2 11:44:24 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.158.0.143, lip=10.0.3.1 Sep 2 11:44:25 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.52.200.131, lip=10.0.3.1 Sep 2 11:44:26 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.53.20.53, lip=10.0.3.1, TLS Sep 2 11:44:35 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.0.90.117, lip=10.0.3.1 Sep 2 11:44:41 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=189.33.173.226, lip=10.0.3.1 Sep 2 11:44:45 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.82.135.42, lip=10.0.3.1 Sep 2 11:45:03 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.19.218.250, lip=10.0.3.1 Sep 2 11:45:04 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.83.2.206, lip=10.0.3.1 Sep 2 11:45:05 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.81.250.119, lip=10.0.3.1 Sep 2 11:45:21 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.171.100.233, lip=10.0.3.1 Sep 2 11:45:23 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=64.233.182.131, lip=10.0.3.1 Sep 2 11:45:27 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.43.185.179, lip=10.0.3.1 Sep 2 11:45:40 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.161.155.35, lip=10.0.3.1 Sep 2 11:45:41 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.62.149.20, lip=10.0.3.1 Sep 2 11:45:43 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.83.43.154, lip=10.0.3.1 Sep 2 11:45:47 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=134.171.76.5, lip=10.0.3.1 Sep 2 11:45:49 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.92.248.84, lip=10.0.3.1 Sep 2 11:45:55 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.21.114.120, lip=10.0.3.1 Sep 2 11:45:57 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.229.107.85, lip=10.0.3.1 Sep 2 11:46:04 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.204.69.20, lip=10.0.3.1 Sep 2 11:46:04 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.53.83.146, lip=10.0.3.1 Sep 2 11:46:05 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.152.100.77, lip=10.0.3.1 Sep 2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.95.95.108, lip=10.0.3.1 Sep 2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.0.90.117, lip=10.0.3.1 Sep 2 11:46:35 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=200.159.87.122, lip=10.0.3.1 Sep 2 11:46:40 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=83.131.211.245, lip=10.0.3.1 Sep 2 11:46:41 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.6.61.147, lip=10.0.3.1 Sep 2 11:47:13 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.1.153.202, lip=10.0.3.1 Sep 2 11:47:38 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=189.0.252.144, lip=10.0.3.1 Sep 2 11:47:39 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.20.236.248, lip=10.0.3.1 Sep 2 11:47:47 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=134.171.76.5, lip=10.0.3.1 Sep 2 11:47:51 relay01 dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=201.12.103.67, lip=10.0.3.1 After restart, everything just back working. Any ideia? Raphael Costa

2 1

[Dovecot] shared mailbox subfolder permissions
by David Leuschner 09 Sep '07

09 Sep '07

Hi all, when I create a subfolder in a public mailbox the dovecot-shared file is copied for the newly created subfolder and all mails get the owner, group and permissions from the file. Unfortunately the cur, new and tmp folders only get the permissions from the file but owner and group are set according to the creator. This effectivly makes the folder private to the creator. Is this the intended behavior? Is it a bug that has already been fixed in a later version? I am using 1.0.rc29. An example follows. Thanks for your help! David As an example .foobar was created manually (maildirmake) and permissions were setup using the shell: uml public # ls -al . .foobar .: total 24 drwxrwx--- 6 root pub 4096 Aug 18 13:05 . drwxrwxr-x 3 root mail 4096 Aug 18 11:10 .. drwxrwx--- 5 root pub 4096 Aug 18 11:42 .foobar drwxrwx--- 2 root pub 4096 Aug 18 10:50 cur -rw-rw---- 1 root pub 0 Aug 18 11:40 dovecot-shared drwxrwx--- 2 root pub 4096 Aug 18 10:50 new drwxrwx--- 2 root pub 4096 Aug 18 10:50 tmp .foobar: total 20 drwxrwx--- 5 root pub 4096 Aug 18 11:42 . drwxrwx--- 6 root pub 4096 Aug 18 13:05 .. drwxrwx--- 2 root pub 4096 Aug 18 11:42 cur drwxrwx--- 2 root pub 4096 Aug 18 11:42 new drwxrwx--- 2 root pub 4096 Aug 18 11:42 tmp After creating a subfolder 'baz' with Thunderbird the group of .baz is the group from dovecot-shared but the contained new/cur/tmp directories have the users primary group (instead of pub). uml public # ls -al . .baz .: total 28 drwxrwx--- 7 root pub 4096 Aug 18 13:09 . drwxrwxr-x 3 root mail 4096 Aug 18 11:10 .. drwxrwx--- 5 dleuschner pub 4096 Aug 18 13:09 .baz drwxrwx--- 5 root pub 4096 Aug 18 11:42 .foobar drwxrwx--- 2 root pub 4096 Aug 18 10:50 cur -rw-rw---- 1 root pub 0 Aug 18 11:40 dovecot-shared drwxrwx--- 2 root pub 4096 Aug 18 10:50 new drwxrwx--- 2 root pub 4096 Aug 18 10:50 tmp .baz: total 20 drwxrwx--- 5 dleuschner pub 4096 Aug 18 13:09 . drwxrwx--- 7 root pub 4096 Aug 18 13:09 .. drwxrwx--- 2 dleuschner dleuschner 4096 Aug 18 13:09 cur -rw-rw---- 1 dleuschner pub 0 Aug 18 13:09 dovecot-shared drwxrwx--- 2 dleuschner dleuschner 4096 Aug 18 13:09 new drwxrwx--- 2 dleuschner dleuschner 4096 Aug 18 13:09 tmp Here's my configuration: listen: localhost ssl_listen: * ssl_ca_file: /root/ca/ca.crt ssl_cert_file: /root/ca/crt/uml.crt ssl_key_file: /root/ca/keys/uml.key ssl_verify_client_cert: yes verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login namespace: type: private separator: . prefix: Priv. location: maildir:~/.maildir:CONTROL=~/.maildir/ctrl/priv:INDEX=~/.maildir/idx/priv inbox: yes namespace: type: public separator: . prefix: Pub. location: maildir:/var/mail/public:CONTROL=~/.maildir/ctrl/pub:INDEX=~/.maildir/idx/pub auth default: passdb: driver: pam args: * userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: -- David Leuschner Meisenweg 7 79211 Denzlingen Tel. 07666/912466

2 1

[Dovecot] SSL connections frozen on Dovecot 1.0.0
by Thibault VINCENT 09 Sep '07

09 Sep '07

Hello, We are running Dovecot 1.0.0 (Debian Etch, Backports.org, OpenSSL) in a production environment and we experience sporadic SSL connection problems. At the moment, it's difficult to tell if the server goes back to normal operation after some time or if it can be reproduces at any time because we have to restart it as soon as we get Nagios alerts. Some tests with openssl s_client have shown difficulties to proceed the SSL handshake (hanging at different stages), or no response to IMAP commands. SSL client used: openssl s_client -host imap -port 993 - First case : s_client hangs on the first output "CONNECTED(00000003)" and there is no handshake at all; - Second case : like the first but the handshake starts after a few minutes; - Third case : the handshake goes fine but the "OK" server banner is never sent (no response to commands); - Fourth case : the greeting banner is received but dovecot will never answer. The configuration file is almost identical to the default and SSL certificate is not the autogenerated one. Log files do not show dying process. I've searched the ML archive for SSL issues but not found related bug. Does anyone use the Backport.org package of Dovecot ? Thank you :) -- Thibault VINCENT tibal(a)reloaded.fr thibault.vincent(a)reloaded.fr PGP Key : 0x4BA8A39B

2 3

[Dovecot] postfix + dovecot lda,
by Michael Moritz 09 Sep '07

09 Sep '07

I'm trying to replace procmail with deliver but I'm having problems with the group part of things. I keep getting: Aug 29 16:44:19 dingbat deliver(mimo): open(/var/mail/.temp.dingbat.3969.d1689935a308e0dd) failed: Permission denied Aug 29 16:44:19 dingbat deliver(mimo): file_lock_dotlock() failed with mbox file /var/mail/mimo: Permission denied My primary group is mimo and I think it's trying to use that. I changed it to mail and things work. But I do not want all my users to have a primary group mail. Is there a way I can force deliver to use group mail as group and ignore the per user gid? I tried chmod 6755 /usr/lib/dovecot/deliver but no change. This is on debian/etch, help appreciated.... mimo

3 4

[Dovecot] too many files opened
by Joshua, C.S. Chen 09 Sep '07

09 Sep '07

Hi folks, My institute's mail server was upgraded to RHEL5 with dovecot 1.0-2.1rc5 recently. And it uses PAM authentication which points to LDAP server. Now from time to time it gets Error like dovecot: Aug 29 09:23:59 Error: auth(default): pam(joshua,192.168.177.52): pipe() failed: Too many open files and users can not login. My config is like dovecot -n # /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot listen: * login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: ASIAA Dovecot ready. login_processes_count: 4 mail_location: mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes mail_debug: yes mail_full_filesystem_access: yes mail_drop_priv_before_exec: yes mail_executable(default): /etc/dovecot_postlogin_beforeimap.sh mail_executable(imap): /etc/dovecot_postlogin_beforeimap.sh mail_executable(pop3): /etc/dovecot_postlogin_beforepop3.sh mail_process_size: 512 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu auth default: passdb: driver: pam userdb: driver: passwd Any suggestion or help is appreciated Cheers Joshua

3 3

Re: [Dovecot] Dovecot + Sieve
by Marcin Michal Jessa 09 Sep '07

09 Sep '07

> Steffen Kaiser wrote: >>>> Any idea how to fix that? >>> Second: >>> When you remove the compiled Sieve script, is it re-created by deliver? >>> >> I have the same problem with the same config myself. No evidence that >> the script is being compiled automatically. If I remove the >> "sieve=path" global setting from dovecot.conf, deliver complains about >> not finding a per-user sieve or home path - so I assume the sieve module >> is being activated. Is there a particular format for the global sieve >> parameter? Does the script file HAVE to be named ".dovecot.sieve"? >I've got the global script working. Global setting is there in >dovecot.conf. deliver should have write access to that directory, to save >compiled script. > >It's called .dovecot.sieve, but I don't think it's that important: > >require "fileinto"; > >if header :matches ["X-Spam-Flag"] [ > "YES" >] >{ >fileinto "INBOX.Spam"; >stop; >} > >Calling the folder INBOX.Spam is important, if it is to be delivered to >users' Spam folders. It doesn't work with '+' delimited address+extension >(I reported it in this list, but had no replies). Actually I managed to fix this setting global_script_path = /usr/local/etc/sieve/Junk instead of sieve_global_dir = The emails marked as spam were moved to correct directory which is Junk, as listed in user's subscriptions file and not INBOX.Junk. I also correcred my sieve file to say: require ["fileinto"]; # Move spam to Junk folder if header :contains ["X-DSPAM-Result"] "Spam" { fileinto "Junk"; # Stop here so that we do not reply on spams stop; } But now I can see following logs for some of the accounts. Any idea what that may be? This account is not above quota which is set to 51200000 (just to be sure). deliver(lists(a)yazzy.org): Sep 04 18:04:16 Info: sieve runtime error: Keep: Generic Error deliver(lists(a)yazzy.org): Sep 04 18:04:16 Error: sieve_execute_bytecode(/usr/local/etc/sieve/Junkc) failed deliver(lists(a)yazzy.org): Sep 04 18:04:16 Info: msgid=<200709042006.51319.flash(a)preferance.ru>: Rejected: Quota exceeded Some work fine: deliver(abc(a)def.com): Sep 04 19:08:34 Info: msgid=<s6dd58a7.055(a)xyz.abc.state.ga.us>: saved mail to Junk deliver(abc(a)def.org): Sep 04 19:13:37 Info: msgid=<9B1E9600-42CC-49E0-8CB8-AF826257EE1B(a)abc.no>: saved mail to INBOX Cheers, Marcin P.S Becouse of that error I sent the same message twice yesterday and did not receive any follow ups so I had to copy and paste this thread from the web archive.

8 16

[Dovecot] Don't let deliver create index files
by Martin Strand 09 Sep '07

09 Sep '07

For various reasons I want to use deliver with Postfix and Courier-IMAP, and it seems to work fine except for one thing: deliver creates some dovecot.* index files that Courier never uses (and I assume deliver doesn't need them) Is there a way to prevent that? Thanks, Martin

3 2

[Dovecot] Using NID_x500UniqueIdentifier as ssl_username_from_cert
by S. Wefel 09 Sep '07

09 Sep '07

Hi, please have a look at the attached patch for dovecot-1.0.3 These patch modifies ssl_proxy_get_peer_name() to use the NID_x500UniqueIdentifier as username instead of NID_commonName. The reason is, that the Common Name doesn't have to be unique for the whole mailserver. Example; in germany a lot of people got the first name "Andreas" and the last name "Schulz". Therefore a lot of certificates exists with subjects like this: C=DE,O=ABC,CN=Andreas Schulz/emailAddress=andreas.schulz(a)abc.de C=DE,O=DEF,CN=Andreas Schulz/emailAddress=andreas.schulz(a)def.de ... dovecot couldn't distinguish between these users. So we decide to use certificates with an X509v3 extension NID_x500UniqueIdentifier which allows to extend the subject by an unique ID, e.g. the unix-uid or a database unique key. The new certificates may look like this: C=DE,O=ABC,CN=Andreas Schulz/emailAddress=andreas.schulz(a)abc.de/x500UniqueIdentifier=user1 C=DE,O=DEF,CN=Andreas Schulz/emailAddress=andreas.schulz(a)def.de/x500UniqueIdentifier=user2 With the attached patch the user is taken from this extension and e.g. with userdb=ldap you can use the filter string user_filter = (&(objectClass=posixAccount)(uid=%u)) A good solution to use booth, the common name and the UniqueIdentifier is to extend settings like ssl_username_from_cert = no | yes | cn | uid where "yes" is similar to "cn". Regards, Sandro Wefel

2 1

[Dovecot] Server Timed Out: Outlook Express
by Jackie Hunt 09 Sep '07

09 Sep '07

Hi all, We just started running Dovecot this fall here on campus v 1.0. I've started getting some trouble reports from users. An Outlook Express users reported seeing the "Server has not responded in 60 seconds" messages. Waiting longer doesn't help, he has to stop/start Outlook Express to get connected again. Also have a Thunderbird user who is seeing that type of behavior first thing in the morning after being logged in all night. He has to stop/restart Thunderbird. Also, have had some reports of "disconnected" showing up on the Outlook2007 status bar. I've looked at the Dovecot log, and don't see any errors. I do see lots of "Disconnected", "Disconnected in IDLE" and "Disconnected: Logged Out". These last two seem normal, if I just see "Disconnected" is that a flag that we're losing connections abnormally? I know version 1.0.3 is out. I've looked at the changes, and the only one I can see that might be related to what we are seeing is the IDLE commmand fix. Was hoping for some advice on whether upgrading might resolve these issue. Any insight would be greatly appreciated. Jackie --- Jackie Hunt ACNS Voice: (970) 663-3789 Colorado State University FAX: (970) 491-1958 Fort Collins, CO 80523 Email: jackie.hunt(a)colostate.edu

3 2

[Dovecot] LDA bouncing mails after upgrade -- again
by Milan Holzäpfel 09 Sep '07

09 Sep '07

Hi Timo, some time ago (2007-03-24 and following) I asked whether it was intended that Dovecot deliver bounces mails (by terminating with status 89) if the deliver version is older than the rest of the dovecot installation. You replied that it was a bug, and that it had been fixed in <URL:http://dovecot.org/list/dovecot-cvs/2007-March/008346.html>. When I upgraded from Dovecot 1.0.2 to 1.0.3 a few days ago, I found out that this problem probably still exists: | Aug 28 09:38:03 host.example.org deliver(user(a)example.org): Module is for different version 1.0.3: /usr/lib/dovecot/lda/lib10_quota_plugin.so | Aug 28 09:38:03 host.example.org postfix/pipe[18356]: <ID>: to=<user(a)example.org>, relay=dovecot, delay=0.4, delays=0.13/0.09/0/0.18, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/postfix-deliver/deliver") The error message I posted in march was: | Mar 22 20:29:20 host.example.org deliver(user(a)example.org): Module is for different version 1.0.rc27: /usr/lib/dovecot/lda/lib10_quota_plugin.so | Mar 22 20:29:20 host.example.org postfix/pipe[17344]: <ID>: to=<user(a)example.org>, relay=dovecot, delay=1.9, delays=1.5/0/0/0.35, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/libexec/dovecot/postfix-deliver/deliver") I suppose you still want to fix it. Regards, and thanks for all your work, Milan -- Milan Holzaepfel <mail(a)mjh(d)name> <URL:http://mjh.name/> pub 4096R/C790FC23 EB8E 5E81 81E3 53A9 9B74 B895 5179 54C0 C790 FC23

2 1

[Dovecot] processing Dovecot maildirs with shell scripts
by M. Fioretti 09 Sep '07

09 Sep '07

Hello, I have a postfix server which uses procmail as its delivery agent to deliver incoming messages to several maildirs. For several reasons, not really relevant here, I need to process/refilter/sort again the content of these mailboxes before delivering the messages to the _other_ maildirs which Dovecot sees and serves to local or remote imap users. Basically, I need to write some shell scripts that, from cron jobs, regularly do this: foreach file in some_incoming_mailbox/new/ do #process the file and/or set some variable according to its content delete the file or mv it to some_other_maildir/new/ where the actual action and value of some_other_maildir is set every time by the "process the file" part of the script. The part that I still miss is guidelines to do these things safely, that is without losing or corrupting messages or doing anything else that would confuse dovecot. For example, under which conditions it is sure to move or delete (the Unix way, with mv or rm) a message from mailbox1/new/ to mailbox2/new, when the latter is served via dovecot to remote users? What is advisable and most efficient? Use locks (how?), only work on file which are at least one minute old? Should I move the messages to tmp instead of new? What else? Tips or pointers about this are very welcome. Ciao, Marco

3 5

[Dovecot] How can i complie and install the dict modules
by Oliver Eales 09 Sep '07

09 Sep '07

Hello, I want to migrate from courier-imap to dovecot and now i am trying out dovecot1.1.alpha3 But i have problems getting the expire plugin to work. At startup i get the message: Unknown dict module: db As far as i understood i have to compile the backend manually an copy it into tho appropirate place. But how can i do this ? Thanks in advance, Oliver Eales

2 1

[Dovecot] Today's dovecot-1.1.alpha3 checkins fail to build
by David Favor 09 Sep '07

09 Sep '07

net1#uname -a Linux net1.coolsurf.com 2.6.22.4-65.fc7 #1 SMP \ Tue Aug 21 21:50:50 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux make[5]: Entering directory `/build/work/dovecot-1.1.alpha3/src/lib-storage/index/dbox' gcc -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-storage -I../../../../src/lib-storage/index -pipe -O2 -I/common/pkgs/sqlite-3.4.2.1/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -MT dbox-file.o -MD -MP -MF .deps/dbox-file.Tpo -c -o dbox-file.o dbox-file.c mv -f .deps/dbox-file.Tpo .deps/dbox-file.Po make[5]: *** No rule to make target `dbox-keywords.o', needed by `libstorage_dbox.a'. Stop. make[5]: Leaving directory `/build/work/dovecot-1.1.alpha3/src/lib-storage/index/dbox' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/build/work/dovecot-1.1.alpha3/src/lib-storage/index' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/work/dovecot-1.1.alpha3/src/lib-storage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/work/dovecot-1.1.alpha3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/work/dovecot-1.1.alpha3' make: *** [all] Error 2 exp=0, got ec=2, abort=1 -- Love feeling your best ever, all day, every day? Email join(a)RadicalHealth.com for the easy way.

2 1

[Dovecot] Index and Thunderbird
by Jon 09 Sep '07

09 Sep '07

Hi, Whitbox Linux 3 (RHEL) Dovecot 1.0.rc29 Using NFS From time to time does all mail get re-downloaded to Thunderbird. I would believe this has something to do with an index problem. I upgraded to 1.0 a few months ago but that didn't work well so I installed version 1.0.rc29 which worked better but we still get this problem from time to time. DOes anyone know if it is a good idea to install 1.03 or perhaps 1.1alpha? dovecot: Sep 01 04:47:30 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist) failed: No such file i dovecot: Sep 01 04:47:30 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 04:47:30 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist: next_uid was lowered (19065 -> 19064) dovecot: Sep 01 04:47:30 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist) failed: No such file dovecot: Sep 01 04:47:30 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/.Sent/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 09:11:23 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 09:11:23 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 09:11:23 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (18094 -> 18093) dovecot: Sep 01 14:32:25 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 14:32:25 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 14:32:25 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (18095 -> 18094) dovecot: Sep 01 17:13:27 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 17:13:27 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 17:13:27 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (18096 -> 18095) dovecot: Sep 01 17:31:26 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 17:31:26 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 17:31:26 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (18097 -> 18096) dovecot: Sep 01 17:38:28 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 17:38:28 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 19:05:24 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 01 19:05:24 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:53:34 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:53:34 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:53:35 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (33015 -> 33014) dovecot: Sep 02 09:54:57 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (33015 -> 2) dovecot: Sep 02 09:58:49 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:58:49 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:58:49 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (33017 -> 33016) dovecot: Sep 02 09:58:50 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 02 09:58:50 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 03 06:18:40 Error: IMAP(XXXXXX): rename(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist.lock, /mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 03 06:18:40 Error: IMAP(XXXXXX): file_dotlock_replace(/mail2/home/XXXXXX/.Maildir/dovecot-uidlist) failed: No such file or directory dovecot: Sep 03 06:18:40 Error: IMAP(XXXXXX): /mail2/home/XXXXXX/.Maildir/dovecot-uidlist: next_uid was lowered (24248 -> 24247) Best regards - Jon

3 2

[Dovecot] passing quota to deliver via command line
by bill-dovecot＠carpenter.ORG 09 Sep '07

09 Sep '07

Is there any way to pass things like "quota=" for the quota plugin to the deliver LDA via the command line or as an environment variable or whatever? I've got all the info I need in my MTA to avoid a userdb lookup in the LDA, but I still have to do the userdb query to get the per-user quota number (the default quota works fine, of course). -- bill-dovecot(a)carpenter.ORG (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3

2 1

[Dovecot] passdb/userdb args
by Daniel L. Miller 09 Sep '07

09 Sep '07

I'm a bit unclear on these - give me a moment to ramble on. I should mention I'm using version 1.0.3, my primary backend is LDAP, and I do NOT want to store user mail folders in my LDAP directory. I currently have the following: default_mail_env = maildir:/var/mail/%d/%n passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } # Instructions for deliver state a userdb is still required if using prefetch userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb prefetch { } My dovecot-ldap.conf is pretty simple - the trimmed version is: hosts = localhost auth_bind = no user_attrs = %d/%n=mail user_filter = (mail=%u) pass_attrs = (&(userPassword=password)(mail=%u)) user_global_uid = 5000 user_global_gid = 8 I recognize that the pass_attrs is incorrect for a prefetch config - but I couldn't get it to work. My mail folder structure is /var/mail/domain/username. If, under 1.0.3, I can't use the %d/%n variables to build the user/home/mail parameters in the LDAP config, can I do it in the configuration stanza? Something like: passdb ldap{ args = home=%dn/%n mail=%d/%n /etc/dovecot/dovecot.conf } -- Daniel

3 4

[Dovecot] Timeout while waiting for lock for transaction log file
by Peter Eriksson 09 Sep '07

09 Sep '07

I have a user that gets client timeout errors when he tries to delete/clean up his massive "Spam" folder (many thousands of mail messages). He uses Thunderbird and has it configured to use "Move to Trash" when he deletes messages. I find the following in Dovecot's log file when it happens: Aug 28 10:38:22 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(bpn): Timeout while waiting for lock for transaction log file /home/bpn/Maildir/.Trash/dovecot.index.log Aug 28 10:38:24 ifm.liu.se dovecot: [ID 107833 mail.info] IMAP(bpn): Disconnected Any suggestions on what I can tuned/fix in Dovecot to solve this issue? We're using Dovecot 1.0.3 with Maildirs. This is the only user (so far) where we are seeing this. - Peter

2 1

[Dovecot] BUG REPORT - Stops logging after sleep
by Bruce Bodger 09 Sep '07

09 Sep '07

Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are running fine but dovecot has stopped logging. (I have modified nothing in dovecot.conf relative to logging: dovecot logs to syslog using the "mail" syslog_facility.) ps -aux | grep dovecot root 53 0.0 -0.0 27772 544 ?? Ss 4:23PM 0:04.69 /usr/local/sbin/dovecot -F root 79 0.0 -0.0 28176 556 ?? S 4:23PM 0:03.21 dovecot-auth dovecot 9548 0.0 -0.0 27780 496 ?? S 7:12AM 0:00.05 imap-login dovecot 9631 0.0 -0.0 27780 500 ?? S 7:17AM 0:00.03 imap-login dovecot 9632 0.0 -0.0 27780 500 ?? S 7:17AM 0:00.03 imap-login I am starting dovecot via OS X's launchdaemon facility thus the "-F" command line switch requirement. Sending a "kill -HUP" to the process did not get it to start logging. Sending a "Kill -9" to the process forced a restart and logging began again. ps -aux | grep dovecot root 9738 0.0 -0.0 27772 540 ?? Ss 7:26AM 0:00.03 /usr/local/sbin/dovecot -F root 9739 0.0 -0.0 28176 544 ?? S 7:26AM 0:00.02 dovecot-auth dovecot 9740 0.0 -0.0 27780 500 ?? S 7:26AM 0:00.02 imap-login dovecot 9751 0.0 -0.0 27780 500 ?? S 7:27AM 0:00.01 imap-login dovecot 9762 0.0 -0.0 27780 500 ?? S 7:27AM 0:00.01 imap-login Before posting this bug I compared v1.0.0's /src/lib/ioloop.c to that in the nightly snapshot and saw no adjustments in, what I presumed to be, the relevant portion of the code. Output of "dovecot -n" protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 490 mail_extra_groups: mail mail_location: mbox:~/Library/Mail/IMAP:INBOX=/var/mail/%u:INDEX=%h/ Library/Mail/DOVECOT.indexes dotlock_use_excl: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd Thank you.

4 14

[Dovecot] trouble with deliver in 1.0.4
by Jack Bailey 09 Sep '07

09 Sep '07

Ok, here's one for the idiot file. I just installed dovecot-1.0.4 on my personal system for testing, a system which has to be the simplest dovecot configuration possible. deliver is barking about something with which version 1.0.3 has no problem. I looked over the wiki, googled, and see nothing wrong. The error: deliver(jjb): Sep 07 21:39:40 Fatal: Failed to create storage for 'jjb' with mail 'mbox:/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB/:INBOX=/var/mail/jjb' In dovecot.conf: userdb passwd { # [blocking=yes] - By default the lookups are done in the main dovecot-auth # process. This setting causes the lookups to be done in auth worker # processes. Useful with remote NSS lookups that may block. # NOTE: Be sure to use this setting with nss_ldap or users might get # logged in as each others! #args = args = blocking=yes } and mail_location = mbox:~/:INBOX=/var/mail/%u Clues generously accepted, Jack

2 2

[Dovecot] v1.0.4 released
by Timo Sirainen 08 Sep '07

08 Sep '07

http://dovecot.org/releases/1.0/dovecot-1.0.4.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.4.tar.gz.sig * Assume a MIME message if Content-Type: header exists, even if Mime-Version: header doesn't. - IMAP: CREATE ns_prefix/box/ didn't work right when namespace prefix existed. - deliver: plugin {} settings were overriding settings from userdb. - mbox: Expunging the first message might not have worked always - PostgreSQL: If we can't connect to server, timeout queries after a while instead of trying forever. - Solaris: sendfile() support was broken and could have caused 100% CPU usage and the connection hanging. And one more thing I forgot from NEWS file: - IMAP: Fixed infinite loop in some situations

1 0

[Dovecot] Two newbie problems
by Timothy Murphy 08 Sep '07

08 Sep '07

I've started running dovecot on my server under Fedora 7, to act as an IMAPS server for kmail. 1. I see my email fine on my laptop in an IMAPS account, but it doesn't get updated - I mean I don't get any new email - until I run kmail on my server. This isn't a great problem, as I am always logged to the server with ssh, and I just start kmail and stop it after a few minutes. Then I run kmail on my laptop, and the new mail is there. But I assume this is not the intended system? 2. I opted (probably mistakenly) to set ~/Mail/inbox/ as my base IMAPS directory on my server. I'd like to change this to ~/Maildir (I use maildir folders). Is it relatively easy to do this? I tried copying my email to ~/Maildir/ and changing the setting in /etc/dovecot.conf (and restarting dovecot), but for some reason I could not see the email on my laptop. Any advice or suggestions gratefully received.

3 3

[Dovecot] o/s tuning for imap
by Ken A 07 Sep '07

07 Sep '07

I'm switching from a pop3 only dovecot install to a pop3/imap install and I'm wondering how many connections every 100 'normal' imap users might have/keep open? I'm wondering if I need to tweak any o/s related things, like time_wait, etc. Any pointers would be greatly appreciated. Thanks, Ken A.

6 10

[Dovecot] dovecot/postfix+vda
by Neil Wilson 07 Sep '07

07 Sep '07

Hi guys, Been fighting with postfix+vda/dovecot/ My postfix delivers the emails to /vmail/ which is owned by user maild:users 501(uid):100(gid) without any problems. When I... # telnet localhost 110 +OK Dovecot ready. user samichand +OK pass wordpass +OK Logged in. -ERR [IN-USE] Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2007-09-05 16:32:52] Connection closed by foreign host. I get... Sep 5 16:32:52 mail dovecot: pop3-login: Login: user=<samichand>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 5 16:32:52 mail dovecot: POP3(samichand): Effective uid=4841, gid=27021 Sep 5 16:32:52 mail dovecot: POP3(samichand): maildir: data=/vmail/samichand/Maildir Sep 5 16:32:52 mail dovecot: POP3(samichand): maildir: root=/vmail/samichand/Maildir, index=/vmail/samichand/Maildir, control=, inbox= Sep 5 16:32:52 mail dovecot: POP3(samichand): stat(/vmail/samichand/Maildir/cur) failed: Permission denied Sep 5 16:32:52 mail dovecot: POP3(samichand): stat(/vmail/samichand/Maildir/cur) failed: Permission denied Sep 5 16:32:52 mail dovecot: POP3(samichand): Couldn't open INBOX: Internal error occurred. Refer to server log for more information. [2007-09-05 16:32:52] Sep 5 16:32:52 mail dovecot: POP3(samichand): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 In my mail log. Below is my dovecot.conf mail:/ # cat /usr/local/etc/dovecot.conf base_dir = /var/run/dovecot/ protocols = imap pop3 listen = * disable_plaintext_auth = no ssl_disable = yes mail_location = maildir:/vmail/%u/Maildir mail_debug = yes protocol imap { } protocol pop3 { pop3_uidl_format = %v.%u } protocol lda { postmaster_address = postmaster(a)bla.co.za } auth default { mechanisms = plain passdb shadow { } userdb passwd { } user = root } dict { } plugin { } If I change the ownership on the Maildir to the user:users then I can log in, but then postfix doesn't deliver successfully. I need to set the mail user that dovecot uses to access the maildir to the same uid that postfix uses, how can I do this, I've read the wiki over and over and although it says you can do it, I don't know how. Taken from the WIKI... http://wiki.dovecot.org/UserIds#mailusers Virtual users where all Dovecot users run under a single system user, for example vmail (just NOT dovecot). Also taken from WIKI http://wiki.dovecot.org/VirtualUsers You can create for example one vmail user which owns all the mails, or you can assign a separate UID for each user. See UserIds#mailusers for more information about different ways to allocate UIDs for users. All I want is to be able to access the mail, with the same my "virtual_uid_maps = static:501"(set in my postfix main.cf) All of these say it can be done, but how do I do it? Please could someone assist me :( Thanks. Neil -- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html

2 2

[Dovecot] Quota bug in deliver?
by FORMER 03 | Baltasar Cevc 06 Sep '07

06 Sep '07

Hi, I may be wrong, but I suspect a bug in dovecot deliver when using quotas. I've put some mails into a mailbox and then reduced the quota, to have the mailbox be over quota - here's the quota informaiton: [...] 2 getquotaroot INBOX * QUOTAROOT "INBOX" "" * QUOTA "" (STORAGE 880 5) 2 OK Getquotaroot completed. [...] When I have a setup with quotas only in the database, everything works as expected and deliver denies the message: Sep 5 21:50:14 ms4 deliver(postfach(a)email5.former03.local): msgid=<20070905195014.9D874239C007(a)ms4.srv.hoster03.de>: save failed to INBOX: Quota exceed ed Sep 5 21:50:14 ms4 deliver(postfach(a)email5.former03.local): msgid=<20070905195014.9D874239C007(a)ms4.srv.hoster03.de>: Rejected: Quota exceeded When I put a standard quota into the config as follows, the delivery succeeds (apparently deliver checks the standard quota, while IMAP correctly checks the quota from the database if it is returned. Sep 5 21:46:11 ms4 deliver(postfach(a)email5.former03.local): msgid=<20070905194611.9FE49239C007(a)ms4.srv.hoster03.de>: saved mail to INBOX The mailbox is still over quota here, but deliver does not seem to notice. == standard quota in the config plugin { quota = maildir:storage=102400:messages=1000 [...] } In case I've overlooked something, please let me know. Otherwise let me know if you need some more information. Baltasar _____ FORMER 03 GmbH _____ www.former03.de _____ fon 089.322112.0

4 4