- dovecot - dovecot.org

[Dovecot] RC16 is a lot slower that RC7
by Marc Perkel 11 Jan '07

11 Jan '07

I tried RC16 from RC7 and like other releases since RC7 it is significantly slower. I'm still trying to figure out why. But I have again switched back. Do new version take up a lot more ram perhaps? I'm running with a gig of ram, and I'm running a few other apps. It's not a fast computer, just an old 754 pin semptron. But the point is that RC7 runs a lot faster than RC16.

2 2

[Dovecot] rc17 Linux RPM distribution rebuild trouble.
by Serge D 11 Jan '07

11 Jan '07

The question is addressed to Linux RPM-packagers. Hello! I was trying to rebuild rc17 binaries from dovecot-1.0-1_38.rc17.at.src.rpm taken at ATrpms <http://ATrpms.net/>. The process fails with following messages: -------------------- Making install in imap-quota make[3]: Entering directory `/usr/src/asplinux/BUILD/dovecot-1.0.rc15/src/plugins/imap-quota' make[4]: Entering directory `/usr/src/asplinux/BUILD/dovecot-1.0.rc15/src/plugins/imap-quota' make[4]: Target `install-exec-am' does not require perform any command. test -z "/usr/lib/dovecot/imap" || mkdir -p -- "/var/tmp/dovecot-1.0-0_34.rc15-root/usr/lib/dovecot/imap" mkdir: `/var/tmp/dovecot-1.0-0_34.rc15-root/usr/lib/dovecot/imap' exists, but it is not a directory make[4]: *** [install-imap_moduleLTLIBRARIES] Error 1 ------------------- As I have not so much experience at RPM-packaging, so would be thankful for the ideas how to fix it? Kind regards, - Serge.

2 5

[Dovecot] mbox-rewrite errors
by T. Horsnell 11 Jan '07

11 Jan '07

I've noticed a burst of about 12000 of these mbox-rewrite msgs in the log, spread over about 10 minutes. They are always for the same person (XXX'd out here), and have not occurred before or since. There's no evidence of device problems in the message log. Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Jan 10 17:46:43 ls1 dovecot: child 6004 (imap) killed with signal 6 Jan 10 17:46:43 ls1 dovecot: child 6006 (imap) killed with signal 6 Jan 10 17:46:43 ls1 dovecot: child 6008 (imap) killed with signal 6 Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 dovecot: child 6010 (imap) killed with signal 6 Jan 10 17:46:43 ls1 dovecot: child 6012 (imap) killed with signal 6 Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Do I need to worry? I'm still using dovecot-0.99.11-4 on a RHEL4 Opteron box. Cheers, Terry.

1 0

[Dovecot] 1.0.rc17 released
by Timo Sirainen 11 Jan '07

11 Jan '07

http://dovecot.org/releases/dovecot-1.0.rc17.tar.gz http://dovecot.org/releases/dovecot-1.0.rc17.tar.gz.sig - MySQL authentication caused username to show up as "OK" in rc16.

5 9

Re: [Dovecot] LDAP authentication stops working...
by "Αποστόλης Παπαγια ννάκης (Apostolis Papagiannakis)" 11 Jan '07

11 Jan '07

> > Date: Wed, 10 Jan 2007 16:07:03 +0100 > From: "J.M. Maurer" <mmaurer(a)betterbe.com> > Subject: Re: [Dovecot] LDAP authentication stops working... > To: dovecot(a)dovecot.org > Message-ID: <1168441623.11613.3.camel(a)sigma.lan.uwog.net> > Content-Type: text/plain > > On Tue, 2007-01-09 at 09:54 +0000, Gavin Henry wrote: > >> > <quote who="Adrian Close"> >> >>> > > Hi all, >>> > > >>> > > I'm running dovecot-1.0.rc17 on OpenBSD 3.9, using userdb and passdb >>> > > methods of "ldap" (SSL on 636/tcp) in addition to "passwd". >>> > > >>> > > Occasionally (generally after a few hours of operation, but not always), >>> > > LDAP-based logins stop working (e.g. hang/timeout after POP3 PASS >>> > > command). Accounts with local passwords (as opposed to accounts with a >>> > > password field of "x") still work fine at this point. >>> >> > >> > We also get this. Twice a day we have to restart dovecot, using userdb and >> > passdb via LDAP, with userdb_prefetch. >> > > Just to add: we moved from rc<something before 5> to rc15 recently, and > we now also see a lot of hangs with > > The result handler for the initial ldap_search to find the dn to bind to > is never called. I assume Timo fscked something up recently in my > auth_bind code ;-P > > Anyway, restarting ldap every hour or so with cron does the job :-| > > I'd debug this if I had the time, but I won't have before next week. > > Cheers, > Marc > > > > --- I haven't documented it properly (yet) but when using rc15 with userdb_prefetch + passdb + ldap_authbind (200-500 concurrent clients) directly with LDAP it operates OK only for a few minutes. After a while authentication freezes. On the LDAP server (openldap v2.2.28) I see countless log entries such as: " slapd[24721]: connection_input: conn=1134942 deferring operation: binding". Dovecot show I tried to increase various dovecot and openldap limits without success. Until the problem is solved, I use Dovecot with getpwnam (/etc/passwd) + pamldap which works always OK. Could anybody please verify that direct LDAP userdb_prefetch, passdb, auth_bind work ok with openldap under heavy stress? Is it possible that multiple concurrent LDAP bind requests and searches under different LDAP credentials through the very same TCP connection produce some kind of spourious problem? Apostolis Papagiannakis Aristotle University of Thessaloniki, Greece

1 0

[Dovecot] [sfs: dovecot-auth file descriptor usage]
by Steven F Siirila 10 Jan '07

10 Jan '07

I am re-posting this message from last Friday, as I have seen no replies. It is critical that we address this problem, since until then we cannot put more than a few hundred users on our server. If Dovecot-auth TRULY needs to keep open a file descriptor for every single login session, we will have to start looking at alternatives. In short: Help! ----- Forwarded message from Steven F Siirila <sfs> ----- Date: Fri, 5 Jan 2007 13:55:38 -0600 From: Steven F Siirila <sfs> To: dovecot(a)dovecot.org Subject: dovecot-auth file descriptor usage User-Agent: Mutt/1.4.2.1i In dovecot-auth (rc15) we experienced problems when the file descriptors reached 256 (due to a Solaris fdopen() call described previously). The issue was that there was one file descriptor being used for every imap-login and pop3-login process (in our environment of SSL-only that means one for every active IMAP and POP connection). Mods were made (and appear in rc16) to close out the descriptor in question after using it during authentication (as I understand it). However, I am still seeing plenty of file descriptors left open in rc16 (one per session). For example, on a Solaris 9 server with 9 IMAP connections open here is an lsof excerpt of dovecot-auth: dovecot-a 26071 root 7u unix 105,136 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3000d084250) dovecot-a 26071 root 8u unix 105,140 0t80 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3c9c4227b68) dovecot-a 26071 root 9u unix 105,149 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3cbaa7680b8) dovecot-a 26071 root 10u unix 105,266 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3cbaa765d48) dovecot-a 26071 root 11u unix 105,160 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3cbaa7667e0) dovecot-a 26071 root 12u unix 105,255 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x3cbaa769288) dovecot-a 26071 root 13r DOOR 265,0 0t0 50 /var/run (swap) (door to nscd[7752]) dovecot-a 26071 root 14u unix 105,258 0t79 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x30002dc4008) dovecot-a 26071 root 15u unix 105,282 0t80 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x30003185738) dovecot-a 26071 root 16u unix 105,141 0t80 3190 /devices/pseudo/tl@0:ticots->/var/opt/dovecot/run/dovecot/login/default (0x30003185ac8) With the modification made, shouldn't these no longer accumulate? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593 ----- End forwarded message ----- -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 2

[Dovecot] pre-1.0.rc6 / index file problems? try this
by Timo Sirainen 10 Jan '07

10 Jan '07

People who have had "duplicate header extension" and whatever other random index file corruption problems, please see if this fixes anything: http://dovecot.org/list/dovecot-cvs/2006-December/007315.html The change is also in the latest nightly snapshot (http://dovecot.org/ nightly/dovecot-latest.tar.gz). You could in general treat the latest snapshot as "pretty much the same as the 1.0.rc16 release", so some testing for it would be nice. I've updated autotools that were used to build the snapshot, does anyone have problems with compiling the snapshot? I'm going to build the 1.0rc16 release using the same autotools. rc16 has several changes intended to make Mac OS X's HFS+ happy. This is mostly because currently the only computer I have is a Powerbook. I'll get a new Linux machine in a couple of weeks hopefully. I've still about 50 unread/possibly unanswered mails. I'll try to get to them soon. Here's a list of all the important changes: * IMAP: When trying to fetch an already expunged message, Dovecot used to just disconnect client. Now it instead replies with dummy NIL data. * Priority numbers in plugin names have changed. If you're installing from source, you should delete the existing plugin files before installing the new ones, otherwise you'll get errors. * Maildir: We're using rename() to move files from tmp/ to new/ now. See http://wiki.dovecot.org/MailboxFormat/Maildir -> "Issues with the specification" for reasoning why this is safe. This makes saving mails faster, and also makes Dovecot usable with Mac OS X's HFS+ (after you also set dotlock_use_excl=yes, see below). + Added dotlock_use_excl setting. If enabled, dotlocks are created directly using O_EXCL flag, instead of by creating a temporary file which is hardlinked. O_EXCL is faster, but may not work with NFS. + If Dovecot crashes with Linux or Solaris, it'll log a "Raw backtrace". It's worse than gdb's backtrace, but better than nothing. + Added maildir_copy_preserve_filename=yes setting. + Added a lazy-expunge plugin to allow users to unexpunge their mails. + maildir quota: Added ignore setting to maildir quota, which allows ignoring quota in Trash mailbox. + dict quota: If dictionary doesn't yet contain the quota, calculate it by going through all the mails in all the mailboxes. + login_log_format_elements: Added %a=local port and %b=remote port - Doing a STATUS command for a selected mailbox (not a recommended IMAP client behavior) caused Dovecot to sync the mailbox silently. This could have lost eg. EXPUNGE events from clients, causing them to use wrong sequence numbers. - deliver was treating boolean settings set to "no" as if they were "yes" (they were supposed to be commented out for "no") - Running "dovecot" with -a or -n option while Dovecot was running deleted all authentication sockets, which caused all the future logins to fail. - maildir: RENAME and DELETE didn't touch control directory if it was different from maildir or index dir. - We treated internal userdb lookup errors as "user unknown" errors. In such situations this caused deliver to think the user didn't exist and the mail get bounced. - pam: Setting cache_key crashed - shared maildir: dovecot-keywords file's mode wasn't taken from dovecot-shared file. - dovecotpw wasn't working with PowerPC

4 7

[Dovecot] 1.0.rc16 released
by Timo Sirainen 10 Jan '07

10 Jan '07

http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz http://dovecot.org/releases/dovecot-1.0.rc16.tar.gz.sig If you've had problems with getting errors about index files sometimes being corrupted, please try if this release fixes it. If you've reported any bugs that this release hasn't fixed, please report them again so I know they still didn't get fixed and that I didn't forget them. * IMAP: When trying to fetch an already expunged message, Dovecot used to just disconnect client. Now it instead replies with dummy NIL data. * Priority numbers in plugin names have changed. If you're installing from source, you should delete the existing plugin files before installing the new ones, otherwise you'll get errors. * Maildir: We're using rename() to move files from tmp/ to new/ now. See http://wiki.dovecot.org/MailboxFormat/Maildir -> "Issues with the specification" for reasoning why this is safe. This makes saving mails faster, and also makes Dovecot usable with Mac OS X's HFS+ (after you also set dotlock_use_excl=yes, see below). + Added dotlock_use_excl setting. If enabled, dotlocks are created directly using O_EXCL flag, instead of by creating a temporary file which is hardlinked. O_EXCL is faster, but may not work with NFS. + If Dovecot crashes with Linux or Solaris, it'll log a "Raw backtrace". It's worse than gdb's backtrace, but better than nothing. + Added maildir_copy_preserve_filename=yes setting. + Added a lazy-expunge plugin to allow users to unexpunge their mails. + maildir quota: Added ignore setting to maildir quota, which allows ignoring quota in Trash mailbox. + dict quota: If dictionary doesn't yet contain the quota, calculate it by going through all the mails in all the mailboxes. + login_log_format_elements: Added %a=local port and %b=remote port + Added -i and -o options to rawlog to restrict logging only to input or output. - Doing a STATUS command for a selected mailbox (not a recommended IMAP client behavior) caused Dovecot to sync the mailbox silently. This could have lost eg. EXPUNGE events from clients, causing them to use wrong sequence numbers. - deliver was treating boolean settings set to "no" as if they were "yes" (they were supposed to be commented out for "no") - Running "dovecot" with -a or -n option while Dovecot was running deleted all authentication sockets, which caused all the future logins to fail. - maildir: RENAME and DELETE didn't touch control directory if it was different from maildir or index dir. - We treated internal userdb lookup errors as "user unknown" errors. In such situations this caused deliver to think the user didn't exist and the mail get bounced. - pam: Setting cache_key crashed - shared maildir: dovecot-keywords file's mode wasn't taken from dovecot-shared file. - dovecotpw wasn't working with PowerPC

4 6

Re: [Dovecot] 1.0.rc17 released
by Janne Johansson 10 Jan '07

10 Jan '07

Ouch didn't get the maillist on the receiver list. > > > 2007/1/10, Thomas Zajic <zlatko(a)zlatko.fdns.net>: > > > > * John Peacock, 2007-01-09 19:35 > > > > > [...] > > > When trying to move large numbers of messages to Trash using > > Thunderbird > > > 1.5.0.9, I would get "Lost connection with server" messages at > > anything > > > over about 1500 messages. The strange thing is that when I checked > > the > > > trash folder, the deleted messages were there multiple times, i.e. > > > everytime I attempted to move all messages to Trash, plus everytime it > > > > > failed until I got below the magic number. > > > [...] > > > > I think this is a Thunderbird problem rather than a Dovecot one. I had > > the same thing happening recently when I moved last year's logfiles to > > my archive folder (36000+ messages). > > > > I had this on 1.0rc10, and moved to 1.0rc15 and it went away (or pushed > the limits > over the number of messages I wanted to delete) and I was also using > Thunderbird 1.5.0.x. > I'll report if it happens to me again. > > > -- Some mornings, it's just not worth gnawing through the straps...

3 3

[Dovecot] dovecot cannot access the then new created folders by squirrel mail?
by shamsurrahman 10 Jan '07

10 Jan '07

hi, i use dovecot and squirrelmail wwbmail to access my mails in fc6, every thing is working ok, but the only thing quirrel mail can create new folders but can't acces or open them for example i created folder accounts by squirrelmail it was created but can't open, this is the permissions for the accounts in the ~/mail/: drwx------ 2 jaan jaan 4096 Jan 8 07:14 accounts -rwxr-xr-x 1 jaan jaan 0 Jan 8 20:35 draftbox any one can help please?

2 1