- dovecot - dovecot.org

[Dovecot] parser bug
by DINH Viêt Hoà 13 Oct '06

13 Oct '06

hello Timo (and maybe other Dovecot developers), It looks like the MIME parser won't parse this correctly : Content-type: text/html Note the lower-case '-type' in 'Content-type'. -- DINH V. Hoa

2 1

[Dovecot] Feature req: auth_cache_relookup
by Bill Boebel 13 Oct '06

13 Oct '06

With auth_cache_size set to a value greater than zero, when our users change passwords their accounts stop working for a few minutes, because they are trying to log in with their new password, but Dovecot is comparing that against the cached old password. It would be nice if an option could be added so that if the login password does not match the cached password, the cache value is dropped and dovecot-auth queries the userDB, but only if the previous login was successful (to avoid frequent queries for bad logins). Maybe this option could be called "auth_cache_relookup" Bill

2 1

[Dovecot] default_mail_env renaming
by Timo Sirainen 13 Oct '06

13 Oct '06

I was thinking about renaming default_mail_env to something that is more understandable. I'll keep it working for backwards compatibility anyway. How about: # Location for users' mailboxes. This is the same as the old default_mail_env # setting. The default is empty, which means that Dovecot tries to find the # mailboxes automatically. This won't work if the user doesn't have any mail # yet, so you should explicitly tell Dovecot the full location. # # If you're using mbox, giving a path to INBOX file (eg. /var/mail/%u) isn't # enough. You'll also need to tell Dovecot where the other mailboxes are and # where Dovecot can place its index files. # # There are a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # mail_location = maildir:/var/mail/%1u/%u/Maildir # mail_location = mbox:~/mail/:INBOX=/var/mail/%u # mail_location = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # # http://wiki.dovecot.org/MailLocation # #mail_location =

2 2

[Dovecot] Todo page?
by Francisco Reyes 13 Oct '06

13 Oct '06

Is there a Todo list? Looking for it in search function I think I saw one in CVS.. Is there a web CVS interface? I found the changelog in http://dovecot.org/nightly/, but did not see a Todo.

2 2

[Dovecot] 1.0.rc8 released
by Timo Sirainen 13 Oct '06

13 Oct '06

I've still over 200 mails unread in the mailing list, and important things left in TODO. This release is an improvement over rc7 anyway, hopefully I'll have time to fix the rest soon. http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz http://dovecot.org/releases/dovecot-1.0.rc8.tar.gz.sig * GSSAPI: Changed POP3 service name to "pop", which is what the standard says * "mbox:/var/mail/%u" no longer works as the mail location. You'll have to specify the mail root explicitly, just like the examples always have: "mbox:~/mail:INBOX=/var/mail/%u" + SHA1, LDAP-MD5, PLAIN-MD5, PLAIN-MD4: The password can be now either hex or base64 encoded. The encoding is detected automatically based on the password string length. + Allow running only Dovecot master and dovecot-auth processes with protocols=none setting + deliver: -f <envelope sender> parameter can be used to set mbox From_-line's sender address + deliver: Log all mail saves and failures + Tru64 SIA passdb support. Patch by Simon L Jackson. - INBOX was listed twice in mailbox list if namespace prefix was used - INBOX-prefixed namespaces were a bit broken - kqueue: Fix 100% CPU usage - deliver: Duplicate storage was a bit broken - dictionary code was broken (ie. dict quota) - SIGHUP caused crashes sometimes

3 14

[Dovecot] 1.0rc8: another problem? Possibly 64-bit index?
by David Lee 13 Oct '06

13 Oct '06

Yesterday I gave a status report about 10.rc8 in production, which mentioned a problem about "Login process died too early..." Timo suggested a patch for logging error messages. I've applied this. Others suggested increasing "login_max_processes_count". That was already way above our likely maximum, but I've doubled it anyway. Today, I've just repeated the trial, but with one significant difference and one significant new problem. The significant difference is that today's machine is not a 32-bit i686 but a 64-bit (and faster) x86_64. The new problem is lots of occurences of: [...]: IMAP([...]): file ../../../src/lib-index/mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) [...]: child 4365 (imap) killed with signal 6 and: [...]: IMAP([...]): file ../../../../src/lib-storage/index/index-mail.c: line 105 (index_mail_get_fixed_field): assertion failed: (buffer_get_used_size(buf) == data_size) [...]: child 15009 (imap) killed with signal 6 Naturally, I've backed off quickly. Theoretically, this problem could be attributed to any of the three changes: logging, max processes, different (64-bit) machine. I suspect it's not the "login_max_processes_count" increase. Is it a side-effect of the better logging? (That is, was it always happening but the information simply not getting logged?) Note that our index files (and mail spool (INBOX, folder) areas) are on an NFS (NetApp) shared area accessed by all three classes of our machines: o existing UW-IMAP (which doesn't use the indexes) o yesterday-dovecot (32-bit) o today-dovecot (64-bit) My sneaky suspicion is that this is a subtle 64-bit-ism, either on its own, or in some sort of interaction with an indexes created from yesterday's 32-bit client. (Yes, theoretically, I could try another test to attempt to confirm or eliminate the 32/64 difference. But these issues didn't show up under testing, but only when we began trial service; I can't experiment on the users!) -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

8 10

[Dovecot] Received dates problem in Outlook after migration
by James Wyper 13 Oct '06

13 Oct '06

Hello everyone, I've just started using 1.0-beta3 on Ubuntu Dapper, having migrated from an mbox / UW-IMAP combination to a Maildir / Dovecot one. For some reason the mb2md tool failed to recognise some of my mbox files as valid ones, so I migrated my email by running UW-IMAP, copying my folders to local storage in Evolution, then running Dovecot instead and copying the folders back. All seems OK, except that in Outlook 98 all the emails now have the date/time of their migration, not when they were received. This isn't a problem in Thunderbird or Evolution - but my wife uses Outlook and doesn't wish to switch. I've tried using touch to change the timestamps of the mails in my inbox (in ~/Maildir/cur) but this hasn't had any effect. I've also tried deleting ~/Maildir/dovecot.index and ~/Maildir/dovecot.index.cache but this hasn't made any difference either. Something else in dovecot must be being sent to Outlook as the date / time on these emails. Can anyone suggest what it would be and how I might go about changing it (to, for example, the Received: date on the email header?). Thanks in advance, James. ___________________________________________________________ Try the all-new Yahoo! Mail. "The New Version is radically easier to use" The Wall Street Journal http://uk.docs.yahoo.com/nowyoucan.html

3 2

[Dovecot] problem from beta7 to rc7
by Roberto Tagliaferri 13 Oct '06

13 Oct '06

Hi, today i've upgrade from beta7 to rc7; i've pop3 with real user (no db or other thing). The config file remain the same. After few hours the master process hang without any messages in log.. Is there a problem on config file? (I've upgraded because sometime i've a duplicated messages in pop3.. one deliver by postfix but 2 messages) -- Roberto Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

2 1

[Dovecot] Dovecot freeze - 1.0 rc7 - FreeBSD 6.1
by Floris van den Berg 13 Oct '06

13 Oct '06

Hi, One of my customers currently experiences a dovecot freeze on random accassions. Trying to figure out what's wrong with no luck. Dovecot is running fine, up until it suddenly stops responding. The log file says: dovecot: Oct 05 10:12:26 Info: pop3-login: Disconnected: Inactivity: rip=82.217.29.*, lip=85.17.42.165 dovecot: Oct 05 10:12:29 Info: pop3-login: Disconnected: Inactivity: rip=86.87.152.*, lip=85.17.42.165 dovecot: Oct 05 10:12:30 Info: pop3-login: Disconnected: Inactivity: rip=62.131.94.*, lip=85.17.42.165 dovecot: Oct 05 10:12:30 Info: pop3-login: Disconnected: Inactivity: rip=62.131.94.*, lip=85.17.42.165 dovecot: Oct 05 10:13:17 Info: pop3-login: Disconnected: Inactivity: rip=86.88.180.*, lip=85.17.42.165 No other errors are logged. When i restart dovecot it runs fine again for some time. Sometimes it works for a few days, sometimes just a few hours. There's always a point where it freezes again. Reinstalled dovecot. Fiddled a bit with the auth_worker_max_count and auth_process_size settings. No change in behavior was observed. There's no out of the ordinary cpu or memory use. Any ideas? Floris

2 1

Re: [Dovecot] Dovecot LDA
by Timo Sirainen 13 Oct '06

13 Oct '06

[repost] On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > I am calling dovecot deliver from Postfix (main.cf): > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > Upon switching to dovecot deliver, I observed two problems: > > 1) An extraneous "From " header now appears at the top of each message > delivered, e.g.: > > From dovecot.deliver Fri Oct 06 19:59:57 2006 > From sfs(a)tc.umn.edu Fri Oct 6 19:59:57 2006 > Return-Path: <sfs(a)tc.umn.edu> > > Using Postfix delivery the first of these lines does not appear. > This, of course, confuses MUAs. Don't give F flag to Postfix's pipe command. Although this reminds me that the "dovecot.deliver" is wrong in there.. Hmm. I think I'll add a maildrop-compatible -f <envelope> parameter here. There, done in CVS. I'll also make 1.0rc8 release today. > 2) The "Content-Length:" header appears after a blank line, essentially > putting it into the RFC822 body, e.g.: > > User-Agent: Mutt/1.4.2.1i > X-UID: 11510 > Status: > X-Keywords: > > Content-Length: 200 > > test Are you sure it's a blank line? Dovecot adds lots of spaces after X-Keywords which could just make it look like that. If it really is a blank line, then it's most likely something else than Dovecot that changes the spaces that way.

1 0