- dovecot - dovecot.org

[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

[Dovecot] Thinking about switching from courier-imap to Dovecot: 2 simple questions
by kadafax 23 Dec '05

23 Dec '05

Hi, I'm using RHEL4 and since the dovecot RPM is present in the main repository, I'm thinking about switching from courier-imap (with whom I've got trouble to update) to Dovecot. Here are two questions about Dovecot (google didn't answer me): 1. Is it possible for dovecot to use the bind mecanism against ldap for authentification purpose. My main concern is to avoid the clear-text password in the dovecot-ldap.conf file. With courier-imap, the process simply bind to the ldap tree with the users's supplied login/password. No need for a special authentification purpose user. 2. Does imap's dovecot implementation support folders imbrication (more than one level folders) ? Thanks, kfx.

3 3

RE: [Dovecot] Vacation Message HOWTO
by Joshua Goodall 23 Dec '05

23 Dec '05

John Peacock wrote: > It's probably possible to use with any LDA which support delivery > scripts (e.g. .forward files). The CVS version of dovecot-lda has Sieve script support, and it works well. http://wiki.dovecot.org/moin.cgi/LDA - Joshua.

1 0

[Dovecot] Dovecot & pam_mkhomedir
by Stroller 22 Dec '05

22 Dec '05

Hi there, Does anyone have Dovecot working correctly with pam_mkhomedir, please? I seem to be going through quite a number of IMAP servers this week, trying to find one that will not only authenticate against a Windows domain but which will also create home directories for users the first time they log in. I'm using winbind to do the authentication & that seems to be doing the trick in the first instance - if I log in using Squirrelmail I see entries written to the system log saying: Dec 16 11:58:35 baby pam_winbind[9319]: user 'ned' granted access I have set Dovecot to log to /var/log/mail and in that I see only three entries saying: imap-login: Dec 16 11:58:36 Info: Login: ned [127.0.0.1] But Squirrelmail gives: ERROR: Could not complete request. Query: SELECT "INBOX" Reason Given: /etc/pam.d/imap says: #%PAM-1.0 auth required /lib/security/pam_winbind.so account required /lib/security/pam_winbind.so session required /lib/security/pam_mkhomedir.so skel=/etc/skel umask=0022 If I use the same configuration for SSH then the user's home directory is created upon authenticaton, but not with Dovecot. I chose to try Dovecot because I understood it handled PAM session wossisnames, which Courier-IMAP doesn't. My dovecot.conf is attached - I'm wondering if the problem could be with the "auth_userdb" setting, but `getent passwd` does show an entry for the user: # grep ned /etc/passwd # getent passwd | grep ned ned:x:10012:10000:Ned Nedbody:/home/DOMAIN/ned:/bin/false # Many thanks in advance for any advice or suggestions - I'd really like to understand what's going on here. I believe I can authenticate against the domain using LDAP / Active Directory, but since I don't know if that'll help I'd rather not go that route yet. If I first try to log in using ssh with pam_mkhomedir enabled then the users' home directory is created successfully & I can subsequently log on in Squirrelmail. But it's important to me that I shouldn't have to create users' home dirs for them - I should be able to add them on the Windows domain controller & just tell them to log in to their email - the home dir on the mailserver should be created automagically when they authenticate against the domain. Stroller.

7 13

[Dovecot] Authentication trouble.
by Michael Peters 22 Dec '05

22 Dec '05

I am not having much luck with resolving my authentication issue. The environment is "SunOS 5.10 Generic_118822-11 sun4u sparc SUNW,UltraSPARC-IIi-cEngine". dovecot-1.0.alpha5 ./configure --with-passwd --with-shadow --with-pam --with-checkpassword --with-mysql --with-storages=maildir # telnet 172.16.0.40 143 Trying 172.16.0.40... Connected to 172.16.0.40. Escape character is '^]'. * OK mailhub is for business purposes only. Usage is monitored. A01 login username mypassword * BAD [ALERT] Plaintext authentication is disabled, but your client sent password in plaintext anyway. If anyone was listening, the password was exposed. A01 NO Plaintext authentication disabled. A04 Logout * BYE Logging out A04 OK Logout completed. Connection to 172.16.0.40 closed by foreign host. *I have tried adding digest-md5 cram-md5 and shadow but Dovecot will not start.* auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi mechanisms = plain *Dovecot will not start when I tried these options. Maybe I am entering this wrong?* passdb shadow { /etc/shadow } passdb passwd { /etc/passwd } Any assistance would be appreciated. -- Best regards, Michael

2 1