- dovecot - dovecot.org

[Dovecot] sluggish updating of gnome mail-notification?
by Greg Troxel 19 Jul '07

19 Jul '07

Sorry if this is a repeat query. I am running dovecot 1.0.2 under NetBSD/i386 (3.1 and 4.0ish). I use maildirs, and deliver into them with procmail. For clients I use Gnus (CVS head) mostly and thunderbird, and also the gnome mail-notification status applet (4.0). Gnus fixed a bug in the last few months where exiting a group didn't unselect the folder and thus didn't necessarily push read marks back. Mostly everything works perfectly. When new mail arrives, thunderbird shows it as new/unread, gnus will find it with 'g', and mail-notification shows it as well. After reading it in gnus, when I exit the group (which pushes read marks to the IMAP server), thunderbird usually shows the message as read immediately, but often mail-notification waits for a while (up to about a minute) before withdrawing the new-mail notification. I just tried this and thunderbird was also slow in showing the mail read. marking the message read in thunderbird caused mail-notification to show the message as read, but with a 30s lag. mail-notification is supposed to use IDLE if available. Sometimes it withdraws new-mail claims at the right time. I know that I need to turn on debugging and trace all this. So I'm really just asking if anyone else has seen this or similar behavior.

2 1

[Dovecot] Performance question
by Stewart Dean 19 Jul '07

19 Jul '07

I now have Dovecot in production and things are apparently trouble-free. The one known problem is that initial client inbox load can take 30 seconds - 2 minutes. For instance: 'I got fed up waiting and went and got coffee'...this with a 3MB mbox inbox...and my mail server is a substantial machine consuming 25% CPU just for this person's IMAP session. I realize that a certain amount of performance piggishness is inevitable with large mbox inboxes (the prize goes to the user with a 500MB inbox). Eventually, I plan to move to maildir format, but for now I'm here. Also, we have legacy requirement for procmail, so I can't currently use deliver. Questions: 1) Any tuning I can do to improve this? 2) Any metrics, troubleshooting I should be doing to better characterize the problem? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] avoiding getting maildir cur/ folder contents?
by Johannes Berg 19 Jul '07

19 Jul '07

Hi, On my server with many mails in one folder and slow IO, getting the mail listing in the cur/ folder is becoming a serious bottleneck. Dovecot is the only thing accessing the mail folders, so would there be any way to avoid getting a listing all the time? johannes

3 8

[Dovecot] Small problem with src/lib/mountpoint.c [now with patch attached!]
by Mike Brudenell 19 Jul '07

19 Jul '07

Greetings - [SIGH: I hit the "Send" button instead of "Attach". Here's Take 2...] Whilst playing with getting quotas from NFS-mounted filestores I've just discovered a slight problem with src/lib/mountpoint.c I had things working on a Solaris 10 test machine which had the mailstore mounted 'normally' using an entry in /etc/vfstab. However when I changed to use the automounter for the mailstore obtaining the quota broke. The problem lies with mountpoint_get(). On a 'normally' mounted filestore this obtains the device_path of the remote filestore in the form remoteservername.some.domain:/remote/path However when the mailstore was automounted I was instead getting back auto_direct which is the name of the automounter map we're using. The /etc/mnttab file has TWO entries for the auto-mounted filestore, like this: auto_direct /mailstore/messages/p autofs direct,ignore,dev=4740014 1184648400 crypt2.york.ac.uk:/vol/vol9/p /mailstore/messages/p nfs proto=tcp,xattr,dev=4700386 1184668792 Although there are two entries they have different device numbers. The mountpoint_get() function attempts to guard against this by checking the device number obtained matches that of the path being located. However for some reason I don't understand when getmntent() returns the FIRST of the above two entries it supplies the device number of the SECOND. Thus the device numbers match in the mountpoint_get() test and it thinks it has found the correct entry. This leads to the device_path being set to the map name -- auto_direct -- instead of the host:/path My fix is to add an additional fstype for the test to ignore: "autofs". The loop skips over any such mounts (along with the existing tests for "swap" and "ignore"). I'm attaching my minimal patch in case it's of help to anyone else. (Timo: would it be possible to get this added into the distribution code if you agree it's right?) Cheers, Mike Brudenell -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 5

[Dovecot] Shared folders and LDAP?
by Gavin Henry 19 Jul '07

19 Jul '07

Dear All, Is it possible to store shared folder lists in an LDAP Directory along with your virtual users? Will check the wiki too. Thanks, Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

2 4

[Dovecot] assertion failed
by Ralf Hildebrandt 19 Jul '07

19 Jul '07

I'm getting these in my log: Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child 24406 (login) killed with signal 6 This is dovecot-1.0.2 -- is this something to worry about? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de There are two ways to write error-free programs. Only the third one works.

2 4

[Dovecot] Integrating dovecot 1.01 into CentOS-3.8 systemw with chroot passwd dirs?
by Gary Goldberg 19 Jul '07

19 Jul '07

Hello. I'm administrating a CentOS 3.8 linux system (RHEL3) and I just replaced the imap-2002d-12 package that came with the system, with a dovecot 1.01 package I obtained through the dovecot home page. The problem I have, is that many of my POP3 users have jailed user accounts set up through wu-ftpd, where the dir field is of the form /home/group/./pop/user, and wu-ftpd chroots them from /home/group but then places them into their home directories, in this case /home/group/pop/user. dovecot can't seem to locate their mail directory. Can anyone offer any advice on this situation? Please respond to my email address <og at digimark.net> if you could. --- Here are some relevant stats: example user: lda01 home directory (in /etc/passwd: /home/lda/./pop/lda01 mail folder directory: /home/lda/pop/lda01/mail INBOX: /home/mail/lda01 (/var/mail, /var/spool/mail symlinked to /home/mail.) dovecot 1.01 output of dovecot -n: #1.0.1: /etc/dovecot.conf base_dir: /var/run/dovecot log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s ssl_disable: yes ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/certs/dovecot.pem 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: mail.digimark.net ready. valid_chroot_dirs: /var/mail:/var/spool/mail:/home/mail:/home mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/home/mail/%u mail_debug: yes mail_full_filesystem_access: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 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): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu auth default: passdb: driver: pam args: blocking=yes dovecot userdb: driver: passwd attempt to login using a Squirrelmail (webmail) client gave these entries in the dovecot.log error log: dovecot: Jul 12 16:22:50 Info: imap-login: Login: user=<lda01>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Jul 12 16:22:50 Info: IMAP(lda01): Effective uid=10572, gid=510, home=/pop/lda01 dovecot: Jul 12 16:22:50 Info: IMAP(lda01): mbox: data=/pop/lda01/mail:INBOX=/home/mail/lda01 dovecot: Jul 12 16:22:50 Info: IMAP(lda01): mbox: root=/pop/lda01/mail, index=/pop/lda01/mail, inbox=/home/mail/lda01 dovecot: Jul 12 16:23:04 Error: IMAP(lda01): open(/home/mail/lda01, O_CREAT) failed: No such file or directory dovecot: Jul 12 16:23:04 Error: IMAP(lda01): access() failed with mbox file /home/mail/lda01: No such file or directory dovecot: Jul 12 16:23:04 Error: IMAP(lda01): stat() failed with mbox file /home/mail/lda01: No such file or directory dovecot: Jul 12 16:23:58 Info: IMAP(lda01): Disconnected: Logged out -- -- "Outside of a dog, a book is a man's best friend. -- Inside of a dog, it is too dark to read." -- Groucho Marx. Gary Goldberg KA3ZYW <og(a)digimark.net> V:301/249-6501 F:301/390-1955 AIM:OgGreeb Digital Marketing/Bowie MD/Systems & Networks Consult <http://www.digimark.net/>

3 7

[Dovecot] production switchover questions
by Stewart Dean 19 Jul '07

19 Jul '07

So far so good...other than a my-bad fubar with the permission on the index directory that kept DC from creating index dirs for the entering-for-the-first-time users, quickly noticed (thanks to the excellent logging) and corrected. Some questions 1) the max_mail_processes parm in dovecot.conf...is that *all* processes owned by dovecot? 2) I thought there was a parm to limit how many processes each user can have, but can't seem to find it. Is there any way to control that? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] deleting maildir files
by Tom Bombadil 18 Jul '07

18 Jul '07

Greetings all... Can we delete maildir files directly from the file system? Basically, we use dovecot to train spam, and we want to delete messages that are older than 30 days, using a simple "find /maildirs -cname +30 -name *imap-server* -exec rm {} \;" I have seen a post a while ago saying that dovecot can rebuild the indexes, but I don't remember if it's when the index is deleted or when the maildir files are deleted. And if we cannot delete files with the 'rm' command, whats the best/proper way to delete these older files. Thanks

8 16

[Dovecot] A little OT but hopefully still related enough... Maildir Delivered mail naming problems.
by Jesse C. Smillie 18 Jul '07

18 Jul '07

Normally I wouldn't post off topic to a mailing list, but I have posted every where else I can think of and haven't had any success yet working this out. I know there has to be a few people here with extensive knowledge of how mail works and maybe just a tip in the right direction would help me out at this point. I have migrated from mbox format to Maildir format in the last week. I used the utility mb2md.pl to convert all of our existing emails from one system to the next. I then modified my /etc/procmailrc file by putting this at the top: MAILDIR=$HOME/Maildir DEFAULT=$MAILDIR/ This way procmail is forced to deliver to the new format as well. For the most part all of this is working perfectly. Procmail is delivering emails to their new proper folder and even extended rules in users own ~/.procmailrc are working well once the folder path was changed from $MAILDIR/whatever to $MAILDIR/.whatever/. Works great. I am using Dovecot 1.0.1 to deliver our email through the IMAP protocol and with the clients we support (Thunderbird and Outlook) things are working very well for us. So now to my problem. We also use Usermin for our users to access their email when they don't have a supported client available to them. When users look at their email with Usermin their emails are out of order regardless of weather I have Usermin's "Read Mail" module using IMAP to get mail or have it read the users Maildir directly. Sorts are just all jacked up. Sometimes if users then click the "Date" button to sort by date it snaps to; sometimes it don't. I currently have multiple posts on the Webmin/Usermin mailing list about this problem and it really seems to point back to the naming scheme of our emails now. All emails which were converted have the classic maildir format. UnixTime.PID.Server... 1183737827.002379.mbox:2,RS 1183737827.002388.mbox:2,RS 1183737827.002392.mbox:2,RSa 1183737827.002394.mbox:2,RS However, all the email that is delivered after the fact is different. They all look like this: _oTH.XqwlGB.gator:2,RS _p2F.qjVlGB.gator:2,RS _qQF.2mpjGB.gator:2,Sa _sK.8mTlGB.gator:2,RSa _uOG.gCtjGB.gator:2,RS _uxG.a6lkGB.gator:2,RS _vnF.n-2lGB.gator:2, _x9H.llckGB.gator:2, _z3G.k8klGB.gator:2,S _z5G.kAilGB.gator:2,RS I have been searching the net for a few hours and reading various documentation here and there and I haven't been able to find anything that tells me why my mail is being named this way or how to fix it. I can say that my test box which also runs 10.2 slamd also delivers this exact same way.... For the most part I'm being told that the reason why Usermin's sort is all screwed up (order wise) in IMAP mode is that messages are displayed in the order that the IMAP server reports them. Like wise in Maildir mode the order which they are read. I can understand why this naming stuff throws everything off at this point. What I don't understand is why its doing this. I mean I'm pretty sure there is nothing here out of the ordinary as far as my config. I have searched all over the net the last few days and haven't been able to find anything useful. So in wrap up sorry for being a little OT and thanks a head of time for any info or light anyone can share here. -Jesse Smillie

2 2