- dovecot - dovecot.org

[Dovecot] Dovecot and MySQL auth - initial setup issues
by Andrew Hearn 11 Jul '06

11 Jul '06

Hello, I'm just setting up a new server and wanting to use MySQL for user authentication. Here is what I have: Fedora Core 5: 2.6.17-1.2145_FC5 Dovecot v1.0.rc2 (RPM install from atrpms.net) MySQL v5.0.22 SquirrelMail v 1.4.6-7.fc5 ...Running on a Dual XEON machine I've added the following to dovecot.conf: auth default { passdb sql { args = /etc/dovecot-mysql.conf } userdb sql { args = /etc/dovecot-mysql.conf } The rest of dovecot.conf is standard. /etc/dovecot-mysql.conf has: driver=mysql connect = host=127.0.0.1 port=3306 dbname=maildb user=root client_flags=0 password_query = SELECT password FROM users WHERE id = '%u' user_query = SELECT maildir FROM users WHERE id = '%u' (I've run the SQL queries within mysql and they give the right results) When I start Dovecot the log shows: dovecot: Jul 11 12:47:25 Info: Dovecot v1.0.rc2 starting up dovecot: Jul 11 12:47:27 Info: auth-worker(default): mysql: Connected to 127.0.0.1 (maildb) When I try to log in using SquirrelMail, it takes about 3 seconds, then I get dovecot: Jul 11 12:48:00 Info: imap-login: Aborted login: user=<andrew(a)mail-test.aaisp.net.uk>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured ...So, no log of it trying MySQL... And SquirrelMail then says: Unknown user or password incorrect Any ideas of what I'm missing? Thanks! Andrew.

1 0

[Dovecot] Authentication error with corrections
by Bruce Lane 11 Jul '06

11 Jul '06

Hi, Curtis (and the group), I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. I don't have any more time to mess with it this morning, but I will make it a point to try 'shadow' when I get in this evening. It's possible that NetBSD wants to work that way. Thanks for your help. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"

3 4

[Dovecot] dovecot-1.0-rc2
by Lucas Valdeón 11 Jul '06

11 Jul '06

Hi, I´m testing dovecot with Thunderbird 1.5.0.4 and when I try to access several folders this error appear: " ... use the Advanced IMAP Server Settings dialog to reduce the number of cache connections." in config file: auth_cache_size = 0 So cache is disable If I send a message server fails when try to copy message to Sent folder. Any idea? Thank you in advance, Lucas

2 3

[Dovecot] Assertion fails (mail_cache_add) in dovecot 1.0 RC 2
by Jens 11 Jul '06

11 Jul '06

The log looks like this: dovecot: Jul 11 10:38:39 Error: IMAP(ni): file mail-cache-transaction.c: line 703 (mail_cache_add): assertion failed: (file_field != (uint32_t)-1) dovecot: Jul 11 10:38:39 Error: child 31316 (imap) killed with signal 6 What I did: 1. Start dovecot with a fresh account so that no folders exist. 2. Start Thunderbird and create a folder "Mails gespeichert auf nasdrive" 3. Put a message into the folder (with Outlook) 4. Edit this message with Thunderbird and Save it. 5. Thunderbird creates the "Draft" folder but the message never gets there. 6. The log file contains the message above! 7. Check if missing folder is source of issue: Edit the message again with Thunderbird and Save it again. 8. The message appears properly in the Draft folder. Additional Info: # dovecot --version 1.0.rc2 # dovecot --build-options Build options: ioloop=poll notify=dnotify ipv6 openssl SQL drivers: Passdb: checkpassword passwd passwd-file shadow Userdb: checkpassword passwd prefetch passwd-file static Regards, Jens

1 0

[Dovecot] Any news with the MS OE "Headers only" problem?
by Sysadmin 11 Jul '06

11 Jul '06

Hello. About year ago I tested OE and dovecot imap and met this problem (http://wiki.dovecot.org/Clients#head-129bcbfc238b5c34362b8216db87c05e7a34af…) - Using "Headers only" synchronization is buggy and can cause "Message is no longer available on this server" error when opening a mail. I configured OE to sync All messages, and it worked, but then it's acts like pop3 and downloads all messages and the local computer mailboxes are still there. However is there any news according this issue? How to use dovecot imap with OE and "Headers only" option selected? -- Sysadmin

2 5

[Dovecot] 1.0 migration
by jeff sacksteder 11 Jul '06

11 Jul '06

The version of Dovecot I am currently using keeps different read pointers depending on if it's being accessed by POP or IMAP. I understand that in 1.0this is unified. If I upgrade the server in place, what will the status of my messages be? Will everything be marked unread? IMAP pointers become official? POP pointers become official?

2 1

[Dovecot] Authentication by certificats (a bug or my misconfiguration)
by Michal Soltys 11 Jul '06

11 Jul '06

Today I've been trying to get dovecot (1.0 rc2) to use certificates for client side authentication. If my memory serves right, beta8 had no problems with it (although it was some time ago and on different machine). Similar setup works perfectly well for postfix (for authentication that is, on the same machine). Originally I thought I overdid some certificate settings (keyUsage, nsCertType, etc.), so for the sake of testing I've simplified the setup to bare minimum - 1 simple selfsigned root certificate, another 1 for dovecot, and the last one for the user. Unfortunately, the results were the same. Configuration: OpenBSD 3.9 (stable branch), i386, no nfs or afs (only local ffs) standard OpenSSL 0.9.7g (+ patches) dovecot 1.0 rc2, compiled from sources, with sysconfdir set to /etc and with disabled pam Tested with the most recent opera and mozilla thunderbird, using pop3s. (note: both clients work with postfix, authetnicating only by certificates). They do send requested certificates. Important dovecot configuration: ssl_cert_file = /etc/ssl/ca_ppgk/certs/pop3_crt.pem (common name - pop3.ppgk.com.pl, valid dns name) ssl_key_file = /etc/ssl/ca_ppgk/private/pop3_key.pem ssl_ca_file = /etc/ssl/ca_ppgk/ca_crt.pem ssl_verify_client_cert = yes verbose_ssl = yes auth_verbose = yes ssl_require_client_cert = yes ssl_username_from_cert = (tested both with yes and no, with common name of user certificate set both as username@domain or as bare username) The rest is just pretty standard, using passwd for both user auth and userdb, with plain and login mechanisms allowed. I tested "few" sets of certificates (for ca, server and user) with configurations ranging from quite specific ones (with basicConstraints, nsCertType, keyUsage, extendedKeyUsage fields set) to very simple ones (basicConstraints + typical stuff like subjectKeyIdentifier). All of them gave the same results with dovecot (postfix didn't complain with any of them either). This is what I get in logs, when trying to pull mail using opera or mozilla: Jul 7 14:33:47 ppgk-wa dovecot: Dovecot v1.0.rc2 starting up Jul 7 14:33:57 ppgk-wa dovecot: pop3-login: Invalid certificate: /C=PL/ST=Mazowieckie/L=Warszawa/O=PPGK/OU=Z10/CN=adminms@ppgk.com.pl/emailAddress=adminms@ppgk.com.pl Jul 7 14:33:57 ppgk-wa dovecot: pop3-login: Invalid certificate: /C=PL/ST=Mazowieckie/L=Warszawa/O=PPGK/OU=Z10/CN=RootCA/emailAddress=admin(a)ppgk.com.pl Jul 7 14:33:57 ppgk-wa dovecot: pop3-login: Valid certificate: /C=PL/ST=Mazowieckie/L=Warszawa/O=PPGK/OU=Z10/CN=RootCA/emailAddress=admin(a)ppgk.com.pl Jul 7 14:33:57 ppgk-wa dovecot: pop3-login: Valid certificate: /C=PL/ST=Mazowieckie/L=Warszawa/O=PPGK/OU=Z10/CN=adminms@ppgk.com.pl/emailAddress=adminms@ppgk.com.pl Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=192.168.100.77 rip=192.168.100.75 resp=<hidden> Jul 7 14:34:05 ppgk-wa dovecot: auth(default): PLAIN(?,192.168.100.75): Client didn't present valid SSL certificate Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client out: FAIL 1 reason=Client didn't present valid SSL certificate Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client in: AUTH 2 LOGIN service=POP3 secured lip=192.168.100.77 rip=192.168.100.75 resp=<hidden> Jul 7 14:34:05 ppgk-wa dovecot: auth(default): LOGIN(?,192.168.100.75): Client didn't present valid SSL certificate Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client out: FAIL 2 reason=Client didn't present valid SSL certificate Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client in: AUTH 3 PLAIN service=POP3 secured lip=192.168.100.77 rip=192.168.100.75 resp=<hidden> Jul 7 14:34:05 ppgk-wa dovecot: auth(default): PLAIN(?,192.168.100.75): Client didn't present valid SSL certificate Jul 7 14:34:05 ppgk-wa dovecot: auth(default): client out: FAIL 3 reason=Client didn't present valid SSL certificate Jul 7 14:34:07 ppgk-wa dovecot: pop3-login: Disconnected: method=PLAIN, rip=192.168.100.75, lip=192.168.100.77, TLS Those two "Invalid certificate" lines, followed immediately by two "Valid certificate" lines seem suspicious. Is there some configuration detail I might have missed or messed, or is it (probably) a bug ?

3 4

[Dovecot] Group-based filesystem quota
by Scott Alter 11 Jul '06

11 Jul '06

Hello. After using Dovecot for over a year, I have just started experimenting with the filesystem quotas, and I have a suggestion for improvement. On my mail server, I use group-based quotas, and would like to have Dovecot be able to report these quotas. It should be simple to implement, requiring only changes to the quota-fs.c file of the quota plugin. Simply changing USRQUOTA to GRPQUOTA should do the trick. In terms of the configuration file, "quota = fs" could be expanded to something like: quota = fs:storage=group # use filesystem quota with group storage limit Adding in support for message (inode) limits is just as easy, replacing dqb_curblocks with dqb_curinodes and dqb_bsoftlimit with dqb_isoftlimit. It could be easy to configure too, like: quota = fs:storage=group:messages=user # use filesystem quota with group storage limit and user messages limit Although I think I know what would need to be changed, I'm not a C programmer and my code would not be clean nor efficient. Since the messages and storage parameters of the quota setting are defined elsewhere (quota-maildir.c), I don't think it would be too difficult to duplicate this in the quota-fs.c file. Also, I am having the same problem as others with used space off by a factor of 4096, total limit off by a factor of 4. Stian's patch (http://dovecot.org/list/dovecot/2006-June/014159.html) does the trick, but I'm wondering if everyone is having this problem, or just those running Linux. Thanks, Scott

5 9

[Dovecot] Corrupted index & index data file
by james edwards 10 Jul '06

10 Jul '06

We just moved to a new box for POP/IMAP services. I rsynced /home and /var/spool/mail to the new box from the old with the archive switch. It went smoothly but I am seeing more corrupted index & index data file errors in the log than I normally do. I thought I read that Dovecot would rebuild these files after the user accessed them the second time, if corrupt. Is this correct ? Is there a better way to deal with this issue other than deleting them so they are recreated the next time the user checks their mail ? james <jedwards(a)nmcourts.com>

2 4

[Dovecot] PAM Error on POP3s auth? And apop?
by Bruce Lane 10 Jul '06

10 Jul '06

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin(a)bluefeathertech.com,192.168.42.40): pam_start() failed: system error Jul 9 21:14:17 featherweb dovecot: pop3-login: Aborted login: user=<kyrrin(a)bluefeathertech.com>, method=PLAIN, rip=192.168.42.40, lip=192.168.42.130, TLS THE PLATFORM: NetBSD 3.0, Postfix 2.3-RC8 (soon to be replaced by an official release in the coming week), and whatever the current release candidate of Dovecot is. I did some googling for that pam_start error, and discovered (much to my annoyance) that it may be a system bug within NetBSD 3.0. If that's the case, given that I don't have anywhere near the programming skill to even try and correct it, it'll mean I'm pretty much stuck until the NetBSD developers fix it, or until I can figure out an alternate authentication method that won't be an administrative nightmare. Does anyone have any ideas on this? For the benefit of poking and pondering, this is the relevant section of my dovecot.conf file. auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain login passdb pam { } userdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } And this is the contents of the file 'dovecot' in the directory /etc/pam.d # PAM configuration for the "dovecot" subsystem. # # auth auth required pam_nologin.so no_warn auth required pam_unix That entry should, in theory, block all logins if the /etc/nologin file is present, and then hand off to the pam_unix module if it's not. pam_unix, in NetBSD, is the module that authenticates against the /etc/passwd file. As I said, further thoughts would be welcome. If it is a NetBSD system bug causing that pam_auth error, ideas for a simple workaround until the NetBSD crew gets things patched up would also be welcome. Thanks in advance. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"

2 2