- dovecot - dovecot.org

[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