- dovecot - dovecot.org

[Dovecot] fix: LDA logging
by David Lee 09 Oct '06

09 Oct '06

Timo: As discussed over the last couple of days. Please could the attached patch be applied to "deliver.c" so that it can log (syslog etc.) final delivery into the destination mailbox. This completes a hitherto missing part in logging an email's progress; it is useful (for example) to diagnose "my email wasn't delivered" problems. Thanks. -- : 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. :

2 2

[Dovecot] dovecot, procmail and deliver
by David Lee 09 Oct '06

09 Oct '06

(Using dovecot 1.0 RC7 on Fedora Core 5) <scene set> Hitherto we have used UW-IMAP on a "farm" of Linux machines mounting NFS from a NetApp. (The UW-IMAP author doesn't like use of NFS, but with careful use of NFS mount arguments ('noac,actimeo=0' etc.) and trying to ensure that all activity for a given user takes place within one machine in the farm, we seem to have been OK.) We have also used UW-IMAP's 'tmail' (in sendmail.cf) and 'dmail' (from any user procmail recipes), so that access to the INBOX has been consistently UW-IMAP software. We are now considering doing a transparent migration to dovecot to improve performance. </scene> --- First: a general question: To complement the UW->dovecot migration of the IMAP daemon (reading the INBOX and folders), ought I to do a similar delivery-side migration from [UW] tmail/dmail to [dovecot] 'deliver'? It would feel safer this way, but maybe I worry too much... --- Second: "deliver" seems to add an unconditional "From " line at the start of each delivery. From sendmail, using the 'n' flag, "Mlocal F=...n..." that is OK. (Although I'm not convinced that "dovecot.deliver", nor its two-space separator (emphasis on "two") from the following date are ideal. Nor, come to that line's lack of "@somewhere".) But from a procmail recipe, I end up with two "From " lines. Surely this is incorrect. How can this be reduced to one? Shouldn't "deliver" ensure that there is only "From " line? --- Third: Would it be possible for "deliver" to do a "syslog" entry to confirm final delivery into the destination mailbox, please? (I could try and produce a patch, but someone else with more dovecot familiarity could probably do the job must more quickly and probably also more cleanly!) (I think that's all for the moment.) -- : 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. :

6 9

[Dovecot] patch: mailboxcasecmp()
by Frank Cusack 09 Oct '06

09 Oct '06

Here is a patch which adds mailboxcmp() and mailboxcasecmp() functions, similar to mailbox_equals(). Names were chosen to match strcmp() and strcasecmp(). I needed this for Johaness Berg's dspam plugin. It watches a folder "SPAM" and forcing this to be uppercase is unacceptable for me. (I also had to modify the plugin to use the new routine.) It's against dovecot-1.0.beta8 but should be trivial to port to CVS. -frank

3 10

[Dovecot] How to store Dovecot Logs in SQL DB
by Krzysztof 09 Oct '06

09 Oct '06

Hello! I would like to put user login attempts into SQL DB (PostgreSQL). Any idea how to do it (without manual parsing log files)? Kind regards, Krzysztof Kiszewski

8 10

[Dovecot] Converting UW MBX mail folder
by Anne Hammond 09 Oct '06

09 Oct '06

We converted from uw-imapd to dovecot but are still having problems with MBX mail folders. The user can't access this "MBX mail folder": [root@volt Resume's]# file "Sys Admin" Sys Admin: MBX mail folder [root@volt Resume's]# mailutil copy ./"Sys Admin" '#driver.unix/new' Can't open mailbox ./Sys Admin: no such mailbox [root@volt Resume's]# mailutil copy -debug -verbose./SysAdminSave '#driver.unix/new' Can't open mailbox ./SysAdminSave: no such mailbox Could you tell me what I am doing wrong? Anne M. Hammond - Systems / Network Administration - Tech-X Corp

6 7

Re: [Dovecot] Dovecot LDA
by Steven F Siirila 09 Oct '06

09 Oct '06

On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > 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. The messages in question are accepted by the Postfix smtpd process and processed by Postfix, and handed off to dovecot deliver. I am not specifying an F flag anywhere. If I remove the "mailbox_command" I specified above, Postfix delivers the mail with only the one "From " header -- with the mailbox_command above (no options specified), I get two "From " headers. > 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. How will this help me? I don't even want the added "From " header. If Postfix is not supposed to be writing one, then how do I tell it not to and how does Postfix tell dovecot deliver what to put in the "From " header it writes? (It must be the proper return address seen in the original SMTP transaction as the MAIL FROM value) > 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. You're correct; the line prior to the "Content-Length:" header was indeed an "X-Keywords:" header padded out to exactly 80 characters, making it appear that there was an extra blank line after it (my xterm window is set to 80 columns). -- 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

1 0

[Dovecot] which e-mail client can work with recent dovecot?
by Sergey Ivanov 09 Oct '06

09 Oct '06

Hi, I'm trying to use dovecot-1.0.rc7. Before I've used dovecot-1.0 from nightly cvs build of August 08, 2006. It worked perfectly, on Linux 64-bit, you can see spec and patches at http://www.sisyphus.ru/srpm/dovecot/ When I tried to upgrade to rc7 and to recent nightly cvs builds with the same configuration and patches (provided necessary adaptations), it builds O.K, but can not move messages from folder to folder. I've tried the following mail clients: thunderbird-1.5.0.7, evolution-2.0.2, sylpheed-claws-2.0 and KMail-1.7.1 (all from Centos-4.4). KMail refuses to copy (or to move) multiple selected messages, saying:" Error while copying messages.Connection to Server Closed Unexpectedly ...". Evolution is not able to open folders at 3-rd level (like dovecot/2006/09), or it is so slow that I was not able to test moving/copying messages in it. Sylpheed-claws died whan I tried this message copying. Thunderbird tries to move infinetly in a loop, filling the dovecot's log with lines: --- Sep 28 12:56:25 alt64 dovecot: imap-login: Login: user=<seriv>, method=plain, rip=66.80.117.2, lip=192.168.10.8, TLS Sep 28 12:56:25 alt64 dovecot: IMAP(seriv): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Sep 28 12:56:25 alt64 dovecot: child 25177 (imap) killed with signal 6 Sep 28 12:56:25 alt64 dovecot: imap-login: Login: user=<seriv>, method=plain, rip=66.80.117.2, lip=192.168.10.8, TLS Sep 28 12:56:25 alt64 dovecot: IMAP(seriv): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Sep 28 12:56:25 alt64 dovecot: child 25183 (imap) killed with signal 6 --- (approximitely 2 cicles per second). And when I reinstalled back the previously worked version of dovecot, the problem remains. -- With best regards, Sergey Ivanov.

3 3

[Dovecot] 1.0rc8 - not quite yet
by Timo Sirainen 08 Oct '06

08 Oct '06

OK, I know I promised rc8 today in my recent mails, but it's way too late and writing changes to NEWS file takes time. :) So I guess it'll happen tomorrow then. In the mean time it would be nice if you'd test that I didn't break anything badly with my recent changes. Especially when I changed the password verifications to detect if the password is in hex or base64 encoding based on the string length. This also allowed me to make LDAP-MD5 and PLAIN-MD5 use the same password verification function. I like this change. :) So, the almost-rc8 snapshot is in: http://dovecot.org/nightly/dovecot-latest.tar.gz I also started building dovecot-sieve snapshots: http://dovecot.org/nightly/sieve/

1 0

[Dovecot] Maildir++ quota inconsistency
by Anand Buddhdev 08 Oct '06

08 Oct '06

I've found what I think is an inconsistency in the Maildir quota implementation. According to the Maildir++ quota specification at: http://www.inter7.com/courierimap/README.maildirquota.html Maildir++ quota can be specified as maximum size, or maximum number of messages, or even both. The size specification is supposed to be in bytes. So I could use '10000000S' to set a quota of around 10MB. Now, the Exim MTA has an independent Maildir++ quota implementation, and it follows the specification, so if I set the quota in Exim to 10000000, it will work perfectly with sqwebmail and courier-imap. However, it doesn't play well with Dovecot, because Dovecot chooses to interpret the quota as kilobytes, rather than bytes. An example: If I set the quota to 10240 in Dovecot, it creates a maildirsize file with the value 10240000 in it. If I then set the quota to 10M in Exim, Exim calculates that as 10485760. It detects that the value in the maildirsize file is wrong, and recreates the file with a quota of 10485760 bytes. Exim's behaviour is consistent with the courier family of packages, as well as the specification, so I'm venturing to say that Dovecot's implementation is slightly non-standard, and should be fixed so that the quota setting is interpreted as bytes, and not as kilobytes, to avoid a situation like the above. -- Anand

4 4

[Dovecot] Password mismatch - SHA1 authentication problem.
by guard 08 Oct '06

08 Oct '06

Hello, I have problem with authentication. I'm using SHA1 passwords stored in MySQL. >From debug: Info: auth-worker(default): sql(test@mail, IP): query: SELECT password FROM vmail WHERE mail = 'test@mail' Info: auth-worker(default): sql(test@mail ,IP): Password mismatch Info: auth-worker(default): sql(test@mail ,IP): SHA1(dupadupa) != '2bca9dbe8a14811c687bb8c51c0e1cd14db8a018' I tried convert password to upper case, but it didn't help. Then I tried authentication in plain text and everything works fine... So, does dovecot crypt SHA1 using other method? I also use same SHA1 passwords to authenticate users in exim and it doesn't have any problem with that. I'm using mysql 5.0.24 and dovecot 1.0 rc7. Best regards, Tomasz Krynicki

2 1