- dovecot - dovecot.org

[Dovecot] Namespaces and subscriptions
by Chris Wakelin 17 Mar '05

17 Mar '05

I've got a problem with subscriptions in 1.0-stable when migrating from UW-IMAP. I've modified the SUBSCRIPTION_FILE_NAME entries as suggested in the Wiki http://wiki.dovecot.org/Migration and included the "~/mail/" etc. hidden namespaces. The .mailboxlist files contain entries like "~/mail/somefolder" and the clients have "~/mail/" set as a prefix. In UW-IMAP: xyz LSUB "" "*" * LSUB () "/" ~/mail/somefolder xyz LSUB "~/mail/" "*" * LSUB () "/" ~/mail/somefolder Now with Dovecot: xyz LSUB "" "*" * LSUB () "/" "~/mail/somefolder" xyz LSUB "~/mail/" "*" * LSUB () "/" "~/mail/~/mail/somefolder" In other words, Dovecot is prepending the namespace to the list of folders stored in .mailboxlist. This causes Thunderbird to show the folders as -~ - mail | somefolder which are accessible. Squirrelmail gets completely confused and tries to display "~/mail/~/mail/somefolder" (but works with the prefix set to ""). Am I missing something? I tried Geo's empty namespace patch, just in case that would help, but it didn't. Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 1

[Dovecot] Warning, newbie!
by Pete 17 Mar '05

17 Mar '05

Greetings again all, <snip> I am a Postfix/Courier-IMAP user and am interested in Dovecot. I have install Dovecot via FBSD ports. I have got to the part where I can telnet in to the server. </snip> I guess I ought to backup a little, now that I have the above resolved. I am wanting/wondering about using Dovecot with Postfix. I assume some of you have done this. Have you any thoughts, comments, how-to -- Pete http://milneweb.com http://nomorevirus.com

4 4

[Dovecot] Warning, newbie!
by Pete 17 Mar '05

17 Mar '05

Greetings All, I am a Postfix/Courier-IMAP user and am interested in Dovecot. I have install Dovecot via FBSD ports. I have got to the part where I can telnet in to the server. -bash-2.05b$ telnet 192.168.1.61 143 Trying 192.168.1.61... Connected to 192.168.1.61. Escape character is '^]'. * OK dovecot ready. x login pete testing * BAD [ALERT] Plaintext authentication is disabled, but your client sent password in plaintext anyway.If anyone was listening, the password was exposed. x NO Plaintext authentication disabled. x logout * BYE Logging out x OK Logout completed. Connection closed by foreign host. -bash-2.05b$ I am afraid I dont know what to do from here. Anyone care to assist me? Thanks, -- Pete http://milneweb.com http://nomorevirus.com

2 1

[Dovecot] 1.0-test65
by Timo Sirainen 17 Mar '05

17 Mar '05

http://dovecot.org/test/ If dovecot-auth was crashing with you, this release should fix it. I don't know when it did though, I just applied a patch from Andrey Panin with that description :) Fixed also another dovecot-auth crash with Solaris and maybe some other systems. Contains the first attempt of a Dovecot LDA. It's still in pretty ugly shape, but it should work, more or less. I wouldn't recommend using it in production yet. There are two ways to use it: 1. As a normal user. The username is taken from passwd. 2. Giving -d <username> option. This connects to dovecot-auth and requests the uid, gid, home, etc. from it. dovecot-auth's master socket is expected to be in /var/run/dovecot/auth-master but you can override this with -a parameter. To actually create the auth-master socket you'll need to add this inside auth { .. } : socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 } } Dovecot LDA also currently needs dovecot-lda.conf file. Everything that is read from it is just dumped into environment variables internally. You should be able to set pretty much all the same settings in there as exists in dovecot.conf. The most important exception is that instead of default_mail_env there's just "mail". Example dovecot-lda.conf would be: # note that namespaces aren't supported yet.. mail = mbox:~/mail:INBOX=/var/mail/%u mbox_read_locks = flock mbox_write_locks = flock # EOF All this goes away once I get the config process implemented. The actual usage goes something like: /usr/local/libexec/dovecot/deliver -d username < mail_file ie. the mail is read from standard input. Any suggestions if the "deliver" name should be changed and maybe moved to /usr/bin/? Another large change is that I created dynamically growing array implementation with possibility to do compile time type checking. The old code was using buffer_t for arrays, but that got pretty ugly. I changed most of those in lib-index/ to the new array API. I'd be happy if someone changed the rest of them since it's pretty boring and time consuming job :) See lib/array.h for explanation how it works. And finally a small advertisement: http://mjr.iki.fi/texts/patentfund

2 1

[Dovecot] corruption and errors in dovecot-stable
by Nicholas Riley 17 Mar '05

17 Mar '05

Hi, We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10) a few days ago and have been seeing many errors and one corrupted mailbox so far. Almost everyone uses mbox format, and most users primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well as accessing the mailboxes locally with Mutt, and have not noted any visible problems. There have been several of these messages: dovecot: Feb 21 11:40:06 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (5308 > 1151) dovecot: Feb 21 22:57:13 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/trac (6458 > 1151) dovecot: Feb 22 08:37:03 Error: IMAP(njr): mbox sync: UID inserted in the middle of mailbox /usr/home/njriley/mail/lists/reportlab-users (5162 > 3812) Others: dovecot: Feb 22 11:44:17 Error: IMAP(njr): file mbox-sync-parse.c: line 221 (parse_x_uid): assertion failed: (!ctx->sync_ctx->sync_restart) dovecot: Feb 22 11:44:17 Error: child 19931 (imap) killed with signal 6 dovecot: Feb 25 06:26:09 Error: IMAP(kbode): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) dovecot: Feb 25 06:26:09 Error: child 83423 (imap) killed with signal 6 (I think this refers to the mailbox that was corrupted) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:30:40 Error: IMAP(sachs): Corrupted transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: Extension record update update without intro prefix dovecot: Feb 25 12:30:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: marked corrupted dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1109356120 != 1108933119) dovecot: Feb 25 12:39:34 Error: IMAP(sachs): Lost transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Feb 25 12:39:41 Error: IMAP(sachs): Transaction log file /home/sachs/Mail/.imap/INBOX/dovecot.index.log: invalid indexid (1108933119 != 1109356120) I am currently reinstalling 0.99.14, but it would be nice to be able to switch to a 1.0-derived version again - we have to run two copies of 0.99.x to get what we want. If there is any additional testing I can do to help fix these problems, please let me know. Thanks, -- Nicholas Riley <njriley(a)uiuc.edu> | 4111 Siebel Center Department of Computer Science | 201 N. Goodwin Ave. and Medical Scholars Program | Urbana, IL 61801-2302 Univ. of Illinois at Urbana-Champaign | +1 217 244 2274

3 4

[Dovecot] Minor documentation bug with 0.99.14
by John Peacock 16 Mar '05

16 Mar '05

The sample dovecot-example.conf contains these lines: > # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before > # dropping root privileges, so keep the key file unreadable by anyone but > # root. Included doc/mkcert.sh can be used to easily generate self-signed > # certificate, just make sure to update the domains in dovecot-openssl.cnf > #ssl_cert_file = /etc/ssl/certs/dovecot.pem > #ssl_key_file = /etc/ssl/private/dovecot.pem but the aforementioned doc/mkcert.sh contains these lines: > CERTFILE=$SSLDIR/certs/imapd.pem > KEYFILE=$SSLDIR/private/imapd.pem either the script should be changed to reflect the sample config file or vice versa. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

2 1

[Dovecot] Problems with Outlook 2002 SP3 & Dovecot 0.99.13 Redux
by Md 16 Mar '05

16 Mar '05

Hi, I posted this question a while back and didn't get much response. Since then, I've done a bit more experimenting and wonder if someone can help me move forward towards resolution. The orignal question... > I'm running Dovecot0.99.13 on Fedora Core 3 and things work fine when using either > Thunderbird 1.0 or Outlook Express as IMAP clients. Outlook (2002 SP3) on the other hand > runs incredibly slowly, or just outright hangs. I've discovered that if I delete and recrete .../Maildir in the user account such that the directory exists but is empty, then outlook seems to behave. If on the other-hand, I try to create a folder, with outlook, outlook will hang and the folder won't be created. If I create the folder with another client and then go back to using outlook, outlook will hang. I've taken some network traces and have annotated them here... Starting with an empty "Maildir" Time Source Destination Protocol Info 8.515435 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 8.516056 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 8.516539 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 8.516733 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 8.594634 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 8.640521 192.168.73.3 192.168.73.1 IMAP Response: + idling 8.640709 192.168.73.1 192.168.73.3 IMAP Request: DONE 8.640983 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 8.641165 192.168.73.1 192.168.73.3 IMAP Request: 0003 LIST "" "" 8.641315 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\Noselect) "." "" 8.642387 192.168.73.1 192.168.73.3 IMAP Request: 0004 LIST "" "INBOX" 8.642956 192.168.73.3 192.168.73.1 IMAP Response: * LIST (\HasNoChildren) "." INBOX 8.657424 192.168.73.1 192.168.73.3 IMAP Request: 0005 LSUB "" "*" 8.657925 192.168.73.3 192.168.73.1 IMAP Response: 0005 OK Lsub completed. 8.660627 192.168.73.1 192.168.73.3 IMAP Request: 0006 IDLE 8.660973 192.168.73.3 192.168.73.1 IMAP Response: + idling Now try to create a sub-folder using outlook: 0.000000 192.168.73.1 192.168.73.3 IMAP Request: DONE 0.000587 192.168.73.3 192.168.73.1 IMAP Response: 0006 OK Idle completed. 0.000910 192.168.73.1 192.168.73.3 IMAP Request: 0008 IDLE 0.001113 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs. Killing outlook and starting it again gives this trace: 5.110260 192.168.73.1 192.168.73.3 TCP 1953 > imap [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460 5.111826 192.168.73.3 192.168.73.1 IMAP Response: * OK dovecot ready. 5.112139 192.168.73.1 192.168.73.3 IMAP Request: 0000 CAPABILITY 5.112600 192.168.73.3 192.168.73.1 IMAP Response: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN 5.112798 192.168.73.1 192.168.73.3 IMAP Request: 0001 LOGIN "xxx" "xxx" 5.127237 192.168.73.3 192.168.73.1 IMAP Response: 0001 OK Logged in. 5.135355 192.168.73.1 192.168.73.3 IMAP Request: 0002 IDLE 5.137334 192.168.73.3 192.168.73.1 IMAP Response: + idling 5.138060 192.168.73.1 192.168.73.3 IMAP Request: DONE 5.138273 192.168.73.3 192.168.73.1 IMAP Response: 0002 OK Idle completed. 5.138505 192.168.73.1 192.168.73.3 IMAP Request: 0004 IDLE 5.138646 192.168.73.3 192.168.73.1 IMAP Response: + idling And there outlook just hangs again. Any ideas or help would be greatly appreciated. Thanks, Md

2 1

[Dovecot] imap-login zombies
by Robin Breathe 16 Mar '05

16 Mar '05

Running dovecot-0.99.13 on Solaris9/Sparc with ~25k users, we are having regularly recurring problems with large numbers imap-login/pop3-login drones, cycling on poll(). Over the course of 1-2 days, the number of such processes slowly rises to >1000, exhausts resources, and necessitates that dovecot be restarted (having killed all current active and zombie child processes). Nothing of interest seems to be logged with the possible exception of a reasonably high number of aborted logins (~10/hour). Can anyone offer any guidance as to how to track down this bug and help get it resolved? Any help would be much appreciated, as we would very much like to see this resolved in the 0.99 branch. Regards, Robin

2 1

[Dovecot] dovecot-auth hangs with IO leak
by Alan Tam 16 Mar '05

16 Mar '05

Hi dovecot, I am using the debian dovecot packages on a system running LDAP. My /etc/pam.d/common-* looks like this, which simply means try /etc/passwd first, and try LDAP using the same password if it is failed. account [success=1 default=ignore] pam_unix.so account required pam_ldap.so use_first_pass account required pam_permit.so auth [success=1 default=ignore] pam_unix.so auth required pam_ldap.so use_first_pass auth required pam_permit.so session [success=1 default=ignore] pam_unix.so session required pam_ldap.so use_first_pass session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_permit.so When many LDAP users login, /var/log/auth.log shows many (expected) error like: (note "pam_unix") Feb 3 18:16:15 eta dovecot-auth: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=127.0.0.1 Feb 3 18:16:19 eta dovecot-auth: (pam_unix) check pass; user unknown After recent upgrades from probably 0.99.10 to 0.99.13, these lines begin to appear in /var/log/mail.log: Feb 3 16:31:00 eta dovecot-auth: Login process has too old (123s) requests, killing it. Feb 3 16:31:00 eta dovecot-auth: Login process has too old (124s) requests, killing it. And some more like this, which shows the problem: Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (13) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (14) Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (15) The problem can be solved by changing /etc/pam.d/dovecot to: auth required pam_ldap.so account required pam_ldap.so session required pam_mkhomedir.so skel=/etc/skel umask=0002 session required pam_ldap.so This change means PAM not fail auth for /etc/passwd again. I think dovecot has some problem dealing with the pam_unix + pam_ldap configuration. Do you have any idea? I am Cc-ing this message to the corresponding bug in Debian BTS. -- Regards, Alan

2 2

[Dovecot] Bit of a Newbie Question
by Jud 16 Mar '05

16 Mar '05

Apologies in advance - I'm sure there's something quite obvious I'm not doing correctly, but since I'm unable to resolve the problem myself.... I've installed Dovecot 99.14 on FreeBSD-CURRENT using the Dovecot FreeBSD port. My "network" consists of a cable modem connected to a router which is in turn connected (only) to my computer. My ISP assigns a dynamic IP address. I have ddclient set up to sync the dynamic IP to my hostname and MX via dyndns.org. Local operations (local delivery via Postfix or copying/moving/deleting with Thunderbird) work fine. Mail delivery from remote machines does not seem to work via either IMAP or IMAP-SSL. (That is, test e-mails I send from this [Fastmail] account to my local IMAP server never reach their destination.) Enabling port forwarding on my router for ports 993 and 143 has made no difference. What should I be doing to make this work correctly? Jud

5 7

[Dovecot] Strange behaviour with moving mail
by Remy Zandwijk 15 Mar '05

15 Mar '05

Hi All, Sorry to bother you again. I am not too familiar with IMAP yet, so maybe I am asking stupid questions. Here goes anyway: In our (Dovecot 1.0-stable) setup, we have two namespaces: the default namespace, which location is '/var/mailstore/1%u/%u' and the "Mailstorage" namespace, which location is '~/.Mailstorage/'. Now we create a folder called 'Test' in the default namespace and the "Mailstorage" namespace. As far as I know this is possible and not a strange thing to do. When moving an email from the first 'Test' folder to the other 'Test' folder, it appears that everything works like expected, but when refreshing the mailbox, the message is still in the original folder. This happens with a number of different mailclients (which are configured with an empty namespace setting). I guess Dovecot doesn't look at the namespace in which the mail folder is. Is this a Dovecot bug or is this normal behaviour? Best regards, Remy B.T.W: When moving the mail, this is the IMAP conversation: 00029 UID COPY 4 TEST * 2 EXISTS * 2 RECENT 00029 OK Copy completed. 00030 UID STORE 4 +Flags.silent (\Deleted) 00030 OK Store completed.

2 3

[Dovecot] Is it possible to regenerate the index files?
by Joakim Verona 15 Mar '05

15 Mar '05

Is it possible to regenerate the index files, on other conditions than the mbox file being read? For instance, it would be nice if I could regenerate the index for a specific mbox whenever procmail delivers mail to it. If theres no existing solution, would it be possible to make a small script with something like "nc" that could send an imap command to dovecot, so that dovecot would rebuild its index for that mbox? If so, which imap command triggers an index rebuild? -- Joakim Verona www.verona.se

2 5

[Dovecot] Visibility of .subscriptions and .customflags
by justin 15 Mar '05

15 Mar '05

Hi, I upgraded to test65 from 0.99 (mostly to get the namespace feature) and now it seems my .subscriptions and .customflags are showing up as mail folders in my IMAP client (Eudora). If I try and open those folders, of course I get an error. How can I configure dovecot so that these aren't displayed to my IMAP client? I looked through about 6 months of acrhives and couldn't find it mentioned anywhere. Thanks.

2 1

[Dovecot] logging
by F. Even 15 Mar '05

15 Mar '05

I'm curious about exactly what this means in my log: Mar 13 10:56:20 cerebus dovecot: imap-login: Disconnected [130.94.242.20] Mar 13 10:56:51 cerebus last message repeated 177 times Mar 13 10:57:32 cerebus last message repeated 179 times Now...does Dovecot ONLY log the names of users on successful attempts? Is this "Disconnected" log entry an indication someone ran a username/password attack against the imap server and failed to authenticate? If so, is there any way to make this a little more verbose, so I can perhaps see what names, etc. the annoying idiot is throwing against my server....? Thanks.

2 1

[Dovecot] (no subject)
by Gabriel Granger 15 Mar '05

15 Mar '05

Hi All, Bit the bullet last night and switched off UW-IMAP and turned on Dovecot. With any migration I've got some teething problems and hoping someone might be able to point me in the right direction. I tested the system using apple's Mail.app which worked fine, no problems at all, but it seems that most of my users are getting problems, i suspect Mail.app is hiding these messages from me. All my users are using ThunderBird 1.0 lastest stable release. Some messages in their IMAP folders are producing the following error. The current command did not succeed. The mail server responded: Error in IMAP command UID: Invalid BODY[_] parameter: Missing '>' in '<16384.-14781>'. it occurs on the same messages in the users email client but happens randomly, it does not stop you from viewing the message, its just pops up with this error. I'm current using IMAP over SSL and using mbox not maildir for IMAP Any ideas or hep would be great as I'd rather not have to roll back out to UW-IMAP Gabe

6 16

Re: [Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 15 Mar '05

15 Mar '05

hey timo, On Tue, Mar 15, 2005 at 07:32:35PM +0200, dovecot-request(a)dovecot.org wrote: > From: Timo Sirainen <tss(a)iki.fi> > > i set: > > > > mailbox_check_interval = 0 > > This has been the default since 0.99.5 which was released over 2 years > ago. How old version are you using? :) Or had you changed the default? i had indeed changed the default, thinking that it would be a nice feature to turn on. when the problem first surfaced, i immediately thought of this option. however, since the problem was that applemail wasn't seing the new mail, and this was an option to notify the client that there *was* new mail, i guess common sense got the better of me and i forgot this was something i had changed... > > mailbox_idle_check_interval = 0 > > This shouldn't matter because OSX Mail doesn't use IDLE. Probably better > idea to turn it back on or clients using IDLE don't see new mails (I > think?) aha. well then i'll have to try turning that back on :) thanks, sean

1 0

[Dovecot] corrupted inboxes
by Josh Burley 15 Mar '05

15 Mar '05

Hi all, Two users on our system have recently had trouble reading their inbox, and it seems to be a result of their inbox getting corrupted. In the most recent case, their Mailbox file (in /home/eric/Mailbox in this case), has the following as the first line: cnw.igmg-- Here's a piece of the logs below... if you look for "eric", there's a successfully delivery, followed a bit later by a POP attempt by "eric" that returns that the Mailbox isn't in mbox format. Any ideas? .josh Mar 11 14:59:04 core postfix/local[8203]: 27D18279857E: to=<eric(a)kuci.org>, relay=local, delay=0, status=sent (delivered to mailbox) Mar 11 14:59:04 core postfix/qmgr[7238]: 27D18279857E: removed Mar 11 14:59:06 core postfix/smtpd[8199]: disconnect from user-0c8gg6h.cable.mindspring.com[24.136.64.209] Mar 11 14:59:13 core pop3-login: Login: gtt [::ffff:67.120.76.169] Mar 11 14:59:18 core postfix/smtpd[7575]: connect from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/smtpd[7575]: setting up TLS connection from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/smtpd[7575]: TLS connection established from webhost2.ethr.net[208.37.25.24]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits) Mar 11 14:59:18 core postfix/smtpd[7575]: 242E2279857E: client=webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/cleanup[8201]: 242E2279857E: message-id=<bb165712392a2b4375d6da0efa3c046c(a)www.ethr.net> Mar 11 14:59:18 core postfix/qmgr[7238]: 242E2279857E: from=<nobody(a)webhost2.ethr.net>, size=1527, nrcpt=1 (queue active) Mar 11 14:59:18 core postfix/cleanup[8201]: 6F63A2798580: message-id=<bb165712392a2b4375d6da0efa3c046c(a)www.ethr.net> Mar 11 14:59:18 core postfix/local[8203]: 242E2279857E: to=<r-ethr(a)kuci.org>, relay=local, delay=0, status=sent (forwarded as 6F63A2798580) Mar 11 14:59:18 core postfix/qmgr[7238]: 6F63A2798580: from=<nobody(a)webhost2.ethr.net>, size=1653, nrcpt=1 (queue active) Mar 11 14:59:18 core postfix/smtpd[7575]: disconnect from webhost2.ethr.net[208.37.25.24] Mar 11 14:59:18 core postfix/qmgr[7238]: 242E2279857E: removed Mar 11 14:59:18 core postfix/smtp[8250]: setting up TLS connection to blade.butterzone.net Mar 11 14:59:18 core postfix/smtp[8250]: verify error:num=19:self signed certificate in certificate chain Mar 11 14:59:18 core postfix/smtp[8250]: Peer verification: CommonName in certificate does not match: tloin.butterzone.net != blade.butterzone.net Mar 11 14:59:18 core postfix/smtp[8250]: Peer certficate could not be verified Mar 11 14:59:18 core postfix/smtp[8250]: 6F63A2798580: to=<r(a)butterzone.net>, orig_to=<r-ethr(a)kuci.org>, relay=blade.butterzone.net[208.37.27.136], delay=0, status=sent (250 Ok: queued as 4783AC2C130) Mar 11 14:59:18 core postfix/qmgr[7238]: 6F63A2798580: removed Mar 11 14:59:23 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3-login: Login: eric [::ffff:128.195.131.49] Mar 11 14:59:24 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:24 core pop3(eric): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-03-11 14:59:24] Mar 11 14:59:49 core pop3-login: Login: eric [::ffff:128.195.131.49] Mar 11 14:59:49 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:49 core pop3(eric): File isn't in mbox format: /home/eric/Mailbox Mar 11 14:59:49 core pop3(eric): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-03-11 14:59:49] Mar 11 14:59:53 core imap-login: Login: jeanie [::ffff:128.195.131.2] Mar 11 14:59:58 core last message repeated 5 times

2 4

Re: [Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 15 Mar '05

15 Mar '05

hello! On Mon, Mar 14, 2005 at 11:08:39PM +0200, dovecot-request(a)dovecot.org wrote: > From: "Dominik 'Rathann' Mierzejewski" <D.Mierzejewski(a)icm.edu.pl> > > According to RFC3501 (is this the right one?), NOOP can be used to check > for new mail, but it doesn't say that the server should return status > data every time NOOP is issued. i think the problem is that when the server asynchronously reports to the client that there's new mail apple mail gets confused. then noop doesn't report new mail. also, it seems that this is also the cause of apple mail having to re-download the entire mailbox every time it checks for new mail. > From: Timo Sirainen <tss(a)iki.fi> > > How did you disable them? I think enabling oe6-fetch-no-newmail > workaround should help. i set: mailbox_check_interval = 0 mailbox_idle_check_interval = 0 which did the trick (i already had all the client workarounds enabled). thanks, sean

3 2

[Dovecot] empty namespace prefix doesn't honor hidden (PATCH)
by Geo Carncross 15 Mar '05

15 Mar '05

diff -u -r1.44 cmd-list.c --- src/imap/cmd-list.c 5 Feb 2005 18:07:26 -0000 1.44 +++ src/imap/cmd-list.c 15 Mar 2005 16:15:27 -0000 @@ -213,7 +213,7 @@ ctx->inbox && cur_ref == ctx->ref, ns->sep); if (*cur_ref != '\0' || *cur_prefix == '\0') - match = IMAP_MATCH_CHILDREN; + match = ns->hidden ? IMAP_MATCH_NO : IMAP_MATCH_CHILDREN; else { len = strlen(cur_prefix); if (cur_prefix[len-1] == ns->sep) -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/

1 0

[Dovecot] Authentication to Active Directory
by Chris Wakelin 15 Mar '05

15 Mar '05

Has anybody managed to have Dovecot authenticate to Microsoft Active Directory? I've tried to get it to work using LDAP and the following settings dovecot.conf: userdb = ldap /etc/dovecot-ldap.conf passdb = ldap /etc/dovecot-ldap.conf dovecot-ldap.conf: hosts = rdg-home.ad.rdg.ac.uk dn = cn=bind-user,cn=users,dc=rdg-home,dc=ad,dc=rdg,dc=ac,dc=uk dnpass = XXXXX ldap_version = 2 base = dc=rdg-home,dc=ad,dc=rdg,dc=ac,dc=uk user_filter = (sAMAccountName=%u) pass_filter = (sAMAccountName=%u) I've also tried things like "(&(objectClass=sAMACcountName)(cn=%u))" to no avail. It appears to bind properly, but never finds the account, so login fails. I've had Active Directory authentication working with Squid and with Cyrus SASL/IMAP. Best Wishes, Chris --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 1

[Dovecot] Drac and Dovecot, almost there ...
by Jon Shoberg 15 Mar '05

15 Mar '05

I have dracd and dovecot up and running and trying to get the two connected. I'm using the FC3 rpms from callimg yum install. I've downloaded the drac patch from http://dovecot.org/patches/drac.c and compiled it with both gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac and gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so I get no warnings or errors on the compiling to drac.so. In the conf file I have imap_use_modules = yes imap_modules = /usr/lib/dovecot/imap However, I don't see the module being called. Is there a way to tell. The dracd database (/etc/mail/dracd.db) is not being updated via testing with the drac utilities. Thoughts? Ideas? Below is output from a strace ... I don't see /usr/lib/dovecot/imap/drac.so being opened ... execve("/usr/sbin/dovecot", ["/usr/sbin/dovecot"], [/* 20 vars */]) = 0 uname({sys="Linux", node="masra.org", ...}) = 0 brk(0) = 0x8c85000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=28209, ...}) = 0 old_mmap(NULL, 28209, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6ff9000 close(3) = 0 open("/lib/libssl.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\226"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=213600, ...}) = 0 old_mmap(0x7c0000, 212692, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7c0000 old_mmap(0x7f1000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x31000) = 0x7f1000 close(3) = 0 open("/lib/libcrypto.so.4", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\31d\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=933408, ...}) = 0 old_mmap(0x617000, 949656, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x617000 old_mmap(0x6ea000, 73728, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd2000) = 0x6ea000 old_mmap(0x6fc000, 11672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x6fc000 close(3) = 0 open("/usr/lib/libgssapi_krb5.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\214"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=82944, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff8000 old_mmap(0x724000, 80272, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x724000 old_mmap(0x737000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13000) = 0x737000 close(3) = 0 open("/usr/lib/libkrb5.so.3", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\370[\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=415188, ...}) = 0 old_mmap(0x5b0000, 413000, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x5b0000 old_mmap(0x613000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x63000) = 0x613000 close(3) = 0 open("/lib/libcom_err.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\3548Y\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=7004, ...}) = 0 old_mmap(0x593000, 8636, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x593000 old_mmap(0x595000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x595000 close(3) = 0 open("/usr/lib/libk5crypto.so.3", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Bp\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=136016, ...}) = 0 old_mmap(0x701000, 134560, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x701000 old_mmap(0x721000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x20000) = 0x721000 close(3) = 0 open("/lib/libresolv.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\363"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=81316, ...}) = 0 old_mmap(0x57d000, 80040, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x57d000 mprotect(0x58c000, 18600, PROT_NONE) = 0 old_mmap(0x58d000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf000) = 0x58d000 old_mmap(0x58f000, 6312, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x58f000 close(3) = 0 open("/lib/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\313"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=16908, ...}) = 0 old_mmap(0x4ec000, 12388, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4ec000 old_mmap(0x4ee000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x4ee000 close(3) = 0 open("/usr/lib/libz.so.1", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\205"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=63528, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff7000 old_mmap(0x517000, 65028, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x517000 old_mmap(0x526000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x526000 close(3) = 0 open("/lib/tls/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 O=\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1524828, ...}) = 0 old_mmap(0x3c0000, 1219740, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x3c0000 mprotect(0x4e3000, 27804, PROT_NONE) = 0 old_mmap(0x4e4000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x123000) = 0x4e4000 old_mmap(0x4e8000, 7324, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4e8000 close(3) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6ff6000 mprotect(0x4e4000, 8192, PROT_READ) = 0 mprotect(0x4ee000, 4096, PROT_READ) = 0 mprotect(0x58d000, 4096, PROT_READ) = 0 mprotect(0x3bc000, 4096, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0xf6ff66c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0xf6ff9000, 28209) = 0 time(NULL) = 1110856826 brk(0) = 0x8c85000 brk(0x8cae000) = 0x8cae000 uname({sys="Linux", node="masra.org", ...}) = 0 getpid() = 18177 geteuid32() = 510 open("/etc/dovecot.conf", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=20533, ...}) = 0 pread(3, "## Dovecot 1.0 configuration fil"..., 2048, 0) = 2048 pread(3, "ges, use this logfile instead of"..., 2023, 2048) = 2023 pread(3, "g\n# we check only once in a seco"..., 1970, 4071) = 1970 pread(3, "to give \"mail\" group write acces"..., 2046, 6041) = 2046 pread(3, "STRUCTURE\n# gen"..., 1981, 8087) = 1981 pread(3, "is setting specifies the minimum"..., 2034, 10068) = 2034 pread(3, "dlinks = no\n\n# Check if mails\' c"..., 2026, 12102) = 2026 pread(3, "processes then.\n#mail_drop_priv_"..., 1986, 14128) = 1986 pread(3, " client authenticates in the IMA"..., 2029, 16114) = 2029 pread(3, "ice> | *]: PAM authentication\n# "..., 2034, 18143) = 2034 pread(3, "s, so it may be 0600-root owned "..., 356, 20177) = 356 close(3) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3) = 0 open("/etc/nsswitch.conf", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=1686, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "#\n# /etc/nsswitch.conf\n#\n# An ex"..., 4096) = 1686 read(3, "", 4096) = 0 close(3) = 0 munmap(0xf6fff000, 4096) = 0 open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=28209, ...}) = 0 old_mmap(NULL, 28209, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6ff9000 close(3) = 0 open("/lib/libnss_files.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\32"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=47496, ...}) = 0 old_mmap(NULL, 41604, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xf6feb000 old_mmap(0xf6ff4000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0xf6ff4000 close(3) = 0 mprotect(0xf6ff4000, 4096, PROT_READ) = 0 munmap(0xf6ff9000, 28209) = 0 open("/etc/passwd", O_RDONLY) = 3 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=3306, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 3306 close(3) = 0 munmap(0xf6fff000, 4096) = 0 access("/usr/libexec/dovecot/pop3-login", X_OK) = 0 open("/etc/passwd", O_RDONLY) = 3 fcntl64(3, F_GETFD) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 fstat64(3, {st_mode=S_IFREG|0644, st_size=3306, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf6fff000 read(3, "root:x:0:0:root:/root:/bin/bash\n"..., 4096) = 3306 close(3) = 0 munmap(0xf6fff000, 4096) = 0 access("/usr/libexec/dovecot/imap-login", X_OK) = 0 access("/usr/libexec/dovecot/imap", X_OK) = 0 access("/usr/lib/dovecot/imap", R_OK|X_OK) = 0 access("/usr/libexec/dovecot/pop3", X_OK) = 0 access("/usr/lib/dovecot/pop3", R_OK|X_OK) = 0 access("/usr/share/ssl/certs/dovecot.pem", R_OK) = -1 EACCES (Permission denied) write(2, "Fatal: ", 7Fatal: ) = 7 write(2, "Can\'t use SSL certificate /usr/s"..., 77Can't use SSL certificate /usr/share/ssl/certs/dovecot.pem: Permission denied) = 77 write(2, "\n", 1 ) = 1 exit_group(89) = ?

2 1

[Dovecot] Dovecot 64-bit and Pine error
by Remy Zandwijk 15 Mar '05

15 Mar '05

Hi all, I compiled a 64-bit Dovecot stable (13-03-2005) version on a Solaris 9 box with gcc 3.4.2. OpenSSL and libiconv are compiled 64-bit also. The configure I use: export CPPFLAGS="-m64 -I/var/tmp/openssl/include" export LDFLAGS="-m64 -L/var/tmp/openssl/lib" ./configure \ --prefix=/opt/dovecot \ --sysconfdir=/etc/opt/dovecot \ --disable-shared \ --with-libiconv-prefix=/var/tmp/iconv \ --without-passwd-file \ --without-shadow \ --without-vpopmail \ --without-static-userdb \ --with-ssl=openssl \ --with-ssldir=/etc/opt/dovecot/cert \ --without-pop3d Dovecot is running fine, all email clients are running fine, except for Pine (4.62). When saving a mail to another IMAP mailbox, Pine report an error message and the logfile shows: Mar 14 16:33:28 tbox dovecot: [ID 107833 local1.error] IMAP(tstud1): utime(/var/tmp/var_mailstore/ t/tstud1/.Drafts/tmp/1110814408.P2681Q0M979308.tbox) failed: Value too large for defined data type Compiling Dovecot in 32-bit, saving mail within Pine is doing just fine. I guess this is caused by maildir-save.c, line 219. Is this a bug in Solaris or Dovecot? -Remy

2 2

[Dovecot] dovecot 0.99 + apple mail.app
by sean finney 15 Mar '05

15 Mar '05

hello all, first off, a success story. after much testing and preperation, we've switched from uw-imap to dovecot. i am not kidding when i say that we have experienced an order of magnitude decrease in server load (previously load peaks were 40-60, now they are 3-4). so, suffice to say that the mail admins here are very happy :) one problem that has come up though is particular to apple's mail.app. when a client recieves a new message, they aren't notified that it's arrived, and often even when pressing "check for new mail" they don't see it come in. however, if they move from one mailbox to another, and then back, it shows up. it also shows up if thtey completely quit out of the program and start it back up. i'm going to try and get a packet dump of this to see if i can find out what's happening in the conversation, but figured in the meantime i'd put my feelers out to see if anyone else is having this problem. thanks, sean

7 9

[Dovecot] dovecot-stable mbox weirdness
by Matt Howard 14 Mar '05

14 Mar '05

I just tested dovecot-stable from 2005-03-08 and 03-12 and saw the following behavior. All of my mbox folders show is the first message's header. None of the files were truncated (whew, saves a restore). I had 0.99.12.1 installed before this, and just switched back to 0.99.14. Both 0.99.x versions work fine. I removed all of the index files to see if there was a hiccup there, with no effect. System is Slackware 10.0. My package was built with this: http://tinyurl.com/6l2vv

2 3

[Dovecot] aha! (was apple mail vs. v0.99)
by sean finney 14 Mar '05

14 Mar '05

it seems that when you say "check for new mail" in apple mail, it sends a NOOP to the imap server to get the response. in uw, the conversation is something like: 25 NOOP 25 OK NOOP completed 26 NOOP * 2796 EXISTS * 7 RECENT 26 OK NOOP completed however, with dovecot, if it has already notified the client that new mail has arrived, it will look something like: * 24 EXISTS * 2 RECENT 22 NOOP 22 OK NOOP completed. 23 NOOP 23 OK NOOP completed. (the counts are different because these are seperate accounts) so evidently, apple mail is too stupid to realize to read info from the server unless it asked for it... so now that i think i have a short-term fix (disabling notification for new mail server-side), i can breathe a sigh of relief. for a long-term fix, would it be possible to have the server always notify the client of new mail after a NOOP? thanks, sean

3 2

[Dovecot] Authentication error after authentication query (for Eudora 5.2 on Mac)
by Tim Alberts 14 Mar '05

14 Mar '05

Greetings all, I'm a new user of Dovecot and want to say thanks for the great software. I am having a problem at the moment. I run a heterogeneous network with windows and Mac clients logging into a Fedora Linux 2 box running sendmail and previously UW-IMAP, but now Dovecot. I am using strictly pop3, plain authentication with mbox format. Every computer in the network is working fine with this sytem, except 1. A mac running Eurdora mail 5.2. It gives me an Authentication error every time it tries to get mail. I telnet into the server and when I skip the AUTH process and just log in, the server works fine as follows: [talberts@localhost ~]$ telnet mail.inside.msi 110 Trying 192.168.0.3... Connected to mail.inside.msi (192.168.0.3). Escape character is '^]'. +OK dovecot ready. user tdazey +OK pass ****** +OK Logged in. quit +OK Logging out. Connection closed by foreign host. [talberts@localhost ~]$ However, when I do the following session: [talberts@localhost ~]$ telnet mail.inside.msi 110 Trying 192.168.0.3... Connected to mail.inside.msi (192.168.0.3). Escape character is '^]'. +OK dovecot ready. auth cram_md5 -ERR Unsupported authentication mechanism. auth login -ERR Unsupported authentication mechanism. auth plain + user tdazey -ERR Authentication failed. user tdazey +OK pass ****** +OK Logged in. quit +OK Logging out. Connection closed by foreign host. [talberts@localhost ~]$ I don't need any authentication except plain. However, when the client queries the settings, it fails the login. I tried this on multiple accounts with the same results. What do I do to fix this?

3 3

[Dovecot] Dovecot, pam and OpenLDAP
by Rune Hamnvik 14 Mar '05

14 Mar '05

Hello We have a Dovecot installation using only pop3 where auth data is stored in OpenLDAP and accessed using pam. With Fedora 2 everything has worked fine, but when we upgraded to Fedora 3 we started to get problems. After a while a lot of dovecot processes existed, and error messages was logged in maillog telling that the processes was too old. Then some error messages telling about memory leak was logged. Our /etc/pam.d/dovecot looks like this: #%PAM-1.0 auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth Any idea what is happening? Rune Hamnvik Mobinor AS Norway

1 0

Re: [Dovecot] Plain Authentication - Outlook not working
by F. Even 14 Mar '05

14 Mar '05

What problems exist with Thunderbird? Both my wife and I are using Thunderbird with no issues on both OSX and WindowsXP. (No issues that I'm noticing anyway). I'm using 1.0 Test 64: Dovecot v1.0-test64 starting up Frank Simon Windsor wrote: > Hi > > Thanks for the advice, but no luck. > > In the end, I am now using Evolution, which I do not like but it works. > It appears that Kmails IMAP and Thunderbirds IMAP are broken, > particularly kmails! > > Installing Dovecot 1.0.59 improves Dovecots IMAP software, but exposes > flaws for Kmail and Thunderbird! > > So, until the update to KDE, due at the end of March, I will endure > Evolution. > > Thanks, once again > > Simon > > On Sun, 2005-03-13 at 17:40 -0600, F. Even wrote: > >>>Hi >>> >>>I tried re-subscribing and still, I get not emails with kmail. >>> >>>Outlook appeared to pick the change in Subscription file automatically. >>> >>>Any other ideas, or should I drop the IMAP connection and re-do it? >> >>I've always had to drop my IMAP connection and reconnect to recognize >>changes I've made on the server side. A kill -1 to dovecot will only >>reload the server process and the login auth processes...it won't kill >>your already established IMAP connection, which as far as I can tell, >>keeps using old settings. >> >>If you are having that many problems, delete all of your subscriptions >>files and dovecot caches and start from scratch. I've had to do it a few >>times to get things to work as expected. >>

2 1

RE: [Dovecot] Plain Authentication - Outlook not working
by F. Even 14 Mar '05

14 Mar '05

> Hi > > I tried re-subscribing and still, I get not emails with kmail. > > Outlook appeared to pick the change in Subscription file automatically. > > Any other ideas, or should I drop the IMAP connection and re-do it? I've always had to drop my IMAP connection and reconnect to recognize changes I've made on the server side. A kill -1 to dovecot will only reload the server process and the login auth processes...it won't kill your already established IMAP connection, which as far as I can tell, keeps using old settings. If you are having that many problems, delete all of your subscriptions files and dovecot caches and start from scratch. I've had to do it a few times to get things to work as expected.

1 0

[Dovecot] Restrict Imap access
by Sergiu Zaharia 14 Mar '05

14 Mar '05

Hello. I need to restrict access to IMAP ports to a few users, so that all users can use POP3 and just a few of them will be able to access IMAP. I use secure connections POP3s and IMAPs. Is it possible? Also... When I connect to the Dovecot server using Outlook (IMAPs) I get a Warning message,something like: "The server you are connectiing to uses a non verified protection certificate. A chain of certificates ...so on ( I can't translate :) ) Continue using the server? " How can I fix that warning? Thanks

3 2

RE: [Dovecot] Plain Authentication - Outlook not working
by Timo Sirainen 13 Mar '05

13 Mar '05

On Sun, 2005-03-13 at 15:18 +0000, Simon Windsor wrote: > Hi > > I tried re-subscribing and still, I get not emails with kmail. > > Outlook appeared to pick the change in Subscription file automatically. > > Any other ideas, or should I drop the IMAP connection and re-do it? Do you even see the mailbox list? Maybe kmail got somehow confused and recreating the IMAP account entirely would be easiest way to fix it.

4 7

[Dovecot] pop before smtp with 'exact' and 'exim4'
by Jools Smyth 13 Mar '05

13 Mar '05

Hello, I just thought I would write this in case its useful to anyone. I've used dovecot for a while, as its so easy to set up, its fast and it and just "works". I recently wanted to be able to send via my server after pop3s authentication. I'm also running debian (testing) which utilises exim4 by default. I found no information about how to do it with this combination of software so went about sorting it out myself. First I got exact : (a pop before smtp daemon) http://adju.st/dist/exact/ After compiling and installing i edited its /usr/local/etc/exact-servers.conf It doesn't support dovecot's log format out of the box, so i created a regular expression entry for it. <server dovecot> order username,address match (Login): (.*) \[(.*)\] </server> I then edited its main configuration, (/usr/local/etc/exact.conf) changing only the user its running on (default mail/mail) to Debian-exim/mail. (so that the state file it creates can be read fine by exim4) I also changed the mail log ownership so that group mail can read them, /usr/local/var/state/exact to drwxr-sr-x 2 Debian-exim mail 1024 Mar 13 16:39 exact and /usr/local/var/run/exact to drwxr-sr-x 2 Debian-exim mail 1024 Mar 12 21:54 exact Exact's exim documentation is not for the most recent version, so I had to locate the correct line to modify. I went into the exim4 configuration files. I use the debian split format configuration. In the file /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt there is a line near the bottom which reads accept hosts = +relay_from_hosts I changed this to accept hosts = +relay_from_hosts : net-lsearch;/usr/local/var/state/exact/rela y I then just set exact to and start/stop in /etc/init.d/exim4 thats all! Best Regards Jools -- Oxford Inspire jools(a)oxfordinspire.co.uk Tel: 01865 751879 Mob: 07966 577498

2 1

[Dovecot] Plain Authentication - Outlook not working
by Simon Windsor 13 Mar '05

13 Mar '05

Hi I have just upgraded a mail server from dovecot-0.99 to stable (dovecot-1.0.59). My normal desktop email client, kmail is working fine, but outlook keeps producing PLAIN authentication errors, and refusing to authenticate. From dovecot.log, I can see dovecot: Mar 13 10:57:30 Error: auth(default): sql(<xxxxxxxMy Detailsxxxxxxxxxxx>): Password query must return a field named "password" I have tried setting, unsetting disable_plaintext_auth in dovecot.conf, to no avail. What is happening, and what should I do to get all email cleints to work. Simon -- Simon Windsor Email: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07720 447385

2 5

[Dovecot] "not listening" notification
by Alan Tam 13 Mar '05

13 Mar '05

Hi dovecot, My dovecot log shows this: Feb 27 03:08:38 eta imap-login: Login: sltam [X.X.X.X] Feb 27 03:09:38 eta imap-login: Disconnected: Inactivity [X.X.X.X] Feb 27 03:10:32 eta dovecot: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) Feb 27 03:10:42 eta dovecot-auth: Login process has too old (124s) requests, killing it. Feb 27 03:10:42 eta dovecot-auth: Login process 8 disconnected Any clues what it means? Recently I have to restart dovecot several times a day, after I have report that all users cannot login. I am running Debian sarge (2.6.8 kernel) with dovecot version 0.99.14-1 with auth_verbose and auth_debug on. -- Regards, Alan

1 1

[Dovecot] Errors when searching large folders
by Mike Jakubik 12 Mar '05

12 Mar '05

I am getting errors from dovecot when trying to search, in large Maildir folders. The folder has 40454 messages and is 371MB in size. The email client is squirrelmail 1.4.3, running on FreeBSD-current. I've had this problem before, and i posted a message here. The author said he would fix this, but it seem the problem is still not resolved. This is the error i get: --- ERROR : Connection dropped by imap-server. Query: SEARCH CHARSET ISO-8859-1 ALL BODY {5} hello BODY {5} there --- At this point the HD led remain on for another 30 seconds or so. Thanks.

3 9

[Dovecot] Logging options
by Joebstl Thomas 12 Mar '05

12 Mar '05

Hi, is it possible to configure dovecot's logging so it logs stuff like "User x logged in from IP/Host y and had z new messages" like I'm used from qpopper? That immensely helps when debugging PEBKAC issues. Enabling auth_verbose isnt really helpfull since a failed login generates 4 lines, some even without a pid - so it's a bit hard guessing which log entry belongs to which login attempt or even writing a script which checks for those. Regards, Thomas

4 6

[Dovecot] dovecot test62 vs test64
by akolasny＠jhu.edu 12 Mar '05

12 Mar '05

Greetings: I've been using Dovecot 1.0-test62. It has been working well. I tried to upgrade to 1.0-test64 but users could not authenticate. Both versions I compiled with: ./configure --with-ssl=openssl; make; make install They compiled and installed fine. The /usr/local/etc/dovecot.conf needed to be modified due to the new syntax. 1.0-test64 with the new dovecot.conf didn't work. I'm using imaps. The error related to not being able to authenticate. I reinstalled test62 with the original dovecot.conf and everything worked fine again. My config files look like: dovecot.conf-test62 looks like: base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = no ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot-login login = imap login = pop3 mail_extra_groups = mail default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root dovecot.conf-test64 looks like: base_dir = /var/run/dovecot/ protocols = imap imaps ssl_disable = no ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem disable_plaintext_auth = yes login_dir = /var/run/dovecot/login default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u protocol imap { } protocol pop3 { } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } What am I doing wrong? Am I missing something in the 1.0-test64 config file? Your comments or suggestions are greatly appreciated. Thanks, Anthony

2 1

[Dovecot] more info on apple mail vs dovecot 0.99
by sean finney 11 Mar '05

11 Mar '05

hey folks, i have a little more info on this problem... about my setup: i have a mail server running dovecot imap on port 143 and uw imap on 8143. all mail is delivered directly to ~/mbox. what happens: when mail talks to dovecot, every time you check new mail, it re-downloads the entire mailbox. new mail does not show up in the inbox, even after it can be confirmed delivered (via mutt on the server). the really wierd part: even though the message doesn't show up in the list of messages in the inbox, the number of new messages floating above the dock icon (and next to the combined "In" box) *does* go up! wtf?? if you switch between mailboxes, or select "rebuild mailbox", the new message shows up of course both involve resynching the entire mailbox again... my first thought was that this was some kind of wierd application bug, but i'm not so sure. with uw-imap, when you select check new mail it does not re-download the entire mailbox, but the new message does not reliably show up until you switch from one message to another in your inbox. so it seems like there's *some* kind of difference between the two servers... and here come the questions: what would cause apple mail to always download all messages from dovecot but not from uw-imap? i found the following link, is it still relevant? http://lists.freebsd.org/pipermail/freebsd-questions/2004-April/044513.html is this something that might be resolved with 1.0-stable? is there something specific i should look for in protocol dumps? would compacting mailboxes have any effect on this? anyway, thanks to everyone who's helped so far... sean

1 0

Re: [Dovecot] Bit of a Newbie Question
by Wouter Van Hemel 11 Mar '05

11 Mar '05

On Thu, 10 Mar 2005, Jud wrote: >> You have not yet told us if you actually can receive email from outside; >> both with respect to your MTA configuration and an open (i.e. not >> firewalled) internet ip. > > I will have to investigate my MTA configuration. It's not clear to me > what is meant by an "open (not firewalled) internet ip." What > can/should I do on my system to create this condition? > Well, you should have an ip that is publicly accessible for mail servers on the internet, especially for the ones you expect will forward email. If your provider has a firewall for its customers that disallows access to certain ports (such as 25 and 80), you simply can not receive email (by SMTP). Perhaps FastMail will allow you to specify a specific port, but I doubt it. IMO, it's not a good idea to run a mailserver on a residential line with a dynamic ip; likely the contract with your isp even forbids this. Ofcourse, it's up to you to decide and try anyway. >> There is no difference for dovecot. For now, I'd say rather that the >> problem is either that your MTA doesn't accept email, or that your isp >> firewalls port 25 (which is rather likely on a dynamic ip home >> connection). > > It is probably true that my isp blocks port 25; it will be easy to > determine for sure. If so, are there any solutions you can suggest? > Do you have any accounts on remote servers? Just do a 'telnet your_internet_ip 25' ... or something along those lines. If not, try an online open relay testing service such as the one ordb provides: http://www.ordb.org/submit/ Be sure to enable test feedback. It will probably tell you enough for you to find out if it can reach your server or not. >> Read the MTA logs. See if there is any connection at all. If there is, >> check what happens with the messages (refused?). If there is not, you >> either are not accepting connections on your outside interface, or your >> provider has blocked access to port 25. >> >> Did you receive any bounces? > > Yes, though I deleted them, not even thinking to read them for > information. However, it is quite simple for me to create more bounces! > ;-) > Do so, and read the actual error message. This has very little to do with dovecot...

1 0

[Dovecot] dovecot and vpopmail
by radus＠smartpost.ro 10 Mar '05

10 Mar '05

Hello Does dovecot know to expand %d in default_mail_env to the default vpopmail domain in case the user logs without attaching the @domain in his login ? I last tried this on an old dovecot and this didn't work... Radu

1 0

[Dovecot] 1.0-test64
by Timo Sirainen 10 Mar '05

10 Mar '05

http://dovecot.org/test/ Possibly fixes the mail-cache-transaction assert. Passdb and userdb configuration changed. New format is: passdb sql { args = /etc/dovecot-sql.conf } passdb pam { } userdb passwd { } The above would first try to authenticate from SQL database, if it failed because user wasn't found, or password was wrong, it would then try PAM. The same is done for userdbs. I'll probably do some other configuration file changes still before v1.0. I'm also thinking about having a separate config process which can read the actual configuration from files or sql.

9 12

[Dovecot] Is it possible with mysql ?
by kaka 10 Mar '05

10 Mar '05

Is it possible to install dovecot imap / pop3 with mysql authentication, with postfix as mta and with squirrelmail as webmail ? Is it reliable for production state ? I'm working with courier-imap but I don't like it. Hi, kakà.

4 3

Re: [Dovecot] mail-cache-transaction.c error
by Jamie Herre 09 Mar '05

09 Mar '05

On Mar 8, 2005, at 12:50 AM, F. Even wrote: > Timo Sirainen wrote: >> On 7.3.2005, at 01:09, F. Even wrote: >>> Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- >>> transaction.c: line 250 (mail_cache_transaction_reserve_more): >>> assertion failed: (size >= 2) >> I saw this a few times with my tests, but since it happened pretty >> rarely I thought it wouldn't matter much.. Guess you found a way to >> reproduce it much more easily. I'll try to look into it soon. > > Very regularly... Here's a recipe that works for me: Shutdown dovecot; Delete all "dovecot*" files from Maildir; Restart dovecot; Synchronize mailboxes. Every time I get a ton of the above exceptions.

1 1

[Dovecot] dovecot patch for TCB auth
by Thomas Hummel 08 Mar '05

08 Mar '05

Hi, I'm writing to you on behalf of the Pasteur Institute's (Paris, France) IT team. We're currently using dovecot-0.99.10.5_2 on a FreeBSD 5.3. We're planning to upgrade to dovecot-1.x with an openLDAP user and password database and patch it at the same time to include some authentication feature we're using : Since most of our user currently don't use dovecot at all and still authenticate on a DEC alpha running OSF1 [digital unix] V5.1 732, an authentication profile is maintained for each of them on the system. This user profile is kept in the protected password database, accessible only to trusted programs acting on behalf of the trusted computing base (TCB). Some TCB fields are useful to us so we're planning to use their LDAP attibute equivalents and we wrote a custom LDAP shema that includes those which were missing from the standard openLDAP distribution [see details below]. So we're planning (in fact are about to) patch dovecot-1.x in order to take those LDAP attribute (matching the TCB field of interest to us) into account. To do so, we wrote some documentation (still in a draft state) to extend our understanding of dovecot architecture and authentication process. Of course, we're going to give it (patch + doc) back to you and make it freely available. But we'd like to know if you : - were already working on such a patch or planning to do so - were interested, once done (by us or you) to include it into the official release, since it could interest some other person who runs digital unix with TCB authentication Thanks -- Thomas Hummel | Institut Pasteur, Paris, France <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau -------- Here are some details about which attribute we're planning to use and their TCB equivalents uidNumber ~ u_id uid ~ u_name userPassword ~ u_pwd shadowLastChange ~ u_succhg shadowExpire ~ u_expdate shadowMax ~ u_life shadowWarning ~ u_exp [ shadowWarning = u_life - u_exp] plus the one we wrote : maxTries ~ u_maxtries [ maximum number of consecutive unsuccessful login attempts to the account that are permitted until the account is disabled ] numUnsucLog ~ u_numunsuclog [ number of unsuccessful login attempts to the account. It is reset when a successful login to the account occurs.] Lock ~ u_lock [ A boolean indicating if the account is locked ]

2 2

[Dovecot] mail-cache-transaction.c error
by F. Even 08 Mar '05

08 Mar '05

Hello all. I've just recently (this last weekend) migrated to Dovecot on my FreeBSD 4.x box. So far, so good, I like it a lot, and plan on moving mboxes to Maildirs sometime this next weekend. BUT....I've currently run into a problem. I'm seeing an error when one user account tries to access the INBOX from Squirrelmail: Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) I'm using 1.0-test63: Mar 6 04:17:47 cerebus dovecot: Dovecot v1.0-test63 starting up I've since blown away the .imap folder for this user and tried again, it still fails. Other user accounts are having no problems. Here are the relevant log snippets: Mar 6 16:18:02 cerebus dovecot: imap-login: Login: noproblems [127.0.0.1] Mar 6 16:48:48 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:48:49 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:48:52 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:48:52 cerebus dovecot: child 64331 (imap) killed with signal 6 Mar 6 16:48:52 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:50:42 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:50:59 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:50:59 cerebus dovecot: child 64391 (imap) killed with signal 6 Mar 6 16:52:54 cerebus dovecot: imap-login: Login: problemuser [127.0.0.1] Mar 6 16:52:57 cerebus last message repeated 2 times Mar 6 16:52:58 cerebus dovecot: IMAP(problemuser): file mail-cache- transaction.c: line 250 (mail_cache_transaction_reserve_more): assertion failed: (size >= 2) Mar 6 16:52:58 cerebus dovecot: child 64420 (imap) killed with signal 6 Mar 6 16:53:31 cerebus dovecot: imap-login: Login: noprob2 [127.0.0.1] Mar 6 16:53:54 cerebus last message repeated 4 times Mar 6 16:56:12 cerebus last message repeated 12 times Mar 6 16:58:12 cerebus last message repeated 11 times Mar 6 16:58:30 cerebus dovecot: imap-login: Login: noproblems [127.0.0.1] Mar 6 16:58:34 cerebus last message repeated 2 times Any help would be appreciated. Thanks, Frank

2 3

[Dovecot] Upgrade to new server question
by John Peacock 07 Mar '05

07 Mar '05

I'm vainly trying to get a new server ready to become the default mail server. We have a SAN, so I don't need to move the mailboxes (I can mount the same partition from both machines), but the question is what version of dovecot to load. I'm assuming that I cannot run both 0.99.14 and 1.00.x on the same maildirs (the indexes differ?). However, is it safe for me to mount the same maildirs from two different boxes? John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

2 2

[Dovecot] 1.0-test63 released
by Timo Sirainen 07 Mar '05

07 Mar '05

http://dovecot.org/test/ A new test release for a change. Fixed several problems with indexes, especially related to transaction log rotating (pretty easy to find bugs when you set them to be rotated every 5 seconds and keep bombing the same mailbox with 10 test clients). Please report both new and old bugs. The changes might have fixed lots of different randomly occuring problems. The most important bugfixes were also done to dovecot-stable. The tarball is already updated. Looking at changelog, there seems to be: - Don't crash if client disconnects in the middle of APPEND - LDAP and static passdbs can return "extra parameters" (http://wiki.dovecot.org/AuthSpecials) now. Only SQL did before. - Added "nice" extra parameter for userdb to set imap/pop3 process's priority - RPA/SQL passdb patches from Andrey - Major rearrangements (again) to auth code: - Blocking passdbs (SQL) now create auth worker processes to do the actual blocking work. auth_worker_max_count setting specifies the maximum number of these processes to create. PAM and checkpassword code should be fixed to use this method as well. - Fallback to using expired records from auth cache if database lookups fail. - multiple auth setting blocks still not working - Transaction logs are now rotated when they're over 128kB and created (not updated as before) more than 5 minutes ago. So with high traffic mailboxes the log file shouldn't grow forever anymore.. - other fixes and cleanups

2 1

[Dovecot] Too many open files, etc.
by Martin Preen 07 Mar '05

07 Mar '05

Hello, a few days ago I switched out UW-server installation to dovecot 0.99.14 (Solaris 9). There were a few client issues, but mostly the migration was ok. But I have still some questions/problems: +) dovecot-auth: ... PAM: pipe() failed: Too many open files I increased the max. number of open files. Is this normal behaviour, that more than 512 open files are needed ? +) we're using mbox on NFS and index files on local disks. When building the index files for the first time, it takes (of course) a long time for large folders. But we have these users, and this will happen sometimes. Is there a way to improve performance ? +) in general dovecot saves a lot of NFS-bandwidth compared to UW-imap. Thats what I was looking for. But there also seems to be a problem with large inboxes (> 10 MB) and/or large attachments. Is this right ? One user currently gets this error from Pine when accessing a large attachment: MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR. AFAIK this error is related to some timeout problem. Has anyone seen this (and a solution for it) ? Thanks. Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

4 5

[Dovecot] Can't create subfolders of my INBOX or delete folders with IMAP
by Matthew Exon 07 Mar '05

07 Mar '05

Hi, I've been using the dovecot IMAP server for about a year now, and basically it works. But there's an annoying problem, that I can't make any subfolders. I can only make folders that are at the same level as my INBOX folder. Worse, I can't delete folders once I've created them. I'm using Debian unstable on both the server machine and my client machine. The dovecot version is 0.99.13. For my mail client, I'm using Mozilla Thunderbird version 1.0. I've done a bit of investigation on my filesystem, and by googling for all kinds of stuff, but I'm really drawing a blank on this particular problem. Most of the general linux email documentation I've found either doesn't mention IMAP, or doesn't mention dovecot, or both. I can barely find any references to the concept of "subfolder" at all. I really don't want to know anything about email servers, I just want the bloody thing to work. Trying to figure out what the hell's going on is really frustrating! On the server, I seem to have various mailboxes distributed around the place. I've got a mail box in /var/spool/mail. I've got a file ~/mbox, which seems to be very old and is therefore probably a red herring. I've also got a directory ~/Mail with a bunch of files in, one for each of my folders. Having some of my mail in /var/spool, and some in my home directory, seems a really horrible way of arranging things, but anyway... Various online sources seem to suggest that maildir is better than mbox. I don't have any particular preference for one or the other, but I don't want to change if I don't have to because: 1) From experience, I don't screw with settings if I don't have to. Debian made it that way, and changing it behind Debian's back is a surefire way to cause trouble later. 2) Any other accounts on that machine (especially ones I might create in future) will probably still be mbox, causing even worse confusion later. 3) Porting mailboxes is always risky, and I don't want to lose my mail, or have incoming email dropped, or accidentally corrupt it, or anything like that. So I'm not going to do any of that unless I'm sure that it's actually going to fix the subfolder problem, and until now I haven't found any information anywhere to guarantee that that's the case. Intuitively I can guess that if a folder is just a big file full of concatenated email, then making a subfolder is going to be pretty much impossible, but I don't want to guess here. The actual symptoms in thunderbird are: When I select "New folder...", I get the "Create as a subfolder of:" dropdown hierarchy box thingy, but the "Inbox" option is greyed out (side complaint: no user interface should ever have a greyed out option without providing an explanation as to why it's not available, and what you should do if you want it to be available. Displaying it like that is just cruelly teasing the user). When I try to delete a folder, I get a dialog box saying "The current command did not succeed. The mail server responded: Mailbox doesn't exist: <name of folder>". This is pretty frustrating, because I can *see* the damn thing in thunderbird. (another side complaint: "The current command"? You're *running* the bloody command, you should have a better description than that!) For some reason though, I can rename a folder with no problems. I went into /var/log/ on the server, to see what was in the Dovecot log file about the server errors above, but there *is* no log file, nor anything in the syslog. That can't be good. How do you tell the sysadmin when there's a problem? Does anyone have any suggestions for how I can fix this? And if possible, I want to fix this the Debian way, that is by modifying a debconf setting or a /etc/default file or something like that, so that when I upgrade Debian, or uninstall dovecot and then reinstall it, it'll be handled gracefully. Thanks, Matthew Exon

6 12

[Dovecot] pop before smtp
by F. Even 07 Mar '05

07 Mar '05

I'm using the latest version of dovecot on my FreeBSD 4.x box with OpenPKG to keep other services up to date. Now...I'm able to get pbsmtp to allow relaying through postfix on this server using UW IMAP, but I would like to get dovecot working with relaying...but pbsmtp is not adding the ip when I uncomment the dovecot section after I authenticate. The log is below: [root@cerebus:/opt/sbin] ./pop-before-smtp --version version: 1.36 Mar 4 05:14:09 cerebus last message repeated 5 times Mar 4 05:19:46 cerebus dovecot: Killed with signal 15 Mar 4 05:20:00 cerebus dovecot: Dovecot v1.0-test62 starting up Mar 4 05:20:34 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] Mar 4 05:30:21 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] I had uncommented the stock pattern in the latest version to no avail: # For Dovecot POP3/IMAP #$pat = '^(... .. ..:..:..) \S+ (?:dovecot: )? (?:imap|pop3)-login: ' . # 'Login: \S+ \[(\d+\.\d+\.\d+\.\d+)\]'; Thanks for any help anyone might be able to provide. Frank

3 7

[Dovecot] No 'from' in messages
by Remy Zandwijk 06 Mar '05

06 Mar '05

Hi all, Over the weekend, we've migrated our old mail environment to Sendmail and Dovecot: - Dovecot 1.0 stable - Sendmail 8.13.3 - Procmail 3.22 Procmail is MDA for Sendmail and it delivers mail to Maildir boxes. Email clients like Eudora, Thunderbird, Outlook and mutt are working OK. When using Outlook Express and Pine however, in the message list the 'from' or 'sender' field is empty. This means users of these programs cannot see who did send the mail to them. When running Dovecot 0.99 in a early test period, this problem did not occur. Question: Did anyone see this behaviour before and how to fix it? Best regards, Remy Zandwijk

2 4

[Dovecot] Dovecot 1.0-stable .deb file?
by Ian R. Justman 06 Mar '05

06 Mar '05

Hi, all. I know that there's no official Dovecot 1.0-stable .deb, given Timo's recommendations. However, does anyone have even an "unofficial" deb of it for, say, Sarge? I want to use 1.0's ability to use both mbox and maildir; the latter is very helpful for dealing with mailing lists. Thanks in advance for any help. --Ian.

3 2

[Dovecot] Password scheme overides
by Andrew Hutchings 06 Mar '05

06 Mar '05

I notice in the wiki you can have password sceme overides (such as {PLAIN}password). Would this work with the password fields in SQL databases (as it isn't clear in the wiki or conf file)? Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 06 Mar '05

06 Mar '05

In my original email I noted that the directory /usr/local/etc was in the dovecot.conf variable valid_chroot_dirs : valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib Is that not sufficient? Under the /var/run/dovecot directory the directories ./usr/local/etc exist with dovecot-pgsql.conf in. Is there some big RTFM item I'm missing here? -Matthew P.S. - email address changed due to problems with upstream, will jump back as soon as this is fixed so I can finish my migration :) On Sat, 2005-03-05 at 09:06 +0100, Gunter Ohrner wrote: > Am Samstag, 5. März 2005 05:27 schrieb Matthew J. Harmon: > > I have dovecot (+ssl) configured on debian in a chroot with > ^^^^^^ > > I've never run dovecot chrooted, but... > > > The file exists, and permissions look good: > > root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf > > ...let me guess, you're not in the chroot here? > > So, how should dovecot be able to find this file while it runs chrooted? > You need to put all needed files into the chroot. > Yep, that's how it's with 0.99.x. With 1.0-tests however Dovecot opens > the dovecot-pgsql.conf before chrooting. --- Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root at alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root at alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root at alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root at alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

1 0

[Dovecot] Still having problems deleting messages through IMAP
by Doug Eubanks 05 Mar '05

05 Mar '05

Hello, I am using SquirrelMail with the 1.0 releases, and I have even backed up to the latest stable release based on 1.0. I am using MailDirs. When I delete a message, the message still shows up in the message list until either I log out and back in or a new message arrives in that folder. Any ideas? Thanks Doug Eubanks doug(a)simflex.com The speed of time is one-second per second.

2 1

[Dovecot] fd_send broken pipe
by Mike Foley 05 Mar '05

05 Mar '05

Hi, I'm trying to move from UW-IMAP to Dovecot. This is on a RedHat 7.3 system and I'm using the Dovecot RPM from Dag Weirs site. dovecot-0.99.13-1.0.rh7.rf.i386.rpm http://rpmfind.net/linux/RPM/dag/redhat/7.3/i386/dovecot-0.99.13-1.0.rh7.rf… When I start up Dovecot, I get the following: dovecot: Dovecot starting up Feb 28 01:41:54 yelofsrv dovecot: Auth process died too early - shutting down Feb 28 01:41:54 yelofsrv dovecot: child 13724 (auth) returned error 127 Feb 28 01:41:54 yelofsrv imap-login: fd_send(-1) failed: Broken pipe I'm just trying to do a simple PAM/passwd type login. No MySQL/LDAP/PGSQL stuff. I've Googled till the cows came home (almost literally. I was up till 2am last night searching) and can't seem to find a straight answer. Any help/pointers? thanks, mike

2 1

[Dovecot] compile dovecot with mysql support
by Jefferson Campos 05 Mar '05

05 Mar '05

Hello! Is not possible to compile dovecot 0.99.14 version with mysql4, the dovecot configure scripts not detect the mysql4 libs. I already installed the mysql libs and devel packages... --with-mysql doesn't work! Any help or suggestion? Thanks, Jefferson

2 1

[Dovecot] dovecot-pgsql.conf can't find in chroot? (debian)
by Matthew J. Harmon 05 Mar '05

05 Mar '05

Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process died too early - shutting down pop3-login: Mar 04 22:09:07 Fatal: fd_send(-1) failed: Broken pipe I have dovecot (+ssl) configured on debian in a chroot with postfix+pgsql+sasl. The file exists, and permissions look good: root@alfa:~# ls -la /usr/local/etc/dovecot-pgsql.conf lrwxrwxrwx 1 root dovecot 31 2005-03-04 20:35 /usr/local/etc/dovecot-pgsql.conf -> /etc/dovecot/dovecot-pgsql.conf root@alfa:~# ls -la /etc/dovecot/dovecot-pgsql.conf -rw-r--r-- 1 root dovecot 2875 2005-03-01 23:38 /etc/dovecot/dovecot-pgsql.conf But... dovecot-auth can't see it? That's weird... root@alfa:~# strace -vffF /etc/init.d/dovecot start 1>& ~/dovecot.strace root@alfa:~# less ~/dovecot.strace [...] :/chroot [...] :/dovecot-pgsql.conf [pid 18211] open("/var/log/dovecot_info.log", O_WRONLY|O_APPEND|O_CREAT|O_LARGEFILE, 0666 <u nfinished ...> [pid 18213] fcntl64(5, F_SETFD, FD_CLOEXEC <unfinished ...> [pid 18211] <... open resumed> ) = 5 [pid 18213] <... fcntl64 resumed> ) = 0 [pid 18211] fstat64(5, <unfinished ...> [pid 18209] <... fcntl64 resumed> ) = 0 [pid 18211] <... fstat64 resumed> {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|060 0, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=200 5/03/04-22:09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x40019000 [pid 18211] fstat64(5, {st_dev=makedev(22, 1), st_ino=917830, st_mode=S_IFREG|0600, st_nlink =1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=16, st_size=4264, st_atime=2005/03/04-22: 09:07, st_mtime=2005/03/04-22:09:06, st_ctime=2005/03/04-22:09:06}) = 0 [pid 18211] _llseek(5, 4264, [4264], SEEK_SET) = 0 [pid 18211] fcntl64(5, F_GETFD) = 0 [pid 18211] fcntl64(5, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 6 [pid 18211] fcntl64(6, F_GETFD) = 0 [pid 18211] fcntl64(6, F_SETFD, FD_CLOEXEC) = 0 [pid 18211] open("/etc/localtime", O_RDONLY) = 7 [pid 18211] fstat64(7, {st_dev=makedev(22, 1), st_ino=6193169, st_mode=S_IFREG|0644, st_nlin k=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=1279, st_atime=2005/03/04-22: 09:07, st_mtime=2004/12/26-20:19:40, st_ctime=2005/02/09-03:35:52}) = 0 [pid 18211] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0 x4001a000 [pid 18211] read(7, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\5\0\0\0\5\0"..., 4096) = 127 9 [pid 18211] close(7) = 0 [pid 18211] munmap(0x4001a000, 4096) = 0 ** chrooting dovecot-auth [pid 18211] chroot("/var/run/dovecot-auth") = 0 [pid 18211] chdir("/") = 0 [pid 18211] gettimeofday({1109995747, 798541}, {360, 0}) = 0 [pid 18211] rt_sigaction(SIGHUP, {0x404a07a0, [], SA_RESTORER, 0x4027e678}, NULL, 8) = 0 [pid 18211] rt_sigaction(SIGINT, {0x404a07a0, [INT], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGTERM, {0x404a07a0, [TERM], SA_RESTORER|SA_RESTART, 0x4027e678}, {SIG_DFL}, 8) = 0 [pid 18211] rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 *** lets look at dovecot-pgsql.conf! [pid 18211] open("/usr/local/etc/dovecot-pgsql.conf", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 18211] time(NULL) = 1109995747 [pid 18211] write(4, "dovecot-auth: Mar 04 22:09:07 Fa"..., 128) = 128 [pid 18211] munmap(0x40018000, 4096) = 0 [pid 18211] exit_group(89) = ? Process 18211 detached Excerpts from /etc/dovecot/dovecot.conf: auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf login_chroot = yes valid_chroot_dirs = /usr/local/etc:/etc:/var/mail:/lib auth_chroot = /var/run/dovecot-auth Any recommended next steps? Thanks a million! -Matthew

3 2

[Dovecot] mbox or maildir?
by Brian Read 04 Mar '05

04 Mar '05

I am using dovecot in an SMEServer (aka e-smith), and recently backed-up on one system and restored on another system the imap email directories. The trouble was that dovecot "guessed" the mail type wrongly, and I ended up with "empty" ~/Mail directories (did it create or populate these?), and full, but ignored ~/Maildir directories for every user. Could someone point me to the chapter and verse of how (and when) dovecot decides which type of mail is in use, and how you can change the decision. I tried editing /etc/dovecot.conf, but that didn't seem to make any difference. Using dovecot 0.99-10 under a Redhat 7.3 base on kernel 2.4.20-18.7 -- Cheers Brian http://www.abandonmicrosoft.co.uk

3 3

[Dovecot] Dovecot response to "FETCH" command
by Alex Tang 04 Mar '05

04 Mar '05

Hi folks. I just converted my site from UW+mbox to dovecot+maildir (stable-test59, 2005/02/25). For the most part, everything is great. The server seems faster and less memory intense than the UW server (this part has made me very happy). And it's definitely more user friendly to me than Courier. There is one thing however... A few of my users are using the web based mail reader (Squirrelmail-1.2.11) that i provide for them. Once i converted to dovecot, the squirrelmail users were reporting that when viewing the folder list page, 2 things were happening: * The date for all of the messages was being displayed as "Sun 4:00 pm" * all messages were shown as being "new". they never would be transferred into the "Seen" state. After doing some IMAP protocol sniffing, i found this difference in the way that the UW server and the dovecot server handles the "FETCH" command... Squirrelmail issues a FETCH command to get message header information like this (lines broken with backslashes for readability): A009 FETCH 1:1 (FLAGS RFC822.SIZE INTERNALDATE BODY.PEEK \ [HEADER.FIELDS (Date To From Cc Subject X-Priority \ Content-Type)]) The UW server returns: * 1 FETCH (FLAGS () RFC822.SIZE 710 \ INTERNALDATE "27-Feb-2005 23:50:42 -0800" \ BODY[HEADER.FIELDS ("DATE" "TO" "FROM" "CC" "SUBJECT" \ "X-PRIORITY" "CONTENT-TYPE")] {153} Date: Sun, 27 Feb 2005 23:50:42 -0800 From: root <root(a)scorchedearth.us.proofpoint.com> To: altitude(a)scorchedearth.us.proofpoint.com Subject: asdf When the same FETCH response is returned by dovecot, the response looks like this: FLAGS () RFC822.SIZE 3358 INTERNALDATE "27-Feb-2005 07:55:27 -0800") * 1 FETCH (BODY[HEADER.FIELDS (DATE TO FROM CC SUBJECT X-PRIORITY CONTENT-TYPE)] {205} Date: Mon, 28 Feb 2005 00:04:22 +0800 From: xxx xxx <xxx(a)xxx.com> To: dovecot(a)dovecot.org Content-Type: text/plain; charset=UTF-8; format=flowed Subject: [Dovecot] "not listening" notification I noticed that in the UW response, the "* 1 FETCH ..." is the first line, and contains all of the data except for the message header info. However, in the dovecot response, the data is split into 2 lines, and the first line is not the "* 1 FETCH" line. In reading through the squirrelmail source, squirrelmail is not recognizing this as a valid response, and thus the date, size, and flags are not being properly set in the internal squirrelmail message objects. This explains why both the date as well as the "seen" status of the message is never properly set. OK, after all this blabbing on...here's my question. Is the data being sent back by dovecot a valid response? My knowledge of the IMAP protocol is weak to say the least. I tried reading the IMAP RFC (3501), in particular section 6.4.5 which defines the FETCH command), and the RFC seems to specify that the response should have the "* # FETCH" lines come first. However, the RFC seems vague, and i didn't wade through any of the other RFCs out there. I figure it is legal, since the two other clients i've used seem to understand it just fine (thunderbird/mozilla, mutt). However, could this be the reason why mozilla/thunderbird sometimes gets the message size wrong (and hence why the "tb-negative-fetch" workaround is needed). For now, i'll bang on squirrelmail to support the response sent by dovecot. Thanks. ...alex...

3 4

[Dovecot] hanging imap... and users getting other users' emails!
by Josh Burley 03 Mar '05

03 Mar '05

Hi All, We recently upgraded from UW (boy, starting to sound like a broken record, eh?)... Two problems: 1. Every two or three days users are unable to access their email via IMAP. It seems that it's because dovecot-auth has hung. Has anyone seen anything like this? 2. (the really serious one)... one of our users, "angie" has twice had her Outlook download other users' email! Once as another user, "helene", and just now as "mkarlin". The first time she got 800 of helene's email, and just now, about 30 of mkarlin's.... from our log, I noticed: Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:10 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core pop3-login: Login: angie [::ffff:68.231.223.128] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Mar 2 17:27:11 core imap-login: Login: mkarlin [::ffff:128.195.131.2] Our server setup: Fedora Core 3. dovecot-0.99.13. OpenLDAP, and dovecot auth'ing off PAM (mostly default setup, using Mailbox, and mail/ as a subdir). Any ideas? Any more debug info I can supply? .josh

4 10

[Dovecot] Is Dovecot SMP and thread-safe?
by Peter Franck 03 Mar '05

03 Mar '05

Josh´s problem report reminds me of other multi-CPU issues. Just a guess, Peter

5 5

[Dovecot] selective POP3 user
by Barry Kwok 03 Mar '05

03 Mar '05

I want to know if it is possible to limit some users to use POP3 service only in a server running BOTH IMAP and POP3 service. In other words, some users can choose IMAP or POP3 and some users can only use POP3. Barry

3 2

[Dovecot] Several issues with 1.0-stable
by Remy Zandwijk 03 Mar '05

03 Mar '05

All, We have Dovecot 1.0-stable deployed in our 3000 users environment as of last weekend. Up untill now, I have 3 issues: - When stopping Dovecot with: kill -TERM `cat /var/run/dovecot/master.pid`, the 'dovecot' process itself dies, the 'imap-login' processes die, but the 'imap' processes (there are a lot of them) don't die, but become a zombie. I think the way I stop Dovecot is the way to do it. The zombies can be killed by doing a 'pkill -9 imap', but that's not quite elegant. - Dovecot is running in a Solaris 9 environment. It turned out that Dovecot crashes when more then 256 filedescriptors are being used. This is rather normal, since Solaris only support 256 descriptors per 32-bit process. After starting Dovecot, I do a 'plimit -n 8192, 8192 `cat /var/run/dovecot/master.pid`, which allows Dovecot to have 8192 filedescriptors. Timo, is it possible to introduce a config file option to configure the number of descriptors? - Pine and Outlook users don't see the adresses or names of the people who sent them email. In my email yesterday, I said I remembered that tests with Dovecot 0.99 showed no problems. Today, I installed both Dovecot 0.99 and 1.0-stable on my test box. It turned out that 0.99 indeed works OK and that 1.0-stable is the problem. The user mailboxes are 'Maildir'; we do not use mbox format. I like to see this problem being fixed..... We have 2 namespaces in our setup: the default namespace and a namespace which location is set to ~/.Mailstorage. When not using a prefix in the email client setup, users can make new email folders in the default namespace and the 'Mailstorage' namespace. We want users only to create mail folders in the Mailstorage namespace, not in the default namespace. Questions: - Is it possible to force a prefix to clients? - If not, is it usefull to have an option in the namespace configuration that allows or disallows the creation of mail folder? If so: consider this as a feature request. Thank you for reading, best regards, Remy Zandwijk Free University of Amsterdam The Netherlands

2 1

[Dovecot] Newby Question
by Troy Bull 03 Mar '05

03 Mar '05

Hello I just setup my IMAP server and everything works great, except for 1 small detail. I am upgrading from uwashington's imap server, and in theirs I had to put a directory "mail" in for the imap folder (this is on the client). The problem I have is with dovecot this makes an extra level (I think). So on my server ~/mail is where the mail folder is located, but when the client puts in the "mail" for the imap server directory dovecot looks in and creates folders in ~/.mail/mail. This is a problem for me because I have many clients and I would have to go reconfigure each one. My question is this, is there a way to make dovecot look in ~/ so that when combined with the imap folder from the client it ends up in ~/mail? I hope that is clear enough, I was thinking maybe I need to set default_mail_env, but i have no idea to what? Thanks in advance Troy

2 1

[Dovecot] Trigger getmail via mail-client action?
by Gert Brinkmann 03 Mar '05

03 Mar '05

Hello, I want to use dovecot on my private debian/unstable-system to have the advantages of an IMAP-Server (Access to mails from different computers, Simply changing the mail client). I decided to use dovecot, because I very often have read (in the web) that it should be more simple to configure than other servers. Now I have the following question: I want to use getmail to retrieve mails from my provider's pop3-server. I do have a dial-up-connection that is not online permanently (I do not have a flat rate). I could start a script on ppp's ip-up that periodically invokes getmail and on ip-down to kill it again. But I would prefer to invoke getmail only when I really want it to be run. The ideal solution for me was to invoke getmail when the "Get Mail"-Button of the mail client is pressed. Is this possible? Perhaps there is something like a connection- or refresh-trigger in dovecot? Thank you, Gert

4 5

[Dovecot] Dovecot started by inetd
by Peter Franck 03 Mar '05

03 Mar '05

Is anyone else starting dovecot by inetd on the list? I'm unable to get it running, stupid me. I need help by someone more experienced. Peter

2 1

Re: [Dovecot] Too many open files, etc.
by Remy Zandwijk 28 Feb '05

28 Feb '05

> a few days ago I switched out UW-server installation to > dovecot 0.99.14 (Solaris 9). There were a few client issues, > but mostly the migration was ok. > > But I have still some questions/problems: > > +) dovecot-auth: ... PAM: pipe() failed: Too many open files > I increased the max. number of open files. Is this normal > behaviour, that more than 512 open files are needed ? Martin, we're dealing with the same problem right now. We are using dovecot 1.0 stable and we migrated last weekend. 32-bit processes in Solaris 9 have 256 filedescriptors avail- able. This seems a bit to small. Using this command to get the number of file descriptors used by dovecot: ls -1 /proc/`cat /var/run/dovecot/master.pid`/fd | wc In our enviroment this is currently around 390. You can limit the number of file descriptors per process in Solaris 9. After starting Dovecot, we issued the command: plimit -n 8192,8192 `cat /var/run/dovecot/master.pid` This gives Dovecot 8192 filedescriptors. HTH, Remy

1 0

[Dovecot] UID inserted in the middle of mailbox
by Nicolas STRANSKY 28 Feb '05

28 Feb '05

I'm seeing these with latest 1.0-stable : Feb 27 16:48:12 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (176 > 150) Feb 27 16:49:58 zamok dovecot: POP3(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (4409 > 4237) Feb 27 16:50:04 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (7122 > 5116) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (15571 > 14535) Feb 27 16:50:16 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /home/****/Mail/trash (16578 > 14535) Feb 27 16:50:19 zamok dovecot: IMAP(****): mbox sync: UID inserted in the middle of mailbox /var/mail/**** (23318 > 13713) -- Nico L'étude approfondie de la nature est la source la plus féconde des découvertes mathématiques. -+- Joseph Fourier -+-

2 1

[Dovecot] Protect some mailbox to remove
by FireFly 25 Feb '05

25 Feb '05

I've installed dovecot 0.99.14 (maildir, postfix, RHEL3) and I would like to create , for every user, 4 mailbox (in skel): mail-sent, spam, virus-alert and sysadm. Procmail, parsing header mail, will move mails into a specific mailbox. Every users could move, delete, read these mails but they must not delete mailbox folder (such as INBOX mail). Thanks in advance, Francesco __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[Dovecot] APOP
by Steven Stern 25 Feb '05

25 Feb '05

I want to turn off POP3 and use POP3S in its place. So far, it's working well for Outlook and Thunderbird. But I'm running into problems with Agent: It supports APOP but not POP3S. Is there a way to have Dovecot support APOP authentication on a normal POP3 connection? I'm running 0.99.13 on Fedora Core 3. -- Steve

2 1

[Dovecot] A few words about NFS please?
by Jeff A. Earickson 25 Feb '05

25 Feb '05

Hi, Could you say a few words about Dovecot and POP/IMAP to an NFS mounted filesystem? I thought I saw on the dovecot webpage that NFS is "no way" with 0.99 and "maybe" with 1.x. I was looking for the FAQ and couldn't find it. My setup is like so: My mail server is a Solaris 9 system, running sendmail/procmail, and qpopper POP. Mail is stored in mbox format. The /var/mail filesystem is NFS exported to another Solaris 9 system that runs UW-IMAP. The user community also has login access to this second system, so there are also local email clients like Pine and emacs using the NFS /var/mail. So, POP and sendmail/procmail accesses /var/mail locally, while UW-IMAP accesses it via NFS. The user community has been warned to do either POP or IMAP, but not both. There are very few problems with this setup. I would like to use Dovecot for both POP and IMAP on the two machines. I know NFS is frowned upon, but this has worked for me. Comments and suggestions, please? Jeff Earickson Colby College

4 3

[Dovecot] Inotify
by Nicolas STRANSKY 25 Feb '05

25 Feb '05

Hi, Is there any plans to use the Linux inotify, which is a major improvement over dnotify ? (Linux mechanism for communicating filesystem events to user space) Regards, -- Nico Écrivez dans l'ivresse, mais relisez-vous à jeun. -+- André Gide (1869-1951) -+-

2 1

[Dovecot] Authentication woes
by woollettg 25 Feb '05

25 Feb '05

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability completed. Authentication failed. no mechanism available Security strength factor: 0 mercury:/etc/dovecot# Below is my configuration file for version 0.99-14.1 on a Debian Sarge box I'm quite happy with plaintext auth for now. Any help or suggestions much appreciated. Graeme ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc/dovecot # --localstatedir=/var --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. login_executable = /usr/lib/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/lib/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's a few special # variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # outlook-pop3-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location imap_executable = /usr/lib/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/lib/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # An Authentication process is a child process used by Dovecot that # handles the authentication steps. The steps cover an authentication # mechanism (auth_mechanisms, how the client authenticates in the IMAP or # POP3 protocol), which password database should be queried (auth_passdb), # and which user database should be queried (auth_userdb, to obtain # UID, GID, and location of the user's mailbox/home directory). # # You can have multiple processes, though a typical configuration will # have only one. Each time "auth = xx" is seen, a new process # definition is started. The point of multiple processes is to be able # to set stricter permissions. (See auth_user below.) # # Just remember that only one Authentication process is asked for the # password, so you can't have different passwords accessible through # different process definitions (unless they have different # auth_mechanisms, and you're ok with having different password for # each mechanisms). # Authentication process name. auth = default # Specifies how the client authenticates in the IMAP protocol. # Space separated list of permitted authentication mechanisms: # anonymous plain digest-md5 cram-md5 # # anonymous - No authentication required. # plain - The password is sent as plain text. All IMAP/POP3 clients # support this, and the password can be encrypted by Dovecot to match # any of the encryption schemes used in password databases. # digest-md5 and cram-md5 - both encrypt the password so it is more # secure in transit, but are not well supported by clients, and # require that the password database use a matching encryption # scheme (or be in plaintext). # # See auth.txt for more details. # # If you are using SSL there is less benefit to digest-md5 and # cram-md5 as the communication is already encrypted. auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_userdb = passwd # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see /etc/dovecot/dovecot-ldap.conf # mysql <config path>: a MySQL database, see /etc/dovecot/dovecot-mysql.conf # pgsql <config path>: a PostgreSQL database, see # /etc/dovecot/dovecot-pgsql.conf auth_passdb = passwd #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by auth_userdb above. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_mechanisms = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5"

3 2

[Dovecot] Re: Problems with MySQL/PAM authentication
by KATOH Yasufumi 25 Feb '05

25 Feb '05

> I'm using (or trying to at least) a combination of PAM/passwd and MySQL > authentication: : (snip) > MySQL authentication works without problems but authentication real > (system) users dosn't: : I have similar problem using Multiple Auth Database: auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } I tested: | % telnet localhost 143 | Trying 127.0.0.1... | Connected to localhost. | Escape character is '^]'. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 NO Authentication failed. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | Connection closed by foreign host. "kato(a)harp.gr.jp" is registered in /etc/dovecot/passwd. First time it failed, but success at second time. "auth local" works without problem. | Feb 24 11:19:24 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(local): shadow(kato(a)harp.gr.jp,127.0.0.1): unknown user | Feb 24 11:19:33 tara dovecot: auth(virtual): userdb(kato(a)harp.gr.jp,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:19:33 tara dovecot: IMAP(kato(a)harp.gr.jp): mkdir(/home/kato(a)harp.gr.jp/Maildir/cur) failed: Permission denied | Feb 24 11:19:33 tara dovecot: imap-login: Login: kato(a)harp.gr.jp [127.0.0.1] | Feb 24 11:19:35 tara dovecot: auth(local): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:19:35 tara dovecot: child 14884 (auth) killed with signal 6 I rewritten dovecot.conf and tested. The result is different. auth local { mechanisms = plain userdb = passwd passdb = shadow user = root } auth virtual { mechanisms = plain userdb = passwd-file /etc/dovecot/passwd passdb = passwd-file /etc/dovecot/passwd user = root } At this time, "auth virtual" work, and "auth local" doesn't work. | * OK Dovecot ready. | 1 login kato(a)harp.gr.jp password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. | * OK Dovecot ready. | 1 login kato password | 1 NO Authentication failed. | 1 login kato password | 1 OK Logged in. | 1 logout | * BYE Logging out | 1 OK Logout completed. (kato is system user) | Feb 24 11:28:52 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(virtual): passwd-file(kato,127.0.0.1): unknown user | Feb 24 11:28:59 tara dovecot: auth(local): userdb(kato,127.0.0.1): uid=1000 gid=100 home=/home/kato mail= | Feb 24 11:28:59 tara dovecot: imap-login: Login: kato [127.0.0.1] | Feb 24 11:28:59 tara dovecot: auth(virtual): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) | Feb 24 11:28:59 tara dovecot: child 14924 (auth) killed with signal 6 It is not worked well to write configuration previously, but worked well to write after. I tested with ldap auth instead of paswd-file auth. I got same result. Env: Plamo Linux 4.01 (kernel 2.6.10, glibc 2.3.2) dovcot-1.0-test62, dovecot-stable-20050222 -- karma @ jazz.email.ne.jp / Y.KATOH Sorry for my poor English.

2 2

[Dovecot] Limit Number of Postgres Database Connections
by Dan Fitzpatrick 25 Feb '05

25 Feb '05

I have dovecot running with postgres backend. I am exceeding my maximum database connections (currently 40) with dovecot 0.99.10.9 and postfix and was wondering if dovecot has a parameter to limit the total number of database connections that it will create. Dan

2 1

[Dovecot] mozilla, error in imap command uid
by Nicolas Kowalski 24 Feb '05

24 Feb '05

Hello. Mozilla (1.7.3) gives me the following error message when trying to view some messages: the mail server responded: Error in IMAP command UID: Invalid BODY[..] parameter: Missing '>' in '<10240.-7730>'. What's wrong ? Thanks. -- Nicolas

5 9

[Dovecot] Nightly stable & SSL-problems
by Jani Karlsson 23 Feb '05

23 Feb '05

Getting it otherwise to work, but I still can't get it to listen any SSL-ports. been testing: protocols = imap imaps pop3 pop3s listen = 193.65.59.150 ssl_listen = 193.65.59.150 doesn't help. with: ssl_disable = no of course. protocol imap { # Login executable location. login_executable = /usr/local/libexec/dovecot/imap-login # IMAP executable location mail_executable = /usr/local/libexec/dovecot/imap ssl_listen = 193.65.59.150 .... } tried it there also.. yet: tcp 0 0 193.65.59.150:110 0.0.0.0:* LISTEN 29030/dovecot tcp 0 0 193.65.59.150:143 0.0.0.0:* LISTEN 29030/dovecot is the result I get. Anyone succeeded in this? Platform is Debian/Linux, running 2.4 series kernel, compiled with openssl-support. Version is dovecot-stable-20050221. All help appreciated. Jani Karlsson

2 1

[Dovecot] Build error in stable branch
by Andrew Hutchings 23 Feb '05

23 Feb '05

Hi guys, Just tested yesterday's stable build, when including SQL into the build I am getting an error on like 86 of passdb-sql.c (passdb_result = PASSDB_RESULT_OK;) It rightly says passdb_result is undeclared. Commenting out this line fixes it and build appears to work fine after that. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] Problems with Dovecot and self-signed cert
by Seth Bokelman 22 Feb '05

22 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've recently set up a Red Hat Enterprise Linux 4 WS server, and decided to try using Dovecot as my IMAP server, as I was impressed with the dedication to security that seems to be the core development goal. I'm really happy with it, but I can't get it to work with a self-signed cert. Normally, on a RHEL system, you just go into /user/share/ssl/certs/ and type: make whatever.pem Then you fill out the various address fields, and you've got a cert. However, when I rename/delete the existing dovecot.pem and generate a new one using this method, Dovecot won't start and I'm unable to connect to the box. The cert that it's currently using is called "localhost.localdomain", and while that works, mail clients gripe every time about the domain name not matching the certificate. I've looked through the RHEL documentation, and it appears I'm doing everything correct. Anyone have any suggestions? - -- Seth H. Bokelman (Seth.Bokelman(a)UNI.edu) Systems Administrator ITS-Network Services, University of Northern Iowa 15 Curris Business Building, Cedar Falls, Iowa 50614 Phone: (319) 273-7423 http://www.sethb.com/ ICQ#: 6497760 MSN Messenger: seth.bokelman(a)uni.edu AOL/AIM: sethb2 Yahoo Messenger: sethbokelman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCG3QhOiUz+Af5BIIRAv0VAKCm9JlKio9Z9Dzdr+WnZVtoYBNVqACdHNQH TuiLbT6yIXmeJLFg9ggibcM= =yPVK -----END PGP SIGNATURE-----

2 2

Re: [Dovecot] apple mail, and mails marked as deleted
by Joerg Lentsch 22 Feb '05

22 Feb '05

On 22.02.2005, at 03:17, Jim Tittsler wrote: > On Feb 22, 2005, at 04:36, Joerg Lentsch wrote: > >> is this a feature or a bug in conjunction with apple mail. i usually >> use the feature in imap to not delete the emails, but only mark them >> as deleted, which is a very usefull feature if you use a emailbox >> with more people accessing it. Im now trying an SME server >> installation with dovecot 0.99.10, and when i delete a message, it >> gets marked as deletet, but as soon as i change the mailbox the mail >> gets also expunged from it. is this a bug fixed in the newer dovecot >> releases ? or is this a feature that i can configure ? > > Do you have Mail.app set to "Compact mailboxes automatically" (on the > Advanced tab of the preferences for the account you are using)? When > that is checked, Mail.app issues an IMAP CLOSE command when you leave > a mailbox, which removes messages with the \Deleted flag set. > Hi there! thank you all for the answer. Yes indeed, after trying all the various options on the mail client, i discovered that it was this "Compact" switch. Thanks again for your help. /Maximus -- W.E.L.T. - Joerg Lentsch Mitterweg 16 Via di mezzo ai piani Tel: +39 0471 973020 I-39100 Bozen Bolzano Fax:+39 0471 974131 Suedtirol - Italien - Italia

1 0

[Dovecot] uw-imap and gnu-pop3d to dovecot transition/replacement
by Jani Karlsson 22 Feb '05

22 Feb '05

Hi I am trying directly to replace old uw-imap + GNU pop3d with Dovecot. Problems I am having with new (1.0-stable 22.02.2005) are: - How to get SSL working with new config? imaps_listen doesn't exist anymore. cannot add protocol imaps for some reason. - need to get Dovecot run on another port the test-phase, ie 144 for imap, 994 for IMAPs - need to use .mailboxlist (modified the source already, this maybe works - due SSL problem not tested?) - no symlinks etc can't be done (simply too many mailboxes) so how to make dovecot read IMAP-directories from user's homedir.. Anything else I should know before trying this transition? All help truely appreciated. Jani. (Mailbox count is high which why transition to faster postclient-server software is necessary - or adding few more dual CPU-servers.. and doing anything but editing config/such by hand is not a option.)

2 2

[Dovecot] apple mail, and mails marked as deleted
by Joerg Lentsch 22 Feb '05

22 Feb '05

hi, is this a feature or a bug in conjunction with apple mail. i usually use the feature in imap to not delete the emails, but only mark them as deleted, which is a very usefull feature if you use a emailbox with more people accessing it. Im now trying an SME server installation with dovecot 0.99.10, and when i delete a message, it gets marked as deletet, but as soon as i change the mailbox the mail gets also expunged from it. is this a bug fixed in the newer dovecot releases ? or is this a feature that i can configure ? TIA /Maximus -- W.E.L.T. - Joerg Lentsch Mitterweg 16 Via di mezzo ai piani Tel: +39 0471 973020 I-39100 Bozen Bolzano Fax:+39 0471 974131 Suedtirol - Italien - Italia

3 2

[Dovecot] Bug?: Authentication still doesn't work with imap-login
by Peter Franck 21 Feb '05

21 Feb '05

I tried digging it all through. I can't find a solution. The problem pops up in auth-master-connection.c in function master_input_request. It does a auth_client_connection_lookup with the "client_pid" (which behaves as a counter, where i would expect a constant process-id...) Something is very wrong with this PID. Maybe someone can explain the Master <--> Auth IPC to me so I can understand and fix it myself? Where does Master take this client number from? Hints are highly appreciated, Peter --- LOG --- Feb 21 21:04:36 office dovecot: Dovecot v1.0-test62 starting up Feb 21 21:04:48 office dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=192.168.23.1 rip=192.168.23.42 resp=AHZpYwBzeXNpbnQyMQ== Feb 21 21:04:48 office dovecot: auth(default): client out: OK 1 user=vic Feb 21 21:04:48 office dovecot: auth(default): master in: REQUEST 1 2 1 Feb 21 21:04:48 office dovecot: auth(default): Master requested auth for nonexisting client 2 --- my configuration: --- base_dir = /var/run/dovecot/ protocols = imap imaps ssl_cert_file = /etc/ssl/certs/imapd-192.168.23.1.pem ssl_key_file = /etc/ssl/certs/imapd-192.168.23.1.pem protocol imap { } protocol pop3 { } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb = pam imap userdb = passwd user = root }

1 1

[Dovecot] index corruption with test62 on openbsd 3.6
by Ben Lovett 21 Feb '05

21 Feb '05

i noticed this while browsing through my maillog.. Feb 21 11:27:43 selenium dovecot: IMAP(ben): Corrupted index cache file /u/home/ben/Maildir/.INBOX.ML-SunHELP.rescue/dovecot.index.cache: field index too large (3337 >= 22) i have no problems reading that box after this, and see no other messages about corrupt index files from today, or the past 14 days. --ben

1 0

[Dovecot] Dovecot SSL-Certificate
by Adam Pordzik 21 Feb '05

21 Feb '05

Hello, I've a not really dovecot specific problem with my certificate. Since the OpenSSL documentation isn't what I expect to be at least good, I hope someone here can give me a hint how/where fo fix it; I've created a root-Certificate with almost untouched openssl.cnf and issued a server-certificate for dovecot. This cert and it's key I placed in somewhat like /var/dovecot. To state explicitly, away from it's superior root-cert. So, a: openssl s_client -connect server.tektoform.lan:993 -showcerts ends up in: unable to get local issuer certificate. Althougt connections from clients are working, I prefer to set it up cleanly. Does openssl-clientlib looks up for openssl.cnf, where the place of root-CA-cert is denoted, or do I have to put all cert together in a single directory, or, or, or ...? Or to be more verbose for "openssl s_client": CONNECTED(00000003) depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=27:certificate not trusted verify return:1 depth=0 /C=DE/ST=Hamburg/L=Hamburg/O=d-dt/OU=lan/CN=server.tektoform.lan/emailAddress=hostmaster(a)tektoform.lan verify error:num=21:unable to verify the first certificate verify return:1 --- Thanks for your comments. A --

2 1

[Dovecot] login: Missing protocol from server name 'imap'
by Peter Franck 20 Feb '05

20 Feb '05

I also tried the 0.99 and hacking login-process.c, with no success. It seems to expect a slash delimited string like 'name/protocol' and it just gets "imap" there, but I didn't figure out where this string comes from or what it ought to be. So I would be grateful if someone could enlighten me. Thanks, Peter --- Some blafa: Feb 17 21:45:44 office dovecot: Dovecot v1.0-test59 starting up Feb 17 21:45:44 office dovecot: login: Missing protocol from server name 'imap' Linux office 2.4.20-64GB-SMP #1 SMP Fri Jan 14 15:08:48 UTC 2005 i686 unknown unknown GNU/Linux Client: Mozilla Thunderbird 1.0 (20041206) IMAPS port 993 Dovecot Started by xinetd: # # imaps - imap mail daemon over ssl # service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login server_args = --ssl flags = IPv4 }

3 6

[Dovecot] Re: Need 2 additional folders like INBOX for JUNK and INFECTED mails
by Mirko Schulze 17 Feb '05

17 Feb '05

Hi there. I've solved now the problem, but it's not really fine yet. The "special-folders" are undeletable in the filesystem, but the Mailclient displays different errormessages for the same action. I've modified following source files. The new additional lines are similar to the INBOX "lines" /src/imap/cmd-list.c: 63 /src/imap/cmd-delete.c :20 /src/lib-storage/index/maildir/maildir-storage: 294,308,437,601 Notice that the linenumbers are not really correct, because of the deferrals by inserting new sourcecode. The new problem is, that the mailclient displays incorrect error messages. When i use another folder caching method i'll get no errors. Perhaps someone has a better solution, than i? Thanks Mirko

1 0

[Dovecot] Problems with MySQL/PAM authentication
by Allan Joergensen 17 Feb '05

17 Feb '05

Hi, I'm using (or trying to at least) a combination of PAM/passwd and MySQL authentication: auth vmail { mechanisms = plain userdb = sql /etc/dovecot/dovecot-sql.conf passdb = sql /etc/dovecot/dovecot-sql.conf user = root } auth system { mechanisms = plain userdb = passwd passdb = pam imap user = root } MySQL authentication works without problems but authentication real (system) users dosn't: Feb 13 02:05:57 coredump dovecot: auth(vmail): sql(alj,127.0.0.1): query: SELECT crypt AS password FROM passwd WHERE id = 'al j' Feb 13 02:05:57 coredump dovecot: auth(vmail): sql(alj,127.0.0.1): unknown user Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: auth(vmail): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) Feb 13 02:05:57 coredump dovecot: auth(system): userdb(alj,127.0.0.1): uid=10000 gid=1000 home=/home/alj mail= Feb 13 02:05:57 coredump dovecot: imap-login: Login: alj [127.0.0.1] Feb 13 02:05:57 coredump dovecot: child 22359 (auth) killed with signal 6 Feb 13 02:05:58 coredump dovecot: auth(vmail): mysql: Connected to (null) (vmail) After a few logins authentication stops working and dovecot needs to be restarted. It seems that the mysql dovecot-auth crashes if the MySQL query does not return anything but only if it is combined with the PAM authentication. -- Allan Joergensen - http://nowhere.dk/ "I believe my plan has a fatal flaw." -- The Brain

1 1

[Dovecot] dovecot-stable: NIL from in envelope request
by Michael P. Cosby 16 Feb '05

16 Feb '05

Using the latest dovecot-stable (20050213) with pine, I get an empty "from" header in my e-mails. This doesn't happen with 1.0.59-test, nor did it happen with the first dovecot-stable (20050131). A partial connection log is below: 1.0-test59: IMAP DEBUG 15:23:32 2/13: 00000007 FETCH 1:41 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition Content-Language Content-Location resent-to resent-date resent-from resent-cc resent-subject List-Help List-Unsubscribe List-Subscribe List-Post List-Owner List-Archive Followup-To References)] INTERNALDATE RFC822.SIZE FLAGS) IMAP DEBUG 15:23:32 2/13: * 1 FETCH (ENVELOPE ("Wed, 03 Mar 2004 18:54:05 -0000" "[rowingdockmembers] Next Wed." (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) (("Charles Barksdale" NIL "cbarksdale" "austin.rr.com")) ((NIL NIL "rowingdockmembers" "yahoogroups.com")) NIL NIL NIL "<c259kd+rqe4(a)eGroups.com>") BODY[HEADER.FIELDS (NEWSGROUPS CONTENT-MD5 CONTENT-DISPOSITION CONTENT-LANGUAGE CONTENT-LOCATION RESENT-TO RESENT-DATE RESENT-FROM RESENT-CC RESENT-SUBJECT LIST-HELP LIST-UNSUBSCRIBE LIST-SUBSCRIBE LIST-POST LIST-OWNER LIST-ARCHIVE FOLLOWUP-TO REFERENCES)] {76} IMAP DEBUG 15:23:32 2/13: UID 1 INTERNALDATE "03-Mar-2004 13:56:55 -0500" RFC822.SIZE 2722 FLAGS (\Seen)) dovecot-stable 20050213: IMAP DEBUG 15:18:30 2/13: 00000007 FETCH 1:41 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Newsgroups Content-MD5 Content-Disposition Content-Language Content-Location resent-to resent-date resent-from resent-cc resent-subject List-Help List-Unsubscribe List-Subscribe List-Post List-Owner List-Archive Followup-To References)] INTERNALDATE RFC822.SIZE FLAGS) IMAP DEBUG 15:18:30 2/13: * 1 FETCH (ENVELOPE ("Wed, 03 Mar 2004 18:54:05 -0000" "[rowingdockmembers] Next Wed." NIL NIL NIL NIL NIL NIL NIL "<c259kd+rqe4(a)eGroups.com>") BODY[HEADER.FIELDS (NEWSGROUPS CONTENT-MD5 CONTENT-DISPOSITION CONTENT-LANGUAGE CONTENT-LOCATION RESENT-TO RESENT-DATE RESENT-FROM RESENT-CC RESENT-SUBJECT LIST-HELP LIST-UNSUBSCRIBE LIST-SUBSCRIBE LIST-POST LIST-OWNER LIST-ARCHIVE FOLLOWUP-TO REFERENCES)] {76} IMAP DEBUG 15:18:30 2/13: UID 1 INTERNALDATE "03-Mar-2004 13:56:55 -0500" RFC822.SIZE 2722 FLAGS (\Seen)) Any help would be appreciated..... Thanks - Michael

5 4

[Dovecot] Messages keep getting resent.
by poohba＠blkpoohba.dyndns.org 16 Feb '05

16 Feb '05

I have IMAP and POP running and when I log in thru pop from my blackberry which is the only way it pulls all the new emails. When I log into my computer and check email via PINE i guess something is refreshed because very soon there after if not immediately all the emails in the INBOX are sent/pulled from my blackberry again. Why is this happening?

2 1

[Dovecot] Speed up large maildirs
by Leen Besselink 15 Feb '05

15 Feb '05

Hi, I'm very fond of maildirs, they are simple, I like that. But I've never really understood the significance of maildir/new/. The only use I can see is that (for example in the case of dovecot), you'd move a message from new to cur and then update the index-file, that's it. So to make put it more direct, you'd know when and with what to update the index-file, based on where the file resides. I've never been bothered by them, until I found that that is the last hurdle for fast access to a large (and receiving a lot of mail) Maildir. I've been thinking long and hard about what to do to make them work even better. My idea at this point is the following, use maildir/new as little as possible, just use it for what it was intented and spread the time of updates. If someone would make a wrapper-program around the delivery-program (like qmail-local, vpopmaildeliver, procmail or local and virtual from postfix) and the delivery program would print to standard output the path+filename it saved a (or more) message(s) to, the wrapper would be able to send an update-message to a dovecot-daemon. That mean, updates are small, and opening a large maildir would be sped up. How does that sound ? I hope this is a helpfull suggestion. _____________________________________ New things are always on the horizon.

6 11

[Dovecot] Why am I getting more imap folders?
by poohba＠blkpoohba.dyndns.org 15 Feb '05

15 Feb '05

At one point I was just using what was under ~/mail now I have: ~/mail ~/mail/fedora ~/mail/trash ~/mail/mplayer ~/mail/yahoo ~/mail/Scott ~/mail/.imap/fedora ~/mail/.imap/fedora/.imap.index ~/mail/.imap/fedora/.imap.index.tree ~/mail/.imap/trash ~/mail/.imap/trash/.imap.index ~/mail/.imap/mplayer ~/mail/.imap/mplayer/.imap.index ~/mail/.imap/yahoo ~/mail/.imap/yahoo/.imap.index ~/mail/.imap/yahoo/.imap.index.data ~/mail/.imap/yahoo/.imap.index.tree ~/mail/.imap/Scott ~/mail/.imap/Scott/.imap.index ~/mail/.imap/INBOX ~/mail/.imap/INBOX/.imap.index ~/mail/.imap/old_subscriptions/.imap.index ~/mail/.imap/old_subscriptions/.imap.index.data ~/mail/.imap/ffmpeg ~/mail/.imap/ffmpeg/.imap.index ~/mail/.imap/apache ~/mail/.imap/apache/.imap.index ~/mail/.imap/dovecot ~/mail/.imap/dovecot/.imap.index ~/mail/ffmpeg ~/mail/apache ~/mail/dovecot These are not all the files but just the most recently touched files. Can I not just have imap view and use the ~/mail files? Is this normal? Can I have it set up to use the maildir files that are already there? It used to work that way but I guess that is with the other imap server that came with fc1.

3 3

[Dovecot] changing user mail folders
by Jason M. Wilde 15 Feb '05

15 Feb '05

I have a working dovecot server with user mail in Maildir:~/Maildir What is the proper way to change the location of user mail to /var/mail/username to take advantage of a large /var drive space? Would you recommend adding the creation of new user directories in /var/mail to my Redhat "adduser" script to get the permissions correct? Or via some other method? Also, any idea how to make Postfix deliver mail to the the new user directories? Thank you for any help and for a great product. Jason

1 0

[Dovecot] assertion failed in mail-transaction-log-view.c
by Alan Schmitt 15 Feb '05

15 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, After having moved to using Apple mail.app for offline imap reading (served by a dovecot 1.0-test59 server), I noticed the following in the logs: Feb 14 13:52:48 top dovecot: 3102(schmitta): file mail-transaction-log-view.c: line 86 (mail_transaction_log_view_set): assertion failed: (min_file_seq <= max_file_seq) Is this bad? Would upgrading to a newer version of dovecot help in this case? Thanks, Alan Schmitt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCEKDFNIAqM4hFUWgRAjfeAKCRpPafj/Pfhbi4wh1YFHnRxbPx3QCfSMqY S3nnORob3OXAfkDre1o7x5s= =iBoA -----END PGP SIGNATURE-----

2 1

[Dovecot] Need 2 additional folders like INBOX for JUNK and INFECTED mails
by Mirko Schulze 15 Feb '05

15 Feb '05

Hi there, i need for JUNK & INFECTED mail two folders like INBOX. The folders must be fixed in naming, permissions and so on. I've adjusted some commands in the ./src/imap folder. But it's work not really fine: Creating a folder works, but deleting too. *smile* Moving a "special-name-folder" (f.e. from Trash) to its correct place, Dovecot says, that the folder is currently there. subsribing / unsubscribing doesn't work, too. ... ... ... I think that this is a "standard" problem for much people, who don't want, that the users will delete files through the imap protocol. Are there any solutions? Thanx Mirko

1 0

[Dovecot] 0.99.14 released
by Timo Sirainen 14 Feb '05

14 Feb '05

One more change since -rc3 (the last one in list). v0.99.14 2005-02-11 Timo Sirainen <tss(a)iki.fi> - Message address fields are now parsed differently, fixing some issues with spaces. Affects only clients which use FETCH ENVELOPE command. - Message MIME parser was somewhat broken with missing MIME boundaries - mbox: Don't allow X-UID headers in mails to override the UIDs we would otherwise set. Too large values can break some clients and cause other trouble. - passwd-file userdb wasn't working - PAM crashed with 64bit systems - non-SSL inetd startup wasn't working - If UID FETCH notices and skips an expunged message, don't return a NO reply. It's not needed and only makes clients give error messages.

2 1

[Dovecot] Help, problems with permissions
by Simon Windsor 14 Feb '05

14 Feb '05

Hi I am replacing my current mail system, using Exim/Postgres/WU-IMAP to another host using Dovecot. Everything has gone well, until I have tried to access some test mails via POP. The error message I am getting is Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): lstat (/home/dovecot/users/orion-w-t.co.uk/simonw/cur) failed: Permission denied Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-02-14 03:03:57] The file permissions are drwx------ 2 dovecot dovecot 4096 Feb 13 23:24 cur drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 new drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 tmp The UID/GID I am using is 1001, and the orion-w-t.co.uk/simonw directories are owned by that uid/gid. Can anyone provide advice on what I have to do to get POP, and eventually IMAP working? Many thanks Simon -- Simon Windsor Eml: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07960 321599

3 4

Re: [Dovecot] Help, problems with permissions
by Simon Windsor 14 Feb '05

14 Feb '05

Hi Thank you for the reply. The documentation on the wiki/dovecot site clearly provides an example exim transport statements showing mail writes as dovecot/dovecot with permisions of 600. The mail system uses virtual users, and I have provided mail/group ids of 1001/1001. The current directory tree is /home - owned by root /home/dovecot - owned by root /home/dovecot/users - owned by root, 777 /home/dovecot/users/DOMAIN - owned by 1001:1001, 777 /home/dovecot/users/DOMAIN/USER - owned by 1001:1001, 777 /home/dovecot/users/DOMAIN/USER/cur - owned by dovecot:dovecot, 600 /home/dovecot/users/DOMAIN/USER/new - owned by dovecot:dovecot, 600 /home/dovecot/users/DOMAIN/USER/tmp - owned by dovecot:dovecot, 600 Can you confirm that all files should be owned by 1001/1001? What permissions should should exist on these directories/files? Thanks, once again Simon Amelia A Lewis (amyzing(a)talsever.com) wrote: > >It looks as though cur/new/tmp are owned by user dovecot, rather than >the user whose mail it is. In my (similar, prolly) setup, maildirs are >owned by their owners. Dovecot is executed as the user reading the >mail. > >Amy! >On Mon, 14 Feb 2005 02:19:09 +0000 >Simon Windsor <simon.windsor(a)cornfield.org.uk> wrote: > >> Hi >> >> I am replacing my current mail system, using Exim/Postgres/WU-IMAP to >> another host using Dovecot. >> >> Everything has gone well, until I have tried to access some test mails >> via POP. >> >> The error message I am getting is >> >> Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): lstat >> (/home/dovecot/users/orion-w-t.co.uk/simonw/cur) failed: Permission >> denied >> Feb 14 03:03:57 wpc1273 pop3(simonw(a)orion-w-t.co.uk): Couldn't open >> INBOX: Internal error occured. Refer to server log for more >> information. [2005-02-14 03:03:57] >> >> The file permissions are >> >> >> drwx------ 2 dovecot dovecot 4096 Feb 13 23:24 cur >> drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 new >> drwx------ 2 dovecot dovecot 4096 Feb 14 02:53 tmp >> >> The UID/GID I am using is 1001, and the orion-w-t.co.uk/simonw >> directories are owned by that uid/gid. >> >> Can anyone provide advice on what I have to do to get POP, and >> eventually IMAP working? >> >> Many thanks >> >> Simon >> >> >> >> -- >> Simon Windsor >> >> Eml: simon.windsor(a)cornfield.org.uk >> Tel: 01454 617689 >> Mob: 07960 321599 >> > > > -- The Last Song of Sirit Byar > -- Simon Windsor Eml: simon.windsor(a)cornfield.org.uk Tel: 01454 617689 Mob: 07960 321599

1 0

[Dovecot] Bug?
by Adam Pordzik 13 Feb '05

13 Feb '05

Hello, I noticed with different MUA (at least Thunberdird and OutlookExpress) endmost characters beeing sometimes cut-off my mails, so I assume dovecot is affected in this. Is this a known bug? Is it mayby already fixed? dovecot-0.99.10.6 on FreeBSD 5.2.1-RELEASE #1: Fri Mar 12 20:05:38 CET 2004 root@MONSTER.tektoform.lan:/usr/src/sys/i386/compile/SERVER A --

3 2

[Dovecot] Problems with dovecot using Maildir on JFS.
by Jacob Robert Wilkins 12 Feb '05

12 Feb '05

Howdy, I have dovecot installed on CentOS (rhel3 clone), and I'm using Dag's dovecot package. I have postfix setup to deliver to Maildir, in /home. The /home volume was formatted with JFS. In this setup, both Outlook and Thunderbird would not show any new mail unless they were completely shutdown and restarted. I have moved /home to an ext3 formatted and all is well. Anyone have any insight on this? Thanks, jrw

4 6

[Dovecot] can i get a list about the describtion of all sources of dovecot?
by bigbox＠mails.de 12 Feb '05

12 Feb '05

I want to control, which user, when and what modify in their mailbox done. which sourcecode must i modify? Please

2 1

[Dovecot] Trouble with Dovecot
by Paul A. Novojeeloff 11 Feb '05

11 Feb '05

Hello! I'm trying the Dovecot as IMAP server, so I have one problem: I can log in to server, but nothing appears in mailclient and following message appears in log: imap(user): Feb 08 20:36:34 Fatal: We couldn't drop root group privileges dovecot: Feb 08 20:36:34 Error: child 21356 (imap) returned error 89 What could be wrong? Thanks for your answer. WBR, Paul.

4 8

[Dovecot] PoP3 AutoDeletion
by Cheema, Ravi 10 Feb '05

10 Feb '05

Qpopper has a compile time option '--enable-auto-delete Automatically delete downloaded msgs' Is there anything similar in dovecot. I'm trying to migrate from qpopper to dovecot any help is appreciated.

4 3

Re: [Dovecot] Corrupted index file
by Tero Ripattila 10 Feb '05

10 Feb '05

Hello guys, --On 9. helmikuuta 2005 15:25 -0300 Edgardo Pezoa <epezoa(a)safp.cl> wrote: > We have almost same problem: both using Postfix, Dovecot and Procmail > in different OS and with different MUA. For me, the key is > Dovecot+Procmail. I I've seen this too on OpenBSD 3.6-current. I' running Postfix w/ Dovecot. My users uses Mulberry, Mutt, Pine, Thunderbird, Outlook, Outlook Express, The Bat! as their MUA. > The question is: someone have a real fix? I'd love to hear about this too :-) Thanks, Tero -- Tero Ripattila -- Tero Ripattila Leenankuja 2 G 67 FI-02230 Espoo, Finland Telephone: +358-45-638 0242 Fax: +358-45-689 0743 E-mail: tero(a)ripattila.com WWW: http://www.ripattila.com

2 2

[Dovecot] outstanding issues with 0.99.13
by sean finney 10 Feb '05

10 Feb '05

hi list, i'm in the process of testing dovecot before a hopeful switchover from uw-imap/qpopper to dovecot, primarily to get off of the uw-imap/mbox combo and moved to Maildir. i think we've worked out the logistics to avoid any service downtime, with only a short window of a few minutes per user for when we convert from mbox to maildir format. however, during testing a few issues have come up, some of which i've been able to work around, others which i haven't. for those that i have been able to work around, i'll include my solution so that fellow googlers may profit, and for those that i haven't i'd really appreciate your feedback. logistical problems: 1 - automagic detection and uw-imap inbox in ~/mbox. i'm not sure if this is a default characteristic or if it's specific to us, but our spool is in /var/mail/foo and inbox in ~/mbox. the automagic Maildir/mbox detection doesn't find the "mbox", and i can't tell it where it is because then it doesn't look for the Maildir. solution: i wrote a small patch to dovecot's autodetect code to help it find the location of our mailboxes. if anyone would like a copy of said patch i can send it off list. 2 - uw-imap's spool/inbox message moving. i read from the wiki that this isn't a feature currently being worked on. solution: deliver all mail to the same place. since we use procmail as our MDA, this isn't too hard of a problem. basically we redirect mail to the inbox and redeliver everything in the spool. 3 - supporting multi-homed services + ssl. for historical reasons we provide services from multiple hostnames (mail.foo, imap.foo, etc). with ssl, that means a different cert for each, otherwise some clients will break. solution: we're spawning off three seperate dovecot instances, each using a different config file. not the most graceful, but it works... application problems: 4 - dovecot imap + ms lookout 2002 + deleting messages. i'm not sure if this is an app or server side problem. basically, a user will delete a message, only to have it reappear in the mailbox a short time (few minutes) later. if i monitor the state of the mbox file, no changes are made to it until the user selects "empty trash", after which point they are expunged. looking at a protocol dump, i see the client setting the deleted flag on the message when they originally delete it. here's an excerpt: <snip> tg7i OK Idle completed. 6gzd UID STORE 30021 +FLAGS (\Deleted \Seen) * 51 FETCH (FLAGS (\Deleted \Seen \Recent) UID 30021) 6gzd OK Store completed. stpw IDLE <snip> i'm not too familiar with imap, but it looks like the server is caching the deletion request and then forgetting later forgetting about it? i have all the "client workarounds" enabled, fwiw. solution: ??? 5 - mac os x + eudora + deleting mail. a different problem alltogether. in eudora deleting a mail seems to immediately move it to the "trash" mailbox, so the above problem does not occur. what *does* happen is that if a user rapidly deletes messages one-by-one, an error message pops up about UID's not existing. i haven't gotten a full description of this problem, but here's an excerpt from what i think is the symptom: <snip> A00109 UID COPY 30002 Trash A00109 OK Copy completed. A00110 UID STORE 30002 +Flags.silent (\Deleted) A00110 OK Store completed. A00111 EXPUNGE * 31 EXPUNGE A00111 OK Expunge completed. <snip> and later: <snip> A00040 UID FETCH 30002 (UID BODYSTRUCTURE) A00040 NO Some of the requested messages no longer exist. A00041 UID FETCH 30002 RFC822.SIZE A00041 NO Some of the requested messages no longer exist. A00042 UID FETCH 30002 (BODY.PEEK[]) A00042 NO Some of the requested messages no longer exist. <snip> which i suppose is correct that it doesn't exist (since it was moved out of the inbox). however, eudora does not have this problem with uw-imap, and i'm wondering what might be causing it? solution: ??? okay, i think that's everything that i've ran into. we're still pushing ahead with this because we need to get the hell off of uw-imap/mbox, but i don't think we'll be able to stick with dovecot if these are unresolvable issues. in that case, we'll probably use dovecot with these minor nuisances while we transition, and then perhaps use courier in the long run. hopefully that won't have to be the case though :) if anyone has any experience specifically with "5" and "5", i'd really, really like to hear about it. in the meantime, i'll continue to test other things, and also see if the problem also persists when mail is stored in Maildir format. anyway, thanks for your time! sean

4 4

[Dovecot] oh, and status of 1.0?
by sean finney 09 Feb '05

09 Feb '05

sorry for splitting this off into a second message :) is there a roadmap/schedule for the release of 1.0? ever curious, sean

2 1

[Dovecot] Dovecot Maildir to read /var/spool/mail
by Ben Halicki 09 Feb '05

09 Feb '05

Hi all, Does anyone know how to configure dovecot to read /var/spool/mail as the inbox using maildir format? Thanks in advance, Ben Halicki

2 2

Re: [Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

On Wed, Feb 09, 2005 at 02:55:51PM -0500, Michael Baird wrote: > Frank, exactly the same thing happened to me. Last week I tried to > migrate over to dovecot, from courier-imap for all the reasons you > mentioned, I ran into the Corrupted index file issue and had to cut back > to courier-imap. I am using dovecot for maildir as it appears you are, > however I specified an outside directory for index files (/var/indexes). > I have a few thousand people using my webmail/imap system so this issue > quickly became a big issue after the cutover. > > Regards > Michale Baird It was probably my own fault. Timo Sirainen noticed Edgardo Pezoa was using MH style filenames. And I did the same thing. My main inbox configured in procmail was $HOME/Maildir/new and it should be $HOME/Maildir/ (notice the slash at the end). Now, new mails have filenames such as 1107960126.14681_2.hive:2, instead of msg.uC:2,S. I never had this problem with courier so I didn't thought it could be a configuration error. Thanks everyone for the help. Timo's mail: http://dovecot.org/list/dovecot/2005-February/006215.html -- make install, not war

1 0

[Dovecot] Corrupted index file w/Procmail in FC2
by Edgardo Pezoa 09 Feb '05

09 Feb '05

Hello: We have a Fedora Core 2 (FC2) server with Dovecot and Procmail. Versions are: dovecot-0.99.13-4.FC2 procmail-3.22-13 We use "maildir" below home directory like: /users/operaciones/epezoa/maildir, where "epezoa" is my account. If I receive an e-mail, is stored at "new" folder. When I try to get e-mail from server, message is transfered from "new" folder to "cur" folder, but I can't see my e-mail and Dovecot generates a "Corrupted index file" in log file: Feb 8 14:02:34 dlp1 pop3(epezoa): Corrupted index file /users/operaciones/epezoa/maildir/.INBOX/.imap.index: index.next_uid (14836) > uid_rec.uid (14825) But, If I receive another e-mail (at "new" folder) and I try to get messages, I get both. My clients are Mozilla (with "pop3") and Squirrel (from another server with "imaps"). Both have same behavior, so I think client is not involved in this problem. MTA is Postfix, but all accounts works well, except who use Procmail. I read about locking in Procmail and Dovecot and I think locking may produce this problem, but I can't find what's wrong. I upgraded dovecot from dovecot-0.99.10-5 to try fix this. Thanks in advance, -- Edgardo Pezoa

2 4

[Dovecot] 0.99.14-rc2
by Timo Sirainen 09 Feb '05

09 Feb '05

http://dovecot.org/rc/ I should have released 0.99.14 already, but I've been way too busy lately. Among other things I started working half-time at Movial (www.movial.fi) I had forgotten 8 hour work days at office could take so much time :) Anyway.. There has been a few changes since RC1 so I'll still make RC2 before the final. Changes since RC1: - passwd-file userdb wasn't working - PAM crashed with 64bit systems - non-SSL inetd startup wasn't working - upgraded setuid/setgid initialization code from 1.0-tests

1 0

[Dovecot] New user Q: dovecot-0.99-13 / UnixWare 7.1.0
by Steven Palm 09 Feb '05

09 Feb '05

Trying to get dovecot up and running. I managed to get everything compiled and linked correctly, but there seems to be some problem with either the auth process or communication between the main process and the auth process. When I try to login, I get: * OK dovecot ready. 1 login n9yty testing * OK Waiting for authentication process to respond.. And I keep getting the same message over and over until eventually it dies if I let it sit: * BYE Disconnected for inactivity. In the log, all I see is: dovecot: Feb 05 02:24:46 Info: Dovecot starting up imap-login: Feb 05 02:32:46 Info: Disconnected: Inactivity [127.0.0.1] I have this in my config, but yet that is all the logging I see: auth_userdb = passwd auth_passdb = shadow auth_verbose = yes auth_debug = yes I then tried to do ./configure with --enable-debug, but if I do that I get this in the log when trying to run dovecot: dovecot: Feb 05 02:08:01 Info: Dovecot starting up dovecot: Feb 05 02:08:03 Error: Auth process died too early - shutting down dovecot: Feb 05 02:08:03 Error: child 8441 (login) killed with signal 6 dovecot: Feb 05 02:08:03 Error: child 8440 (auth) killed with signal 6 (sometimes the (login) line is not send, but always (auth)) Any thoughts on where to next start tracking this down? I tried to use test62, but get this (haven't dug much further into this one since I'd like a stable release for this application): main.c: In function `listen_protocols': main.c:284: error: structure has no member named `_listen' main.c: At top level:

2 2

[Dovecot] possible bug in 1.0-test62
by Dominik 'Rathann' Mierzejewski 09 Feb '05

09 Feb '05

When connecting with mutt via IMAPS, I get "connection to server closed" and this appears in logs: dovecot: Feb 04 12:48:30 Error: IMAP(rathann): file mail-index-sync-ext.c: line 118: assertion failed: (size <= synch_size) The problem goes away after deleting the index from ~/Mail/.imap/INBOX. We're running 1.0-test62 on Solaris 9. -- Dominik 'Rathann' Mierzejewski <rathann*at*icm.edu.pl> Interdisciplinary Centre for Mathematical and Computational Modelling Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810

2 1

[Dovecot] File isn't in mbox format - Couldn't open INBOX
by Girish Patangay 09 Feb '05

09 Feb '05

I cannot reproduce this error everytime, but it seems to happen when Outlook tries to delete the first message (the first message in the file, message on top) in the /var/mail/user file. I tried looking through the mailing list but came up blank. Is this a known problem? I can fix this problem by editing the file manually and fixing the file. If I delete the first 2 lines (in the example below) and make sure the Inbox file starts at "From ..." it works fine again. Here is the log: ---------------------------------------------- Feb 2 09:23:45 angel pop3-login: Login: sathyan [127.0.0.1] Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): File isn't in mbox format: /var/mail/sathyan Feb 2 09:23:45 angel pop3(sathyan): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-02-02 09:23:45] ---------------------------------------------- The inbox file for this user looks like this: ---------------------------------------------- [root@angel mail]# head sathyan zenxoI6Jdi_xPyRoBhrhf-- >From caecelius(a)payaway.every1.net Wed Feb 2 07:03:36 2005 Return-Path: <caecelius(a)payaway.every1.net> ---------------------------------------------- -- ------------------------- Girish Patangay <girish(a)intoto.com> Intoto Inc <www.intoto.com> Phone: 408.844.0480x304 Fax: 408.844.0488 PG ID: 0x74D3A118

2 1

[Dovecot] assertion failed in imap-bodystructure.c
by Martin Preen 09 Feb '05

09 Feb '05

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird) and that seemed to cause this error. What does that mean ? Should I worry about ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet Freiburg, Institut fuer Informatik Georges-Koehler-Allee, Geb.52, Zi.00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 1

[Dovecot] TROUBLES WITH dovecot configuration
by Alexey S. Kuznetsov 09 Feb '05

09 Feb '05

Hello! I'm new in this list and new to dovecot, so I have some troubles with its configuration. I have an Linux OS installed and Postfix what supports virtual domains and places mail to: /var/spool/mail/vhosts/DOMAIN_NAME/ I've installed dovecot, configured it to use only pop3 proto. Configuration like this (most important lines from config) # cat /usr/local/dovecot/etc/dovecot.conf login_user = dovecot default_mail_env = mbox:/var/spool/mail/vhosts/%d/%n auth = default auth_mechanisms = plain auth_userdb = passwd-file /usr/local/dovecot/ps/pop.users auth_passdb = passwd-file /usr/local/dovecot/ps/pop.users auth_user = root cat /usr/local/dovecot/ps/pop.users testemail@mydomain.org:1a1dc91c907325c69271ddf0c944bc72[34]:1000:7266::/var/spool/mail/vhosts/mydomain.org/::: My system uid is 508, when I set it in pop.users file it works nice: accepts password, lists mail, everything. But when I want to create uniq. id for my domain: useradd -d /dev/null -s /bin/date -u 1000 mydomainorg telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. +OK dovecot ready. user testemail(a)mydomain.org +OK pass pass +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host. And in logs: # cat /var/log/dovecot.log Jan 28 22:11:02 Error: mkdir_parents(/var/spool/mail/vhosts/mydomain.org//mail/.imap/INBOX) failed: Permission denied pop3(testemail(a)mydomain.org): Jan 28 22:11:02 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-01-28 22:11:02] If I set uid 508 everything will be cool! I don't understand why it works like this? I logged in to my account and via sudo su - I became root user. Root has uid 0, and why it works with uid 508 I can't even imagine :( Please help me with this problem. Thanx! -- Sincerely, Alexey S. Kuznetsov AK2351-RIPE

2 1

[Dovecot] can't login in pop3 accounts
by Sebastian Alduncin Pisanty 09 Feb '05

09 Feb '05

hi there... i HAVE practically searched in ALL messages from 2004 year, and haven't any luck with this problem, so I'm inserting here "dovecot.conf" content: ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/usr/share/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap pop3 # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". imap_listen = * pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 0 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability) #disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. Note the extra space at the end of line. log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. login_dir = /var/run/dovecot-login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/libexec/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 16 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/libexec/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # maildir:/var/mail/%1u/%u/Maildir # mbox:~/mail/:INBOX=/var/mail/%u # mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. #client_workarounds = outlook-idle # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 30 # Like mailbox_check_interval, but used for IDLE command. mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. mbox_locks = fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location #imap_executable = /usr/libexec/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/libexec/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules =yes #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # You can have multiple processes; each time "auth = xx" is seen, a new # process definition is started. The point of multiple processes is to be # able to set stricter permissions to others. For example, plain/PAM # authentication requires roots, but if you also use digest-md5 authentication # for some users, you can authenticate them without any privileges in a # separate auth process. Just remember that only one auth process is asked # for the password, so you can't have different passwords with different # processes (unless they have different auth methods, and you're ok with # having different password for each method). # Authentication process name. auth = default # Space separated list of wanted authentication mechanisms: # plain digest-md5 anonymous # EBRAIN changed #auth_mechanisms = plain digest-md5 auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm to use if none was specified. #auth_default_realm = # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf auth_userdb = passwd # auth_userdb = pgsql /usr/local/etc/dovecot-pgsql.conf # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # auth_passdb = pgsql /usr/local/etc/dovecot-pgsql.conf auth_passdb = pam #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = no # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5" =================================================== OK sorry about pasting all .conf, but didn't know what to do... so here is the deal, I have configured IMAP to use in SquirrelMail, and it's working flawless, and before that i went putting up POP3 access, and in that time went flawless, but dunno what is going on that I can't login from neither Outlook 2003 or Outlook Express 6, when i turn ON Verbose, in "maillog" appears this message (i don't think trying to login from other prog would help, but right now starting to download Thunderbird): Jan 29 14:37:33 cddserver dovecot: Dovecot starting up Jan 29 15:15:41 cddserver dovecot: Killed with signal 15 any clue what could it BE??? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

I've recently switched from Courier-imap to dovecot and I'm impressed with it's speed and reliability. However, my index file gets regularly corrupted: Feb 8 21:23:16 hive imap(hart): Corrupted index file /home/hart/Maildir/.INBOX/.imap.index: index.next_uid (129) > uid_rec.uid (128) dovecot version: 0.99.13-3 Debian sid) I use dovecot in combination with mutt, procmail and postfix. If I rename the last received mail I can use my inbox folder again (until the next time the index gets corrupted). Debian bug# 294284 -- make install, not war

2 2

[Dovecot] Server going crazy!!!
by poohba＠blkpoohba.dyndns.org 09 Feb '05

09 Feb '05

I have dovecot-0.99.11-1FC3.4. I use Pine on the server and Outlook 2003 on remote computers to access IMAP and POP3 to access via my blackberry 7100t. It seems that after using IMAP and then going back to pine it somehow refreshes everything and all the messages are picked up on my blackberry once again as if the emails are new. So everything that is in my inbox is now pushed or grabbed by my blackberry as new messages when they are not and have been read already (at least most of them). Why is this happening? ## Dovecot 1.0 configuration file base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot-login login_chroot = yes login = imap login = pop3 default_mail_env = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root

2 1

[Dovecot] Multiple auth sections, stable branch - 7/2/05
by Andrew Hutchings 07 Feb '05

07 Feb '05

Hi, Great job with the dovecot 1.0 stable branch, much more stable than the test57 I was using. Only one slight oddity, I know multiple auth sections is not stable yet but I am finding that one auth section at random is being ignored at login time (acknowledges it at startup). The auth section that is ignored is the same each time, but different on each server I use it on and changes at random after modifying the dovecot.conf file. Used both my test57 (hacked to remove the auth command) conf file and a new one I created using today's stable branch conf file. I sorted a work around by duplicating the failing auth sectio with a different name in each server and it works great! :) If this is easy thing to fix, great, you are still our hero either way Timo, you have made our mail server -> cluster migrations much less painless. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] crash with test62
by Juergen Daubert 07 Feb '05

07 Feb '05

Hi, Got the following today with test62 and mbox: IMAP(juergen): Fixed index file /home/juergen/Mail/.imap/INBOX/dovecot.index: recent_messages_count 19 -> 0 imap-login: Login: juergen [192.168.0.1] file mail-index-sync-ext.c: line 118 (mail_index_sync_deinit_handlers): assertion failed: (size <= synch_size) child 31196 (imap) killed with signal 6 after that I had to delete dovecot.index to be able to select the folder. And another one: IMAP(juergen): Corrupted transaction log file /home/juergen/Mail/.imap/dovecot/dovecot.index.log: record size too small (type=0x0, size=0) imap-login: Login: juergen [192.168.0.1] IMAP(juergen): Transaction log file /home/juergen/Mail/.imap/dovecot/dovecot.index.log: marked corrupted Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

2 1

[Dovecot] Migrating from mbox to maildir: Message ordering?
by Ian R. Justman 06 Feb '05

06 Feb '05

Hi, all. I have been playing with the notion of migrating some of my folders to maildir because it's a lot easier to manage that way from a reader standpoint. The big question I have is how do I maintain message ordering in each folder? When I use a mail program to do the migration from mbox to maildir, selecting "order received ascending", it works nicely, but one very small problem: When I go to look at the newly-populated folder, everything is in reverse order. I've tried it with T'bird and I've tried it with Pine. Both yield the same results. I'm thinking the issue might be with Dovecot. Or is it a peculiarity with maildir? Or am I better off using other means to convert a mbox folder to maildir? I like maintaining the message delivery order so especially items like mailng list threads can (normally) flow right. I don't always trust the message's date field because it CAN be faked (and sometimes is by the sender, whether accidental or intentional). And while we're on the subject, since maildir's a file-per-message mailstore, what happens to ordering when you delete a message and a new message arrives? However, otherwise, everything else is working beautifully. I haven't gone into bashing the living hell out of it to make sure it REALLY works The testing was done with Dovecot 1.0test62, Thunderbird 1.0, and Pine 4.62. Both mbox and maildir folderstores are on the same machine and Dovecot's configured to use both with a maildir in the user's directory, oddly enough, called "maildir", for their maildir store. Thanks in advance for any help anyone can render. --Ian.

3 3

[Dovecot] pam_mkhomedir and dovecot
by Ben Halicki 03 Feb '05

03 Feb '05

Hi all, Just wondering if anyone has successfully managed to configure pam_mkhomedir and dovecot, so that users home directories are automatically created? As far as I can tell, the login process runs as a non-root user, which results in a permission denied error while trying to create the users home directory. I'm not sure if this error is specific to dovecot or pam though. Any thoughts would be greatly appreciated. Thanks, Ben Halicki Information Technology Officer Macquarie Textiles Group Ltd Phone: 02 6043 0235 Fax: 02 60411 321 E-mail ben.halicki(a)macquarietextiles.com.au

2 1

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir
by Nicolas Lopez 03 Feb '05

03 Feb '05

I hit a small snag using Dovecot-imapd smoothly in my environment with maildir and most of my accounts in LDAP. Since the accounts are created through a web interface on another server home directories on the mail server don't get created automatically. There's the handy pam module pam_mkhomedir.so to automagically create home directories, but unfortunatly Dovecot wasn't calling pam_open_session to run the session setup pam modules. I made a small patch to passdb-pam.c to call pam_open_session between pam_acct_mgmt and pam_get_item and now I my home dirs are automagically created and everyone is happy. So, I figured I'd share the little patch in case someone else finds it useful. My patch doesn't properly close the session which will probably iritate more advanced session modules that actually have something to clean up, oh well. Aside from manually having to create home directories Dovecot-imapd has been working really well for us for a number of months, I just finally got around to dealing with the home dir creation issue. - Nick Lopez nlopez(a)espri.arizona.edu

3 3

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir (fwd)
by Pasi Sjoholm 02 Feb '05

02 Feb '05

On Tue, 1 Feb 2005, it was written: > Nicolas Lopez wrote: > > maildir and most of my accounts in LDAP. Since the accounts are created > > through a web interface on another server home directories on the mail > > server don't get created automatically. There's the handy pam module > > pam_mkhomedir.so to automagically create home directories, but > > unfortunatly Dovecot wasn't calling pam_open_session to run the session > > setup pam modules. I made a small patch to passdb-pam.c to call > > pam_open_session between pam_acct_mgmt and pam_get_item and now I my > > home dirs are automagically created and everyone is happy. > > So, I figured I'd share the little patch in case someone else finds it > > useful. My patch doesn't properly close the session which will probably > > iritate more advanced session modules that actually have something to > > clean up, oh well. This patch closes the session.. but you will see many "opened session\n closed session"-lines on your log files. =) --cut-- --- src/auth/passdb-pam.c-org 2004-10-07 08:38:28.000000000 +0300 +++ src/auth/passdb-pam.c 2004-10-07 08:38:59.000000000 +0300 @@ -193,6 +193,18 @@ return status; } + if ((status = pam_open_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_open_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + + if ((status = pam_close_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_close_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + status = pam_get_item(pamh, PAM_USER, (linux_const void **)&item); if (status != PAM_SUCCESS) { *error = t_strdup_printf("pam_get_item(%s) failed: %s", --cut-- > I am running dovecot-0.99.13 on FC2 with pam_mkhomedir, and it has been > working fine. Not sure why you are having a problem. If I could just > figure out how to get Exim to do the same, I'd be happy :-) I think that Fedora has probably patched that version of dovecot which they are providing. -- Pasi Sjöholm

1 0

[Dovecot] test61 ./configure fails on OpenBSD 3.6
by Jamie Herre 02 Feb '05

02 Feb '05

Test version 61 ./configure is failing on my OpenBSD 3.6-stable system. The following corrects the problem. Would it be possible to test for gnu99 option before using it in subsequent tests? --- configure.in.orig Fri Jan 14 14:04:10 2005 +++ configure.in Fri Jan 14 16:44:22 2005 @@ -236,7 +236,7 @@ # say specifically that we want C99 features. # we can make use of GNU features as well, so don't use -std=c99. - CFLAGS="$CFLAGS -std=gnu99" + CFLAGS="$CFLAGS -std=gnu9x" fi dnl **

2 2

[Dovecot] dovecot-stable branch
by Timo Sirainen 01 Feb '05

01 Feb '05

To confuse Dovecot versioning even more, I've added "dovecot-stable" module into CVS. This is a version of Dovecot before the recent keyword changes but with several bugfixes backported to it. It's thought to be mostly stable. I intend to keep it updated with important bugfixes and with other simple bugfixes. Although I'm not sure if I'll make a large code base upgrade once keyword changes are stable. This is mostly meant for people who _really_ want to use 1.0-test codebase in production right now. Perhaps it's already more stable than 0.99.x, but upgrading should probably be made easier for v1.0. The dovecot-stable module itself is just a hack that will go away at some point. Once the main codebase is stable enough for v1.0 beta release, I'll make a stable branch instead in the main dovecot module (and probably with different RCS than CVS).

6 10

[Dovecot] vpopmail oddities
by Allen Parker 01 Feb '05

01 Feb '05

vpopmail + qmail + dovecot + thunderbird = huge headache ;-) alright, when attempting to connect via imaps to my .maildir based vpopmail install, $user@$domain is having some problems. /var/vpopmail/domains/$domain/$user is the location of the user folders with vpopmail and yet dovecot isn't exactly passing on the domain :-\ i'm not sure if this is a pebkac issue or if it's the root of something far more evil, but this is really bothering me after about 4 days. i've got dovecot set to auth against vpopmail and i'm running a dovecot authd. i know that i've given very little information, is there any way that someone can ping me back requesting the particular information they need to properly diagnose this? -- ________________________________________ To avoid being added to my spam filter: 1. Utilize list replies unless otherwise requested. 2. If you DO send me a personal email, use english. 3. HTML isn't cute. It belongs on the web, not in my inbox.

2 1

[Dovecot] mbox vs maildir
by poohba＠blkpoohba.dyndns.org 31 Jan '05

31 Jan '05

I am a little confused and maybe if I figure this out I will be able to get this to work. I am now able to get my pop3 working but not imap. My inbox is in /var/spool/mail/%u and my mail directory is /home/%u/mail and then all the 'folders' are there which are actually files. Is that maildir or mbox? Which do I have to use for dovecot? Or can I use whichever I choose. I would like to keep the setup I have and use IMAP but i am finding this very difficult. I find some places that say I have to convert what I have and other places that say I don't. Can someone please break it down for me.

3 6

[Dovecot] 1.0-test62
by Timo Sirainen 31 Jan '05

31 Jan '05

http://dovecot.org/test/ Nothing big, just random fixes. - Crashfixes in keyword code - -std=gnu99 wasn't working well in all systems, configure now checks for it - FreeBSD sendfile() calling was broken sometimes. No need to remove #define HAVE_FREEBSD_SENDFILE anymore. - FETCH BODY[] wasn't setting \Seen flag. - LDAP fixes (by Kazuo Moriwaka) - Don't crash if client disconnects while APPENDing or FETCHing - mbox: write dummy message if all mails were expunged - POP3: RETR wasn't setting \Seen flag. - Treat ::ffff:127.* addresses as secure - If maildir-shared exists in the Maildir root, copy it for each created mailbox. - inetd startup fix (by Magnus Holmgren) - passwd-file wasn't working as userdb (by Joseph Tam)

1 0

[Dovecot] How to run in debug format for SSL testing?
by Jeff A. Earickson 31 Jan '05

31 Jan '05

Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out on Solaris 9. BTW, if I compile with Sun's StudioOne version 8 compiler, I get a core dump of dovecot-auth into /var/run/dovecot. The gdb backtrace looks like: gdb dovecot-auth core GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.8"... (gdb complaints about lack of debug symbols from numerous libs snipped out) Core was generated by `dovecot-auth'. Program terminated with signal 10, Bus error. #0 0x0002b64c in pam_child_input () (gdb) backtrace #0 0x0002b64c in pam_child_input () #1 0x00036c68 in io_loop_handler_run () #2 0x00035e5c in io_loop_run () #3 0x00025940 in main () The code works when compiled with gcc 3.4.3. Jeff Earickson Colby College

2 3

[Dovecot] Corrupted mailboxes
by Vincent Jaussaud 31 Jan '05

31 Jan '05

Hello, We are currently facing some weird problems, and although it may not be directly related to dovecot, I hope some of you guys may have a clue on this. We used to have a POP/IMAP server running Fedora Core1, with dovecot 0.99.13 (DAG). Everything was working fine, until an hardware problem forced us to install a new server, on another machine. We installed a fresh new Fedora Core 3 box, running both sendmail 8.13.1, procmail 3.22 and dovecot 0.99.13. Now, we are seeing strange errors in our dovecot logfiles. It seems to happen randomely, but always on the same mailboxes. The following error is logged: pop3(username): Jan 27 17:26:46 Error: Error syncing mbox file /var/spool/mail/szameitatd: LF not found where expected pop3(username): Jan 27 17:26:46 Error: Error indexing mbox file /var/spool/mail/username: LF not found where expected pop3(username): Jan 27 17:26:46 Error: Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-01-27 17:26:46] People having that problem are able to login, but cannot retrieve new mails. Clients simply says no new mails are available. We tried to remove completely the mailbox file, waiting for procmail to create a new, but after a few minutes, the problem happens again. We cannot reproduce the bug with a particular mail; it seems the problem come from nowhere. Verbosing procmail didn't helped either. The only way to fix it when this happens, is to manually edit the file, and remove the first line feed at the very beginning of the mailbox file. I saw one post in the mailing list with the same problem, and we tried the "mail_extra_groups = mail" workaround, but that didn't help either. I actually think this has nothing to do with my problem :) We have around 500 mailboxes, and only a couple of them (3-5) do have the problem. Any idea how this can happen ? Any suggestions ? Thanks ! Vincent. -- Vincent Jaussaud Kelkoo.com Security Manager email: tatooin(a)kelkoo.com GPG key: 1024D/3BFE3FC7 2002-02-07 "Those who desire to give up freedom in order to gain security will not have, nor do they deserve, either one." -- President Thomas Jefferson. 1743-1826

2 3

[Dovecot] Execute Query after Logon ...
by wiki kaha 31 Jan '05

31 Jan '05

Hello list, is there a possibility to submit a query after a login. I use this feature in tpop3d to write a popb4smtp log into mysql. I would like to replace tpop3d with dovecot for pop3 and imap. Therefor I would need something similar. Thanks for answers. Regards Karl-Heinz __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail

4 6

[Dovecot] kqueue errors in maillog
by Chris Phillips 31 Jan '05

31 Jan '05

Hello Dovecot, Version: dovecot-1.0-test61 OS: FreeBSD 5.3-RELEASE i386 Client: Mozilla Thunderbird 1.0 (on WinXP, FreeBSD & Mac OS X) The maillog entries concerning me: - Jan 30 16:16:37 venus dovecot: imap-login: Login: user [10.6.8.3] Jan 30 16:16:37 venus dovecot: imap-login: couldn't remove filter with kqueue: Bad file descriptor Jan 30 16:16:37 venus dovecot: IMAP(user): couldn't remove filter with kqueue: No such file or directory I see these messages many times in the maillog, with the client(s) idle (no interaction from me). Please can anyone shed any light on something that I may have neglected to do on installation, or perhaps what might be happening/wrong? Regards, Chris Phillips. Scanned for viruses by MailDefender

2 1

[Dovecot] Re: Dovecot doesn't call pam_open_session, thus dodging
by Chris L. Franklin 30 Jan '05

30 Jan '05

Forgot to ask, can this patch be added into dovecot for the next update ? (just to make life a little easier for us rpm'ers) -- Chris L. Franklin -- ----- Original Message ----- From: "Chris L. Franklin" <cfranklin(a)nomadcf.com> To: <dovecot(a)dovecot.org> Sent: Sunday, January 30, 2005 1:49 PM Subject: RE: Dovecot doesn't call pam_open_session, thus dodging > This is great I've been wanting to get rid of my NFS mounts for some time and have just the user MailDirs be local to the web server. And this will help alot ! > > -- Chris L. Franklin -- > >> Message: 1 >> Date: Thu, 27 Jan 2005 16:08:28 -0700 >> From: Nicolas Lopez <nlopez(a)espri.arizona.edu> >> Subject: [Dovecot] Dovecot doesn't call pam_open_session, thus dodging >> pam_mkhomedir >> To: dovecot(a)dovecot.org >> Message-ID: <41F9746C.8080707(a)espri.arizona.edu> >> Content-Type: text/plain; charset="iso-8859-1" >> >> I hit a small snag using Dovecot-imapd smoothly in my environment >> with maildir and most of my accounts in LDAP. Since the accounts are >> created through a web interface on another server home directories on >> the mail server don't get created automatically. There's the handy pam >> module pam_mkhomedir.so to automagically create home directories, but >> unfortunatly Dovecot wasn't calling pam_open_session to run the session >> setup pam modules. I made a small patch to passdb-pam.c to call >> pam_open_session between pam_acct_mgmt and pam_get_item and now I my >> home dirs are automagically created and everyone is happy. >> >> So, I figured I'd share the little patch in case someone else finds it >> useful. My patch doesn't properly close the session which will probably >> iritate more advanced session modules that actually have something to >> clean up, oh well. >> >> Aside from manually having to create home directories Dovecot-imapd >> has been working really well for us for a number of months, I just >> finally got around to dealing with the home dir creation issue. >> >> - Nick Lopez >> nlopez(a)espri.arizona.edu >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: passdb-pam.c.diff >> Type: text/x-patch >> Size: 505 bytes >> Desc: not available >> Url : http://dovecot.org/pipermail/dovecot/attachments/20050127/ac7796ea/passdb-p… >

1 0

[Dovecot] RE: Dovecot doesn't call pam_open_session, thus dodging
by Chris L. Franklin 30 Jan '05

30 Jan '05

This is great I've been wanting to get rid of my NFS mounts for some time and have just the user MailDirs be local to the web server. And this will help alot ! -- Chris L. Franklin -- > Message: 1 > Date: Thu, 27 Jan 2005 16:08:28 -0700 > From: Nicolas Lopez <nlopez(a)espri.arizona.edu> > Subject: [Dovecot] Dovecot doesn't call pam_open_session, thus dodging > pam_mkhomedir > To: dovecot(a)dovecot.org > Message-ID: <41F9746C.8080707(a)espri.arizona.edu> > Content-Type: text/plain; charset="iso-8859-1" > > I hit a small snag using Dovecot-imapd smoothly in my environment > with maildir and most of my accounts in LDAP. Since the accounts are > created through a web interface on another server home directories on > the mail server don't get created automatically. There's the handy pam > module pam_mkhomedir.so to automagically create home directories, but > unfortunatly Dovecot wasn't calling pam_open_session to run the session > setup pam modules. I made a small patch to passdb-pam.c to call > pam_open_session between pam_acct_mgmt and pam_get_item and now I my > home dirs are automagically created and everyone is happy. > > So, I figured I'd share the little patch in case someone else finds it > useful. My patch doesn't properly close the session which will probably > iritate more advanced session modules that actually have something to > clean up, oh well. > > Aside from manually having to create home directories Dovecot-imapd > has been working really well for us for a number of months, I just > finally got around to dealing with the home dir creation issue. > > - Nick Lopez > nlopez(a)espri.arizona.edu > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: passdb-pam.c.diff > Type: text/x-patch > Size: 505 bytes > Desc: not available > Url : http://dovecot.org/pipermail/dovecot/attachments/20050127/ac7796ea/passdb-p…

1 0

[Dovecot] Problem with incorrect permissions with shared folders
by Dave Hatton 30 Jan '05

30 Jan '05

Hi, I'm seeing strange permissions when using an email client to create a new sub folder in a shared folder. This is dovecot-1.0test61 I have a directory /data/mail/shared owner=root group=shared permissions=2770 I have a file /data/mail/shared/dovecot-shared owner=root group-shared permissions=2660 User fred in in group shared (in /etc/group) My understanding is that now in my client I can create a folder called test and so I should have Folder /data/mail/shared/.test owner=fred group-shared permissions=2770 What I actually get is Folder /data/mail/shared/.test owner=fred group-shared permissions=2700 So dovecot doesn't appear to be honouring the permissions on dovecot-shared when creating folders. Also, when creating a folder in a shared folder should the create process automatically copy the dovecot-shared file down to the new folder to allow this to be shared as well? Thanks Daveh

2 3

[Dovecot] Problem using passwd-file authentication: does not read UID, GID
by Joseph Tam 30 Jan '05

30 Jan '05

There seems to be a problem when setting the default authentication method to passwd-file when they use the same file (which they frequently do): auth default { mechanisms = plain userdb = passwd-file /passwd passdb = passwd-file /passwd ... } The log files show dovecot: Jan 11 14:41:40 Info: Dovecot v1.0-test60 starting up dovecot: Jan 11 14:41:49 Info: auth(default): userdb(test,127.0.0.1): uid=0 gid=0 home= mail= dovecot: Jan 11 14:41:49 Error: Logins with UID 0 not permitted (user test) dovecot: Jan 11 14:41:49 Info: imap-login: Internal login failure: test [127.0.0.1] When userdb-passwd-file.c::passwd_file_init() is called, it compares the userdb passwd-file to the passdb passwd-file. If they are the same, it resets the time stamp to force a re-read of the password database during the next look-up. However, I believe it also needs to reset the userdb_pwf->userdb flag to TRUE or else it won't pick up the UID and GID and will use 0 instead: /* resync */ userdb_pwf->userdb = TRUE; /* Was FALSE in v1.0-test60 */ userdb_pwf->stamp = 0; Joseph Tam <tam(a)math.ubc.ca>

2 1

[Dovecot] STARTTLS and inetd
by Magnus Holmgren 30 Jan '05

30 Jan '05

Hi! When running dovecot from inetd (as per the instructions on http://wiki.dovecot.org/InetdInstall) imap-login and pop3-login thinks that TLS is enabled when in fact it isn't (we're connecting to port 110 and port 143, so the --ssl parameter isn't present). The reason for that is found in login-common/main.c:main(): > if (fd != -1) > (void)client_create(fd, &ip, TRUE); I added a flag which I set when ssl_proxy_new() is successfully called (see the following diff) and it seems to work fine. Is there any reason it shouldn't? What's the reason that the code is the way it is? -- Magnus Holmgren holmgren(a)lysator.liu.se P.S. Nice software! --- src/login-common/main.c 2003-11-08 16:15:42.000000000 +0100 +++ src/login-common/main.c.new 2005-01-15 17:49:53.000000000 +0100 @@ -220,7 +220,7 @@ { const char *name, *group_name; struct ip_addr ip; - int i, fd = -1, master_fd = -1; + int i, fd = -1, master_fd = -1, ssl = FALSE; is_inetd = getenv("DOVECOT_MASTER") == NULL; @@ -268,6 +268,7 @@ fd = ssl_proxy_new(fd, &ip); if (fd == -1) i_fatal("SSL initialization failed"); + ssl = TRUE; } else if (strncmp(argv[i], "--group=", 8) != 0) i_fatal("Unknown parameter: %s", argv[i]); } @@ -277,7 +278,7 @@ } if (fd != -1) - (void)client_create(fd, &ip, TRUE); + (void)client_create(fd, &ip, ssl); io_loop_run(ioloop); main_deinit();

2 1

[Dovecot] Dovecot shared folder woes
by Dave Hatton 30 Jan '05

30 Jan '05

Hi I'm new to Dovecot so please be gentle with me. I did a search through the list archives but couldn't quite work out my problem. I have Dovecot installed and running and I can connect to it from my email clients (Outlook and Evolution) ... so looking good so far. I would like to setup three types (groups?) of mail store 1. A per user - e.g. Fred, Harry, Betty. (For my purposes they all have Unix Accounts on the mail server) 2. A public store which can contain folders that may be read and written to by any user who is authenticated 3. A per group store (e.g. accounts, sales, marketing) that may be read and written to by any user who is authenticated and is in the specified group Firstly, should this be possible with Dovecot? I have tried the following dovecot.conf parameters which I thought should do the trick ... --------------------- cut ------------------------- ### this should give each user a mail store default_mail_env = maildir:/var/mail/%lu/%u/Maildir ### Create Public mail store namespace public { separator = / prefix = Public/ location = /var/mail/public inbox = no hidden = no } ### Create mail store for accounts namespace shared { separator = / prefix = Accounts/ location = /var/mail/accounts inbox = no hidden = no } ### Create mail store for sales namespace shared { separator = / prefix = Sales/ location = /var/mail/sales inbox = no hidden = no } --------------------- cut ------------------------- I then: 1. created the directories /var/mail/{public,accounts,sales} 2. chgrp each one to a group (public,accounts,sales respectively) 3. chmod 770 each one 4. created a dovecot-shared in each one - chgrp and chmod appropriately And then restarted the server Now my problem When I try to connect from a client it fails and the tcp/ip connection dies When I look in /var/log/mail I see and error 89 (which I understand is a generic error) and IMAP(fred): Failed to create storage for 'Public/' with data: /var/mail/public What and I doing wrong? TIA Daveh

3 6

[Dovecot] mutt's new mail error
by Frédéric Gobry 30 Jan '05

30 Jan '05

Hi, I use dovecot 0.99.13-3 (debian testing) in conjunction with mutt (1.5.6-20040907+2, also debian), and mutt keeps reporting new mails in my subscribed folders, even when none is available. I've seen a report from december 2003 which seems to correspond http://dovecot.org/pipermail/dovecot/2003-December/002741.html In this thread, it seems that if I don't use INDEX=MEMORY, I should not suffer from the problem. My config uses default_mail_env = maildir:~/Mail:INDEX=/var/indexes/%d/%n Do you have a hint regarding this problem ? Would a traffic dump be useful ? Thanks in advance, Frédéric -- Frédéric Gobry Infoscience DIT-KIS / EPFL Tel: +41216932288 http://people.epfl.ch/frederic.gobry

2 1

[Dovecot] Help with Outlook2003 hanging on receiving email with attachments
by John Suter 30 Jan '05

30 Jan '05

I have one user running Outlook 2003 that hangs up when receiving emails with attachments. He is connecting using POP3. It's almost as if something is timing out and closing the connection. The client is on a 1500/256 DSL connection and the server is on a 768/768 fractional T-1. I have other users that connect with Outlook/POP3 without any problems. I have done a fresh install of Windows/Outlook to make sure it's not a client machine problem. Any help or ideas are greatly appreciated.

2 1

[Dovecot] maildir and /var/spool/mail/$USER
by Rob Campbell 29 Jan '05

29 Jan '05

I was told to use dovecot because it was easier than cyrus. I just upgraded from fc1 to fc3. I am not sure what fc1 used but I think it was cyrus and it worked perfect out of the box no configurations to do. The new cyrus-imapd is not so simple so I got dovecot. I see examples saying to use mbox=~/mail:INBOX=/var/spool/mail/%u but when I try that I cannot map mail folders that reside under ~/mail. I have tried default_mail_env = maildir:~/mail:INBOX=/var/spool/mail/%u default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u which is the setup i have now. I get this error when trying to connect via evolution error while scanning folders in "IMAP server localhost" imap command failed. invalid mask. when I use default_mail_env = maildir:~/mail:INBOX=/var/spool/mail/%u the error i get is: This store does not support subscriptions or they are not enabled. I have an Inbox Junk and Trash folder under that account. When I set up outlook as pop3 it says it connects fine but it doesn't download any mail. When I try to subscribe to folders via Outlook it says that it cannot connect.

3 4

[Dovecot] mbox slowness in dovecot-1.0-test61
by Todd Burroughs 28 Jan '05

28 Jan '05

Hi, We're trying out Dovecot to see if it's a good replacement for UW-imapd. It seems to be very slow in opening an mbox file, even after it's been indexed. (I mean way slower than UW) Here's some info on the system: Dovecot-1.0-test61 SuSE 8.1, Linux kernel 2.4 Using NFS to access mail. I've tried turning off mmap, using dotlocking, using fcntl locking (lockd, etc. are running), mbox_dirty_syncs and mbox_very_dirty_syncs. Also tried putting the cache files on local disk. Compile options where basically default. I'm accessing it with pine, using several filters which tend to do SEARCH commands. Has anyone come across this? Maybe I'm missing something obvious??? Thanks, Todd Burroughs - Hostopia todd(a)hostopia.com

2 2

[Dovecot] Moving to Dovecot
by Matt Saunders 27 Jan '05

27 Jan '05

Hi there, I'm currently running IMAP with Courier and POP3 with Solid-POP3d. I'd like to migrate IMAP and POP3 to both use Dovecot. All this works fine in testing, except for the fact that I have two types of users for legacy reasons. One type of user has a Maildir-style inbox at ~/Maildir/ The other type has a mbox-style inbox at ~/Mailbox Is it possible to make Dovecot look for both? As far as I can see I'd need default_mail_env to accept multiple names, something like this: default_mail_env = maildir:~/Maildir/ mbox:~/Mailbox ...but it doesn't, so I'm stuck. :-( By default, Dovecot would work for me if I moved all my users' ~/Mailbox files to ~/mail/inbox but I really don't want to have to do that if at all possible as that'll break other custom stuff. Does anyone have any ideas? [ Apologies if this is a FAQ - I've had a good Google around and a look at the mail archives but can't find the info. ] TIA, Matt. -- Matt Saunders http://www.yoyo.org/matts/contacts/ "This is getting very silly. Too silly." - Professor Yaffle

3 2

[Dovecot] dovecot Maildir issue
by Tadghe Danu 26 Jan '05

26 Jan '05

I'm working on switching a domain from a Cyrus+postfix+procmail to Dovecot+postfix+procmail (using Maildir). It works great, except one small problem. I cannot figure out what the permissions for my Maildir directories should be. Can anyone point me to a doc or just a few pointers on what the permissions of the Maildirs should be? The only way I seem to be able to make this config work is to make the Maildirs world read+write. I can't exactly roll out a config like that :). I have postfix+procmail delivering to per user Maildirs under /var/mail. The permissions on /var/mail (pulled from the Wiki) are mail:/var/mail# ls -l /var/ |grep mail drwxrwxrwt 7 root mail 4096 Jan 25 22:37 mail The user Maildirs are set as: mail:/var/mail# ls -l /var/mail/ |grep tadghe drwxr-xrwt 2 tadghe tadghe 4096 Jan 25 22:36 tadghe When I try and access a mail box I get this in the logs an 25 22:35:34 mail imap(tadghe): opendir(/var/mail/tadghe/tmp) failed: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir() failed with file /var/mail/tadghe/new: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir() failed with file /var/mail/tadghe/new: Permission denied Jan 25 22:35:34 mail imap(tadghe): opendir(/var/mail/tadghe/tmp) failed: Permission denied Tadghe

2 1

RE: [Dovecot] disable_plaintext_auth, inetd, localhost, IPv6, and mapped addresses
by Villalovos, John L 26 Jan '05

26 Jan '05

dovecot-bounces(a)dovecot.org wrote: > Dovecot 0.99.13. > > I've noticed that the condition > > client->secured = ssl || > (IPADDR_IS_V4(ip) && strncmp(addr, "127.", 4) == 0) || > (IPADDR_IS_V6(ip) && strcmp(addr, "::1") == 0); > > (in (imap-login|pop3-login)/client.c) isn't enough, at least not when > running from inetd. The thing is that you will come across >>> ffff:127.0.0.1, which is secure, but not covered by the above. > > I thought I saw someting on this earlier, but in that case I > cant't find > it now. Yes I mentioned something about it in a message titled, "RE: [Dovecot] Plaintext Authentication from Localhost" On 19-Jan-2005. Seems to be a bug. At least it didn't work quite right for me. John

1 0

[Dovecot] imap://anonymous@dovecot.org/dovecot gets only 4 messages
by Sergey Ivanov 26 Jan '05

26 Jan '05

I have just trying to connect as user anonymous to the imap server at dovecot.org. And got only 4 messages in dovecot folder, one of them unread. Is it some problem at this server I have encountered? WBR, Sergey

1 1

[Dovecot] disable_plaintext_auth, inetd, localhost, IPv6, and mapped addresses
by Magnus Holmgren 25 Jan '05

25 Jan '05

Dovecot 0.99.13. I've noticed that the condition client->secured = ssl || (IPADDR_IS_V4(ip) && strncmp(addr, "127.", 4) == 0) || (IPADDR_IS_V6(ip) && strcmp(addr, "::1") == 0); (in (imap-login|pop3-login)/client.c) isn't enough, at least not when running from inetd. The thing is that you will come across ::ffff:127.0.0.1, which is secure, but not covered by the above. I thought I saw someting on this earlier, but in that case I cant't find it now. Cheers, Magnus Holmgren holmgren(a)lysator.liu.se

1 0

Re: [Dovecot] Outlook 2002 SP3 & Dovecot 0.99.13 Runs really really slowly.
by Md 25 Jan '05

25 Jan '05

Ooops, that would help. IMAP. Md Pop3 or Imap? On Tue, 2005-01-25 at 11:16 -0500, M.d. wrote: >> Hi, >> I'm seeing a problem that I'm hoping someone can help with. Neither Googling or searching >> the list archives have turned up anything useful. >> >> I'm running Dovecot0.99.13 on Fedora Core 3 and things work fine when using either >> Thunderbird 1.0 or Outlook Express as clients. Outlook (2002 SP3) on the other hand >> runs incredibly slowly. >> >> Any ideas, would be greatly appreciated. >> Thanks, >> >> Md

1 0

[Dovecot] Outlook 2002 SP3 & Dovecot 0.99.13 Runs really really slowly.
by M.d. 25 Jan '05

25 Jan '05

Hi, I'm seeing a problem that I'm hoping someone can help with. Neither Googling or searching the list archives have turned up anything useful. I'm running Dovecot0.99.13 on Fedora Core 3 and things work fine when using either Thunderbird 1.0 or Outlook Express as clients. Outlook (2002 SP3) on the other hand runs incredibly slowly. Any ideas, would be greatly appreciated. Thanks, Md

2 1

[Dovecot] Is it possible to access maildir w/ 2 clients at the same time?
by Erhard Guenther 24 Jan '05

24 Jan '05

Hi, I have dovecot with Maildir installed and running. No problems. I use kmail on both desktop and laptop with cachedimap configuration. kmail is configured to look for new mail every two minutes. Now my question: When both maschines are running and kmail is started then two clients access the same Maildir on the server at the same time. Is this possible or can this corrupt the Maildir directory. TIA Guenther

3 2

[Dovecot] Trouble getting TLS to work
by Remy Zandwijk 24 Jan '05

24 Jan '05

Hi. I've Dovecot running on Solaris 9. Logging in without SSL or TLS works. Logging in with SSL (port 993) works. Logging in with TLS does not work. Tried Eudora, Thunderbird and Outlook Express, but none of them could log in. Outlook returns an error message like: "PLAIN authentication failed. None of the authentication methods supported by your IMAP server are supported on this computer.". Since SSL is working, I think I can savely say the SSL parameters are OK. My config includes the lines: disable_plaintext_auth = no auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam What could cause this problem?? Regards, Remy

1 0

[Dovecot] raw logging
by Marco Herrn 23 Jan '05

23 Jan '05

Hi, I have a question about the raw logging feature. As I understand the documentation it is meant for traffic measuring. But it seems to be more targeted at developers. Is there a way for measuring the traffic for the end user? If not with raw loggin in another way? Regards Marco -- The minute a man is convinced that he is interesting, he isn't. -- Marco Herrn _ ___ o ' (_)< _ _ _>(__'> o 0 (_X % >(_`> O o _; _;'7^'_ \;\ % (GnuPG/PGP-encrypted mail preferred) _;\ _.\ _.';;) ;,;_/; Key ID: 0x94620736 _ _'./_$'))_; );/$}/`fsc

2 1

[Dovecot] Experimental FreeBSD ports / packages for test61
by Dominic Marks 23 Jan '05

23 Jan '05

Hello, If anyone would like it I have provided a Dovecot 1.0 test61 port and package for FreeBSD 5.3 here. I made them for my own experimentation but thought they might be interesting to others I suppose. http://www.helenmarks.co.uk/~dom/dovecot/ These deviate from the stock test61 because I've updated and added a patch I wrote a long time ago for ioloop kqueue/kevent support in Dovecot. I have no configure skill at all so you get it even if you don't choose it in the options dialogue. It seems to work still, I tested it very lightly, but I don't use day to day, so YMMV. To use the shar file: gzip -d <path/to/dovecot.shar.gz> shar <path/to/dovecot.shar> cd dovecot make install To use the package: pkg_add -r http://www.helenmarks.co.uk/~dom/dovecot/dovecot-1.0-test61.tbz Cheers, -- Dominic

2 1

[Dovecot] Disallow creation of (sub) folders
by Remy Zandwijk 23 Jan '05

23 Jan '05

Hi. Is there a way to prevent users from creating new mailboxes? In our setup, we've several standard mailboxes (maildir format). Users should use these and only these. I allready tried to chown the base directory, e.g. /var/mailstore/r/remy/, to root, and delivery still works then, but procmail chown's this back to the users' name. I have a workaround by using symlinks, but I think this is a lame solution. Another question: when is Dovecot 1.0 supposed to be released for production purposes? Regards, Remy Zandwijk

2 1

[Dovecot] Strange behaviour with multiple auth channels
by Søren P. Skou 23 Jan '05

23 Jan '05

Hey all Just upgraded to Test-61 and at first everything looked like it worked without a hitch, I could log in and check mail (yay! ;-) ). Since I could log in, I never suspected anything would be amiss. Later one of my users told me he could no longer log in, regardless what he tried. Password error I thought and told him to go change his password, but then he explained he had not changed anything, and that his pop3 client just started complaining. Ok, time to go looking - I compared the dovecot.conf to the example from the tarball, nothing seemed as if it had changed. Then I started fiddling around to see if I could get any pattern. At that point I had two auth channels: auth default { mechanisms = plain userdb = sql /usr/local/etc/dovecot/sql.conf passdb = sql /usr/local/etc/dovecot/sql.conf user = mail } auth localuser { mechanisms = plain userdb = passwd home=/home/%u/Mail passdb = passwd home=/home/%u/Mail } Strangely enough I could see it connecting to the SQL database, I would have expected to see at least some queries when it checked for the user. But no. So I changed the configuration to: auth default { mechanisms = plain userdb = passwd home=/home/%u/Mail passdb = passwd home=/home/%u/Mail } auth virtualuser { mechanisms = plain userdb = sql /usr/local/etc/dovecot/sql.conf passdb = sql /usr/local/etc/dovecot/sql.conf user = mail } Lo and behold, my virtual users could log in - but now localusers could no longer. I've since then tried changing the auth default to auth localuser, but little does it do - I'm sort of out of my bounds here, everything works, but only if it is the second auth. The first channel seems to be ignored. So I tried adding more channels seeing what would happen. My current configuration looks like this: auth default { mechanisms = plain userdb = sql /usr/local/etc/dovecot/sql.conf passdb = sql /usr/local/etc/dovecot/sql.conf user = mail } auth localuser { mechanisms = plain userdb = passwd home=/home/%u/Mail passdb = passwd home=/home/%u/Mail } auth virtualuser { mechanisms = plain userdb = sql /usr/local/etc/dovecot/sql.conf passdb = sql /usr/local/etc/dovecot/sql.conf user = mail } As I suspected it grabs hold of localuser and uses that one. Any suggestions or "Well d'uh! you're missing...." would be welcome ;-) Friendly greetings S. P. Skou -- GPG Key: 8E58ACB3

2 1

[Dovecot] Evolution Slowness Fix
by Michael David Joy 22 Jan '05

22 Jan '05

Well, I seem to have tracked down what's going on with Evolution and Dovecot. It seems that Evolution has defaulted to checked for spam server side using Spamd on Fedora Core 3 without downloading the mail. It seems that spamd is the culprit in all this as it's trying to analyze pop3 mail without simply downloading all the new mail. I turned off the spam checking option in evolution and the crawling (read 5-10 min) email downloads stopped. I guess I should have noticed that this happened when I upgraded from Fedora Core 2 to 3, but we upgraded dovecot around the same time. While it still shouldn't be taking 10 min to download email (1 min a mail), at least I know what's going on now. Michael

4 3

[Dovecot] Kerberos/GSSAPI Auth Mechanism?
by John Waller 20 Jan '05

20 Jan '05

I have been reading that there may be a patch floating around to enable krb5 auth in dovecot <1.0, namely 0.99.10.8 (openbsd port). It could be I have something misconfigured, for openbsd supports kerberos and most programs which use the operating system's auth features use kerberos transparently through login(1). If there is a patch, I would be very interested in testing it. -- John Waller ganreshnu(a)gmail.com

1 1

[Dovecot] problems deleting folders
by Danny Sung 20 Jan '05

20 Jan '05

I've been having this problem for quite some time now of not being able to remove folders. I'm using: Fedora Core 2 dovecot-0.99.10.4-4 And dovecot is setup as using imaps (w/ SSL) and mbox files (instead of maildir). I've done a small amount of tracing to see what the problem is, and it looks like what happens is when all messages in a folder is removed, there's still a 0-byte file lying around. And the "delete" command issued from mail clients (I've used both Thunderbird and MS Outlook) end up trying to throw the file into Trash instead of somehow sending a delete command. This then results in an error. Maybe this is normal IMAP behavior, I don't know. But that's what looks like is happening. If anyone knows of a good solution to this, I would really appreciate it. I'd rather avoid using maildir but if anyone knows whether this will definitely solve the problem, then I'll make the switch. Thanks

5 6

RE: [Dovecot] Plaintext Authentication from Localhost
by Villalovos, John L 19 Jan '05

19 Jan '05

dovecot-bounces(a)dovecot.org wrote: > I noticed that... > > # Disable LOGIN command and all other plaintext authentications unless > # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and > # IPv6 ::1 addresses are considered secure, this setting has > no effect if > # you connect from those addresses. > #disable_plaintext_auth = yes > > ...was added to the latest release. Thanks Timo! This takes the > localhost-SSL burden off. :) I just tried this with the updated RPM for Fedora Core 2. With: imap_listen = [::] disable_plaintext_auth = yes IMAP did NOT work from the local host. Changing it to: imap_listen = 127.0.0.1 disable_plaintext_auth = yes Made it work for me. Not sure if this is a known issue or not. John

1 0

[Dovecot] configure problem with MySQL 4
by Laurent Papier 19 Jan '05

19 Jan '05

Hi, the configure mysql detection doesn't work with MySQL 4.0.x from MySQL AB. Detail information: dovecot 0.99.13, MySQL-devel-4.0.21-0 from MySQL AB. ./configure --with-mysql ... checking for mysql_init in -lmysqlclient... no checking for mysql_init in -lmysqlclient... (cached) no This version of MySQL need to be linked with '-lz'. The configure script check for mysql both with and without '-lz' but the test result is cached ... so the test with -lz failed. The included patch helps me compiling dovecot (only check mysql with -lz). I know that this workaround is not a general solution. Full configure output and config.log available on demand. Execpting this problem, dovecot works fine for us (RedHat, MySQL auth, maildir). -- Laurent Papier - 03 88 75 80 50 Admin. systeme - Sdv Plurimedia - <http://www.sdv.fr/>

1 0

[Dovecot] Re: dovecot Digest, Vol 21, Issue 24: vacation messages
by Ted Knab 19 Jan '05

19 Jan '05

Normally, the vacation message works with the default mail server (MTA). In my case, I use the vacation program. Postfix delivers to the local mail user and if they have a .forward with the vacation info on it gets called. For a truly virtual setup that does not require unique uids on the filesystem there is gnarwl. Gnarwl is a program written in C that does vacation messages for virtual users. It works with Postfix, which is simplier that sendmail. :) >------------------------------ > >Message: 2 >Date: Thu, 13 Jan 2005 23:13:48 -0700 >From: "Del Stoliker" <dstoliker(a)alphagraphics.com> >Subject: [Dovecot] Virtual users vacation notices and forwards >To: <dovecot(a)dovecot.org> >Message-ID: <200501140613.j0E6DfZ9012233(a)smtp2.alphagraphics.com> >Content-Type: text/plain; charset="us-ascii" > >I'm in the process of moving from UW-IMAP to dovecot. I'm exploring the idea >of using virtual users with dovecot and storing all user information in >LDAP. While bouncing this idea off of a coworker, he asked me how we could >handle vacation notices and forwards. Currently, we're using a procmail >recipe to generate the vacation notice, and the sendmail .forward file for >forwards (although most of our forwarding takes place elsewhere so the >.forward file is rarely used). These are, of course, dependant on the user >having an account on the mail server. How are those of you using virtual >users supporting this functionality? > >Thanks! > > > >

2 1

[Dovecot] istream-limit.c - assertion failed
by Mail Admin 19 Jan '05

19 Jan '05

Yes, that seems to eliminate the error on our server. It has been 3 days without seeing it. Thanks! Derek ------------------> I think this is the same problem I was having, try this.. After running configure and before doing a make, edit config.h: /* Define if you have FreeBSD-compatible sendfile() */ /* #define HAVE_FREEBSD_SENDFILE */ ^^ ^^

1 0

[Dovecot] 0.99.14-rc1
by Timo Sirainen 19 Jan '05

19 Jan '05

http://dovecot.org/rc/ Two backports from 1.0-tests and pretty important fix for mbox users if you're not already filtering X-UID header somewhere. For 1.0-tests you can fix it for now by applying patches http://dovecot.org/list/dovecot-cvs/2005-January/004046.html and http://dovecot.org/list/dovecot-cvs/2005-January/004047.html - Message address fields are now parsed differently, fixing some issues with spaces. Affects only clients which use FETCH ENVELOPE command. - Message MIME parser was somewhat broken with missing MIME boundaries - mbox: Don't allow X-UID headers in mails to override the UIDs we would otherwise set. Too large values can break clients and possibly Dovecot itself.

1 1

[Dovecot] Announcement: New Fedora releases
by Kenneth Porter 19 Jan '05

19 Jan '05

For FC2 and FC3. Users of MySQL and postgres should take note as the default build options have changed to remove these. The boot order has also changed to start dovecot after named, but this only takes effect if you run chkconfig to disable and re-enable the service and recreate the symlinks. More details in the RH announcements: <https://www.redhat.com/archives/fedora-announce-list/2005-January/msg00057.…> <https://www.redhat.com/archives/fedora-announce-list/2005-January/msg00058.…>

1 0

[Dovecot] test61 error
by "Branko F. Gračnar" 18 Jan '05

18 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dovecot: Jan 18 10:48:39 Error: IMAP(bfg(a)noviforum.si): file mail-transaction-log-view.c: line 138 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq ~ || min_file_offset <= max_file_offset) dovecot: Jan 18 10:48:39 Error: child 18837 (imap) killed with signal 6 dovecot: Jan 18 10:48:52 Info: imap-login: Login: gregord(a)noviforum.si [127.0.0.1] dovecot: Jan 18 10:48:58 Info: imap-login: Login: bfg(a)noviforum.si [192.168.2.14] dovecot: Jan 18 10:48:59 Warning: IMAP(bfg(a)noviforum.si): Growing pool 'maildir_uidlist_sync' with: 65536 dovecot: Jan 18 10:48:59 Warning: IMAP(bfg(a)noviforum.si): Growing pool 'maildir_uidlist_sync' with: 131072 dovecot: Jan 18 10:48:59 Warning: IMAP(bfg(a)noviforum.si): Growing pool 'maildir_uidlist_sync' with: 262144 dovecot: Jan 18 10:48:59 Warning: IMAP(bfg(a)noviforum.si): Growing pool 'maildir_uidlist_sync' with: 524288 dovecot: Jan 18 10:48:59 Warning: IMAP(bfg(a)noviforum.si): Growing pool 'maildir_uidlist_sync' with: 1048576 dovecot: Jan 18 10:48:59 Error: IMAP(bfg(a)noviforum.si): Corrupted transaction log file /export/mail/noviforum.si/bfg/.Mailing liste.Postfix Users/dovecot.index.log: record size to o small (type=0x0, size=0) linux 2.6, slackware 10, xfs filesystem. Brane -----BEGIN PGP SIGNATURE----- iD8DBQFB7NxlN7LHXgqRB4IRAqEAAJ9g0mJS10crV83rWKnjbmVBYeu40gCgkV4o 3Eh9ZOhjPWbOVfAiGDTAhn0= =R2t6 -----END PGP SIGNATURE-----

1 0

[Dovecot] test61 + kmail problem
by "Branko F. Gračnar" 17 Jan '05

17 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello :) I'm using dovecot 1.0-test61 and it works ok with most MUAs except with KMail (1.7.1 KDE 3.3.1) Kmail downloads message headers from folder (i'm using IMAP), but displays that there is only one email message in each folder... Well, i have thousands of messages in each folder. Everything works okay with Thunderbird 1.0. Ideas? Best regards, Brane -----BEGIN PGP SIGNATURE----- iD8DBQFB68SWN7LHXgqRB4IRAiGyAJsHxm/Zw/rnTbWmUTRd/ZsbnSUUMwCdGQDa m2q9y8TySu99QMq/sfWwkDE= =MSa4 -----END PGP SIGNATURE-----

1 0

[Dovecot] Dovecot + Xmail Setup Howto
by Chris L. Franklin 17 Jan '05

17 Jan '05

OK I finally found time to write this. (this is for dovecot 99.X and Xmail 1.X >= 1.17) (in dovecot 1.0 it'll able to auth against Xmail via a auth script. aka You'll only need to have 1 user account databases, XMAIL's YAY !!!) Steps: 1. Install Dovecot. (rpm or Source) >From Source : http://wiki.dovecot.org/CompilingSource >From RPM : http://wiki.dovecot.org/PrebuiltBinaries 2. Edit config (my's listed below) CODE base_dir = /var/run/dovecot/ imap_listen = * pop3_listen = * info_log_path = /var/log/dovecot login_dir = /var/run/dovecot/login login = imap login_executable = /usr/libexec/dovecot/imap-login login = pop3 pop3_executable = /usr/libexec/dovecot/pop3 verbose_ssl = no default_mail_env = /var/MailRoot/domains/%d/%n/Maildir mail_cache_fields = Envelope MessagePart client_workarounds = outlook-idle mailbox_check_interval = 5 mailbox_idle_check_interval = 30 maildir_stat_dirs = no maildir_copy_with_hardlinks = no maildir_check_content_changes = yes auth_mechanisms = plain auth_userdb = static uid=97 gid=97 home=/var/MailRoot/domains/%d/%n/Maildir auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_passdb = passwd-file /var/MailRoot/dovecotusers.tab 3. Isnatll Xmail >From Source : http://www.xmailserver.org/Readme.html#build >From RPM : (rpm -i xmail-X.rpm) 4. Configure XMail, edit server.tab Server.tab Config: http://www.xmailserver.org/Readme.html#server_tab_variables Heres Mine (with in all xmail files there are no SPACES only TABS !!!) CODE "RootDomain" "nomadcf.com" "SmtpServerDomain" "nomadcf.com" "POP3Domain" "nomadcf.com" "HeloDomain" "nomadcf.com" "PostMaster" "postmaster(a)nomadcf.com" "ErrorsAdmin" "postmaster(a)nomadcf.com" "SMTP-MaxErrors" "0" "NoSenderBounce" "1" "RemoveSpoolErrors" "1" "NotifySendLogToSender" "1" "ReceivedHdrType" "1" "SmtpMsgIPBanSpammers" "Denied due to you being a F'in SPAMMER !!!!!" "SmtpMsgIPBanSpamAddress" "550 Denied due inclusion of your email address in our spam lists" "SmtpMsgIPBanMaps" "550 Denied due inclusion of your IP in the following map" "EnableAuthSMTP-POP3" "0" "AllowNullSender" "1" "AllowSmtpVRFY" "1" "AllowSmtpETRN" "1" "CustMapsList" "list.dsbl.org.:1,blackholes.mail-abuse.org.:1,dialups.mail-abuse.org.:0" "SMTP-RDNSCheck" "1" "CheckMailerDomain" "1" "DefaultSmtpPerms" "MRVZ" 4.5 Setup Admin Account for Xmail moreinfo : http://www.xmailserver.org/Readme.html#ctrlaccounts_tab CODE (Replace BOB with you admin password, Replace ROOT with your Admin userame) cd /var/MailRoot/bin ./XMCrypt BOB | awk '{print "ROOT\t"$1"\n"}' > ../ctrlaccounts.tab 5. Setup your XMail Domains + Users It's easy'st with a interface. Heres a list of some Windows : http://www.alouria.com/ Web : http://dev.waaf.net/xmail/ Web : http://www.akxak.de/xpai/ Web : https://sourceforge.net/projects/phpxmail 6. Give Dovecot permission to the domains dir under MailRoot I used acls to do this so that Xmail can still run as root and Dovecot could still run as a non-root user. (if you rather not do this your other option is tp run xmail as the same user a dovecot See non-Acls below) CODE setfact -R -m d:u:dovecot:rwx,d:g:dovecot:rwx;d:o:---,d:m:rwx /var/MailRoot/domains setfacl -R -m u:dovecot:rwx,g:dovecot:rwx;o:---,m:rwx /var/MailRoot/domains 7. Set Xmail to listen on another port then 110 for pop3. Add "-Pp 20110 " to xmail startup options. 8. Setup User Accounts. As of 99.X of dovecot it doesn't support using a external script to check user acount info (user/password). So it needs a place to have it's own useraccount storage place. For more ways dovecot can store user info see : http://wiki.dovecot.org/Authentication I use " passwd-file /var/MailRoot/dovecotusers.tab" and create it from a modified xmail2smapost script called xmail2dovecot. (See xmail2dovecot below) 9. Restart Xmail 10. Startup Dovecot Non-Acls: To allow Xmail to so it's thing + Allow dovecot Access to XMails MailRoot. You'll need to run Xmail as the user Dovecot runs at. I found after some trial and error that is pretty easy. What you'll need. 1. Iptables 2. su Setup 1. Disable Xmail from starting at boot. 2. Stop Xmail 3. edit the user dovecot and chnage there shell to /bin/bash 4. Create a IPtables rule to route port 25 to 20025 Example: CODE iptables -t nat -A PREROUTING -p tcp --dport 25 -j REDIRECT --to-port 20025 5. Change permissions in MailRoot from root.root to dovecot.dovecot CODE chown -R dovecot.dovecot * 6. Startup Xmail as so : CODE su - dovecot -c "/var/MailRoot/bin/XMail -Mr 24 -Pl -Ph -Sl -Ql -Yi 30 -Yl -Fl -Cl -Ll -PX 0 -Sp 20025 -Pp 20110 -Fp 20079 -Ms /var/MailRoot" XMail2Dovecot Script: This a script that was Org. used with smartpost. And was called xmail2smartpost.php But I changed it to output All the user account info into a simple passwd/Shadow. (user@domain:MD5-password) Download From : http://xmail.nomadcf.com/info.php?program=xmail2dovecot After Downloading it , extract it to the MailRoot/bin/ and then edit it. And lastly Run it as like so : CODE cd /var/MailRoot/bin/ ./xmail2dovecot.php > ../dovecotusers.tab -- Chris L. Franklin --

2 1

[Dovecot] Squirrelmail - messages not marked as read
by Kim Culhan 16 Jan '05

16 Jan '05

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed If I change to test-61, when starting Squirrelmail for the first time the same will logged: log dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed After this initial version switch, it will not log any errors. Each time switching back to test-59 will cause the 'read' state to again work correctly (and a one-time logging as above.) Please let me know if there is anything I can do to help debug this. regards -kim -- w8hdkim(a)yahoo.com __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

4 4

[Dovecot] Proposed dovecot update changes in Fedora
by Kenneth Porter 16 Jan '05

16 Jan '05

FYI, forwarded from the Fedora development list: ------------ Forwarded Message ------------ Date: Saturday, January 15, 2005 7:16 PM -1000 From: Warren Togami <wtogami(a)redhat.com> To: John Dennis <jdennis(a)redhat.com> Cc: Development discussions related to Fedora Core <fedora-devel-list(a)redhat.com> Subject: Proposed dovecot update changes John, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143707 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145214 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145241 Any objections to my proposed changes? I can implement all of this and supply patches for your review, or apply it myself to CVS if you wish. I summarize each problem and my proposed solution below. 1. Unnecessary dependency on mysql/postgresql ============================================= Prereq: postgresql Prereq: mysql These lines are wrong. The package is fine without it, because RPM auto-dep pulls in the client library of mysql and postgresql rather than a larger unnecessary chunk of those databases. These dependencies are resolved properly by yum and handled automatically. Solution: Just remove those lines. 2. dovecot.conf should default to fcntl locking =============================================== https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145214#c7 Our default dovecot.conf changed from fcntl to dotlock sometime after the release of FC2. That is one of the reasons why we see this above bug. This problem must now be attacked on two fronts: 1) Our default dovecot.conf must be changed to use fcntl by default again. If someone uses a broken NFS where fcntl doesn't work, then it is up them to edit their configuration to use dotlocks. If users have not modified dovecot.conf, then upgrading to the new package will set fcntl default. 2) For exisiting users who have modified dovecot.conf, it would be dangerous to force a change to fcntl during %post. Then "mail_extra_groups = mail" is the correct line to add durin 3. FC2 should not link to mysql/postgresql (???) ================================================ https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145241#c1 FC2 dovecot originally did not link to mysql and postgresql, so arguably we should not add those dependencies in an update. Unfortunately our current FC2 update is linked in this way, so we would be breaking existing users if they did begin using this functionality in FC2. I am guessing that the likelihood of this is very low and we should go ahead. (However we could just as easily leave it as is, then it would only be a minor annoyance rather than a real problem.) FC3 dovecot did link to mysql/postgresql libs, so we must not change that or split into sub-packages because then an update would break existing users. FC4 we have the option of splitting mysql/postgresql into sub-packages, which is probably the correct thing to do based on the php precedent. Thoughts? Warren Togami wtogami(a)redhat.com -- fedora-devel-list mailing list fedora-devel-list(a)redhat.com http://www.redhat.com/mailman/listinfo/fedora-devel-list ---------- End Forwarded Message ----------

1 0

Re: [Dovecot] istream-limit.c - assertion failed
by Kim Culhan 15 Jan '05

15 Jan '05

On Fri, January 14, 2005 4:44 pm, Mail Admin said: > dovecot: Jan 14 12:25:49 Error: IMAP(xxxuser): file istream-limit.c: > line 85 (_seek): assertion failed: (v_offset <= lstream->v_size) I think this is the same problem I was having, try this.. After running configure and before doing a make, edit config.h: /* Define if you have FreeBSD-compatible sendfile() */ /* #define HAVE_FREEBSD_SENDFILE */ ^^ ^^ Comment out the define for FreeBSD as above and do a make and install. Please report your results.. -kim -- w8hdkim at yahoo.com __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

1 0

Fwd: [Dovecot] Upgraded and authentication fails with LDAP
by Ren Galskap 14 Jan '05

14 Jan '05

Note: forwarded message attached. In addition to what I've already posted, the output from gdb when I try to use mutt is: Program received signal SIGABRT, Aborted. 0x18234dcf in kill () from /lib/libc.so.5 And then it dies. __________________________________ Do you Yahoo!? All your favorites on one personal page � Try My Yahoo! http://my.yahoo.com

6 12

[Dovecot] istream-limit.c - assertion failed
by Mail Admin 14 Jan '05

14 Jan '05

dovecot: Jan 14 12:25:49 Error: IMAP(xxxuser): file istream-limit.c: line 85 (_seek): assertion failed: (v_offset <= lstream->v_size) That error message is generated when squirrelmail 1.4.4-rc1 attempts to access this peculiar message partially quoted below. It doesn't happen (after copying the message to our testing account) accessing it through squirrelmail now. But it did. The server is running test61 configured --without-pop3d --with-ssl=openssl and --disable-ipv6 and running on FreeBSD 5.2.1. I'm not sure if this bit of a message is useful, but I have seen that error message in dovecot's log more than just this once. Thanks, Derek Message-id: <xxxmessageid> MIME-version: 1.0 Content-type: multipart/mixed; boundary=MS_Mac_OE_3188476518_1255852_MIME_Part User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --MS_Mac_OE_3188476518_1255852_MIME_Part Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable [bunch of readable text stuff here] --MS_Mac_OE_3188476518_1255852_MIME_Part Content-type: multipart/appledouble; boundary="MS_Mac_OE_3188476515_1257535_MIME_Part" --MS_Mac_OE_3188476515_1257535_MIME_Part Content-type: application/applefile; name="xxx.doc" Content-transfer-encoding: base64 Content-disposition: attachment [something short encoded here] --MS_Mac_OE_3188476515_1257535_MIME_Part Content-type: application/msword; name="xxx.doc"; x-mac-creator="4D535744"; x-mac-type="5738424E" Content-disposition: attachment Content-transfer-encoding: base64 [something big encoded here] --MS_Mac_OE_3188476515_1257535_MIME_Part-- --MS_Mac_OE_3188476518_1255852_MIME_Part--

1 0

RE: [Dovecot] Strange behavior of mysql 4.1.8/9 + dovecot1.0-test58~test61 on Fedora 3 x86_64 machine
by #LIU QI# 14 Jan '05

14 Jan '05

Some additional tests. I tried to add a test connection in the main.c under auth, which should be the main file of dovecot-auth. The test connection is done as the first statement in the int main() function. However, it still reports that the connection fails due to access denied. What should I do?? Any suggestions are welcomed. -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of #LIU QI# Sent: Friday, January 14, 2005 11:41 AM To: dovecot(a)dovecot.org Subject: [Dovecot] Strange behavior of mysql 4.1.8/9 + dovecot1.0-test58~test61 on Fedora 3 x86_64 machine I've built & configured the dovecot to use mysql as the passdb and userdb. However, dovecot-auth always claims that the username/password of mysql server is wrong (access denied by mysql server) during the connection. When I set the password to NULL, it can successfully connect to mysql server! I am 100% sure that I typed the correct password (by copy & paste), and I can successfully use this username/password connect to mysql server by mysqladmin and other mysql clients. I even wrote a C program which also successfully connects to mysql server. Furthermore, even I want to use pam_mysql in dovecot, the pam library also claims that it cannot connect to mysql server, but pam_mysql can be successfully used in postfix (exactly the same pam configuration, the same database, the same table, and the same username/password). Can anybody give me a hint why? Thank you very very very very much.... Crying for help....

1 0

[Dovecot] base dn and filter strings are concatenated
by Kazuo Moriwaka 14 Jan '05

14 Jan '05

Hello, When I set LDAP auth's search base dn, base dn and filter strings are concatenated. It cause filter cannot match any entries... I fixed it. Please check following patch. p.s. LDAP userdb/passdb's debug print have " fields=..." but it print junks. regards, -- Kazuo Moriwaka <moriwaka(a)valinux.co.jp> Index: src/auth/passdb-ldap.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/passdb-ldap.c,v retrieving revision 1.21 diff -r1.21 passdb-ldap.c 161a162 > str_free(str); 162a164 > str = t_str_new(512); 172c174 < conn->set.base, conn->set.scope, filter, --- > base, conn->set.scope, filter, Index: src/auth/userdb-ldap.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/userdb-ldap.c,v retrieving revision 1.25 diff -r1.25 userdb-ldap.c 174a175 > str_free(str); 175a177 > str = t_str_new(512); 187c189 < conn->set.base, conn->set.scope, filter, --- > base, conn->set.scope, filter,

1 0

[Dovecot] maildir and /var/spool/mail
by Steve Hickel 14 Jan '05

14 Jan '05

All, Not sure what to do next. Have imap working in that I can see messages in inbox. When I create a folder it won't create one. Looking at maillog shows that I don't have rights to folder /var/spool/mail/.sent or whatever folder I am trying to create. I have procmailrc and dovecot.conf point to /home/Maildir but for some reason something is tied to /var/spool/mail. Of course I am running FC3 and sendmail. Someone have any ideas as to what to try next? thanks in advance, Steve Hickel -- Steve Hickel <steve(a)korehicom.com> Kore/HiCom Corporation

6 8

[Dovecot] REQUEST: Different port(protocol) should be able to use a different certification.
by NAJIMA Hiroki 14 Jan '05

14 Jan '05

Hello, I want to use a different certificate for a different port(protocol). I searched http://wiki.dovecot.org/ and the mail archives. But such mechanism were not found. Could you implement a such mechanism? Or already implemented it, please teach how to do. I am assuming the following situations. MailAddress: [users](a)example.com SMTP Server: smtp.example.com POP3 Server: pop3.example.com IMAP Server: imap.example.com And pop3, imap, smtp are alias of real.example.com When use IMAPS, user connents imap.example.com POP3S, user connents pop3.example.com But one Certification file certificates only one FQDN. For example, dovecot.conf written that protocols = imaps pop3s ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # imap.example.com.cert.pem's CN is imap.example.com In this pattern. MUA such as Thunderbird warn when connect pop3s because FQDN is different. I have an simple idea in this problem. dovecot.conf protocols = imaps pop3s - ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem - ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # certification for imaps + imaps_ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem + imaps_ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # certification for pop3s + pop3s_ssl_cert_file = /etc/ssl/certs/pop3.example.com.cert.pem + pop3s_ssl_key_file = /etc/ssl/private/pop3.example.com.key.pem Dovecot uses imaps_ssl_cert/key whenever MUA connects imaps port, uses pop3s_ssl_cert/key whenever MUA connected dovecot's pop3s port. Could you discuss it? #If it was already discussed, please show pointer(URL) that discussion. Regards. ----- NAJIMA Hiroki

2 2

[Dovecot] Virtual users vacation notices and forwards
by Del Stoliker 14 Jan '05

14 Jan '05

I'm in the process of moving from UW-IMAP to dovecot. I'm exploring the idea of using virtual users with dovecot and storing all user information in LDAP. While bouncing this idea off of a coworker, he asked me how we could handle vacation notices and forwards. Currently, we're using a procmail recipe to generate the vacation notice, and the sendmail .forward file for forwards (although most of our forwarding takes place elsewhere so the .forward file is rarely used). These are, of course, dependant on the user having an account on the mail server. How are those of you using virtual users supporting this functionality? Thanks!

1 0

[Dovecot] Strange behavior of mysql 4.1.8/9 + dovecot 1.0-test58~test61 on Fedora 3 x86_64 machine
by #LIU QI# 14 Jan '05

14 Jan '05

I've built & configured the dovecot to use mysql as the passdb and userdb. However, dovecot-auth always claims that the username/password of mysql server is wrong (access denied by mysql server) during the connection. When I set the password to NULL, it can successfully connect to mysql server! I am 100% sure that I typed the correct password (by copy & paste), and I can successfully use this username/password connect to mysql server by mysqladmin and other mysql clients. I even wrote a C program which also successfully connects to mysql server. Furthermore, even I want to use pam_mysql in dovecot, the pam library also claims that it cannot connect to mysql server, but pam_mysql can be successfully used in postfix (exactly the same pam configuration, the same database, the same table, and the same username/password). Can anybody give me a hint why? Thank you very very very very much.... Crying for help....

1 0

[Dovecot] Upgraded and authentication fails with LDAP
by Ren Galskap 14 Jan '05

14 Jan '05

FreeBSD 5.2.1 Upgraded to dovecot 0.99.12.1 After authentication failed, I also upgraded OpenLDAP to 2.2.19 Dovecot and OpenLDAP are now the most recent versions in the ports. I can access the LDAP info through the OpenLDAP client without a problem, so slapd seems to be working fine. Both dovecot and OpenLDAP worked fine before the upgrade. Any help will be appreciated, since several people would like to have their e-mail back soon. maillog Jan 13 18:51:02 kongemord imap-login: Internal login failure: rjhjr [127.0.0.1] Jan 13 18:51:02 kongemord dovecot: child 1320 (auth) killed with signal 6 messages Jan 13 18:51:02 kongemord kernel: pid 1320 (dovecot-auth), uid 1006: exited on signal 6 debug.log Jan 13 18:51:02 kongemord slapd[1103]: conn=14 op=1 SRCH base="ou=imap,dc=krig,dc=net" scope=2 deref=0 filter="(&(objectClass=posixAccount)(uid=rjhjr))" Jan 13 18:51:02 kongemord slapd[1103]: conn=14 op=1 SRCH attr=uid userPassword Jan 13 18:51:02 kongemord slapd[1103]: conn=14 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Jan 13 18:51:02 kongemord slapd[1103]: conn=14 fd=12 closed Jan 13 18:51:03 kongemord slapd[1103]: conn=15 fd=12 ACCEPT from IP=127.0.0.1:54 185 (IP=0.0.0.0:389) Jan 13 18:51:03 kongemord slapd[1103]: conn=15 op=0 BIND dn="cn=dovecot,ou=imap,dc=krig,dc=net" method=128 Jan 13 18:51:03 kongemord slapd[1103]: conn=15 op=0 BIND dn="cn=dovecot,ou=imap,dc=krig,dc=net" mech=SIMPLE ssf=0 Jan 13 18:51:03 kongemord slapd[1103]: conn=15 op=0 RESULT tag=97 err=0 text= dovecot-ldap.conf hosts = localhost dn = cn=dovecot,ou=imap,dc=krig,dc=net dnpass = <cleartext> ldap_version = 3 base = ou=imap, dc=krig, dc=net deref = never scope = subtree user_attrs = uid,homeDirectory,,,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT user_global_uid = 1003 user_global_gid = 6 dovecot.conf base_dir = /var/run/dovecot/ protocols = imap imap_listen = * ssl_disable = yes login_chroot = yes login = imap login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot verbose_proctitle = yes first_valid_uid = 1003 last_valid_uid = 1003 first_valid_gid = 6 last_valid_gid = 6 valid_chroot_dirs = /var/mail default_mail_env = maildir:/var/mail/%u/Maildir client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls mail_save_crlf = yes maildir_copy_with_hardlinks = yes imap_executable = /usr/local/libexec/dovecot/imap auth = default auth_mechanisms = plain auth_userdb = ldap /usr/local/etc/dovecot-ldap.conf auth_passdb = ldap /usr/local/etc/dovecot-ldap.conf auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_user = dovecot-auth auth_verbose = yes I had the following flags in the Makefile prior to make: --without-shadow --localstatedir=/var --with-ldap __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250

1 0

[Dovecot] 1.0-test61
by Timo Sirainen 13 Jan '05

13 Jan '05

http://dovecot.org/test/ - Fixes crashes with keyword code - Fixes some problems with parsing MIME multipart bodies - Fixes some problems with parsing mail addresses - Support %vars in LDAP base setting

1 0

[Dovecot] Test 57 -> Test 60
by Andrew Hutchings 13 Jan '05

13 Jan '05

I just tried upgrading one of our mail cluster servers to test60 from test57. We have dovecot connecting to 3 different MySQL tables in 3 sql conf files. The error seems to stem from this: Jan 13 14:57:59 svr21 dovecot: auth(sql8): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) After this the auth process gets killed with signal 6. The sql8 is the config in use at the time, but can be any of the 3. I take it this is the auth process not liking the 3 auth lookups (refcount > 1)? Regards Andrew -- Andrew Hutchings Systems Operator / Developer / NWLUG Admin (http://www.nwlug.org.uk) Netserve Consultants Ltd. http://www.domaincity.co.uk/

2 2

[Dovecot] default_ldap_settings' value
by Kazuo Moriwaka 13 Jan '05

13 Jan '05

Hello, When I tested LDAP auth dovecot-auth caught segv, and I found that auth_cache_parse_key() doesn't check query == NULL. I think db-ldap.c/default_ldap_settings.pass_filter should have non-null default value. Please check following patch. regards, -- Kazuo Moriwaka <moriwaka(a)valinux.co.jp> Index: db-ldap.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/db-ldap.c,v retrieving revision 1.24 diff -r1.24 db-ldap.c 62c62 < MEMBER(pass_filter) NULL, --- > MEMBER(pass_filter) "(&(objectClass=posixAccount)(uid=%u))",

2 1

[Dovecot] Dovecot create mbox files. But why?
by Mirko Schulze 13 Jan '05

13 Jan '05

Hi there, my dovecot is now running normaly, but there is a small problem.... We want to to use the maildir format at the mailstorage. But the imap part of dovecot creates the for mbox specific files, but why? I created a passwd-file for a testuser. At this tme, there is only on line: test2@dev2.abc.de:ujAN28k8.5zV2:99:99:*:*:*:* in dovecot.conf are these interesting lines: auth_userdb = static uid=99 gid=99 home=/vrmd/pop3imap/links2mailboxes/%u/Maildir auth_passdb = passwd-file /vrmd/mailin/conf/pop3imapdb.passdb.txt I think, if a path ends of /Maildir dovecot will autodetect the maildir format. So what is wrong? Regards Mirko

2 1

[Dovecot] using separate authentication based on protocol
by Marius Stan 13 Jan '05

13 Jan '05

Hello, I wonder if it's possible to use a different query for authenticating users against the mysql db based on the protocol used: IMAP or POP3. This could come handy for not allowing my users who switched to IMAP from accidentally getting all their mail through a POP3 connection. Using dovecot-0.99.10 here. Marius

2 1

[Dovecot] imap-dovecot accept only from localhost
by Mirko Schulze 13 Jan '05

13 Jan '05

Hi, i want to configure the imap (not imaps) server to accept connections from everywhere. I can't find a command to configure dovecot in this way. Can anybody help me? Thanx Mirko

2 1

[Dovecot] How to configure auth_userdb and auth_passwd?
by Mirko Schulze 13 Jan '05

13 Jan '05

Hi! i want to configure dovecot to use a modified passwdfile. A linie in this file looks like this: "username: <TAB> crypted_password" how i have to use the auth_userdb and auth_passwd command? Now i have: auth_userdb = passwd-file /path/file auth_passwd = passwd-file /path/file (same file) dovecot is starting normaly (i think) but a authentification test via telnet doesnt work. Any suggestions? Thanx a lot. Mirko

2 1

[Dovecot] Maildir configure problem
by Mirko Schulze 13 Jan '05

13 Jan '05

Hi, i want to configure the maildir support. We are using a "multi-level" maildir, so i'm not sure about the default_mail_env command. the Maildir for the user testuser1(a)dev.test.de is located here: .../mailboxes /t (first char of the top-domainname) /te (the first both chars of the top-domainame /test.de (the top domain) /dev (the subdomain) /testuser1 (the username) /Maildir actually i'm using this command (I know, thats not complete *smile*): default_mail_env = maildir:/............./mailboxes/%1d/%2d/%d/%n/Maildir How can i name the subdomain? And is %d only the topdomain, like "test.de" in my example? Thanx a lot for your help Regards Mirko

2 1

[Dovecot] Bug report for test-60
by Juergen Daubert 12 Jan '05

12 Jan '05

I got the following with mbox and test-60: Jan 12 20:11:17 ser dovecot: IMAP(juergen): file mail-index-transaction.c: line 57 (mail_keyword_transaction_free): assertion failed: (kt->keywords->kt == NULL) Jan 12 20:11:17 ser dovecot: child 24762 (imap) killed with signal 6 but only if I try to move/copy a larger number of messages, around >30, from on folder to another. MUA: mutt, no other problems so far. Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

2 1

[Dovecot] delivery to incorrect user
by jpollara＠lawnchair.net 12 Jan '05

12 Jan '05

Yesterday a user reported to me that she received a bunch of emails that were not addressed to her. I'm using dovecot version 0.99.11 along with postfix and amavisd-new. I don't know how this happened because each mail file in /var/mail/ is only readable by the user. Has anyone ever heard of this happening before?

6 10

RE : [Dovecot] dovecot + mysql (complements)
by MAGALLON Lionel 12 Jan '05

12 Jan '05

Hi, OK, it works now. Thanks -----Message d'origine----- De : dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] De la part de mat(a)reynerie.org Envoyé : mercredi 12 janvier 2005 19:48 À : dovecot(a)dovecot.org Objet : Re: [Dovecot] dovecot + mysql (complements) On Wed, Jan 12, 2005 at 07:26:39PM +0100, MAGALLON Lionel wrote: > Hi, Hi, > I've done some supplementary tests with tcpdump. > Apparently, with a login containing the % character, > there's no query send to MySQL. > > Do you know if the % character is filtered by dovecot ? with my config yes, see auth_username_chars in your dovecot.conf -- Matthieu Clavier <mat(a)reynerie.org> Sola dosis facit venenum - Paracelse (1493-1541)

1 0

[Dovecot] dovecot + mysql (complements)
by MAGALLON Lionel 12 Jan '05

12 Jan '05

Hi, I've done some supplementary tests with tcpdump. Apparently, with a login containing the % character, there's no query send to MySQL. Do you know if the % character is filtered by dovecot ? Thanks

2 1

[Dovecot] dovecot + mysql
by MAGALLON Lionel 12 Jan '05

12 Jan '05

Hi, I've got a problem of authenticating users when they've got the % character in their login name. It always returns -ERR Authentication failed. I've done some tests (explained below). 1. the mysql answer to SELECT password FROM users WHERE uid = 'foo%domain.com' is 123 2. the mysql answer to SELECT password FROM users WHERE uid = 'foo(a)domain.com' is 123 3. with a password_query like this : password_query = SELECT password FROM users WHERE uid = '%u' it works fine with foo(a)domain.com but not with foo%domain.com 4. everybody can login with password 123 with a password_query like this : password_query = SELECT password FROM users WHERE uid = 'foo%domain.com' => I don't know what's done with the % character when passed to the %u variable. Can somebody enlight me ? Thanks a lot.

1 0

[Dovecot] link() failed / maildir_copy_with_hardlinks=no / maildir-save.c.patch
by David C. Reeve 12 Jan '05

12 Jan '05

Hi, I have recently been having a small problem with Dovecot (dovecot-0.99.13) not honouring the "maildir_copy_with_hardlinks" config option, specifically when it is set to "no". This results in errors to the syslog looking like: Jan 12 09:59:21 imap imap(dave): link(/afs/.../tmp/1105541958.P1137Q0M41428.imap, /afs/.../new/1105541958.P1137Q0M41428.imap:2,S) failed in maildir_copy: Invalid cross-device link The supplied patch will, when maildir_copy_with_hardlinks=no, rename files inside maildir's instead of hard linking them, hence honouring the configuration option. A word of caution! This all relies on the filenames in maildir being unique (which they should be, and this shouldn't be a problem, but..). It is possible (although unlikely) that renaming the file could destroy a file in the target directory; no checking is done to assure this is not the case! (If you are paranoid you can always write another patch). Yes I am using AFS (openafs specifically) to hold my maildir's, which does not support hard links. However AFS assures that rename operations are atomic so we can use that instead (this may be the case for other filling systems that do not allow hard links). Hope that helps some one else ;) Dave -- David C. Reeve <David.Reeve(a)pnsol.com> Predictable Network Solutions

1 0

[Dovecot] dovecot-auth zombie procs
by jpollara＠lawnchair.net 12 Jan '05

12 Jan '05

Hi, every now and then it seems as if dovecot-auth zombie's out. When this happens nobody can log in. If I kill all the dovecot-auth processes and then restart dovecot everything seems to work again. I'm authenticating against an openldap server on a debian sarge box so I wonder if this has anything to do with it. All my clients are using Outlook. Any help would be greatly appreciated. Thanks. Josh

2 5

[Dovecot] Re: maildir and /var/spool/mail
by C.Lee Taylor 12 Jan '05

12 Jan '05

Greetings ... > Not sure what to do next. Have imap working in that I can see messages > in inbox. When I create a folder it won't create one. Looking at maillog > shows that I don't have rights to folder /var/spool/mail/.sent or > whatever folder I am trying to create. I have procmailrc and > dovecot.conf point to /home/Maildir but for some reason something is > tied to /var/spool/mail. Of course I am running FC3 and sendmail. > Someone have any ideas as to what to try next? I'm not sure of the rest of the history with this, but my FC3 installation has [root@nasrec etc]# cat /etc/procmailrc PATH=/bin:/usr/bin:/usr/bin MAILDIR=$HOME/mail DEFAULT=$HOME/Maildir/ #VERBOSE=on #LOGFILE=/var/log/procmail [root@nasrec etc]# ll /etc/procmailrc -rw-r--r-- 1 root root 109 May 2 2004 procmailrc I do remember having to delete the old mail box of one of my installs, where I had started using dovecot before putting in my procmailrc file ... I stop dovecot, imap* and pop3* ... Removed all the wrong mailboxs both in user folder and in /var/spool/mail ... Ran mail -s Test user Type a message here < Press Control-D here > Message gets delieverd in maildir format, start dovecot and all seemed well. I hope this helps. Mailed Lee

1 0

[Dovecot] Howto host multiple domains
by Mesut Bayrak 11 Jan '05

11 Jan '05

i dont know howto host multiple domains with dovecot are there any way to make it ?

2 1

[Dovecot] can not connect to dovecot using ssl
by Jay Gustafson 11 Jan '05

11 Jan '05

I can connect using imap, but when I try using ssl (imaps) I get a can not connect to server error. I have in my dovecot.conf protocols = imaps imap imap_listen = * imaps_listen = * I DO get a connection when I telnet to port 993 of my server (both localhost and remote work). Any help much appreciated.. Jay

2 1

[Dovecot] Re: delivery agent in 1.0?
by Apostolos Papayanakis 11 Jan '05

11 Jan '05

On Thu, 23 Dec 2004 Geo Carncross wrote: > How about a dovecot-inject tool that writes a message to whatever is > considered the $LOCAL user? It wouldn't have to do much but write the > message (safely) and update indexes -- something dovecot already has to > do. I hope there will soon be a plain delivering tool for dovecot 1.x. I could use it right away as the delivering step with procmail, which would run it under recipient's uid and context (all recipients are real unix users in my case). Without a local delivery agent, dovecot will always seem slower than its rivals when opening INBOXes with new mails, especially large ones, because of index creation delays. A good LMTP implementation has its benefits, but many people have to do without it. -- Apostolis Papayanakis apap(a)ccf.auth.gr, 2310-998416 On Thu, 23 Dec 2004 dovecot-request(a)dovecot.org wrote: > Date: Thu, 23 Dec 2004 11:44:15 -0500 > From: Geo Carncross <geocar-dovecot(a)internetconnection.net> > Subject: Re: [Dovecot] delivery agent in 1.0? > To: Timo Sirainen <tss(a)iki.fi> > Cc: " Branko F. Gra?nar " <bfg(a)noviforum.si>, dovecot(a)dovecot.org > Message-ID: <1103820255.3898.126.camel(a)midget.intranet> > Content-Type: text/plain; charset=iso-8859-2 > > On Thu, 2004-12-23 at 17:52 +0200, Timo Sirainen wrote: > > On 23.12.2004, at 16:06, Branko F. Graθnar wrote: > > > > > Is there any plan to include delivery agent in 1.x? > > > > I'll need to implement one in next few months, so yes. > > > > Hmm. This brings to my mind again that it would need Sieve, and mvmf > > might be a good base for it, but it's still not open source (Mark? :) > > It may be difficult to please everyone. I could have use for [some > elements of] a dovecot-lda but zero use for sieve... > > > > > I would be very happy, if there would be lmtp delivery agent included > > > with dovecot 1.x... This would make creating large mailsystem cluster > > > creation very simple + indexes would be always up2date. > > > > I'm not sure when I'll get around to implementing LMTP server. It's > > actually a bit annoying to implement because it needs to be able to > > deliver mail into multiple accounts, and if each one stores mails with > > different UID, it needs to either run as root (bad) or launch multiple > > processes and do IPC with them. > > How about a dovecot-inject tool that writes a message to whatever is > considered the $LOCAL user? It wouldn't have to do much but write the > message (safely) and update indexes -- something dovecot already has to > do. > > That way: > > * People who do delivery without LMTP baggage aren't treated as second- > class citizens. > > * Sieve implementations merely have to treat "keep" and "fileinto" as > subprocesses. > > * LMTP implementations can do the work they've already have to do > (regarding mapping email addresses to local users) and simply hook into > the sieve processor or the dovecot-inject, or anything else the > administrator/user likes. > > Formally, dovecot-inject would need the following information: > > 1. the envelope recipient ($RECIPIENT) > 2. the envelope sender/return-path/errors-to-address ($SENDER) > 3. the IMAP folder to write the message to (argv[1]) > > On systems with shared-uids, dovecot-inject would also need the concept > of the "localpart" of the address thats applicable. dovecot already > needs to know this in order to ACCESS the maildrop. ($LOCAL) > > This would keep things very easy to integrate without resorting to > shared libraries, "plugin system" nonsense, or forcing people to make > extra levels of indirection (lmtpclient) in order to benefit from pre- > login indexing... > > > > I suppose I'd implement it so that the actual LMTP talking would be > > done in a process very similar to imap/pop3-login processes, ie. > > completely unprivileged. Then it would tell master process to launch > > delivery agent processes to specific users, and those delivery agents > > then would get the mail from lmtp process via .. um. read-only shared > > memory + semaphores might be better than just copying the data over > > pipes/sockets? > > blah blah blah... > >

2 2