- dovecot - dovecot.org

[Dovecot] 1.0.rc11 released
by Timo Sirainen 12 Nov '06

12 Nov '06

http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz.sig Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending rejects, don't include Content-Type in the rejected mail's headers. * LDAP changes: * If auth binds are used, bind back to the default dn before doing a search. Otherwise it could fail if a user gave an invalid password. * Initial binding at connect is now done asynchronously. * Use pass_attrs even with auth_bind=yes since it may contain useful non-password fields. + passdb checkpassword: Give TCPLOCALIP and TCPREMOTEIP and PROTO=TCP environments to the checkpassword binary so we're UCSPI (and vchkpw) compatible. - mbox handling was a bit broken in rc10 - Using Dovecot via inetd kept crashing dovecot master - deliver: Don't crash with -f "". Changed the default from envelope to be "MAILER-DAEMON". - INBOX wasn't shown with LSUB command if only prefixed namespaces were used. - passdb ldap: Reconnecting to LDAP server wasn't working with auth binds. - passdb sql: Non-plaintext authentication didn't work - MySQL passdb ignored all non-password checks, such as allow_nets - trash plugin was broken

3 15

[Dovecot] Deliver: command time exceed limit
by Dominique Feyer 12 Nov '06

12 Nov '06

We use Dovecot on a cluster (10'000 domains, 30'000 account) without any problem with pop/imap. We use Dovecot 1.0 RC10 Now we use virtual transport from postfix for mail delivery. We need the Dovecot LDA for sieve support. We test this solution on some domains with success. But if we change the configuration of all our domains, we have a lots of bounce with this error in postfix log: postfix/pipe[24573]: 4F6D7CF11: to=<info(a)XXXX.com>, relay=dovecot, delay=1200, status=bounced (Command time limit exceeded: "/usr/local/dovecot/libexec/dovecot/deliver") If I watch the deliver activity with ps/awk/watch, I see that if deliver duration time exceed some seconds, the deliver process stay in memory but do nothing. Here a strace output of this case: Process 349 attached - interrupt to quit gettimeofday({1161965973, 768478}, {0, 0}) = 0 poll( Strace output nothing before the SIGKILL from postfix (command time exceed 1200 second), the end of the strace: [{fd=5, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 2147483647) = -1 EINTR (Interrupted system call) +++ killed by SIGKILL +++ I'm not sure is this problem has a relation with our deliver problem. But in the deliver log /var/log/dovecot/deliver, I have a lots of message: deliver(info(a)labomex.com): 2006.10.27 18:29:28 Error: file_dotlock_replace(/var/mail/labomex.com/mails/info/.dovecot.lda-dupes) failed: No such file or directory deliver(info(a)labomex.com): 2006.10.27 18:29:28 Error: rename(/var/mail/labomex.com/mails/info/.dovecot.lda-dupes.lock, /var/mail/labomex.com/mails/info/.dovecot.lda-dupes) failed: No such file or directory Our dovecot.conf (lda parts): protocol lda { postmaster_address = postmaster(a)clm.net4all.ch #hostname = mail_plugins = cmusieve mail_plugin_dir = /usr/local/dovecot/lib/dovecot/lda sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master log_timestamp = %Y.%m.%d %H:%M:%S%t log_path = /var/log/dovecot/deliver info_log_path = /var/log/dovecot/deliver.info } We use on UID/GID per domain so every account of a domain use the same UID/GID. The mail storage is on a Debian Sarge NFS server with 2.4.27-3-686-smp. Indexes are stored localy on each POP/IMAP/LDA server. I don't understand why we have this problem. If somebody can help us, thanks a lots. Dominique Feyer

2 7

[Dovecot] Output to logfile
by Egbert Jan 12 Nov '06

12 Nov '06

Hello, Has everybody those irritating '^I' (tabs?) in his syslog for dovecot messages? Why not replace them by ordinary singe spaces? Maby something for a future release? Egbert Jan

2 1

[Dovecot] Writing to mail directory
by Gerard Seibert 12 Nov '06

12 Nov '06

FreeBSD 6.1 Dovecot 1.0.rc12 Using Dovecot as an LDA produces this error message: // START ERROR MESSAGE // deliver(gerard): Error:open(/var/mail/.temp.scorpio.seibercom.net.812.03034e3c3c1ab1c8) failed: Permission denied deliver(gerard): Error: file_lock_dotlock() failed with mbox file /var/mail/gerard: Permission denied // END ERROR MESSAGE// Actually, there are dozens of similar messages for all of my accounts. One example is enough to see what I am referring to. I am using Postfix for my mail-server. If I change the permissions on the directory to '1777' the error goes away and everything seems normal. The problem is that I should not have to do that and I do not understand what the problem is. Has anyone else experienced this phenomena and come up with a solution? Thanks! -- Gerard "Off list mail from *.gmail.com is rejected/deleted unseen. Don't waste your time."

2 2

[Dovecot] Using Substring Width with Mailhome Variables
by Matthew Fisch 12 Nov '06

12 Nov '06

Hello All, I am currently running Dovecot v1.0.rc13 from dovecot-1.0-0_31.rc13.fc5.at.i386.rpm on Linux HOST 2.6.17-1.2157_FC5 #1 Tue Jul 11 22:55:46 EDT 2006 i686 i686 i386 GNU/Linux. I am trying to install Dovecot in a large mail hosting environment and running into troubles. I have specified my mail home in dovecot.conf as follows: default_mail_env = maildir:/mnt/fileserver/maildir/%0.1d/%1.1d/%d/%n I've also tried among other variations: default_mail_env = maildir:/mnt/fileserver/maildir/%0d/%1.1d/%d/%n The expected behavior here, is to resolve this to: /mnt/fileserver/maildir/a/b/abc.com/user However, Dovecot seems to resolve this to: /mnt/raidzone01/maildir/abc.com/bc.com/abc.com/user/ It appears to me using 'width' with a substring does not work as is advertised on http://wiki.dovecot.org/Variables. This page does describe I need to be using 1.0-tests, what is 1.0-tests? I've also tried the default FC5 package: 1.0-0.beta8.2.fc5. Did I misunderstand the syntax? Am I using the wrong version? I won't be able to use dovecot without support for this feature as I am hosting many thousands of domains and know not how else to resolve them all. Thanks for all your time in advance, Matt Matthew Fisch Your-Site.com

2 1

Re: [Dovecot] Too many open files
by Timo Sirainen 12 Nov '06

12 Nov '06

On Wed, 2006-11-08 at 11:45 -0500, bofh list wrote: > imap 12009 user 16u REG 0,19 135348 > 9876198 /chroot/mailstore/user/Maildir/.Trash/dovecot.index.log.2 > (netapp-storage:/vol/mailstore) > imap 12009 user 17u REG 0,19 135348 > 9876198 /chroot/mailstore/user/Maildir/.Trash/dovecot.index.log.2 > (netapp-storage:/vol/mailstore) .. Oh, I see. Could you test if this patch fixes it: http://dovecot.org/list/dovecot-cvs/2006-November/006767.html

2 3

[Dovecot] RFC 2822 - message-id
by Tom Allison 10 Nov '06

10 Nov '06

I was porting some email from one imap server location to another and ran into a feature of something. One of them writes message-id as 'Message-Id' and the other writes it as 'Message-ID'. Because of this, all the messages are forever different. All mail is delivered from postfix and will be in the future. But I'm asking which of these syntaxes is correct or if there is a right/wrong way of writing the headers? RFC2822 doesn't come right out and say it, but all the examples therein are "Message-ID". RFC 822 says they are all the same. Both?

3 2

[Dovecot] 1.0.rc12 released
by Timo Sirainen 10 Nov '06

10 Nov '06

http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz http://dovecot.org/releases/dovecot-1.0.rc12.tar.gz.sig Since rc11 has problems compiling with BSDs, here's a new release. Just two changes: - rc11 didn't compile with some compilers - default_mail_env fallbacking was broken with --exec-mail Here's also again the rc11 changes: * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending rejects, don't include Content-Type in the rejected mail's headers. * LDAP changes: * If auth binds are used, bind back to the default dn before doing a search. Otherwise it could fail if a user gave an invalid password. * Initial binding at connect is now done asynchronously. * Use pass_attrs even with auth_bind=yes since it may contain useful non-password fields. + passdb checkpassword: Give TCPLOCALIP and TCPREMOTEIP and PROTO=TCP environments to the checkpassword binary so we're UCSPI (and vchkpw) compatible. - mbox handling was a bit broken in rc10 - Using Dovecot via inetd kept crashing dovecot master - deliver: Don't crash with -f "". Changed the default from envelope to be "MAILER-DAEMON". - INBOX wasn't shown with LSUB command if only prefixed namespaces were used. - passdb ldap: Reconnecting to LDAP server wasn't working with auth binds. - passdb sql: Non-plaintext authentication didn't work - MySQL passdb ignored all non-password checks, such as allow_nets - trash plugin was broken

7 10

[Dovecot] LDAP authentication windows 2003
by Matheus Antonio Oliveira 09 Nov '06

09 Nov '06

4 4

[Dovecot] Qpopper migration?
by Steve Goodman (lists) 09 Nov '06

09 Nov '06

Hello, As this is my first post to the list, first and foremost I'd like to thank Timo for writing great software; we've successfully moved to Dovecot for over 10,000 users from UW-IMAP and get great performance. On our overloaded staff POP3/IMAP server, we are looking at replacing qpopper+uw-imapd with dovecot, as an interim before moving them to the main Unix mailstore. The system is primarily POP3, with a small number of heavy IMAP users causing the system grief. There are a large number of POP3 users who leave messages on the server. What I want to ensure doesn't happen is that they are forced to download them again. Do I need to add anything specific in the pop3_uidl_format or am I barking up the wrong tree? Kind Regards, Steve

3 2