- dovecot - dovecot.org

[Dovecot] pam_authenticate() failed:
by Sutton, Geoff 12 May '06

12 May '06

I'm having the same problem.... Did anyone find a solution? -- Geoff

1 0

[Dovecot] 1.0.beta8 released
by Timo Sirainen 12 May '06

12 May '06

Next release will probably be called 1.0.rc1. People just don't seem to like the beta name in the version number. :) Also I think we're nearing the final v1.0. * Fixed a security hole with mbox: "1 LIST .. *" command could list all directories and files under the mbox root directory, so if your mails were stored in eg. /var/mail/%u/ directory, the command would list everything under /var/mail. + Unless nfs_check=no or mmap_disable=yes, check for the first login if the user's index directory exists in NFS mount. If so, refuse to run. This is done only on first login to avoid constant extra overhead. + If we have plugins set and imap_capability unset, figure out the IMAP capabilities automatically by running imap binary at startup. The generated capability list isn't updated until Dovecot is restarted completely, so if you add or remove IMAP plugins you should restart. If you have problems related to this, set imap_capabilities setting manually to work around it. + Added auth_username_format setting - pop3_lock_session setting wasn't really working - Lots of fixes related to quota handling. It's still not working perfectly though. - Lots of index handling fixes, especially with mmap_disable=yes - Maildir: saving mails could have sometimes caused "Append with UID n, but next_uid = m" errors - flock() locking never timeouted because ignoring SIGALRM caused the system call just to be restarted when SIGALRM occurred (probably not with all OSes though?) - kqueue: Fixed "Unrecognized event". Patch by Vaclav Haisman

2 1

[Dovecot] dovecot: pipe() failed: Too many open files
by Obantec Support 12 May '06

12 May '06

Hi stable 1.0 on FC3 , first time i have seen this. May 11 19:40:00 proteus2 dovecot: pipe() failed: Too many open files May 11 19:40:05 proteus2 last message repeated 41406 times had to stop and re-start dovecot to free the error. Any ideas what caused it? Mark -- Obantec Support www.obantec.net 0845 458 3121 WebHosting and Domains Nominet UK Member & IPStag Holder CentralNic Accredited Reseller

2 1

[Dovecot] userdb prefetch not working with dovecot LDA?
by Luca Corti 12 May '06

12 May '06

Hello, I've configured MySQL authentication as follows. -- divecot-sql.conf -- driver = mysql connect = host=localhost dbname=postfix user=myuser password=mypass default_pass_scheme = PLAIN password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT CONCAT('/var/vmail/', maildir, 'Maildir') AS home, '1234' AS uid, '1234' AS gid FROM mailbox WHERE username = '%u' -- dovecot.conf -- passdb sql { args = /usr/local/etc/dovecot-sql.conf } userdb sql { args = /usr/local/etc/dovecot-sql.conf } And both access (IMAP) and delivery (LDA) work correctly. Now I want to setup prefetching to reduce SQL queries, so I did -- dovecot-sql.conf -- driver = mysql connect = host=localhost dbname=postfix user=myuser password=mypass default_pass_scheme = PLAIN password_query = SELECT password, CONCAT('/var/vmail/', maildir, 'Maildir') AS userdb_home, '1234' AS userdb_uid, '1234' AS userdb_gid FROM mailbox WHERE username = '%u' -- dovecot.conf -- passdb sql { args = /usr/local/etc/dovecot-sql.conf } userdb prefetch { } Dovecot mail access (IMAP) works correctly, but when the LDA tries to deliver mail I get: May 11 16:25:00 ns1 dovecot: auth(default): prefetch(luca(a)example.com): passdb didn't return userdb entries May 11 16:25:00 ns1 postfix/pipe[11040]: 21E31847BC: to=<luca(a)example.com>, relay=dovecot, delay=0, status=bounced (user unknown) thanks -- Luca Corti PGP Key ID 1F38C091 BOFH excuse of the moment: user to computer ration too low.

2 1

[Dovecot] dovecot-lda and sieve filtering (SMTP is Postfix)
by Der Olli 12 May '06

12 May '06

Hello list. I've got a working Dovecot with Postfix and MySQL-support but everything from the capabilities of sieve isn't working except one thing: Sorting emails to folders works fine. But no vacation, no reject, no redirect. I don't get any errors in the logs. Verbose logging is enabled. I compiled both from newest cvs-sources but also tried older combinations (nightly snapshots). Always the same result and there's no .dovecot.sieve.err so script is okay. If it is not, .dovecot.sieve.err will be generated. I've tested this :) Anyone here who has a working sieve implementation with dovecot-lda? Where do I have to search? Is it a configuration problem? Where can I configure which sending mechanism dovecot-lda should use? Is it a local sendmail binary? Where does dovecot-lda search for it. Is it a SMTP-server? So there's one on port 25 at the local machine. Greetz, Olli

2 2

[Dovecot] comment on dovecot documentation on PAM
by president＠irithm.com 12 May '06

12 May '06

Dear Dovecote devotees, I have been going through dovecot configuration for the first time. I am not an experienced systems administrator so I had to do a left turn to read up about PAM while doing all the configuration for my new webmail service. I found that the writing in the dovecot documentation about PAM to be rather misleading in at least one aspect. The documentation I am specifically referring to is at http://wiki.dovecot.org/Authentication?highlight=%28authentication%29 and in the comments found in the dovecot.conf file. In this documentation PAM is referred to as a password database. It appears that is not correct, rather PAM is something that uses a password database. Since the default for "auth_passdb" given in dovecot.conf was "pam" I spent sometime trying to find a pam password database. I eventually found out at an independent website that what pam uses is either /etc/passwd or /etc/shadow or /etc/samba/smbpasswd. It was a relief to find out pam uses one of these, since my system has one of them (/etc/shadow), but I was looking to find something quite different for pam since /etc/shadow is one of the listed alternative values for "auth_passdb". I would have been spared a somewhat lengthy search to find out this information if the documentation was written rather more clearly. So, to help others, I suggest changing the following lines in dovecot.conf # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication to: # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: /etc/shadow or similiar, using PAM authentication Updating the documentation in http://wiki.dovecot.org/Authentication?highlight=%28authentication%29 to include a phrase that mentions that PAM authentication works from one of the standard password databases (i.e. /etc/passwd, /etc/shadow or /etc/samba/smbpasswd) would also be helpful. yours sincerely, Rolf

3 2

[Dovecot] Pocket Outlook
by Josh Burley 11 May '06

11 May '06

Hi all, Another user posted the same thing a few months back... after contacting them, they said they never got it working. I'm unable to get Pocket Outlook, or FlexMail 2006 working on Dovecot 0.99.13. According to the logs it connects just fine. With Pocket Outlook I'll see the headers for a few seconds, and then it clears and shows nothing. With FlexMail, which is supposed to have fantastic IMAP support (and has tons of options), I just see an empty inbox. Any ideas?? .josh

2 4

Re: [Dovecot] LDA not being called by postfix?
by Andreas Martin 11 May '06

11 May '06

Hi Luca. Luca Corti schrieb: > On Thu, 2006-05-11 at 15:16 +0200, Andreas Martin wrote: >>> and in the db: >>> >>> +----+-------------+-------------+---------+-----------+----------+-----------+----------+---------------------+---------------------+--------+ >>> | id | domain | description | aliases | mailboxes | maxquota | >>> transport | backupmx | created | modified | >>> active | >>> +----+-------------+-------------+---------+-----------+----------+-----------+----------+---------------------+---------------------+--------+ >>> | 2 | example.com | example.com | 5 | 10 | 20 | >>> virtual | 0 | 2006-05-08 01:30:58 | 2006-05-08 11:42:55 | >> ^^^^^^^ >>> 1 | >>> +----+-------------+-------------+---------+-----------+----------+-----------+----------+---------------------+---------------------+--------+ >> This should be "dovecot" - corresponding to your master.cf: > >>> The transport gets correctly selected upon mail delivery: >> Nope... >> >>> May 11 13:09:47 ns1 postfix/virtual[9797]: 7C4D4847BC: >> ^^^^^^^ >>> to=<luca(a)example.com>, relay=virtual, delay=0, status=sent >> ^^^^^^^ >> >> This should be something like: >> >> May 11 13:09:47 ns1 postfix/pipe[9797]: 7C4D4847BC: >> ^^^^ >> to=<luca(a)example.com>, relay=dovecot, delay=0, status=sent >> ^^^^^^^ > > Now it works... I thought > > virtual_transport = dovecot > > handled this. What is it doing then? Maybe it would work if I didn't > specify the virtual_transport_maps? virtual_transport is the general transport for virtual mailboxes. virtual_transport_maps overrides this to allow you to specify exceptions. Have fun! Andreas

2 1

[Dovecot] mandatory client certificates and crl check in ssl-proxy-openssl.c
by HenkJan Wolthuis 11 May '06

11 May '06

hello, I made a modification to ssl-proxy-openssl.c (patch attached) zo that it a) disconnects when no client certificate is presented b) checks the client certificate against the crl for our root cert. (so you can't use a revoked client cert.) c) returns the CommonName from the client cert. in ssl_proxy_get_peer_name (this way it's easier to use dovecot as imap-proxy with a passwd-like userdb, ssl_require_client_cert and ssl_username_from_cert, it "binds" the emailuser to the clientcertificate, a clientcert. can access only the account from the userdb) in order to use it, the CAfile must be a file which contains the CAcertificate (pem format) followed by the CRL (also in pem format). (servercert and the clientcerts are signed with a self-signed rootcert) there are some issues with the patch: a) it needs openssl > 0.9.7 for the CRL checking b) ssl_verify_client_cert now returns 0 in case of an invalid cert. was there a reason why it always returned 1? c) i'm not too happy with the commonname extraction code, is it secure?? d) i've no experience with programming openssl or dovecot e) i haven't programmed in C for at least 8 years...... does anyone here have more issues, corrections, comments on the patch? can/should this functionality be implemented in dovecot? (conf-file option?) -- groeten, HenkJan Wolthuis --- ssl-proxy-openssl.c.orig 2006-04-04 10:32:58.000000000 +0200 +++ ssl-proxy-openssl.c 2006-05-11 14:08:02.000000000 +0200 @@ -11,6 +11,7 @@ #include <fcntl.h> #include <unistd.h> #include <sys/stat.h> +#include <string.h> #ifdef HAVE_OPENSSL @@ -508,9 +509,42 @@ if (x509 == NULL) return NULL; /* we should have had it.. */ + + // ORIG: X509_NAME_oneline(X509_get_subject_name(x509), buf, sizeof(buf)); + // ORIG: name = t_strndup(buf, sizeof(buf)); + // ORIG: X509_free(x509); + + /* HJHJ get CommonName from peer-certificate */ X509_NAME_oneline(X509_get_subject_name(x509), buf, sizeof(buf)); - name = t_strndup(buf, sizeof(buf)); + + char *tmp; + char *start; + start = buf; + tmp = strstr( buf, "CN=" ); + if( NULL != tmp ) + { + if( strlen(tmp) > 3 ) /* CN= + something */ + { + start = tmp + 3; + tmp = strstr( start, "/" ); + if( NULL != tmp ) /* tmp == NULL: CN is last element in buf */ + { *tmp = '\0'; } + } + else /* empty CN= */ + { + *start = '\0'; + i_warning("get_peer_name empty CN="); + } + } + else + { + *start = '\0'; + i_warning("get_peer_name NO CN="); + } /* CN= not found (no certificate or certificate without commonname??) */ + + name = t_strndup(start, strlen(start) ); X509_free(x509); + /* HJHJ */ return *name == '\0' ? NULL : name; } @@ -582,10 +616,26 @@ proxy = SSL_get_ex_data(ssl, extdata_index); proxy->cert_received = TRUE; + // ORIG: if (!preverify_ok) + // ORIG: proxy->cert_broken = TRUE; + + // ORIG: return 1; + + /* HJHJ */ + char buf[1024]; + X509_NAME_oneline( X509_get_subject_name(ctx->current_cert),buf,sizeof(buf)); + if (!preverify_ok) + { proxy->cert_broken = TRUE; + i_warning("BAD CERT %s: %s",X509_verify_cert_error_string(ctx->error),buf); + } + else + { i_warning("CERT: %s",buf); } - return 1; + return preverify_ok; + /* HJHJ */ + } static int @@ -666,10 +716,20 @@ if (getenv("SSL_VERIFY_CLIENT_CERT") != NULL) { SSL_CTX_set_verify(ssl_ctx, SSL_VERIFY_PEER | - SSL_VERIFY_CLIENT_ONCE, + SSL_VERIFY_FAIL_IF_NO_PEER_CERT, ssl_verify_client_cert); } + /* HJHJ */ +#if OPENSSL_VERSION_NUMBER >= 0x00907000L + X509_STORE *store; + if( (store=SSL_CTX_get_cert_store(ssl_ctx)) != NULL ) + { X509_STORE_set_flags( store, X509_V_FLAG_CRL_CHECK | X509_V_FLAG_CRL_CHECK_ALL); } + else + { i_warning("X509 get cert store failed..."); } +#endif + /* HJHJ */ + /* PRNG initialization might want to use /dev/urandom, make sure it does it before chrooting. We might not have enough entropy at the first try, so this function may fail. It's still been

1 0

[Dovecot] "QUOTA" CAPABILITY keyword advertised incorrectly?
by Mike Brudenell 11 May '06

11 May '06

Greetings - I'm having a frustrating time with mail clients not picking up Dovecot's QUOTA extension to IMAP. The problem is that the QUOTA keyword isn't advertised in Dovecot's response to a CAPABILITY enquiry until *after* the user has authenticated. Unfortunately I've yet to find a mail client that issues a CAPABILITY request after authenticating. Instead all do so upon initial connection to the IMAP server (and, correctly, again after subsequently initiating a STARTTLS session but before authentication). Not re-querying the CAPABILITY after authentication is correct according to the IMAP spec in RFC2060, which says: 6.1.1. CAPABILITY Command Arguments: none Responses: REQUIRED untagged response: CAPABILITY Result: OK - capability completed BAD - command unknown or arguments invalid The CAPABILITY command requests a listing of capabilities that the server supports. The server MUST send a single untagged CAPABILITY response with "IMAP4rev1" as one of the listed capabilities before the (tagged) OK response. This listing of capabilities is not dependent upon connection state or user. It is therefore not necessary to issue a CAPABILITY command more than once in a connection. In particular the last two sentences are relevant. (At present Dovecot is only advertising availability of the QUOTA extension *after* authentication, and hence *is* dependent on the user.) Ths means that at present Dovecot's provision of the QUOTA extension isn't actually getting used by popular mail clients such as Thunderbird. Cheers, Mike Brudenell -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

3 3