- dovecot - dovecot.org

[Dovecot] Re: Warning, newbie!
by Pete 18 Mar '05

18 Mar '05

To make things clearer, this is where I am at now when I login from Mutt. FreeBSD 4.11 Dovecot -0.99.13 Postfix current Mar 18 09:28:15 slippery dovecot: Killed with signal 15 Mar 18 11:10:38 slippery imap(pete): We couldn't drop root group privileges Mar 18 11:10:38 slippery dovecot: child 97190 (imap) returned error 89 -- Pete http://milneweb.com http://nomorevirus.com

1 0

[Dovecot] Moving from 0.99 to 1.0-stable
by Jim Trigg 18 Mar '05

18 Mar '05

What is involved in migrating from 0.99 to 1-stable? (I'd be creating a FreeBSD port to work with, but the main question I have is what would need to be done to configuration files.) Thanks, Jim -- Jim Trigg, Lord High Everything Else O- /"\ Hostmaster, Huie Kin family website \ / ASCII RIBBON CAMPAIGN Verger and System Administrator, X HELP CURE HTML MAIL All Saints Church - Sharon Chapel / \

2 1

[Dovecot] error
by Pete 18 Mar '05

18 Mar '05

Hi, I am getting this error in my syslog when I try to access with Mutt. Mar 18 09:06:55 slippery imap(pete): We couldn't drop root group privileges This is more difficult to get running that I expected but I will stick with it a little longer. -- Pete http://milneweb.com http://nomorevirus.com

2 2

[Dovecot] postfix + SMTP AUTH using DOVECOT AUTH DAEMON
by Ing. Alejandro Rodriguez 18 Mar '05

18 Mar '05

hi ppl I'm the new member of the list. Looking at recent messages look like there is a way to do SMTP AUTH in postfix using the Dovecot AUTH daemon. Currently my Dovecot installation auth again PAM (local users) and a simple shadow file (for virtual users, I plan to move to MYSQL later). I don't want to have different databases one for dovecot a one for SASL. Where I can found the POSTFIX patch, or better, some kind of helper daemon for Postfix. thx A

2 1

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

17 Mar '05

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

1 1

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

17 Mar '05

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

4 4

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

16 Mar '05

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

2 1

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

16 Mar '05

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

2 1

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

16 Mar '05

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

3 4

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

16 Mar '05

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

2 1