December 2004 - dovecot

[Dovecot] IMAP - many folders?
by piotr＠mallorn.ii.uj.edu.pl 05 Dec '04

05 Dec '04

Hi, I've been reading the list and it seems the answer to my (soon to be asked question) is no, at least with 0.99, but I'll ask to be sure. I have following setup: new mail goes to ~/Mail/Maildir, except for mailing lists which are moved by procmail to ~/Mail/mailing_lists/name, spam which goes to ~/Mail/spam. Read mail is moved by mutt to ~/Mail/read. Everything is in maildir format. Is it possibile to configure dovecot in such a way to allow user to access all those mail folders thorough imap/pop? User can access ~/Mail/Maildir by setting default_mail_env, but so far nothing else. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!

9 17

[Dovecot] (_send_istream): assertion failed:
by Kim Culhan 05 Dec '04

05 Dec '04

This is on FreeBSD 5.3, is this fixed in -test or CVS ? Log message is below.. dovecot: Dec 05 07:48:08 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Dec 05 07:48:08 Error: child 42086 (imap) killed with signal 6 -kim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

[Dovecot] 0.99.12-rc1
by Timo Sirainen 05 Dec '04

05 Dec '04

http://dovecot.org/rc/ Just gathered the patches in dovecot.org/patches/ and a few more that I think have been sent to this list before. If there's anything missing, please tell. - Fix memory leaks in LDAP, MySQL and PGSQL userdb/passdb - Fix hanging when parsing mails that have over 4096 bytes in one line (SMTP servers normally don't allow over 1000 bytes so it shouldn't be much of a problem) - FETCH BODYSTRUCTURE sometimes giving a wrong reply (eg. with FETCH (BODYSTRUCTURE RFC822.SIZE) if it wasn't cached) - Never return more than one INBOX in LIST even if there are such files. They don't work anyway and it just confuses clients. - mbox: Don't allow creating INBOX directory by creating/renaming mailboxes under it. They just wouldn't work. - POP3: Don't return PLAIN in SASL list. We don't support initial SASL responses, so it only breaks with most clients that try to use it.

3 6

AW: [Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

> If you really want to use maildir, you can have procmail deliver to > maildirs: > (in .procmailrc): > DEFAULT=$HOME/Maildir/ > > Note the trailing slash - that's the kicker. > > Then tell Dovecot to use maildir. > > If you want to mix and match mailbox formats per user, then you'll > need to use an auth database that allows setting this (passwd-file, or > maybe ldap or sql). Thanks, Jon! I think now I get the picture. I will start playing around with procmail and the with dovecot auth options. Carsten

1 0

[Dovecot] newbie question
by Grammes, Carsten 03 Dec '04

03 Dec '04

Hello all, just managed to install dovecot as imap server on a Suse Linux box. Now running fine with mbox format. A question regarding maildir or mbox. The MDA (in my case sendmail, Mlocal = procmail) stores mbox format. Do have to modify the local mailer to store maildir format or does dovecot convert automatically from mbox when I tell dovecot to use maildir format? Thanks, for any hint. Carsten

2 1

[Dovecot] Maildir/mbox on a per-user basis
by Jon Nathan 03 Dec '04

03 Dec '04

Hello, The Wiki indicates that Dovecot can do either mbox or Maildir on a per-user basis: default_mail_env can be overridden in userdb for each user. This works with userdbs supporting the "mail" attribute (eg. passwd-file, SQL, LDAP). How exactly does one do this for passwd-file? Thanks, -Jon -- Jon Nathan jon(a)rupture.net

9 8

[Dovecot] master or client
by Kirill Miazine 03 Dec '04

03 Dec '04

Hello, Dovecot auth protocol 1.0 defines differend command sets for client and master. How can a daemon distinguish a master connection from a client connection? Clients do send CPID and master does not. I have following auth configuration: auth external { socket connect { master { path = /var/state/dovecot/login/master-auth } } } I try to learn my authentication daemon to learn to speak with Dovecot. I fire up my master.py and try to login via pop3 as foo:bar. Below is what my master.py receives from Dovecot (master and client), VERSION commands are not shown: km@thinkpad:/home/km > ./krot/sbin/master.py CPID : ['11915'] CPID : ['11915'] CPID : ['16652'] CPID : ['11915'] AUTH : ['1', 'PLAIN', 'service=POP3', 'secured', 'lip=127.0.0.1', 'rip=127.0.0.1', 'resp=AGZvbwBiYXI='] REQUEST : ['9', '11915', '1'] CPID : ['16652'] (In the above output command and parameters are parsed.) The protocol specification is mentioning a separate SERVICE command in the client's greeting. I can't let my daemon die if the master issues DIE. Why should a server exit when it receives DIE? Can anybody provide an example dialog of an authentication request that is successful and a reques that fails because of a bad password. Thanks, Kirill -- They make a desert and call it peace. -- Tacitus

2 2

[Dovecot] pop3 with lmos results in multiple downloads
by Juerd 03 Dec '04

03 Dec '04

One of our users wants to use POP3 with leave-mail-on-server (LMOS). That's great and works well for most people. But for some reason, they MUA (outlook) downloads messages more than once. As the MUA asks for messages, I'm sure it's Outlook's fault, but I was wondering if there is anything that can be done about this on the servern side, or if anyone knows how to fix Outlook. I'm sending this here, because they report that with non-dovecot servers it does work correctly. They do not want IMAP, because they want to use Outlook, which cannot support both Exchange and IMAP simultaneously. This user has multiple accounts, and only for some of them things go wrong. A temporary fix is to remove the mail from the server once, but after a few more messages arrive, the problem starts all over again. Please help. Regards, Juerd

3 3

[Dovecot] imap: assertion failed
by Kim Culhan 03 Dec '04

03 Dec '04

This error is returned when reading a certain message using Squirrelmail. Any help on tracing the cause of this is greatly appreciated. >From the logs: dovecot: Nov 20 13:00:29 Error: IMAP(kimc): file ostream-file.c: line 643 (_send_istream): assertion failed: (instream->v_offset <= in_size) dovecot: Nov 20 13:00:29 Error: child 27873 (imap) killed with signal6 -kim __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

2 1

[Dovecot] Problem getting incoming mail to IMAP inbox
by Jeff Sutherland 03 Dec '04

03 Dec '04

I have dovecot-0.99.10.5 on Fedora Core 2 installed and otherwise operating using Maildir format for the folders, Kmail as the email client. Got through all the ssl and other security configuration fine, but have one last problem: I can't read the incoming mail from /var/spool/mail/%u. Tried several 'default_mail_env' settings, including none at all, to no avail. When I try to check in new mail to the inbox, the only messages are "Transmission Complete, no new messages" Tried this setting for example: default_mail_env = maildir:~/Maildir/:INBOX=/var/spool/mail/%u but to no avail. Is something getting cocked up because the folders are all in maildir format and the incoming mail spool is in mbox format? I checked permissions, they seem ok. Kmail can pull the messages in just fine to its local folder inbox, it just seems that dovecot can't read the mail spool file for some reason. All the other maildir folders work fine. ????????? Regards, -Jeff -- Secure your email with Gnu Privacy Guard and Mozilla, the open source cross platform solution for Windows, Linux, and Mac OS X. See http://enigmail.mozdev.org/

2 1