- dovecot - dovecot.org

[Dovecot] Dovecot / Exim with Multiple Domiains
by Marc Perkel 10 Feb '09

10 Feb '09

I'm using a very old scheme for doing multiple domains using an old Linuxconf based setup. Each domain has it's own passwd/shadow file. It works but I need something new and modern and has a web interface and perhaps a mysql backend or something else good. So - what are people using out there for managing email users and domains? Thanks in advance.

2 1

[Dovecot] Imap unlink "failed, is a directory".
by Dovecot＠corwyn.net 10 Feb '09

10 Feb '09

Dovecot 1.1.8-0_85.el5 I'm seeing this set of messages repeat every 15 min. My best guess is the user tried to delete an imap folder and is failing? Feb 9 20:05:58 mailserver dovecot: imap-login: Login: user=<user(a)example.com>, method=PLAIN, rip=10.0.0.1, lip=192.168.250.80, TLS Feb 9 20:05:58 mailserver dovecot: IMAP(user(a)example.com): unlink(/var/spool/mail/example.com/user/Maildir/cur/cur:2,ST) failed: Is a directory Feb 9 20:05:58 mailserver dovecot: IMAP(user(a)example.com): unlink(/var/spool/mail/example.com/user/Maildir/cur/new:2,ST) failed: Is a directory Feb 9 20:05:58 mailserver dovecot: IMAP(user(a)example.com): Disconnected: Logged out bytes=66/623 From here: http://wiki.dovecot.org/VirtualUsers#homedirs I suspect it's a problem with access to the home directory. The users have a home directory: /var/spool/mail/domain/user (or at least that's where Maildir ends up). vuser has 700 access to that entire structure (everything under var/spool/mail/). Users log in with mysql accounts. /etc/passwd: ... dovecot:x:97:97:dovecot:/usr/libexec/dovecot:/sbin/nologin postfix:x:89:89::/var/spool/postfix:/sbin/nologin vacation:x:65501:65501::/var/spool/vacation:/sbin/nologin vuser:x:1015:105:,,,:/home/vuser:/bin/false ... dovecot-sql.conf driver = mysql connect = host=localhost dbname=postfix user=postfix password=xxxxxxx default_pass_scheme = MD5-CRYPT password_query = SELECT username, domain, password FROM mailbox WHERE username = '%u' AND domain = '%d' AND active = '1' user_query = SELECT 1015 as uid, 105 as gid, '/var/spool/mail/%d/%n' as home, 'maildir:/var/spool/mail/%d/%n/Maildir' as mail, concat('*:storage=', quota, 'B') as quota_rule FROM mailbox WHERE username = '%u' AND domain = '%d' and active = '1' dovecot -n # 1.1.8: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 i686 Red Hat Enterprise Linux Server release 5.2 (Tikanga) ext3 ssl_cert_file: /etc/httpd/certs/example_invtitle_com.crt ssl_key_file: /etc/httpd/certs/example.com.key.no.password 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 mail_uid: 1015 mail_gid: 105 mail_location: maildir:/var/spool/mail/%d/%n/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle imap_client_workarounds(imap): delay-newmail outlook-idle imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: static socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vuser group: vuser plugin: quota: maildir quota_rule: *:storage=102400000 quota_rule2: Trash:storage=100M Rick Steeves http://www.sinister.net "The journey is the destination"

3 3

[Dovecot] Authentication woes.
by Roderick A. Anderson 10 Feb '09

10 Feb '09

I'm still searching but hoping someone can offer a clue-stick. Long story short! I had a server crash suddenly and all I can get at are the files. Built a new host and copied the data and config files over, correcting ownership and permissions (hopefully) as I went. But now I can't get logged in. Messages in /var/log/dovecot/dovecot-info.log, without saslauthd running, are like this. dovecot: Feb 03 08:55:46 Info: auth(default): passwd-file(raanders(a)aesoft-sbcs.com,66.193.34.88): no passwd file: username_format=raanders /var/mail/vhosts/aesoft-sbcs.com/passwd dovecot: Feb 03 08:55:48 Info: auth(default): client out: FAIL 1 user=raanders(a)aesoft-sbcs.com dovecot: Feb 03 08:55:48 Info: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=216.64.180.226 rip=66.193.34.88 resp=AHJhYW5kZXJzQGFlc29mdC1zYmNzLmNvbQBrNnpiZTQy dovecot: Feb 03 08:55:48 Info: auth(default): passwd-file(raanders(a)aesoft-sbcs.com,66.193.34.88): no passwd file: username_format=raanders /var/mail/vhosts/aesoft-sbcs.com/passwd dovecot: Feb 03 08:55:50 Info: auth(default): client out: FAIL 2 user=raanders(a)aesoft-sbcs.com dovecot: Feb 03 08:55:54 Info: imap-login: Aborted login: user=<raanders(a)aesoft-sbcs.com>, method=PLAIN, rip=66.193.34.88, lip=216.64.180.226, TLS The passwd file exists and I'm using the correct password. dovecot -n as an attachment. More info this is a semi-good attempt at a mail server for virtual domains. _It was working._ Any ideas as to why dovecot says the file doesn't exist? TIA, Rod # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-info.log protocols: imap imaps listen: *:143 ssl_listen: *:993 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes valid_chroot_dirs: /var/mail first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_access_groups: mail mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes auth default: mechanisms: plain login CRAM-MD5 default_realm: aesoft-sbcs.com master_user_separator: * verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd.masterusers pass: yes master: yes passdb: driver: passwd-file args: username_format=%n /var/mail/vhosts/%d/passwd userdb: driver: passwd-file args: username_format=%n /var/mail/vhosts/%d/passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail plugin: sieve: /var/mail/vhosts/%d/%n/dovecot.sieve

2 1

[Dovecot] Dovecot 1.1.11 segfaults on auth configuration error
by Sebastian Kayser 10 Feb '09

10 Feb '09

Hi, i have compiled & packaged Dovecot 1.1.11 on Solaris 8 x86 with Sun Studio 11 and installed the result on Solaris 10 x86 zone. When i now configure auth mechanisms other than "login" or "plain" while only providing pam as the passdb, Dovecot segfaults on startup. I know that my configuration is wrong here, but i guess this still qualifies as a bug. Remedy would be appreciated. # /opt/csw/sbin/dovecot -F dovecot: Feb 06 22:56:24 Info: dovecot v1.1.11 starting up dovecot: Feb 06 22:56:25 Error: child 26870 (auth) returned error 89 (Fatal failure) Segmentation Fault (core dumped) # /opt/SUNWspro/bin/dbx -f /opt/csw/sbin/dovecot core (dbx) where =>[1] hash_lookup(table = (nil), key = 0x68f6), line 159 in "hash.c" [2] child_process_lookup(pid = 26870), line 31 in "child-process.c" [3] log_it(log_io = 0x80b8598, line = 0x80b7d4a "DIGEST-MD5 mechanism can't be supported with given passdbs", continues = 0), line 129 in "log.c" [4] log_write_pending(log_io = 0x80b8598), line 52 in "log.c" [5] log_read(log_io = 0x80b8598), line 191 in "log.c" [6] log_deinit(), line 331 in "log.c" [7] auth_process_destroy(p = 0x80b86f8), line 357 in "auth-process.c" [8] auth_process_input(process = 0x80b86f8), line 244 in "auth-process.c" [9] io_loop_handler_run(ioloop = 0x80b3518), line 204 in "ioloop-poll.c" [10] io_loop_run(ioloop = 0x80b3518), line 336 in "ioloop.c" [11] main(argc = 2, argv = 0x80478dc), line 599 in "main.c" # /opt/csw/sbin/dovecot -n # 1.1.11: /etc/opt/csw/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc log_path: /dev/stderr login_dir: /var/opt/csw/run/dovecot/login login_executable: /opt/csw/libexec/dovecot/imap-login auth default: mechanisms: plain digest-md5 debug: yes passdb: driver: pam userdb: driver: passwd Please let me know in case there is any other information required to nail down the culprit. Thanks. Sebastian

2 2

[Dovecot] [patch] 'c' and 'd' in setacl
by Sascha Wilde 09 Feb '09

09 Feb '09

Hi Timo, Hi *, I just recognized that the new imap-acl plugin in dovecot 1.2 does not know the obsolete rights 'd' and 'c' when setting. According to RFC 4314 section 2.1.1.: If a client includes the "d" right in a rights list, then it MUST be treated as if the client had included every member of the "delete" right. and If a client includes the "c" right in a rights list, then it MUST be treated as if the client had included every member of the "create" right. Unfortunatly there are actually clients which depend on this behavior. I attached a rather rough[0] patch which implements this. cheers sascha [0] I don't like the use of static indexes witch imap_acl_letter_map but currently I wasn't able to decide on a more elegant solution. -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

4 5

[Dovecot] Rebuild folder listing?
by Roderick A. Anderson 09 Feb '09

09 Feb '09

I don't know what to call what I'm trying to do so I'll explain the situation. I had a total complete crash of the Linux-Vserver system that was hosting a Postfix+Dovecot guest with a three domains and 1-5 accounts per domain. Lots of mail though. Before it completely melted down I as able to get to the data (messages) and save them and the configuration files for both Dovecot and Postfix. I now have a replacement system up and running and have copied the directories onto it. I can log in to the accounts but I don't see the folders (I use Thunderbird as a MUA). Attempts to "subscribe" and "refresh" the list give me no results. No list of folders. What should I do? I'm thinking I could delete the dovecot files: dovecot.index, dovecot.index.cache, dovecot.index.log, dovecot-uidlist, subscriptions, and while I'm at it possibly dovecot-keywords. Then access the account(s) and Dovecot will rebuild them with the true/correct information. Am I heading anywhere near the right direction? TIA, Rod --

2 3

Re: [Dovecot] Disconnected Log messages I'd like to disable?
by dovecot＠corwyn.net 09 Feb '09

09 Feb '09

I understand what the log message means. I currently have dovecot logging flipped up about as high as I can have it set in about every way that I can. What I'd like to know is which logging setting can I lower to not see this message (or if there is one), and what OTHER things won't log if I decrease that logging setting. thx. rick At 08:43 AM 2/9/2009, Steffen Kaiser wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On Mon, 9 Feb 2009, dovecot(a)corwyn.net wrote: > >>Feb 9 08:06:52 mailserver dovecot: IMAP(user(a)example.com): >>Disconnected: Logged out bytes=479/51185 > >Search the archive for a mail from Timo few times ago, it just means >that the user logges out (LOGOUT command). > >Bye, > >- -- Steffen Kaiser >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.6 (GNU/Linux) > >iQEVAwUBSZAzIHWSIuGy1ktrAQKQDQf/S0zCmCuQ+xtJI0o3goUdDo0++yGXRyCp >fGdDKQ7YnOL1VOM1FnBjGJkhfYs/K6WuVFqQzqVrBjCoItsFWIvZCoeGWeHYPQf1 >6qRYngFSJLfdFDg9Ift5UvCnIS9W5jYv6otkJlddoH0SHeypSb9RZbPR20Ywf2da >whV4bB41W8ys/upUkaBd7+gKKcYcbSp+l3ZBXCrLnDbj7pCISnv2sENkTz2df1eE >wQSgpnbazmr9ePCx1cWDdvN5Wy9RN5KoGc+H0axtI7Uav5tkP7nVJ8GSmqBBH54r >nkvOrtmAjTMwp4MbYh6x2wejZJAY8lp72wQOeg3sJak32f3la0ZLgw== >=mLed >-----END PGP SIGNATURE-----

3 2

[Dovecot] Disconnected Log messages I'd like to disable?
by dovecot＠corwyn.net 09 Feb '09

09 Feb '09

I regularly get this message in my logs: Feb 9 08:03:59 mailserver dovecot: imap-login: Login: user=<user(a)example.com>, method=PLAIN, rip=24.213.158.249, lip=192.168.250.80, TLS Feb 9 08:04:49 mailserver dovecot: IMAP(user(a)example.com): Disconnected: Logged out bytes=189/468 Feb 9 08:06:09 mailserver dovecot: imap-login: Login: user=<user(a)example.com>, method=PLAIN, rip=24.213.158.249, lip=192.168.250.80, TLS Feb 9 08:06:52 mailserver dovecot: IMAP(user(a)example.com): Disconnected: Logged out bytes=479/51185 Feb 9 08:06:52 mailserver dovecot: IMAP(user(a)example.com): Disconnected: Logged out bytes=479/51185 (which I think is from my blackberry users) I'd like to not log Feb 9 08:06:52 mailserver dovecot: IMAP(user(a)example.com): Disconnected: Logged out bytes=479/51185 Suggestions? rick Rick Steeves http://www.sinister.net "The journey is the destination"

2 1

[Dovecot] v1.1.11 released
by Timo Sirainen 09 Feb '09

09 Feb '09

http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.11.tar.gz.sig Hopefully this v1.1 release will last a few months. - IMAP: PERMANENTFLAGS list didn't contain \*, causing some clients not to save keywords. - dbox: INTERNALDATE and save date was returned wrong for converted maildir files. - auth: Using "username" or "domain" passdb fields caused problems with cache and blocking passdbs in v1.1.8 .. v1.1.10. - userdb prefetch + blocking passdbs was broken with non-plaintext auth in v1.1.8 .. v1.1.10. - If mail_chroot is set, don't fail at startup in dump-capability.

10 16

[Dovecot] Maildir structure question
by Nicolas KOWALSKI 08 Feb '09

08 Feb '09

Hello, About the INBOX location when using maildir, in the wiki, http://wiki.dovecot.org/MailboxFormat/Maildir, I can read: " Directory Structure ~/Maildir/new, ~/Maildir/cur and ~/Maildir/tmp directories contain the messages for INBOX. The tmp directory is used during delivery, new messages arrive in new and read shall be moved to cur by the clients. " But in my Maildir, I see this: niko@petole:~$ ls -la Maildir/ total 144 drwxr-xr-x 35 niko niko 4096 2009-02-06 08:37 . drwxr-xr-x 25 niko niko 4096 2009-02-06 10:26 .. drwxr-xr-x 5 niko niko 4096 2009-02-06 09:16 .INBOX ... There are no 'cur', 'new' and 'tmp' directories in ~/Maildir, as written in the wiki, but instead this .INBOX directory which contains these 'cur', 'new' and 'tmp'. Is this expected ? Thanks. My configuration: petole:~# dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28.3 i686 Debian 4.0 ssl_cert_file: /etc/ssl/certs/petole.demisel.net.pem ssl_key_file: /etc/ssl/private/petole.demisel.net.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:~/Maildir namespace: type: private separator: / list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 -- Nicolas

3 8

[Dovecot] Best Imap Transfer Tool?
by Neil 08 Feb '09

08 Feb '09

So I'm looking to do a migration of my IMAP mailboxes, and I'm looking for the best tool to use. I used to use the uw-mailutil tool, a while ago, but that was a bit coarse of a tool. More recently I've used imapsync, but that was giving me some errors. I've sort of tracked those down; but I was wondering if anyone else had any other recommendations...? Thanks.

2 2

[Dovecot] Migrating mail between servers
by Knute Johnson 07 Feb '09

07 Feb '09

I've currently got dovecot running on a Fedora server and I want to move all my mail to my new server running ubuntu. Both use mbox and I have IMAP working in both. Can I just copy the ~user/mail directory and /var/mail/user file and replace them in the new server? Thanks, -- Knute Johnson "The urge to save humanity is almost always a false front for the urge to rule." H.L. Mencken

3 2

[Dovecot] FreeBSD pam auth problems
by Dmitry Samersoff 07 Feb '09

07 Feb '09

I'm impressed by dovecto and try to upgrade my home system from wu-imapd running there for last 5 years to dovecot. It's straghtforward FreeBSD setup with ssl-only auth, inboxes in /var/mail and user mail under %h/Mail But I get some strange error: Fatal: userdb didn't return a home directory, but mail location used it (%h): %h/Mail:INBOX=/var/mail/%u Thank you in advance! -Dmitry mircat:dovecot#./sbin/dovecot -n # 1.1.10: /usr/local/dovecot/etc/dovecot.conf # OS: FreeBSD 6.2-RELEASE i386 base_dir: /var/run/dovecot log_path: /var/log/dovecot_main.log info_log_path: /var/log/dovecot_info.log listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: nobody login_chroot: no login_max_processes_count: 30 max_mail_processes: 30 first_valid_uid: 1 mail_uid: smmsp mail_gid: smmsp mail_location: mbox:%h/Mail:INBOX=/var/mail/%u mail_debug: yes mbox_lazy_writes: no auth default: failure_delay: 1 verbose: yes debug: yes worker_max_request_count: 1 passdb: driver: pam args: imap -- Dmitry Samersoff dms(a)samersoff.net, http://devnull.samersoff.net * There will come soft rains ...

2 4

[Dovecot] Info regarding conversion of mbox to maildir
by Scott Silva 06 Feb '09

06 Feb '09

When I finally decide to convert to maildir, will I have to set up namespaces during the conversion, or will dovecot figure out where everything is by itself? Should I set up deliver to go to maildir/ globally, or per user? I have considered using the convert plugin, if there are not a lot of negatives. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 3

[Dovecot] Public namespace permissions documentation/questions
by Thomas Hummel 06 Feb '09

06 Feb '09

Hello Timo, In my trials to setup a shared namespace with dovecot-1.1.8/LDAP passdb/userdb (prefetch)/Maildir, I found out that : 1) ACL are mandatory (at least if the acl plugin is triggered in dovecot.conf) Am I correct ? I'm still not sure if we can do without ACL at all (only with unix permissions and system_user userdb extra field). 2) the system_user userdb extra field is supposed to be ...the logname of the user the secondary groups of whom we want to check ! i.e. if user foobar belongs to secondary groups foogid, zgid, wgid and doveshared uid=xxx(foobar) gid=yyy(foogid) groups=zzz(zgid),www(wgid),vvv(doveshared) and we dovecot to take them into account, we have to make the usedb return the system_user extra field with the value foobar. Seems obvious now and said this way, but looking at the wiki : "system_user: If this is given, the user's groups are read from /etc/group (or wherever NSS is configured to taken them from)." I thought 'system_user' was a flag (a boolean) which, when triggered made dovecot look for the secondaries group of the user (user whose name is already known). a) am I correct ? b) why isn't system_user such a boolean ? Is there a case where we'd want system_user to be different than the user dovecot runs as at the moment the check takes place ? 3) same idea with acl_groups : since this extra_field holds a list of groups for the ACL plugin, why not rely on the native unix groups of the system the user belong to ? Thanks (and sorry for the 2 previous threads where I was blindly confused by the system_user thing). -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] dovecot-shared file
by Thomas Hummel 06 Feb '09

06 Feb '09

Hello Timo, About the dovecot-shared file, the wiki says : "Unless you're using a single UID for all the users, you'll need to have a dovecot-shared file in each shared maildir. The group and the file permissions for new files inside the maildir are taken from the dovecot-shared file." but says the following too : "With Maildir dovecot-shared file controls if the \Seen flags are shared or private. If you don't have the file, they're shared." The question is "does it make sense (or is it even possible) not to have the file ?". Why would one not have the file and how would it work then ? By relying on the set-gid bit and umask ? Finally, the wiki says : "If you do have the file, the \Seen flag state is stored only in the user's index files. By making each user have their own private index files, you can make the \Seen flag private for the users." So, my undersanding is that : 1) you have the file 1.a) if INDEX points to the same place, flags are shared but are lost if indexes are lost 1.b) if INDEX points to some user dependant place, flags are private but are lost if indexes are lost 2) you don't have the file flags are shared, whatever INDEX points to and, since they're stored in filename, survive indexes lost. but does shared-mailboxes even work if we don't have that file ? maybe only if the set-gid bit and umask does what the file would have done ? So maybe, if you want to share flags, 2) is safer dans if you want them private, 1.b) is the only choice ? thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] Shared subscription, acl-list and uidvalidity(s)
by Thomas Hummel 06 Feb '09

06 Feb '09

Hello, I'm running dovecot-1.1.8/Maildir/ACL plugin. I sucessfully set up a Maildir shared between users of the unix group 'doveshared' via a public namespace, unix permissions and ACL files. The location of my public namespace is /path/to/public. I tried 2 sub-setups : First setup ---------- drwxrws--- 4 root doveshared 4096 Jan 30 13:39 public -rw-r----- 1 root doveshared 18 Jan 30 13:38 public/subscriptions I first connect (in Thunderbird) to dovecot with user 'hummel', then with user 'doveimap'. The following files are created in /path/to/public/ : -rw------- 1 doveimap doveshared 40 Jan 30 14:03 dovecot-acl-list -rw------- 1 hummel doveshared 8 Jan 30 14:03 dovecot-uidvalidity -rw------- 1 hummel doveshared 0 Jan 30 14:02 dovecot-uidvalidity.4982fa7a I've got my own idea about what they're used for, but can you explain what they are supposed to be ? I guess the uidvalidity files are UIDVALIDITY, not for the mailboxes the namespace holds (since my understanding is that the uidvalidities of mailboxes are stored in the first line of dovecot-uidlist files), but for the namespace itself (in case it is destroyed and then recreated for instance). Am I right ? Why 2 files ? Second setup ------------- I follow the 'Shared subscriptions' section of the wiki : drw-r-s--- 4 root doveshared 4096 Jan 30 14:19 public -rw-r----- 1 root doveshared 18 Jan 30 13:38 public/subscriptions As expected, dovecot (and it shows in the logs), has not sufficient permissions to create the files above (dovecot-acl-list, dovecot-uidvalidity, dovecot-uidvalidity.4982fa7a). What are the consequences ? Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 3

[Dovecot] help: "dovecot: pipe() failed: Too many open files"
by Jake Grimmett 06 Feb '09

06 Feb '09

Dear All, I'm having an intermittent problem, with dovecot slowing to a crawl. Restarting dovecot fixes the problem. Looking at the maillog, I see loads of these errors.... dovecot: pipe() failed: Too many open files dovecot: Temporary failure in creating login processes, slowing down for now dovecot: Created login processes successfully, unstalling looking at the processes, I can see ~200 imap-login's and about ~700 imap's there are 1000 email accounts on the server - half of which are in regular use. The server is Dell PE1950 running dovecot (1.0.7-2.el5) as supplied with Centos 5.2 (~Redhat AS 5.2) in 64 bit mode. I've upgraded the server from 4 to 8GB of RAM, and from a dual core 1.5Ghz xeon, to a quad core 1.5GHz xeon, and this does not seem to help. The following settings were increased by me to try and stop this problem - but did not have an obvious effect: login_process_size = 128 login_process_per_connection = yes login_max_processes_count = 512 Other parameters were left commented out: #max_mail_processes = 1024 #auth_process_size = 256 If anyone has any ideas about where I might be going wrong, please let me know..! many thanks Jake -- Dr Jake Grimmett Head Of Scientific Computing MRC Laboratory of Molecular Biology Hills Road, Cambridge, CB2 0QH, UK. Phone 01223 402219 Mobile 0776 9886539

3 4

Re: [Dovecot] ¿DC won't start? "leaked file fd 5:"
by mathemat＠gmx.net 06 Feb '09

06 Feb '09

Hi Timo, >> mail.info dovecot: Dovecot v1.0.15 starting up >> mail.err dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 >> inode 3 > This happens only when Dovecot has been configured with --enable-devel- > checks (or was it --with-debug in v1.0? I'm not sure anymore). The > easiest way to avoid the problem is to not do that. Well, I read that on the net. But the goal was to get it going *without* recompiling... please! :) > The problem is probably related to running in a special environment > which uses some extra fds for some things (possibly a bug or maybe a > feature, who knows) Maybe. But as i got it from an official repo <http://www.dovecot.org/releases/1.0/dovecot-1.0.15.tar.gz>, the thing obviously works for some folks... i'm afraid, they just configured DC somewhat sensefullier (while not documenting this anywhere). Ideas from the profs (you)? -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

2 1

[Dovecot] NFS - inotify vs kqueue
by Jack Stewart 06 Feb '09

06 Feb '09

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really make any difference which is why I ask the question. ---Jack

3 3

[Dovecot] Hi all,
by Jehan Pagès 06 Feb '09

06 Feb '09

Hi all, as I told earlier, I am installing an email server with postfix/dovecot/dspam (for now that's all, though some programs may come later). For now, what works good enough is that I receive mails and spams are tagged. Dovecot version 1.1.7-r1 compiled from the gentoo depository with debug. The path of a mail is 1/ to be passed to dspam by postfix as a virtual transport with this in master.cf: dspam unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/dspam --client --deliver=innocent,spam --user ${recipient} and this in main.cf: virtual_transport = dspam 2/ Then in dspam.conf, I have: TrustedDeliveryAgent "/usr/libexec/dovecot/deliver -d %u" UntrustedDeliveryAgent "/usr/libexec/dovecot/deliver -d %u" QuarantineAgent "/usr/libexec/dovecot/deliver -d %u -m Junk" Now dspam is tagging a lot of my spams, with [SPAM] on the subject and in the header stuffs like this: X-DSPAM-Result: Spam X-DSPAM-Processed: Thu Feb 5 23:49:02 2009 X-DSPAM-Confidence: 0.5232 X-DSPAM-Probability: 0.9869 X-DSPAM-Signature: 498b6cde61901804284693 X-DSPAM-Factors: 27, Subject*watch, 0.99000, a+loved, 0.99000, Subject*for+all, 0.99000, ... ... But I wanted spam to go in my Junk folder (using maildir, this is the directory .maildir/.Junk for my configuration. Hence the above configuration of QuarantineAgent. But it doesn't work as my emails are still deliverd to INBOX. How could I check that dovecot deliver is taking into account the option "-m Junk"? Or maybe I don't use it well? (I tried also "-m .Junk" as it it the name of the directory but it is the same) Note also that I use maildir format, so maybe this option works only with mailbox? The doc says: -m <mailbox>: Destination mailbox (default is INBOX). In my dovecot.conf, I have: protocol lda { hostname = mydomain.tld log_path = /home/vmail/dovecot-deliver.log info_log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master } And when a deliver occures, that's all I have in dovecot-deliver.log: deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: recipient(a)mydomain.tld deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: home=/home/vmail/mydomain.tld/recipient/ deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: uid=1004 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: gid=1004 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: maildir: data=/home/vmail/mydomain.tld/recipient/.maildir deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: maildir++: root=/home/vmail/mydomain.tld/recipient/.maildir, index=, control=, inbox= =/home/vmail/mydomain.tld/recipient/.maildir deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Warning: Growing pool 'Cache fields' with: 2048 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: msgid=<000d01c987ed$879c82f0$6400a8c0@biancauj3>: saved mail to INBOX Is there a way to check the options set on parameters in the logs, so that I check that dspam runs indeed QuarantineAgent? Or would you have other solution/hints? Someone on the dspam ml told me that maildrop or sieve are more flexible. So I explain here that my "reason" was simply that I thought it would be better not to install another software/component to remain simple. Moreover with the "-m" option, dovecot-deliver seemed to do just what I needed (I don't need much more complicated). But maybe I am wrong or it is really better not to use dovecot-deliver. If so, just tell me. Thanks. Jehan

2 1

[Dovecot] Tracing a server problem
by Luigi Rosa 06 Feb '09

06 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Linux CentOS server, 4 Gb RAM, with 50 IMAP users. The server is connected to LAN via a firewall appliance, no filtering applied. Many users with different clients complain a lot of "server disconnected" errors. On the server side Doveco does not report any kind of error. I just ab an unusual rate of "IMAP(xxxxxx@xxxx): Disconnected: Logged out" entries. Given that I am NOT sure about the ethernet an firewall performance, how can I trace this problem? Dovecot is 1.1.10, configured with --with-mysql --with-ssl=openssl - --disable-ipv6 --sysconfdir=/etc --localstatedir=/var Userbase is mysql only. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Too much blood in my alcohol system. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmIG1MACgkQ3kWu7Tfl6ZQaawCeJbF4hplK06BcSkNnjqg7Lq60 5wsAoJGLKo0+GUiLLPKbyXD0bAtxderl =LTpZ -----END PGP SIGNATURE-----

4 5

[Dovecot] Expire plugin does not work
by Nicolas Letellier 06 Feb '09

06 Feb '09

Hi. I test expire plugin for my dovecot 1.1.8. But, it seems to not work. I have 3 mailboxes on my machine. I want my messages in Junk and Trash expire after 1 day. I removed all messages in them before installing expire plugin. See my dovecot.conf: expire: Trash 1 Junk 1 expire_dict: proxy::expire My dabatases in /var/lib/dovecot are used. When I launch /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test, it says: Info: user3(a)domain.tld/Trash: stop, expire time in future: Wed Feb 4 21:00:50 2009 Why this message? I have 3 mailboxes, and the message appears only with this mailbox. The 2 others mailbox have mails into Trash and Junk folders. And the mail are older than 2 days. An ls -lcs say it. When I launch /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool, no messages appears. Nothing in my dovecot logs. Nothing (and I set mail_debug). No messages are deleted. In a mailbox1, I have this into Junk/cur directory: 4 -rw------- 1 dovecot dovecot 3822 Feb 2 13:39 1233569469.M275631P48216.***.***.net,S=3822,W=3945:2,S 4 -rw------- 1 dovecot dovecot 3004 Feb 2 15:43 1233585799.M730005P46882.***.***.net,W=3078,S=3004:2,S 4 -rw------- 1 dovecot dovecot 3056 Feb 2 17:49 1233587786.M676156P51401.***.***.net,S=3056,W=3132:2,S 4 -rw------- 1 dovecot dovecot 3732 Feb 2 17:49 1233592892.M701994P52459.***.***.net,S=3732,W=3823:2,S We are Feb 4, and these message are always here. No informations with mail_debug, or with --test parameter.These messages were arrived Feb 2, and they might have this date in dovecot.index.cache... How expire plugin is working? I don't understand it... -- -Nicolas.

2 2

[Dovecot] ¿DC won't start? "leaked file fd 5:"
by mathemat＠gmx.net 06 Feb '09

06 Feb '09

Hi Gents, (apologizes, new here...) I didn't find any hint on G**gle nor in the Dovecot archieve (maybe due to the lack of a search function :), so: I installed Doovecot, but can't get it going. The logfile states: > mail.info dovecot: Dovecot v1.0.15 starting up > mail.err dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 inode 3 > mail.err dovecot: Auth process died too early - shutting down I tried many obscure things to recover, but had no luck so far. As long i am just guessing around (auth? dev 0.10?? maybe SSL config?), i have no clue what happens here :(. To make things more interesting: the installation lives on an embedded device (xscale, aka arm w/4MB RAM), where are no extended debug features available (like ltrace, ldd,...), and no newer packages (if exist) available. Tried so far: * uninstall (ipkg remove) * rm'd all files listed in the package description + /var/run/dc/* * reinstall (ipkg install) * changed the config file (in many ways... but what??) The init-script does mainly "/opt/sbin/dovecot", so i tried that command on the CLI(bash) to be sure no script mangles fd's around. "echo $?" gives "0" then, but no DC process is running- log messages as above. I have no clue what to do abt that- where's the point?? Can this hopefully be done whithout installing the complete gcc toolchain and compiling a newer version from source, but by just adapting the config? 8-| Any helpful hints appreciated!, acend -- -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

2 1

Re: [Dovecot] The 'dbox' Format
by Alexander Beisig 06 Feb '09

06 Feb '09

Timo Sirainen wrote: > On Thu, 2009-02-05 at 22:42 +0100, Alexander Beisig wrote: > > I'd like to give the dbox format a try, but I could not find any > > information on how to enable it. There's information on how to set > > mail_location for the Maildir and mbox formats in the wiki and also in > > the commented configuration file, but how to set it for dbox is > > strangely missing. I took a guess with 'mail_location = dbox:~/dbox', > > but that didn't work, so it's probably not the right way. > > That's correct. > > > Also, the version of Dovecot that Debian installed was 1.0.15, which > > is kinda old. Should there any serious reasons why I should manually > > install a newer version if I'm going to use dbox? > > v1.0's dbox is completely different from what v1.1 has. It's also not > compiled in by default in v1.0. So don't even try using it. Ok thanks, so I downloaded the recent 1.1.11 release. But I still don't know how to enable the dbox format. I think dovecot-example.conf should explain how to enable it, unless you really don't want people to use this format. ____________________________________________________________________ Psssst! Schon vom neuen WEB.DE MultiMessenger gehört? Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123

2 1