- dovecot - dovecot.org

[Dovecot] Wiki Documentation: missing item
by Luigi Rosa 27 Dec '05

27 Dec '05

In the "MainConfig" section of the online documentation (http://wiki.dovecot.org/) one item in the "logging" section is missing. The missing item is "syslog_facility" described in the dovecot-example.conf file. Ciao, luigi -- +--[Luigi Rosa]--

1 0

[Dovecot] Migrating from Courier-IMAP to Dovecot
by Andreas Mimz 27 Dec '05

27 Dec '05

Hi! I'm currently trying to migrate from courier-imapd to dovecot... Unfortunately I'm experiences some difficulties here... Since I don't want any user to notice the change of the server backend I've tried changing the namespace in dovecot.conf to namespace private { separator = . location = maildir:~/Maildir prefix = INBOX. inbox = yes hidden = no } With this setting almost everything works fine! Almost... ;-) Squirrelmail won't show 'INBOX' on the left side of the folder tree... If I configure dovecot without the 'INBOX.' prefix it works fine in Squirrelmail, except that all other eMail clients show all sub-folders as a sub-folder of root and not the inbox... root \- inbox \- sent \- trash \- drafts \- private \- spam instead of root \- inbox | \- sent | \- trash | \- drafts | \- private | \- spam any Idea what could be wrong? I've read the wiki about the courier-migration and also tried the conversion script ... but something is wrong I'm afraid... thanks in advance, Andreas

2 4

[Dovecot] dovecot behaving badly after upgrade..
by daniel petre 27 Dec '05

27 Dec '05

i upgraded dovecot from 0.99 to the last version and it doesnt seem to work anymore.. im using vpopmail userdb and i get this in the logs : dovecot: Dec 18 03:42:08 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=81.x.x.x rip=81.x.x.x resp= dovecot: Dec 18 03:42:08 Info: auth(default): client out: CONT 1 dovecot: Dec 18 03:42:08 Info: auth(default): client in: CONT 1 AGRhbmlAbGludXhzb2x1dGlvbnMucm8AcG9jcG9j dovecot: Dec 18 03:42:08 Error: auth(default): vmysql: sql error[3]: MySQL server has gone away dovecot: Dec 18 03:42:08 Info: auth(default): vpopmail(dani(a)domain,81.x.x.x): unknown user dovecot: Dec 18 03:42:09 Info: auth(default): client out: FAIL 1 user=dani@domain dovecot: Dec 18 03:42:09 Info: auth(default): client in: AUTH 2 PLAIN service=POP3 lip=81.x.x.x rip=81.x.x.x resp=AGRhbmlAbGludXhzb2x1dGlvbnMucm8AcG9jcG9j anyone encountered this? mysql is not away, i edited dovecot.conf carefully. what am i missing? thanks -- 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.

3 3

[Dovecot] inbox problems when moving from server to server
by Eric S. Johansson 27 Dec '05

27 Dec '05

this is probably an FAQ but I moved all the mailboxes from a gentoo server to an ubuntu one and all old inbox messages "disappeared" for. New messages appear and can be read, deleted etc. the old messages can still be found in the Maildir/cur directory like they were on the old mail server. Ownership was changed to user:user and is 600 permissions. Dovecot version: 0.99.14-1ubuntu1 all other mailboxes are fine, all messages visible as far as we can tell. ideas?

1 0

[Dovecot] dovecot and virtual mailbox - suggestions please
by David Bain 26 Dec '05

26 Dec '05

I've setup postfix to delivered my mail to a maildir located at /var/spool/virtual_mailboxes/mydomain.com/myuser My postgresql database called 'mails' has a user table setup as follows: CREATE TABLE users ( userid VARCHAR(128) NOT NULL, password VARCHAR(128), realname VARCHAR(128), uid INTEGER NOT NULL, gid INTEGER NOT NULL, home VARCHAR(128), mail VARCHAR(255), PRIMARY KEY (userid) ); What would the query look like in my dovecot-pgsql.conf file to retrieve the appropriate INBOX information? mine currently looks like this. user_query = SELECT '/var/spool/virtual_mailboxes/'||home AS home, uid, gid FROM users WHERE userid = '%u' The user authenticates fine via pop, yet I keeping getting the following error. -*ERR No INBOX for user*

2 4

[Dovecot] Dovecot 1.0alpha imap uid store command response
by Tomas Kuliavas 25 Dec '05

25 Dec '05

Hi, Dovecot 1.0alpha (tested 0.99.14, 1.0alpha1, 1.0alpha4 and 1.0alpha5) does not return UID number in 'UID STORE uid-number +FLAGS (\Seen)' command response. Issue is not present in 0.99.14. >From IMAP RFC http://www.isi.edu/in-notes/rfc3501.txt 6.4.8. UID Command ... However, server implementations MUST implicitly include the UID message data item as part of any FETCH response caused by a UID command, regardless of whether a UID was specified as a message data item to the FETCH. ... Could you fix your IMAP server? -- Tomas

2 1

[Dovecot] dovecot - postgresql ERR No INBOX for user.
by David Bain 24 Dec '05

24 Dec '05

I've setup dovecot to authenticate against postgresql. But I consistently get a "No INBOX for user" error when I try to do pop requests. Any pointers would be helpful. Postfix deposits mails in maildirs in the format /var/spool/virtual_mailboxes/{domain}/{username}/ below is the result of a telnet test (altered slightly of course, but gives the idea) telnet localhost 110 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. +OK dovecot ready. USER personx(a)myxdomxain.net +OK PASS herexxxx +OK Logged in. -ERR No INBOX for user. Connection closed by foreign host. here is my dovecot.conf file /etc/dovecot-pgsql.conf =================== ## Dovecot 1.0 configuration file protocols = imap imaps pop3 # "host:port". imap_listen = * pop3_listen = * login = imap login = pop3 # to make sure that users ca here is my dovecot-pgsql.conf file default_mail_env = maildir:/var/spool/virtual_mailboxes/%lu/%u/Maildir # Authentication process name. auth = default auth_user = root auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf /etc/dovecot-pgsql.conf ==================== connect = host=localhost dbname=mails user=xxxxxxname password=xxxxxxx default_pass_scheme = PLAIN password_query = SELECT password FROM users WHERE userid = '%u' user_query = SELECT '/var/spool/virtual_mailboxes/'||home AS home, uid, gid FROM users WHERE userid = '%u' #user_query = SELECT '/%n' as home,uid, gid FROM users WHERE userid = '%u'

1 0

[Dovecot] Corrupted transaction log file
by Will Ling 24 Dec '05

24 Dec '05

Hi, I am new to dovecot and have just got it up and running on mandrake 8.2. Dovecot seems to be running OK, I can telnet in and log in and Mail on OS X will get the folder list but if a client selects a mail box I get an error back. I cannot find any help anywhere on the errors I'm getting so I hope this is the right place to ask. Please see the log file below. Any clues to the problem would be greatly appreciated. This was after an attempted login from Mail then another try using Mutt locally: dovecot: Dec 24 16:17:44 Info: Dovecot v1.0.alpha5 starting up dovecot: Dec 24 16:17:51 Info: imap-login: Login: user=<will>, method=PLAIN, rip =10.0.128.58, lip=10.0.128.55 dovecot: Dec 24 16:17:51 Error: imap(will): Corrupted transaction log file /home /will/mail/.imap/test/dovecot.index.log: record size too small (type=0x20, offse t=24, size=0) dovecot: Dec 24 16:17:51 Error: imap(will): Lost transaction log file /home/will /mail/.imap/test/dovecot.index.log seq 2 dovecot: Dec 24 16:17:51 Error: imap(will): Lost transaction log file /home/will /mail/.imap/test/dovecot.index.log seq 2 dovecot: Dec 24 16:17:56 Error: imap(will): Corrupted transaction log file /home /will/mail/.imap/INBOX/dovecot.index.log: record size too large (type=0x20, offs et=24, size=201326616, end=48) dovecot: Dec 24 16:17:56 Error: imap(will): Lost transaction log file /home/will /mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Dec 24 16:17:56 Info: imap-login: Login: user=<will>, method=PLAIN, rip =10.0.128.58, lip=10.0.128.55 dovecot: Dec 24 16:17:56 Error: imap(will): Lost transaction log file /home/will /mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Dec 24 16:17:56 Error: imap(will): Lost transaction log file /home/will /mail/.imap/INBOX/dovecot.index.log seq 2 dovecot: Dec 24 16:18:46 Error: imap(will): Corrupted transaction log file /home /will/mail/.imap/INBOX/dovecot.index.log: record size too large (type=0x20, offs et=24, size=603979800, end=48) dovecot: Dec 24 16:18:46 Info: imap-login: Login: user=<will>, method=PLAIN, rip =127.0.0.1, lip=127.0.0.will1, secured Regards, Will -- Will Ling

1 0

[Dovecot] PATCH: Dovecot SASL authentication for Postfix 2.3-20051220
by Timo Sirainen 24 Dec '05

24 Dec '05

Tested with PLAIN authentication. Doesn't require any external libraries. Building: make makefiles CCARGS="-DUSE_SASL_AUTH" If you want Cyrus SASL support also (eg. for SASL client), just follow SASL_README instructions normally. main.cf: smtpd_sasl_type = dovecot # non-chrooted smtpd: #smtpd_sasl_path = /var/spool/postfix/private/auth # chrooted smtpd: smtpd_sasl_path = /private/auth dovecot.conf: auth default { .. socket listen { client { path = /var/spool/postfix/private/auth mode = 0666 } } }

2 1

[Dovecot] Re: PATCH: Dovecot SASL authentication for Postfix 2.3-20051220
by wietse＠porcupine.org 23 Dec '05

23 Dec '05

I'm adding the finishing touch to the Postfix Dovecot plug-in, to be released with snapshot 20051223. The plug-in code quality is generally very good. I had two observations, both of minor importance: - The authentication server protocol uses the TAB character as a delimiter, so it is critical that legitimate user names don't contain this character. This is of course trivial to ensure with the authentication server implementation, so I will not worry about it. - I noticed that the plug-in did not satisfy one Postfix principle, namely that operations be bounded in time. I added a time limit for connect, read and write operations. Postfix will time-bound all operations anyway, but the diagnostics of the watchdog timer are less specific and therefore less useful. Wietse

2 1