- dovecot - dovecot.org

[Dovecot] vpopmail authentification broken in dovecot 1.0beta
by daniel petre 05 Feb '06

05 Feb '06

hello, i got * net-mail/dovecot Latest version available: 1.0_beta2 Latest version installed: 1.0_beta2 Size of files: 1,309 kB Homepage: http://dovecot.org/ Description: An IMAP and POP3 server written with security primarily in mind License: LGPL-2.1 and since dovecot-0.99.14-r1 authentification doesnt work no more. i posted something similar with dovecot-1.0_alpha5 but all the answers i got were like "it isnt dovecot's fault, its vpopmails". bummer, my vpopmail did not changed , but dovecot versions yes. so i think dovecot is broken with vpopmail auth. i edited dovecot.conf and enabled all the parts related to vpopmail correctly like in old dovecot.conf here's what i receive in the log: dovecot: Jan 31 14:51:28 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=81.18.x.x rip=81.18.x.x resp= dovecot: Jan 31 14:51:28 Info: auth(default): client out: CONT 1 dovecot: Jan 31 14:51:28 Info: auth(default): client in: CONT 1 AGRhbmlAbGlgudXhzb2x1fdGlvbnMucmh8AcG9jcG9j dovecot: Jan 31 14:51:28 Error: auth(default): vmysql: sql error[3]: MySQL server has gone away dovecot: Jan 31 14:51:28 Info: auth(default): vpopmail(dani(a)domain.ro,81.18.x.x): unknown user dovecot: Jan 31 14:51:29 Info: auth(default): client out: FAIL 1 user=dani(a)domain.ro dovecot: Jan 31 14:51:29 Info: auth(default): client in: AUTH 2 PLAIN service=POP3 lip=81.18.x.x rip=81.18.x.x resp=AGRhbmlAbGlgudXhzb2x1fdGlvbnMucmh8AcG9jcG9j dovecot: Jan 31 14:51:29 Error: auth(default): vmysql: sql error[3]: MySQL server has gone away dovecot: Jan 31 14:51:29 Info: auth(default): vpopmail(dani(a)domain.ro,81.18.x.x): unknown user dovecot: Jan 31 14:51:31 Info: auth(default): client out: FAIL 2 user=dani(a)domain.ro i tried compiling dovecot with and without mysql support and the log is the same. vpopmail support is compiled in. so i use only vpopmail auth, no passdb, no mysql, no ssl. anyone can help with this error? coz dovecot seems such a nice imap/pop3 daemon but so much broken since last 0.9 version which is a shame.. thank you. -- Daniel Petre System Administrator Tech Support Coordinator ............................................................................. RCS & RDS Pitesti Tel.: +40348.400.401 Fax: +40348.400.441 http://www.rcs-rds.ro ............................................................................. Privileged/Confidential Information may be contained in this message. If you are not in the addresses indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such a case, you should destroy this message and kindly notify the sender by reply e-mail.

2 1

[Dovecot] default_mail_env auto-detect woes for maildir users
by David Friedlander 05 Feb '06

05 Feb '06

Hello-- I am a fairly new dovecot user and have run into a problem. I am running dovecot 1.0alpha5 (built from source) on a Fedora Core 1 machine. The system has about 400 users with over 80 IMAP users, and we have just transitioned from UW-IMAP. Thus all users are currently still mbox users. I would like to transition them to maildir users (this was the main point for me switching servers), and I chose dovecot because it could simultaneously support both formats. My dovecot.conf uses auto_detect (no default_mail_env defined, by choice). Auto-detect is working fine for mbox users, as shown by this (edited) log snippet: dovecot: imap(janeuser): maildir: couldn't find root dir dovecot: imap(janeuser): mbox: root exists (/Home/janeuser/mail) dovecot: imap(janeuser): mbox: INBOX exists (/var/mail/janeuser) dovecot: imap(janeuser): mbox: root=/Home/janeuser/mail, index=/Home/janeuser/mail, inbox=/var/mail/janeuser However, for another user who already has ~/Maildir and a proper maildir-format spool location ( /var/mail/joeuser/{cur|new|tmp} ) the log shows: dovecot: imap(joeuser): maildir: root exists (/Home/joeuser/Maildir) dovecot: imap(joeuser): maildir: root=/Home/joeuser/Maildir, index=/Home/joeuser/Maildir, control=, inbox= (Mail clients show no messages, but one can see them from the UNIX shell and with mutt on the server.) If I set default_mail_env = maildir:~/Maildir:INBOX=/var/spool/mail/%u then everything works fine for 'joeuser'. However, I need auto-detect during this transition phase. My questions, please: * How do I get INBOX ("inbox=") to be properly defined/detected? * Must I do this with namespaces, and how does that affect the fact that there will be a transition period where some users use mbox and others use maildir? * Other advice? I have been unable to track this down so far, between reading the Dovecot documentation and Googling the dovecot mailing list archives. Thanks in advance, David

2 2

[Dovecot] Support for Kmail maildir format
by Graham Cobb 04 Feb '06

04 Feb '06

Has anyone looked into providing support in dovecot for Kmail folders? I would like to make my Kmail folders (on my main desktop system) available to my other systems (including over a VPN when I am travelling). Kmail is my main mail program and I have a lot of mail in a lot of folders, so I don't want to set up a separate IMAP service and move all the mail and folders. Kmail's use of maildir seems to folow the basic maildir approach except that sub-folders are handled differently. If you create a folder (say it is called ABC) in Kmail and start putting mail in it, Kmail creates a directory on the disk called ABC (not .ABC) and creates the cur, new and tmp folders within it to contain the email. If you then create a subfolder of ABC (say it is called DEF, contained within the ABC folder), Kmail creates a directory on the disk called .ABC.directory and creates the DEF directory within that. In other words, maildir directories are given the same name as the mail folder (with no leading dot) but sub-folders are contained in disk directories called .<folder-name>.directory. I have taken a quick look at the dovecot code and am fairly sure this could be handled by a variant on the existing maildir code (e.g. by changes to maildir_fill_readdir and other routines). Has anyone tried this? Graham

5 12

[Dovecot] rquotad (NFS) quota plugin
by Thomas Wouters 03 Feb '06

03 Feb '06

The attached patch is an updated version of my quota-rquotad patch for the quota plugin. Like quota-fs, it only does quota reporting, not enforcing or changing. It also only works on FreeBSD, and possibly other *BSD's. It lacks any and all configure-time tests to see if RPC is even supported, and hardcodes the (Free)BSD way of getting at the NFS server of an NFS mount. I'm mostly mailing it around to avoid duplicate work, in case anyone is looking for it. I do intend to generalize the plugin-patch, and add proper configure checks, I just haven't gotten around to testing it on other BSD systems. Linux support would be nice, but getting at the NFS server of an NFS mount is apparently quite a hassle, as it means reading /etc/mtab or /proc/self/mounts. Yuck. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] mbox to maildir conversion on a user-by-user basis!
by Tony Kay 03 Feb '06

03 Feb '06

In the midst of evaluating Dovecot for use in solving some mbox locking issues (while also waiting for our eventual migration to maildir), I had an epiphany. It looks like Dovecot's auto-detection of mail formats would allow us to migrate from mbox to maildir on a user-by-user basis! I was thinking: 1. Let dovecot autodetect mail storage 2. Use some procmail trickery to detect which format to deliver into (I am researching how to do the detection on a user-by-user basis) 3. Manually convert users as you want by: - Temporarily disable mail delivery for that user (at least make it look like the inbox is locked) - Run conversion on mbox files -> maildir format - Put in the procmail hack for them - Re-enable delivery Way cool. I am still working out the details, but I was wondering if anyone sees a problem with this??? -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Sanity is a cozy lie. Susan Sontag

2 1

[Dovecot] not creating homedirs when using maildir format
by Ben Halicki 03 Feb '06

03 Feb '06

Hi all, I'm in the process of setting up dovecot, but for some reason, it's not creating home directories if they don't already exist. I have the following line in dovecot.conf: default_mail_env = maildir:~/mail:INBOX=/var/mail/%u I have set permissions on /home to allow everyone full access, so creating directories in /home by dovecot non-root processes shouldn't be a problem. If I instruct dovecot to use mbox format, directories are created without a problem. The problem only seems to exist with maildir. Any help would be greatly appreciated! Thanks and regards, Ben Halicki Information Technology Officer Macquarie Textiles Group Limited Phone: +61 2 6043 0235 Fax: +61 2 6041 1321

4 3

[Dovecot] Dovecot(imap) problem
by Clovis Tristao 03 Feb '06

03 Feb '06

Feb 1 20:13:15 myhost imap(someuser): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) I'm using Fedora Core 4, dovecot 0.99.14-4. Any idea? How to fix this problem? Thanks a lot, Clóvis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: mailto:clovis@agr.unicamp.br http://www.agr.unicamp.br Fone(0xx19) 37881031-37881038 ou FAX(55xx19) 37881005/37881010

4 3

Re: [Dovecot] not creating homedirs when using maildir format
by Ben Halicki 02 Feb '06

02 Feb '06

"Ben Halicki" <ben.halicki at macquarietextiles.com.au> writes: > Hi all, > > I'm in the process of setting up dovecot, but for some reason, it's not > creating home directories if they don't already exist. > > I have the following line in dovecot.conf: > > default_mail_env = maildir:~/mail:INBOX=/var/mail/%u > > I have set permissions on /home to allow everyone full access, so > creating directories in /home by dovecot non-root processes shouldn't be > a problem. If I instruct dovecot to use mbox format, directories are > created without a problem. The problem only seems to exist with maildir. > > Any help would be greatly appreciated! Never done this, ISTR there is a PAM module that is supposed to do this (create the directory). It would require you to use PAM, obviously. -- Matthias Andree Thanks for the reply Matthias. Only problem with PAM and pam_mkhomedir, is that Dovecot doesn't seem to open a session, so pam isn't called and pam_mkhomedir doesn't get the chanceto create a home directory. I can't understand why this works with mbox, but not withmaildir!Thanks again,Ben HalickiInformation Technology OfficerMacquarie Textiles Group LimitedPhone: +61 2 6043 0235Fax: +61 2 6041 1321

1 0

Re: [Dovecot] Question about Dovecot and NFS
by Tony Kay 02 Feb '06

02 Feb '06

On Thu, 02 Feb 2006 11:48:02 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > -- SNIP -- > As long as both hosts keep using dotlocking, Dovecot should be able to > handle the above without any corruption problems. > > > I did some testing w/dovecot 0.99 earlier in this same config, > > Forget those results and try with 1.0beta instead :) > I ran tests on 1.0b2. I could _not_ make dovecot misbehave on NFS w/two physical servers accessing the same mailbox. All of the "undesirable" things that happened (i.e. really poorly written clients suffering strange views of the mailbox due to their own stupidity) were well within IMAP spec., and are non-destructive/lossy. Kudos Timo! Thanks for writing some really excellent code. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 The camera makes everyone a tourist in other people's reality, and eventually in one's own. Susan Sontag

1 0

[Dovecot] SRC.RPM for dovecot (cvs-2006-01-30) with lda
by Sergey Ivanov 02 Feb '06

02 Feb '06

Hi, there is dovecot.src.rpm for ALTLinux, (dovecot beta2 with sieve local delivery agent) uploaded to http://ftp.altlinux.org/pub/distributions/ALTLinux/Daedalus/SRPMS.daedalus/… -- Sergey Ivanov

1 0

Re: [Dovecot] Question about Dovecot and NFS
by Tony Kay 02 Feb '06

02 Feb '06

On Wed, 01 Feb 2006 11:45:16 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > On Tue, 2006-01-31 at 22:42 -0800, Tony Kay wrote: > > How does dovecot handle this kind of conflict. I.e. how would one dovecot IMAP on server A detect that dovecot on server B had rewritten something like flags on the mailbox they are both accessing? I'm sure it doesn't leave the dot lock sitting around, since that would block mail delivery. > > It just checks if mbox's mtime has changed. If it has, it checks if > there are new mails or if it needs to do some other synchronization > (mbox_dirty_syncs / mbox_very_dirty_syncs causes it to delay it as long > as possible). > > UW-IMAP also checks if mtime has changed, but instead of trying to > figure out what changed it just disconnects the client with an > "unexpected mbox change" error. UW uses a "kiss of death" signal for collaborative locking...the mtime changes are all assumed to be appends as far as I know. The problem (which I can reproduce) comes with a situation like this: - IMAP host A and B access INBOX for the same user from different physical servers which share the inbox via NFS - Neither sees the other (because UW imap assumes lingering opens come from c-client apps, and it uses signals/flock/tmp to sync them, which are not available when A and B are on separate hosts). - Delete and expunge a message on B - 'A' can still read the expunged message. - Mark two messages for delete on A, including the one previously expunged by B - New message delivered to inbox (possibly by yet another host) - Expunge on A - New message is lost My theory is that the two IMAPs are both holding a fd open, and this causes one of the copies to become stale (in the sense it no longer has a filesystem name). The new mail is delivered to the non-stale box, and then the expunge on 'A' causes the stale open file to be "rewritten" over the top of the non-stale one. Result: mail loss. We also see things like message flags that magically reset themselves, etc. I did some testing w/dovecot 0.99 earlier in this same config, and it seems like it has some issues. For example a delete/expunge on IMAP A was "sort-of" seen by the B (fetch complained that the UIDs had changed, and would not work until a NOOP was done...this is technically OK), but B magically restored the deleted message with a new UID (which is not so good, since a client that caches stuff may now have a strange view of the world...I need to examine the set of "update" notices that went along with these events to better understand the implications). This also worries me because the "magic" reappearance indicates a copy from a stale fd, which could exhibit the same mail loss I produced w/UW IMAP. I am planning on updating to your latest source tree tomorrow (I am out of time today), and see if I can make it "lose" new mail. Opinions??? Thanks! Tony

2 1

[Dovecot] Can't send mail through new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

2 2

[Dovecot] Can't send mail from new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

1 0

[Dovecot] Can't send from the new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

1 0

[Dovecot] extremely slow delete/move operations?
by Gregory K. Ruiz-Ade 01 Feb '06

01 Feb '06

I've been working to migrate several hundered users on to our new mail servers, which run dovecot 0.99.11 (RHEL4). The problem I'm seeing is that deleting or moving a message seems to take a very long time. It's not uncommon for Thundirbird (1.0.7) to have delays of 5-10 seconds to delete a single message from my Inbox (<500k) and place it in my Trash folder (~100MB right now). The systems are Dell PowerEdge 1850 (dual 3.6GHz Xeon) with two 300GB SCSI drives in a hardware mirror. Filesystems are ext3 on LVM. Inboxes are on /var/spool/mail (/export/mail, symlinked into /var). User mail folders are in their home directories (/export/homes1/<user>, automounted to /home/<user>; some home directories are NFS automounted from a NetApp). Both the mail spool and home directories are available over NFS for compatibility reasons with the former setup. What's really bugging me is that I've used the same software (RHEL4 and dovecot 0.9x.x) at my last workplace, and the performance was outstanding; it beat UWIMAPd hands-down, especially with large mailboxes. Here, the opposite seems to be true. The primary difference seems to be that we're using NFS here, but I wasn't using NFS at my last job. I'm getting a lot of grief over the delays when users delete mail or move mail from their inbox to one of their mail folders. Enough so that they're now resisting moving to the new server. Where do I look to find out what's causing the slowness? What can I do to make it faster? Mailbox formats are mbox. Using these options in /etc/dovecot.conf: ----- protocols = imaps pop3s imap_listen = [::] pop3_listen = [::] ssl_cert_file = /usr/share/ssl/certs/csefast.ucsd.edu_cert.pem ssl_key_file = /usr/share/ssl/private/csefast.ucsd.edu_key.pem login_dir = /var/run/dovecot-login login = imap login = pop3 verbose_proctitle = yes first_valid_uid = 100 default_mail_env = mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_locks = dotlock fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root ----- Thanks in advance, Gregory -- Gregory K. Ruiz-Ade Sr. Systems Administrator Computer Science and Engineering University of California, San Diego Office: EBU3b 1216 Phone: (858) 822-2625 E-mail: gkra(a)ucsd.edu

9 10

Re: [Dovecot] Question about Dovecot and NFS
by Timo Sirainen 01 Feb '06

01 Feb '06

On Tue, 2006-01-31 at 22:42 -0800, Tony Kay wrote: > How does dovecot handle this kind of conflict. I.e. how would one dovecot IMAP on server A detect that dovecot on server B had rewritten something like flags on the mailbox they are both accessing? I'm sure it doesn't leave the dot lock sitting around, since that would block mail delivery. It just checks if mbox's mtime has changed. If it has, it checks if there are new mails or if it needs to do some other synchronization (mbox_dirty_syncs / mbox_very_dirty_syncs causes it to delay it as long as possible). UW-IMAP also checks if mtime has changed, but instead of trying to figure out what changed it just disconnects the client with an "unexpected mbox change" error.

1 0

[Dovecot] Immutable Maildir (or: "I know drag&drop")
by Michael Renner 31 Jan '06

31 Jan '06

Hi, I'm 'constantly' (every odd month) faced with users happily dragging around or (un)subscribing folders in our shared IMAP account. Is there a "clean" way to prevent users from doing that when having a Maildir? Unix permissions probably won't cut the slack since setting any Maildir (sub)directory to readonly (immutable or chmod u-w ) will probably cause dovecot to hit a wall at high speed sooner or later (lock files, rotated cache/log files) Got any other ideas? best regards, Michael Renner

2 1

[Dovecot] Question about Dovecot and NFS
by Tony Kay 31 Jan '06

31 Jan '06

Hi, We are using mbox and UW IMAP, and are having issues because UW IMAP does not support multiple client access when you use NFS for the mail files. I've done some research (see the comments after my 2 questions below), and most of the other major IMAP servers simply don't support it (courier is about the only one that has a positive comment). How much testing have you done w/NFS-mounted mail in mbox format? Have you found a reliable way to handle NFS mbox files? The UW IMAP docs say that multiple client access to mail spools that are NFS mounted is not safe, and the source has comments like this about NFS mail spools: /* Make fcntl() locking of NFS files be a no-op the way it is with flock() * on BSD. This is because the rpc.statd/rpc.lockd daemons don't work very * well and cause cluster-wide hangs if you exercise them at all. The * result of this is that you lose the ability to detect shared mail_open() * on NFS-mounted files. If you are wise, you'll use IMAP instead of NFS * for mail files. * * Sun alleges that it doesn't matter, because they say they have fixed all * the rpc.statd/rpc.lockd bugs. This is absolutely not true; huge amounts * of user and support time have been wasted in cluster-wide hangs. */ Cyrus' FAQ says this about NFS mail spools: (http://asg.web.cmu.edu/cyrus/imapd/install-FAQ.html#nfs) NFS (don't) Q: Weird things are happening. The mailspool is mounted over NFS, and... A: Don't mount the mail spool over NFS. Due to locking problems with NFS, this doesn't work (and for various other reasons, probably isn't worth the bother; IMAP appears to be I/O bound, not CPU bound, and scaling in this way is not a good idea). More specifically, if you use NFS and it looks to work, you may have locking problems in the future which will result in silently lost mail. If you use NFS and things go berzerk, it's because mmap(2) apparently has different semantics on local disk than it has on NFS. You can get the above behavior (silently lost mail) if you work at it. Courier is the only one that seems friendly (excerpt from their web site): Courier-IMAP is popular on Qmail/Exim/Postfix sites that are configured to use maildirs. The primary advantage of maildirs is that multiple applications can access the same Maildir simultaneously without requiring any kind of locking whatsoever. Maildir is a faster and more efficient way to store mail. It works particularly well over NFS, which has a long history of locking-related woes. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 When they discover the center of the universe, a lot of people will be disappointed to discover they are not it. Bernard Bailey

3 2

[Dovecot] worth a few Euros?
by -- -- 31 Jan '06

31 Jan '06

Yo Timo, did you say that login processes "just don't crash"? Found these while doing load/malformed data tests. Got the kernel patch allow_setid_cores working. Don't have time to check if they're exploitable. Probably time to get a gamma version out for people, eh? Cheers, Jared :) =========================================================================================== Note: Running dovecot-1.0.beta2 with simple (no funniness) config Note: Running on Intel (in VmWare) with RH9. Note: I'm using shadow authentication, but tried with PAM and it still dumped. Note: For this first core, I see the server responding with: "*OK Waiting for authentication process to respond.." Note: Not sure, but I think these problems are timing related. Be sure to check if a pointer is valid and that will get rid of most of these. Note: I have plenty of sample cores if you need one to fix. -Jared DeMott [root@server dovecot]# gdb ./dovecot-auth -c core.22753 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 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 "i386-redhat-linux-gnu"... Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.1...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/libpam.so.0...done. Loaded symbols for /lib/libpam.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 auth_request_unref (_request=0x807b0f0) at auth-request.c:96 96 i_assert(request->refcount > 0); (gdb) bt #0 auth_request_unref (_request=0x807b0f0) at auth-request.c:96 #1 0x080523ee in auth_request_handler_unref (_handler=0x807b0f0) at auth-request-handler.c:66 #2 0x08050217 in auth_client_connection_destroy (_conn=0x807b0f0) at auth-client-connection.c:327 #3 0x0804ffd8 in auth_client_input (context=0x807b0f0) at auth-client-connection.c:227 #4 0x080607d0 in io_loop_handler_run (ioloop=0x8073100) at ioloop-poll.c:189 #5 0x0805fe29 in io_loop_run (ioloop=0x8073100) at ioloop.c:235 #6 0x08055329 in main (argc=1, argv=0xbfffe454) at main.c:309 #7 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) p request $1 = (struct auth_request *) 0x1 (gdb) i r eax 0x807b0f0 134721776 ecx 0x1 1 edx 0x6c 108 ebx 0x8084e78 134762104 esp 0xbfffe2f0 0xbfffe2f0 ebp 0xbfffe2f8 0xbfffe2f8 esi 0x80a43c8 134890440 edi 0xbfffe314 -1073749228 eip 0x80512d1 0x80512d1 eflags 0x286 646 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ==================================================================================== [root@server 1]# gdb ./dovecot-auth -c core.30100 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 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 "i386-redhat-linux-gnu"... warning: exec file is newer than core file. Core was generated by `dovecot-auth'. Program terminated with signal 6, Aborted. #0 0xffffe002 in ?? () (gdb) bt #0 0xffffe002 in ?? () #1 0x42028a73 in ?? () #2 0x0805d47c in default_info_handler (format=0x8067d00 "\024P?u\024?u\020?u\f?u\b?\t", args=0xbffff264 "z|\006\b!") at failures.c:162 #3 0x0805d04b in t_buffer_alloc (size=1108544020) at data-stack.c:347 #4 0x0804fa54 in reply_line_hide_pass (line=0x1 <Address 0x1 out of bounds>) at auth-client-connection.c:35 #5 0x0804fa71 in reply_line_hide_pass (line=0x0) at auth-client-connection.c:36 #6 0x080523bb in auth_request_handler_unref (_handler=0x0) at auth-request-handler.c:74 #7 0x08052b65 in auth_request_handler_auth_continue (handler=0x0, args=0x80774e0 "HU\n\b") at auth-request-handler.c:350 #8 0x0805f916 in io_add (fd=2, condition=39, callback=0x80778e8, context=0x0) at ioloop.c:23 #9 0x080602c8 in io_loop_notify_remove (ioloop=0x0, io=0x8075b00) at ioloop-notify-dn.c:138 #10 0x0805f985 in io_add (fd=0, condition=1073792608, callback=0x80678bc <pwrite_full+64>, context=0x0) at ioloop.c:43 #11 0x08054f94 in add_extra_listeners () at main.c:148 #12 0x42015574 in ?? () (gdb) i r eax 0x0 0 ecx 0x6 6 edx 0x42130a14 1108544020 ebx 0x7594 30100 esp 0xbffff0e0 0xbffff0e0 ebp 0xbffff0e8 0xbffff0e8 esi 0x806daa8 134666920 edi 0x80e92e8 135172840 eip 0xffffe002 0xffffe002 eflags 0x246 582 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ======================================================================================== [root@server login]# gdb ./imap-login -c core.25116 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 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 "i386-redhat-linux-gnu"... Core was generated by `imap-login'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libssl.so.4...done. Loaded symbols for /lib/libssl.so.4 Reading symbols from /lib/libcrypto.so.4...done. Loaded symbols for /lib/libcrypto.so.4 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /usr/kerberos/lib/libgssapi_krb5.so.2...done. Loaded symbols for /usr/kerberos/lib/libgssapi_krb5.so.2 Reading symbols from /usr/kerberos/lib/libkrb5.so.3...done. Loaded symbols for /usr/kerberos/lib/libkrb5.so.3 Reading symbols from /usr/kerberos/lib/libk5crypto.so.3...done. Loaded symbols for /usr/kerberos/lib/libk5crypto.so.3 Reading symbols from /usr/kerberos/lib/libcom_err.so.3...done. Loaded symbols for /usr/kerberos/lib/libcom_err.so.3 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 i_stream_read (stream=0x0) at istream.c:48 48 if (stream->closed) (gdb) bt #0 i_stream_read (stream=0x0) at istream.c:48 #1 0x0804ade2 in client_read (client=0x8070410) at client.c:311 #2 0x0804ae3c in client_input (context=0x8070410) at client.c:333 #3 0x08055558 in io_loop_handler_run (ioloop=0x806cc50) at ioloop-poll.c:189 #4 0x08054bb1 in io_loop_run (ioloop=0x806cc50) at ioloop.c:235 #5 0x0804d3ed in main (argc=1, argv=0xbffff504, envp=0xbffff50c) at main.c:341 #6 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) p stream $1 = (struct istream *) 0x0 (gdb) ====================================================================================== [root@server core]# gdb ./imap -c core.15043 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 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 "i386-redhat-linux-gnu"... warning: exec file is newer than core file. Core was generated by `imap'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 #0 0xffffe002 in ?? () (gdb) bt #0 0xffffe002 in ?? () #1 0x42028a73 in abort () from /lib/tls/libc.so.6 #2 0x0809f9fc in i_internal_panic_handler (fmt=0x80ac360 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfffdd94 "\0251\v\b?") at failures.c:375 #3 0x0809f5cb in i_panic (format=0x80ac360 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #4 0x08082277 in mail_cache_transaction_reserve_more (ctx=0x80cb4a0, block_size=332, commit=true) at mail-cache-transaction.c:257 #5 0x0808248a in mail_cache_transaction_get_space (ctx=0x80cb4a0, min_size=332, max_size=332, offset_r=0x0, available_space_r=0x0, commit=true) at mail-cache-transaction.c:347 #6 0x08082b90 in mail_cache_header_add_field (ctx=0x80cb4a0, field=0) at mail-cache-transaction.c:646 #7 0x08082e0e in mail_cache_add (ctx=0x80cb4a0, seq=1, field=9, data=0x0, data_size=0) at mail-cache-transaction.c:693 #8 0x0807b314 in index_mail_cache_add (mail=0x80cfca0, field=9, data=0x0, data_size=0) at index-mail.c:349 #9 0x0807c799 in index_mail_parse_header_finish (mail=0x80cfca0) at index-mail-headers.c:75 #10 0x0807ce0c in index_mail_parse_header (part=0x42130a14, hdr=0x0, mail=0x80cfca0) at index-mail-headers.c:277 #11 0x0809b3d1 in message_parse_part_header (parser_ctx=0x80d7be8) at message-parser.c:253 #12 0x0809bb01 in message_parser_parse_header (ctx=0x80d7be8, hdr_size=0x80cfd74, callback=0, context=0x0) at message-parser.c:608 #13 0x0807cf18 in index_mail_parse_headers (mail=0x80cfca0, headers=0x80d4088) at index-mail-headers.c:361 #14 0x0807d42f in index_mail_get_headers (_mail=0x80cfca0, field=0x80b0ff5 "Date") at index-mail-headers.c:535 #15 0x0807d4d9 in index_mail_get_first_header (mail=0x80cfca0, field=0x80b0ff5 "Date") at index-mail-headers.c:576 #16 0x080933a4 in mail_get_first_header (mail=0x80d4088, field=0x80b0ff5 "Date") at mail.c:82 #17 0x0807b054 in index_mail_get_date (_mail=0x80cfca0, timezone=0x0) at index-mail.c:253 #18 0x08093370 in mail_get_date (mail=0x80d4088, timezone=0x0) at mail.c:61 #19 0x0805fe97 in mail_thread_input (ctx=0x80bd580, mail=0x80cfca0) at imap-thread.c:456 #20 0x0805f933 in imap_thread (cmd=0x80c37f4, charset=0x80c3b00 "US-ASCII", args=0x80cc628, type=MAIL_THREAD_REFERENCES) at imap-thread.c:143 #21 0x08059863 in cmd_thread (cmd=0x80c37f4) at cmd-thread.c:66 #22 0x08059949 in cmd_uid (cmd=0x80c37f4) at cmd-uid.c:19 #23 0x0805a1a7 in client_handle_input (cmd=0x80c37f4) at client.c:355 #24 0x0805a2c6 in _client_input (context=0x80c37b0) at client.c:406 #25 0x080a4ba8 in io_loop_handler_run (ioloop=0x80c1740) at ioloop-poll.c:189 #26 0x080a4201 in io_loop_run (ioloop=0x80c1740) at ioloop.c:235 #27 0x08061053 in main (argc=1, argv=0xbfffe2d4, envp=0xbfffe2dc) at main.c:238 #28 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) i r eax 0x0 0 ecx 0x6 6 edx 0x42130a14 1108544020 ebx 0x3ac3 15043 esp 0xbfffdc10 0xbfffdc10 ebp 0xbfffdc18 0xbfffdc18 esi 0x80c9cb8 135044280 edi 0x14c 332 eip 0xffffe002 0xffffe002 eflags 0x246 582 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ======================================================================================

3 9

[Dovecot] beta2: strange assert
by Jeff A. Earickson 31 Jan '06

31 Jan '06

Hi, My setup: Solaris 9, mbox format, mailboxes NFS mounted from another S9 system, imap. I got the following assert yesterday: Jan 30 19:57:15 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) Jan 30 19:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) The gdb work on the core file is attached. This is a mystery because part was NULL in the core file. Weird. Jeff Earickson Colby College

2 1

[Dovecot] adding a select or a poll?
by ohp＠pyrenet.fr 31 Jan '06

31 Jan '06

Since I put my hands on dovecot, I had this recuring problem at startup: Imap-login would'nt connect to the 'default' socket. I've been strugling with the fact that it would eventually connect on a slow or moderely fast machine but not on a really fast machine. According to Unixware doc, the FIRST connect ALWAYS returns -1 and errno=EINPROGRESS AFAICT, imap loop is like this: while (1) connect if no error bu EINPROGRESS send_handshake if successfull break; end while Now, I think the time between connect and send_handshake might be too short for async connect to finish in most case. I recognize is a Unixware probleme but I think this senario can happen on any system that CAN set errno to EINPROGRESS. I think the two possibilities are 1 - remove the setting of NONBLOCK before connecting to unix sock, but that would ruin the way dovecot is written. 2 - add a poll or a select before send_handshake to be sure the socket is writable. The third way would be to tell unixware users to disable async connects methink would be a pitta. What do you think? -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0

[Dovecot] Re: extremely slow delete/move operations?
by Roger Weeks 31 Jan '06

31 Jan '06

On Jan 30, 2006, at 11:12 AM, Gregory K. Ruiz-Ade wrote: > Message: 10 > The thing is, these mail servers _are_ the local storage for the > mail spools > and home directories. There is no network involved when dovecot is > accessing the INBOX or saved mail folders. Yes, they're "NFS" > mounted, but > this is RHEL4 (linux 2.6.x), and when an NFS share is mounted from > the local > host, it's done as a bind mount, which means local disk access. I don't understand this at all. Mounting anything via NFS should only be done from a remote server, where when you type "mount" at a commandline you see something like: 10.10.10.2:/data on /var/mail type nfs (rw,nfsvers=3,addr=10.10.10.2) If your /etc/fstab or your automounts on your RHEL4 box are mouting LOCAL disks as type NFS, you have set up something very very wrong. Local disks should be mounted at boot like so: /dev/sda3 on / type ext3 (rw) Let's be certain we're clear about this. The disks where dovecot reads and writes your mboxes are local to the RHEL4 machine? If so, you're not using NFS at all. Roger Weeks

2 1

[Dovecot] Dovecot-lda/deliver - how to deliver root's mail?
by Shayne Hardesty 30 Jan '06

30 Jan '06

There's a good chance I could be missing something obvious here, as I can't find much documentation on the LDA other than on the wiki, which is sparse. Local mail delivery works for normal users, but when attempting to deliver mail for root I get this error: Jan 30 13:42:50 apollo deliver: Running as root isn't permitted Both sendmail and dovecot run as root on my server - since I don't allow shell accounts and have multiple layers of security around the server I'm okay with that. How can I tell dovecot-lda it's okay to deliver root's mail as root? Thanks, Shayne

2 1

[Dovecot] poprelay, ip v4 vs ip v6 adresses
by Gerhard Hofmann 30 Jan '06

30 Jan '06

Hi list, I would like to use poprelay as described here: http://wiki.dovecot.org/PopRelay Excerpt from my /var/log/mail.log: dovecot: 2006-01-26 11:27:52 Info: imap-login: Login: user=<planat99>, method=plain, rip=192.168.1.202, lip=192.168.1.5 dovecot: 2006-01-26 13:10:10 Info: pop3-login: Login: user=<planat99>, method=PLAIN, rip=192.168.1.202, lip=192.168.1.5 (these are only two lines but wrapped by my news client) As you can see, the logged remote ip address is in normal ip v4 style, no "ffff" stuff here. The WIKI page says that ip addresses should be in v6-mapped style, how can I achieve this? Respectively, how must I change poprelay.conf to work with my current mail.log style? TIA Gerhard

1 0

[Dovecot] Timeouts
by vmstech 30 Jan '06

30 Jan '06

Hi All - I have a dovecot imap server that I've been running merrily for 6 mths now - the 2 clients that are used on it are evolution and outlook 2003 - I daily have timeout "closed connection" issues with either of these. I have the outlook idle workaround enabled, but I dont think thats the issue - can anyone give me a hint how I can start to trouble shoot this? Thanks Glenn

1 0

Re: [Dovecot] Invisible messages
by Anne Wilson 30 Jan '06

30 Jan '06

On Saturday 28 Jan 2006 20:21, Markus Dobel wrote: > Anne Wilson wrote: > >> * ^To:.*design@lydgate.org > >> ${MAILDIR}.Design > > > > That just leaves the question of the procmail recipe. Will the > > messages end up in the right place? > > AFAIK, Maildir-folders have to end with a "/" in procmailrc. The > procmail recipe should read > > * ^To:.*design@lydgate.org > ${MAILDIR}.Design/ > > Regards, Markus Unfortunately it just doesn't work. Anne -- Registered Linux User No.293302 (http://counter.li.org/)

4 6

[Dovecot] Question about $pat in pop-before-smtp.conf
by Gerhard Hofmann 30 Jan '06

30 Jan '06

Hi, I have setup dovecot to log all successful pop3 and imap logins into /var/log/mail.log I want to use pop-before-smtp to process the log file and write a .db file where sendmail can look up ip addresses that are allowd to relay. mail.log entries look like this: dovecot: 2006-01-26 17:22:28 Info: pop3-login: Login: user=<planat25>, method=PLAIN, rip=213.83.32.125, lip=192.168.1.98 So the question is: how should $pat variable look in pop-before-smtp.conf? I tried the patterns suggested in the WIKI and they do not work. I must admit I'm a newbie to this regex stuff. BTW, would it be easier to patch my dovecot daemon to use DRAC instead? TIA Gerhard

2 2

[Dovecot] Problem with folders, dovecot-0.99.13-3.FC3 and Eudora 7.0.1
by Davide Bolcioni 30 Jan '06

30 Jan '06

Greetings, the Eudora client is attempting to create a subfolder of an existing folder, using the "Make it a folder option" which creates a directory under /home/<user>/mail/<a few paths>. Eudora is seemingly stuck in attempting to create the directory, but there is nothing under /var/log which seems useful in diagnosing the problem. Thank you for your consideration, Davide Bolcioni -- There is no place like /home.

1 0

[Dovecot] I gonna understand one day
by ohp＠pyrenet.fr 29 Jan '06

29 Jan '06

Hi, I'm still struggling with dovecot and Unixware: On my main server, I have two problems: 1- imap-login has great difficulties to connect to 'default'. I have traced it to accept in auth_master_listener.c witch fails with errno=71 (EPROTO) weird... 2- It some times works and I can log-in but imap gets killed by signal 6 (abort?) See the logs: Jan 24 12:40:25 dovecot: Dovecot v1.0.beta2 starting up Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 12:40:26 dovecot: auth(default): pgsql: Connected to postfix Jan 24 12:41:06 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=<hidden> Jan 24 12:41:06 dovecot: auth(default): client out: OK 1 user=ohp Jan 24 12:41:06 dovecot: auth(default): master in: REQUEST 1 15482 1 Jan 24 12:41:06 dovecot: auth(default): master out: USER 1 ohp system_user=ohp uid=101 gid=130 home=/home4/ohp Jan 24 12:41:06 dovecot: imap-login: Login: user=<ohp>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 12:41:06 dovecot: imap(ohp): Trying to allocate 0 bytes Jan 24 12:41:06 dovecot: child 15812 (imap) killed with signal 6 Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 12:44:53 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:58 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:58 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 14:58:22 dovecot: Dovecot v1.0.beta2 starting up Jan 24 14:58:24 dovecot: auth(default): pgsql: Connected to postfix Jan 24 14:59:32 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 14:59:32 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 14:59:47 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=<hidden> Jan 24 14:59:47 dovecot: auth(default): client out: OK 1 user=ohp Jan 24 14:59:47 dovecot: auth(default): master in: REQUEST 1 16921 1 Jan 24 14:59:47 dovecot: auth(default): master out: USER 1 ohp system_user=ohp uid=101 gid=130 home=/home4/ohp Jan 24 14:59:47 dovecot: imap-login: Login: user=<ohp>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 14:59:47 dovecot: imap(ohp): Trying to allocate 0 bytes Jan 24 14:59:47 dovecot: child 17966 (imap) killed with signal 6 Jan 24 15:22:08 dovecot: imap-login: Disconnected: rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 15:29:04 dovecot: SIGHUP received - reloading configuration Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 15:29:05 dovecot: auth(default): pgsql: Connected to postfix Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:11 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:15 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:20 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:25 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:30 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:33 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:33 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:35 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:36 dovecot: Killed with signal 15 Jan 24 15:29:50 dovecot: Dovecot v1.0.beta2 starting up Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 15:29:51 dovecot: auth(default): pgsql: Connected to postfix Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:56 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:01 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:06 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:11 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:16 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:21 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:26 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:31 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:32 dovecot: Killed with signal 15 Any help? Timo? Would you like an account on my fast server? TIA and keep the good jobs. Regards, -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

2 2

[Dovecot] Openwebmail with Dovecot
by ftnx＠ksbase.com 29 Jan '06

29 Jan '06

KS KARICO Business Services Toronto, ON Canada http://www.karico.ca ... Cursors! Foiled Again!

1 0

Re : [Dovecot] How to make pops
by mickael.choisnard＠free.fr 29 Jan '06

29 Jan '06

Hi, I activate ssl in dovecot.conf and i open 995 in my firewall. But when i launch Eudora, i have an error : Server does not support SSL In Eudora, i choose "Required STARTTLS". Where do I have to declare my ssl certificate ? If you don't like Eudora, you can explain me with evolution. # 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 = /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 = yes

1 0

[Dovecot] pop3_logout_format equivalent for IMAP
by Chris Wakelin 29 Jan '06

29 Jan '06

Hi, I've been thinking for a while that the enhanced logging available for POP would be very useful for IMAP. In particular I'd like to log mailbox size in bytes (at the moment I have a patch that logs SELECTs and number of messages). Even better (though not in the POP code) would be to get some idea of how well the Dovecot indexes and caching are doing by logging the actual number of bytes read. I could have a go at porting the POP changes over to IMAP (programming by imitation as usual :) ) but has anybody else done this? 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 0

[Dovecot] 1.0.beta2 released
by Timo Sirainen 29 Jan '06

29 Jan '06

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the other one. v1.0.beta2 2006-01-22 Timo Sirainen <tss(a)iki.fi> + Added SQLite support. Patch by Jakob Hirsch. + Added auth_debug_passwords setting. If it's not enabled, hide all password strings from logs. + Added mail_cache_min_mail_count and mbox_min_index_size settings which can be used to make Dovecot do less disk writes in small mailboxes where they don't benefit that much. + Added --build-ssl-parameters parameter to dovecot binary - SSL parameters were being regenerated every 10 minutes, although not with all systems. - Fixed dovecot-auth crashing at startup. Happened only with some specific compilers. - base_dir was supposed to be set world-readable, not world-writable

10 18

[Dovecot] Question concerning configuration
by Christopher R. Parr 29 Jan '06

29 Jan '06

Hi! I'm using dovecot and evim4 on a debian sarge system. Now I'd like to set up exim4 using vexim (http://www.debianhowto.de/de:howtos:sarge:exim4_vexim2_courier_mailman) My question: How do I have to configure dovecot? Thanks

1 0

[Dovecot] X-Status: D
by Gerhard Wiesinger 28 Jan '06

28 Jan '06

Hello! I've some folders where I deleted some messages. They are not really deleted, but have the X-Status: D header field set. How can I force a real delete in dovecot? Thank you for the answer. Ciao, Gerhard

2 3

[Dovecot] Invisible messages
by Anne Wilson 27 Jan '06

27 Jan '06

I have pulled in a couple of messages using fetchmail and put them through a procmail filter, which has resulted in the two messages being visible in a file manager in ~/Maildir/Design/new. However, using my Imap account on this box I can't see those messages. Any hints, please? Anne

3 9

[Dovecot] Upgrade to a new system
by Daniel Davidson 27 Jan '06

27 Jan '06

Hello, I have a system that I am preparing to update that currently uses dovecot for pop and imap (will have same ip as old system). In tests, I at times re-download data from the server if I have deleted or moved it in the client and the data is still on the server (just for pop). I am guessing the UIDs generated are different on the new system. Is there any way to check and see if they are the same on each system, and if they are not, how can I move that information over. thanks, Dan

1 0

[Dovecot] nfs and pop3
by Marten Lehmann 27 Jan '06

27 Jan '06

Hi, I'm working with dovecot 1.0.beta2 for pop3 only and have set index=memory, so no indizes are created on the disk. pop3_uidl_format is set to %f. The maildirs are located on an nfs-share. So generally, this setup is very similar to what qmail-popup and qmail-pop3d does. However, everytime I'm switching from qmail-pop3d to dovecot, the system load increases from less than 2 to more than 30 (and later up to 60 and more). The problem is I/O, probably caused by nfs-access. But what is causing this accesses? qmail-pop3d just takes filenames as UIDL, and moves the mails from new to cur, reads them to send them to the client or deletes them. This is working fine. But what is dovecot doing? There must be a lot more things that cause that high I/O load. Indizes are disabled, so they cannot be the cause any longer. Any ideas? I just want to switch to dovecot at some point finally without having qmail-pop3d as backup. Regards Marten

4 7

[Dovecot] gcc 2.95 compile errors
by Chris Wakelin 27 Jan '06

27 Jan '06

Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real PATH environment variable (which didn't include the gcc3 location). Should I be worried? Chris ostream-file.c: In function `o_stream_writev': ostream-file.c:126: warning: `ret' might be used uninitialized in this function ostream-file.c: In function `_send_istream': ostream-file.c:671: warning: assignment from incompatible pointer type mail-cache.c: In function `mail_cache_lock': mail-cache.c:374: warning: `ret' might be used uninitialized in this function mail-index-transaction.c: In function `mail_index_update_header_ext': mail-index-transaction.c:710: warning: unused parameter `t' mail-index-transaction.c:711: warning: unused parameter `ext_id' mail-index-transaction.c:711: warning: unused parameter `offset' mail-index-transaction.c:712: warning: unused parameter `data' mail-index-transaction.c:712: warning: unused parameter `size' maildir-storage.c:891: warning: missing initializer maildir-storage.c:891: warning: (near initialization for `maildir_storage.pool') maildir-storage.c:926: warning: missing initializer maildir-storage.c:926: warning: (near initialization for `maildir_mailbox.pool') mbox-sync.c: In function `mbox_sync_seek_to_uid': mbox-sync.c:921: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_handle_eof_updates': mbox-sync.c:1228: warning: assignment from incompatible pointer type mbox-sync.c:1287: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_update_index_header': mbox-sync.c:1330: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_do': mbox-sync.c:1418: warning: assignment from incompatible pointer type mbox-sync.c: In function `mbox_sync_has_changed': mbox-sync.c:1496: warning: assignment from incompatible pointer type mbox-storage.c:1045: warning: missing initializer mbox-storage.c:1045: warning: (near initialization for `mbox_storage.pool') mbox-storage.c:1080: warning: missing initializer mbox-storage.c:1080: warning: (near initialization for `mbox_mailbox.pool') dbox-storage.c:630: warning: missing initializer dbox-storage.c:630: warning: (near initialization for `dbox_storage.pool') dbox-storage.c:665: warning: missing initializer dbox-storage.c:665: warning: (near initialization for `dbox_mailbox.pool') dbox-transaction.c: In function `dbox_transaction_commit': dbox-transaction.c:20: warning: unused parameter `flags' dbox-transaction.c: In function `dbox_transaction_rollback': dbox-transaction.c:77: warning: unused variable `dbox' auth-server-connection.c: In function `auth_server_connection_new': auth-server-connection.c:200: warning: `fd' might be used uninitialized in this function auth-master-connection.c: In function `master_input_die': auth-master-connection.c:145: warning: unused parameter `conn' main.c: In function `create_unix_listener': main.c:101: warning: `fd' might be used uninitialized in this function dict-process.c:96: warning: `dict_process_listen' defined but not used master-settings.c:360: warning: missing initializer master-settings.c:360: warning: (near initialization for `default_settings.listen_ip') quota-storage.c: In function `quota_save_init': quota-storage.c:165: warning: assignment from incompatible pointer type -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 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] chained ssl cert not working
by harryp＠dmsnev.com 27 Jan '06

27 Jan '06

I am running a production server with 40 pop3 users using dovecot 0.99.14. I am trying to get a chained certificate installed that I purchased through godaddy.com. I need some clarification on how to do this. I found some really vague instructions on the dovecot wiki http://wiki.dovecot.org/ChainedSSLCertificates?highlight=%28chained%29 Unfortunately these instructions are very confusing for me. I also found someone else who asked a similar question http://dovecot.org/list/dovecot/2005-June/007528.html I have tried to get this to work, but have failed. Could someone please explain this better. I don't understand if all of these keys/certificates go into 1 file or what. I need an example if someone could be so kind as to take a moment of their time. Thanks for any help.

3 3

[Dovecot] out of memory error
by Pavel Volkovitskiy 27 Jan '06

27 Jan '06

Hello I have this errors in my dovecot.log every day or two: ============================================= ... dovecot: Jan 24 10:28:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:01 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:03 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:41 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:29:56 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:36 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:38 Error: auth-worker(default): Out of memory (Needed 8164 bytes) dovecot: Jan 24 10:30:39 Error: auth-worker(default): Out of memory (Needed 52 bytes) dovecot: Jan 24 10:30:41 Error: auth-worker(default): pool_system_malloc(): Out of memory dovecot: Jan 24 10:30:41 Error: child 3576 (auth-worker) returned error 83 (Out of memory) ============================================= I use dovecot 1.0-beta1 login_process_size = 128 login_process_per_connection = no login_processes_count = 5 login_max_processes_count = 128 login_max_logging_users = 256 -- Pavel

3 6

[Dovecot] How to make pops
by mickael.choisnard＠free.fr 27 Jan '06

27 Jan '06

Hi, I use dovecot (pop) with gentoo but it's not securize. I would like to use pops but i don't how to do this. I think i have to use certificates... This my dovecot.conf : protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * ssl_disable = no login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam dovecot auth_user = root auth_verbose = yes auth_debug = yes Thanks for your help

2 1

[Dovecot] Dovecot don't recognise new messages in maildir /new
by Tim Wagner 27 Jan '06

27 Jan '06

Hi, i'm google for it and i searched the archives, but i can't find the problem i have or a hint for a solution. I'm using Postfix as MTA, the new messages deliver by postfix to the maildir: /mail/domain.tld/userpart/new/ Dovecot sometimes show the new mails directly (it's very unusual) but mostly it needs for an hour that dovecot recognize the new messages. Reconnecting of the client don't help. Tested with Thunderbird, Sylpheed-Claws, mutt and muttng. Is there a bug known or do i something wrong?

3 5

[Dovecot] 1.0beta2 build error
by Peter Lindgren 27 Jan '06

27 Jan '06

Hi! I received the following error (I ran ./configure and make without options) when running make install: Making all in auth make: don't know how to make db-ldap.h. Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src/auth. *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2/src (line 284 of Makefile). *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2 (line 340 of Makefile). *** Error code 1 Stop in /tmp/dovecot-1.0b2/dovecot-1.0.beta2 (line 224 of Makefile). This is what I found: # ls src/auth/db-ldap.* src/auth/db-ldap.c src/auth/db-ldap.o # find . -name 'db-ldap.*' -print ./src/auth/db-ldap.c ./src/auth/.deps/db-ldap.Po ./src/auth/db-ldap.o I didn't find a db-ldap.h anywhere in /usr either. Any hints? I run OpenBSD 3.7 on sparc. /Peter -- Peter Lindgren, dataingenjör E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

2 2

[Dovecot] Fwd: Weird problem opening mbox in beta1/2
by Chris Wakelin 27 Jan '06

27 Jan '06

Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)". Reverting to beta1, it also failed with the same error! I've deleted indexes, restored the mbox from a backup made in October (no changes) and I still get the error. It *does* open OK in 1.0-stable. I've put it through mboxcrypt.pl, deleted the UW-IMAP pseudo-message (which wasn't converted properly by mboxcrypt) and it still fails to open with a similar error, so I've sent it to Timo (gzipped, of course!) I've e-mailed this to the list minus the attachment as sending unsolicited 1MB attachments is unfriendly! However, if anybody wants to look at it, please let me know. Best Wishes, Chris P.S. The past participle of "shrink" is "shrunk" not "shrinked" - it's yet another irregular English verb :) -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 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 -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- 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 4

[Dovecot] Hang in 1.0.alpha4
by Mark Plaksin 26 Jan '06

26 Jan '06

My IMAP client hangs intermittently. When it does, Dovecot has prematurely stopped sending a response and entered the poll loop. My client is waiting for more data and Dovecot is waiting for an IMAP command. This problem seems to occur when I connect to the dovecot process over the network and when I run the imap binary directly via an SSH tunnel. Below is truss output from the imap process for one of the hangs. It is responding to a FETCH, gets EAGAIN, and then seems to give up sending the rest of the message and enters the poll loop. Below that is the log from my IMAP client to show its side of the story. Nothing shows up in the normal Dovecot log. I haven't caught it in the act recently when running with rawlog. But rawlog output from before I was running with truss shows that Dovecot does not think it has finished sending its response. truss output: 12951: stat64("/home/happy/Mail/banner-ss", 0xFFBFF200) = 0 12951: fstat64(12, 0xFFBFF388) = 0 12951: stat64("/home/happy/Mail/.imap/banner-ss/dovecot.index", 0xFFBFF2F0) = 0 12951: fstat64(18, 0xFFBFF388) = 0 12951: pread64(18, "\n F r o m b e v e r l".., 4096, 1592560) = 4096 12951: pread64(18, " S u n G a r d * S C".., 4094, 1596656) = 4094 12951: pread64(18, " M i c r o s o f t S a".., 4094, 1600750) = 4094 12951: pread64(18, " r g a r e t . d i l l a".., 4094, 1604844) = 3720 12951: pread64(18, 0x0025EEA2, 374, 1608564) = 0 12951: pread64(18, 0x0025EEA2, 374, 1608564) = 0 12951: pread64(18, " R e t u r n - P a t h :".., 4096, 1592616) = 4096 12951: write(1, " * 2 5 0 F E T C H ".., 4073) = 4073 12951: pread64(18, " a l v e r n , P A ".., 4095, 1596712) = 4095 12951: write(1, "\n W i l l i a m B . ".., 4060) = 4060 12951: pread64(18, " l ( i n c l u d i n g".., 4095, 1600807) = 4095 12951: write(1, "\n & # 8 2 2 6 ; < / b".., 4069) = 4069 12951: pread64(18, " m o z - t x t - l i n k".., 4095, 1604902) = 3662 12951: write(1, "\n ".., 4079) Err#11 EAGAIN 12951: write(1, "\n ".., 4096) Err#11 EAGAIN 12951: poll(0x000A0AD0, 3, 533) = 1 12951: write(1, "\n ".., 4096) = 4096 12951: poll(0x000A0AD0, 2, 532) = 0 12951: poll(0x000A0AD0, 2, 0) = 0 12951: poll(0x000A0AD0, 2, 999) (sleeping...) 12951: poll(0x000A0AD0, 2, 999) = 0 Here's the log from my IMAP client. I removed email addresses and most of the body of the message to protect the innocent. The "BYE" was caused by me running 'kill $PID' on the imap process. 3551 OK Fetch completed.! 3552 UID FETCH 252 BODY.PEEK[] * 250 FETCH (UID 252 BODY[] {16341}! Return-Path: <abc(a)usg.edu>! Received: from usg.edu (abc.usg.edu [1.2.8.1])! by abc.usg.edu (8.12.11/8.12.11) with ESMTP id j9KFqoga012884! for <abc(a)USG.EDU>; Thu, 20 Oct 2005 11:52:50 -0400 (EDT)! Message-ID: <4357BD52.1020506(a)usg.edu>! Date: Thu, 20 Oct 2005 11:52:50 -0400! From: abc <abc(a)usg.edu>! User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)! X-Accept-Language: en-us, en! MIME-Version: 1.0! To: abc(a)usg.edu! Subject: [Fwd: [Fwd: Fw: Java Library Problem]] - URGENT, I'm sorry...! Content-Type: multipart/mixed;! boundary="------------010604070704040405060605"! X-USG-MailScanner: Found to be clean! X-USG-MailScanner-SpamCheck: ! X-MailScanner-From: abc(a)usg.edu! ! This is a multi-part message in MIME format.! --------------010604070704040405060605! Content-Type: multipart/alternative;! boundary="------------040009050704020209010709"! ! ! --------------040009050704020209010709! Content-Type: text/plain; charset=us-ascii; format=flowed! Content-Transfer-Encoding: 7bit! ! Guys,! Please create a ssh login on... from ! 24 hours now) with testing. His account should look like Patrick ! I've requested a static IP from Dan.! ! ...! </pre>! </body>! </html>! ! --------------040009050704020209010709--! ! --------------010604070704040405060605! Content-Type: text/x-vcard;! Content-Transfer-Encoding: 7bit! Content-Disposition: attachment;! ! begin:vcard! ...! tel;work:(xxx) xxx-2000! tel;fax:(xxx) xxx-xxxx! url:http://www.u* BYE Server shutting down.! imap(happy): Warning: Killed with signal 15 ------------------------------------------------------------------------------ The mail message in question actually ends like this: tel;work:(xxx) xxx-2000 tel;fax:(xxx) 583xxx-xxxx url:http://www.usg.edu version:2.1 end:vcard --------------010604070704040405060605--

4 12

[Dovecot] dovecot.index.log.2 needed?
by Jeff A. Earickson 26 Jan '06

26 Jan '06

Hi, I just discovered a whole lot of dovecot.index.log.2 files in people's .imap folders? Are these files needed in the long term? Or can they be zapped if they are more than X days old? Jeff Earickson Colby College

2 1

[Dovecot] dovecot 1.0alpha5 not deleting messages from mbox
by Andrew Mendelsohn 26 Jan '06

26 Jan '06

Hi, I have had some problem with duplicate emails using dovecot1.0alpha5using the prebuilt testing binaries on a debian stable/testing 3.1system. I am running both pop3d and imap, but all users are just usingpop3d. I am using mbox format. Users are using Thunderbird 1.5 to access emails. Dotlocks are used,postfix is the email agent. Note that dovecot/[postfix are running in avserver. In debugging the dovecot log, it seems to me that dovecot thinks thatit is deleting the messages, but actually nothing is happening. here is a log of a user logging in and what happens after logging out: dovecot: 2006-01-20 21:41:04 Info: pop3-login: Login:user=<user2(a)example.org>, method=PLAIN, rip=10.8.0.6,lip=192.168.99.5, TLS dovecot: 2006-01-20 21:41:04 Error: pop3(user2(a)example.org): mbox sync:Expunged message reappeared in mailbox /home/vmail/user2(a)example.org(UID 5668 < 5691, seq=2, idx_msgs=0) dovecot: 2006-01-20 21:45:33 Info: pop3(user2(a)example.org): Logout.top=0/0, retr=20/ del=20/20, size=29362389 a quick check show that mbox size has not been changed -- none of the20/20 files have been deleted, even though dovecot states del=20/20 ! Mboxes grow quite large, sometime the problem resolves itself. Interestingly, if I stop dovecot and restart it, on the next access to pop3 all of the messages are deleted correctly and the mboxreturns to the default size. Any ideas? Andy --------------------------------- Yahoo! Photos Showcase holiday pictures in hardcover Photo Books. You design it and well bind it!

2 1

[Dovecot] Dovecot using static uid gid
by Alexandru Ionescu 26 Jan '06

26 Jan '06

Hi All I have postfix deliver the mail in virtual maildirs using the UID of user dovecot. I authenticate users trying to access their mailboxes via IMAP through winbind. The authentication is successfull but dovecot logs imap(username): Date "Error: openidir (vmail/domain/username) failed: Permission denied. I tried to insert in dovecot.conf: static uid=97 gid=97 home=/vmail/domain but I get a report that parameters are missing. Does anybody know the the exact syntax for the static directive? Alexandru

2 1

[Dovecot] Making dovecot and postfix play together
by Anne Wilson 26 Jan '06

26 Jan '06

I am encountering 'transport problems' in postfix, and I can't tie them down. I'm beginning to wonder whether I have conflicting settings in the various parts of the mail server. I have been advised separately by a number of people, so it is entirely possible. I am, therefore, attempting to check every detail of my setup. I was advised to put 'MAIL=/home/$USER/MailDir:INBOX=/var/spool/mail/$USER' into /etc/profile 'because that's the way that dovecot likes it'. Is this correct? I'm using 0.99.14 on Fedora Core 4. Dovecot does appear to be working correctly. I can drag messages to the mailboxes. The problem appears to be in postfix. Fetchmail can download the messages, but they are sticking in postfix's queue. I'm still working on that, but would like confirmation that I was right to follow the advice given above. Anne

3 3