- dovecot - dovecot.org

[Dovecot] Is Dovecot ready for production use?
by Benjamin J. Weiss 12 May '04

12 May '04

Hi! I'm currently running RH 9 with postfix, uw-imap and MailScanner. I want to install Fedora Core 2 (when it comes out next week) with postfix, dovecot and amavisd. I'm unhappy with the problems I'm having with MailScanner, with the difficulty I've had with authentication as I am currently configured, and want to move to Maildir instead of mbox. That being said, is dovecot stable enough yet for production use? I only have four users on my home linux box, but I personally get around 500 emails a day (that fedora list is *busy*). Thanks, Ben

6 11

[Dovecot] php.ini tweak
by Avery 12 May '04

12 May '04

I noticed this is my /etc/php.ini file ---------------------------------------- ; This directive tells PHP whether to declare the argv&argc variables (that ; would contain the GET information). If you don't use these variables, you ; should turn it off for increased performance. register_argc_argv = on ---------------------------------------- I ma trying to squeeze some extra performance out of my email server. If I turn this to off will this cause any problems with SQmail or any of SQmail's plugins. I tried turned this setting to off and everything seems to work fine. I am surprised that no one has asked about this before in this mailing list. Thanks, Avery

1 1

[Dovecot] LDAP + passwd
by Paolo Basenghi 12 May '04

12 May '04

Hello, I'm in the process to choose between Courier and Dovecot. I would like to know if it's possible to configure Dovecot in order to use multiple user database (e.g. ldap+passwd) in order to have both virtual user authenticated by LDAP and system user authenticated by system password and with their own home directory. Another question: at http://dovecot.org/doc/dovecot-example.conf there is a configuration example that seems not work with Dovecot 0.99.10.4 It result in a "Fatal: Error in configuration file /etc/dovecot.conf line 391: Missing value". Line 391 is: "auth default {" Thank you for attention. Best regards. -- ___________________________________________________________________ Ing. PAOLO BASENGHI :::: Systems & Networking Engineer p.basenghi(a)netribe.it ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ NETRIBE srl :: Collaborative E-Business 42100 :: Reggio Emilia :: Italy :: Via della Costituzione, 27/4 ph. +39 0522 232378 :: fax +39 0522 232386 :: http://www.netribe.it ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

2 2

[Dovecot] Case sensitive user names
by Jeff Graves 12 May '04

12 May '04

Hello list. This is my first post and I hope that I have something useful for people. Using Fedora Core 1 with the stock dovecot-0.99.10 RPM I noticed that user names were case sensitive which was a problem for me since I was attempting to set up winbind authentication which meant that what dovecot thought the homedir was could change depending upon the case the user typed in. Sendmail/procmail always changed the username to lowercase so I needed a way to duplicate this behavior. At any rate, I searched the archives and found Andrew's post from March: http://www.dovecot.org/list/dovecot/2004-March/003067.html - using this as a jumping point and I finally have case insensitive user names (better yet, forced lower case usernames) working for plain-text authentication (eg. dovecot.conf: auth = plain, auth_userdb = passwd, auth_passdb = passwd). It has been tested only on the source RPM from Redhat FC1 and I'm not a C programmer so I have no idea if it will work with other authentication methods or newer versions of software. I've rebuilt the RPMs (source and i386) if anyone's interested and here's the patch for those not using RPMs (it's attached as well): diff -ru dovecot-0.99.10/src/auth/mech-plain.c dovecot-0.99.10.new/src/auth/mech-plain.c --- dovecot-0.99.10/src/auth/mech-plain.c 2003-05-18 08:26:28.000000000 -0400 +++ dovecot-0.99.10.new/src/auth/mech-plain.c 2004-05-11 16:58:30.000000000 -0400 @@ -57,6 +57,7 @@ authenid); } + auth_request->user = str_lcase(auth_request->user); if (!mech_is_valid_username(auth_request->user)) { /* invalid username */ if (verbose) { Thanks, Jeff Graves, MCP Customer Support Engineer Image Source, Inc. 10 Mill Street Bellingham, MA 02019 508.966.5200 - Phone 508.966.5170 - Fax jeff(a)image-src.com - Email

1 0

[Dovecot] nfs dotlock issues
by Maikel Verheijen 11 May '04

11 May '04

Hi List, While testing with dovecot-1.0-test8 on our platform, I get al lot of these: May 11 11:42:50 mf1 dovecot: imap(user(a)domain.tld): Our dotlock file /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.log.lock was modified (1084268570 vs 1084268875), assuming it wasn't overridden This is probably due to some time-issues on our platform, and the load the backend has. (our backends run in a live environment). Can the dotlock code get the timestamp of the file when the dotlock gets created in order to be able to keep the time in sync? Is there another way to prevent those seconds of time-difference? we run ntpd on both our frondends and our backends. Kind regards, Maikel Verheijen

1 0

[Dovecot] 1.0-test7
by Timo Sirainen 11 May '04

11 May '04

http://dovecot.org/test/ Lots of bugfixes related to syncing. There's still some left. Somewhat working mbox support: - combined syncing/rewriting uses much less disk I/O than with older mbox code - expunges aren't working yet - last-uid field in X-IMAPbase header isn't updated - it's currently syncing the whole mbox constantly even if it hasn't changed - it isn't hiding the mbox-specific headers from IMAP clients - if mbox hasn't changed, rewriting could start from the message which requires rewriting instead of syncing the whole mbox - syncing could keep the lock file extra two seconds to make sure if someone changes it the file's mtime changes -> as long as only Dovecot is modifying it, we'll never need to sync the whole mbox -> multi-gigabyte mboxes are still fast! One nice thing about this mbox code is that it isn't exactly mbox-specific. Some people are still using formats which use eg. ^A as separator rather than From-line. Some people are using SMTP-formatted data directly ('.' as mail separator, '..' = normal line begins with '.'). These formats should be pretty easy to implement now as all mbox-specific code is in istream-raw-mbox.c file. I'll probably do that once mbox itself is fully working.

3 4

[Dovecot] Mail always is delivered to /var/mail/
by Kevin Breit 07 May '04

07 May '04

Hey, I am setting up Dovecot on Debian with Postfix. I am telling Dovecot to use maildir:~/Maildir but it persists in dumping mail in mbox format in /var/mail/username. Can anyone suggest ideas? My config file is attached. Thanks Kevin

5 7

[Dovecot] imap indexing error when moving multiple mails
by Hauke Fath 06 May '04

06 May '04

Hi, I've got an 'interesting' problem with a dovecot 0.99.10.4 setup on NetBSD/i386 1.6ZK. dovecot is serving imap only at the moment, using mbox format mailboxes. '/etc/dovecot.conf' is pretty vanilla - among the modified settings, mail_read_mmaped = yes maildir_check_content_changes = yes mbox_lock = fcntl could be relevant. Anyway - from time to time when I move a bunch of mails ( < 1) from a mailbox to another (or to the trash), the client (I've seen it with Eudora 6 on a Mac, with Mozilla 1.6 and Sylpheed on NetBSD) reports an "internal error" and the maillog shows Mar 25 14:07:33 bounce imap-login: Login: hf [130.83.xxx.yyy] Mar 25 14:07:44 bounce imap(hf): Error indexing mbox file /home/hf/Mail/Leute/Marc Wirth: LF not found where expected Mar 25 14:09:30 bounce imap(hf): Error indexing mbox file /home/hf/Mail/Leute/Marc Wirth: LF not found where expected which, if I retry the operation to another time, does not persist and is not strictly repeatable. I've set the number of allowed concurrent connections to '1' on the client, but that doesn't help. Is there anything obvious that I overlooked, or have I tripped over a genuine bug? hauke -- Hauke Fath /~\ The ASCII Ribbon Campaign Institut für Nachrichtentechnik \ / No HTML/RTF in email TU Darmstadt X No Word docs in email Ruf +49-6151-16-3281, Fax -3778 / \ Respect for open standards

4 5

[Dovecot] Dovecot chrooting
by ?a??µp?? ?a?a???t?? 06 May '04

06 May '04

hello all i am new to dovecot and i have a small problem. I use qmail as a pop3 server and dovecot as imap. my rc script is as follows: -----snip----- #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start '|preline procmail' splogger qmai -----end----- thus i deliver mails through procmail so all mails are located to /var/spool/mail. The problem exists when i tested chrooting and found it a very good idea to jail all my users.. *but* still qmail delivers mails to the real /var/spool/mail and not to the /home/chrootusers/var/spool/mail so that dovecot can pick them up. Is there any special configuration in dovecot.conf in order to chroot the /var/spool/mail to /home/chrootusers ? some of my conf: login_chroot = yes valid_chroot_dirs = /home/chrootusers mail_chroot = /var/spool/mail default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u PS: tell me if you need more of the dovecot.conf PS2: sorry for my english its not my native

2 1

[Dovecot] Re: Timezone of logentries from dovecot (Timo Sirainen)
by Lars Skovgaard 04 May '04

04 May '04

On Thu, 2004-04-29 at 15:57, Timo Sirainen wrote: > One more reason to make all logging go through dovecot-master process.. > > Temporary fix of course is setting login_chroot = no to config file. Thanks, Timo, that did the trick. Also thanks to Quentin for his reply, though I don't understand any of it. As stated, my knowledge of unix is rather limited... On Thu, 2004-04-29 at 15:48, Quentin Garnier wrote: > It's because the logging process is chrooted, doesn't have TZ env. var. > set, and doesn't have a correct /etc/localtime (or whatever your libc > uses) _inside_ the chroot directory. Therefore its timezone is the > default, UTC (formerly known as GMT). As I understand it, it would be a good idea to come up with a more permanent fix. However, I have no idea where to begin. Timo writes about making all logging go through the dovecot-master process – can anyone point me in the direction of information on how to accomplish this? Quentin writes about TZ env. var. (TimeZone?), /etc/localtime and the chroot directory. I'm sorry, Quentin, but I need a bit more info. I have the correct /etc/localtime, as far as I can tell. I've tried looking up TZ env. var. in my man-pages, but haven't come up with anything. I'll copy my /etc/localtime to the login_dir and see if this is enough. Thanks again, guys! /Lars

2 1