- dovecot - dovecot.org

[Dovecot] Login lockups
by Daniel L. Miller 04 Apr '07

04 Apr '07

When dovecot works - it works great, and I thank you. But it seems like every time I setup a new server, it's a challenge getting the IMAP logins to work reliably. The changelog's top comment is stamped 2007-01-05, 18:48 if that helps nail down the version (I'm using a Debian/Ubuntu package). Both non-SSL and SSL logins have the problem. This time around I'm using LDAP authentication - and once I figured out how it worked beautifully. The problem is from time to time - with no particular consistency - I lose the ability to log in. A "telnet localhost 143" on the server works with a Dovecot response, then followed with a "01 LOGIN <user> <password>" results in a long delay, then a timeout, with no log files affected. What can I provide to try to trace this? protocols = imap imaps disable_plaintext_auth = no login_process_per_connection = yes -- Daniel

2 2

[Dovecot] logfile consistency
by David Lee 04 Apr '07

04 Apr '07

We do some routine logfile (syslog) gathering and analysis. I've been looking at extending this to parse the syslog output of dovecot. Hmmm... Ignoring the leading 'date hostname' prefix, some sample lines are: dovecot: imap-login: Login: user=<uuuuuu>, method=PLAIN, rip=dd.dd.dd.dd, lip=dd.dd.dd.dd dovecot: IMAP(uuuuuu): Disconnected: Logged out dovecot: IMAP(uuuuuu): Disconnected in IDLE dovecot: imap-login: Aborted login: rip=dd.dd.dd.dd, lip=dd.dd.dd.dd dovecot: pop3-login: Login: user=<uuuuuu>, method=PLAIN, rip=dd.dd.dd.dd1, lip=dd.dd.dd.dd dovecot: POP3(uuuuuu): Disconnected: Logged out top=0/0, retr=0/0, del=0/8, size=194970 dovecot: pop3-login: Aborted login: rip=dd.dd.dd.dd, lip=dd.dd.dd.dd deliver(uuuuuu): msgid=<014089712.74355909944644(a)thhebat.net>: saved mail to INBOX I've obfuscated some of the local detail: uuuuuuu represents a username/identifier; dd.dd.dd.dd represents an IP address. Would it be possible, please, to consider improving the consistency of the logging information? For instance: 1. All lines, including the "deliver", to begin "dovecot:"; 2. The "IMAP(uuuu): Disconnected" to become "imap: disconnected user=<uuuu>"; Overall this would make it more consistently amenable to perl-like pattern processing, at least with a reasonably hierarchical structure to the messages. Perhaps something like: dovecot: subprogram: event, key1=value1, key2=value2 ... where: "subprogram" is "{imap,pop,deliver,...}"; "event" is "{login,disconnected, ...}; and one of the "key=value" will usually be "user=<uuuu>". That would really make post-processing of logging information (whether offline, or 'live' via piped syslog) considerably easier. Thanks. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

4 3

[Dovecot] How to integrate dspam and dovecot
by Manilal K M 03 Apr '07

03 Apr '07

Hello all, I am currently setting up a new mail server with Qmail, OpenLDAP and Dovecot in CentOS-4.4. Qmail version is 1.03, OpenLDAP is 2.3 and Dovecot version is dovecot-1.0-3_50.rc27(RPM). I have successfully installed and tested it. But I have two issues with the current setup: #1. I am using dovecot LDA and configured the OpenLDAP such that the mail be delivered to the virtual users through a script. This script is saved in /var/qmail/bin/deliver.sh and the contents is as follows: /usr/bin/dspam --stdout --mode=tum --deliver=innocent,spam --feature=chained,noise --user global |/var/qmail/bin/preline -f /usr/libexec/dovecot/deliver -d $RECIPIENT || exit 77 This script name is mentioned in each user's deliveryProgramPath in the LDAP. I am not sure whether this is the best approach of using dovecot as MDA. I tried to include the following contents in /var/qmail/control/defaultdelivery : |/var/qmail/bin/preline -f /usr/libexec/dovecot/deliver -d $RECIPIENT But it seems that this is not working as desired. Please comment, if I have gone wrong anywhere. #2: I wish to use dspam to filter out the spam messages, but I am unsure whether the dspam plugin mentioned in http://johannes.sipsolutions.net/Projects/dovecot-dspam-integration is already in the dspam version I am using. If it's available please give details to configure it. Kindly share ideas. regards Manilal. -- Better to light one candle than to curse the darkness. Blog: http://librewings.blogspot.com Blog: http://flossvalley.blogspot.com

4 9

[Dovecot] No CA names sent in TLS handshake
by Johnny Chadda 03 Apr '07

03 Apr '07

Hello, I'm setting up Dovecot with client certificates and everything is working fine as long as the client only has one certificate in his store. If he has more than one, the wrong one might be sent to the server. The root of the problem is that Dovecot does not send out a list of valid CA names in the TLS handshake. If I connect using openssl s_client I get: "No client certificate CA names sent" I am using Dovecot 1.0 RC15 from backports.org. Is there a solution to this problem? Regards, Johnny

2 4

[Dovecot] Init.d boot scripts??
by rodman＠thefrowerts.com 03 Apr '07

03 Apr '07

Hello, Trying to figure out how to get dovecot to startup at boot. I saw the Ubuntu script on the dovecot site, but that didn't work on my system (SuSe 10.2). Of course, copying the /usr/local/sbin/dovecot file into /etc/init.d doesn't work at all. Any one have working SuSe script?? Rodman

4 4

[Dovecot] *****SPAM***** Upgrading from rc27 to rc29?
by Francisco Reyes 03 Apr '07

03 Apr '07

After sending a messasge about a problem (The folder 'Inbox' cannot contain items. Namespace problems) I found what seems to be a fix in the release for rc29. Besides any potential configuration files, do I need to delete the old index files? Any of the dovecot files? Based on the release notes for rc29 it seems the following will fix the problem we are experiencing: IMAP: LIST "" "" didn't return anything if there didn't exist a namespace with empty prefix. This broke some clients.

2 1

[Dovecot] [PATCH] to fix 2 pam issues
by Phil Oleson 03 Apr '07

03 Apr '07

Timo, I finally made the time to backport a pam fix I created for proftpd over to dovecot, that allows FreeBSD's pam_group to work as expected. (the bug was escalated to me internally hehe.. ). I also noticed an issue while testing that will be confusing to users. If the docs stay as is, or the other half of this patch is applied, then when the dovecot.conf contains: passdb pam { args = * } the imap files within etc/pam.d right now have to be named 'IMAP' and 'POP3' rather than the expected 'imap' and 'pop3'. The attached patch fixes the code to match the docs. -Phil. --- src/auth/passdb-pam.c.orig Mon Mar 26 10:10:26 2007 +++ src/auth/passdb-pam.c Mon Apr 2 16:18:54 2007 @@ -275,6 +275,8 @@ (void)pam_set_item(pamh, PAM_RHOST, host); /* TTY is needed by eg. pam_access module */ (void)pam_set_item(pamh, PAM_TTY, "dovecot"); + /* FreeBSD's pam_group need this set as well */ + (void)pam_set_item(pamh, PAM_RUSER, request->user); status = pam_auth(request, pamh, &str); if ((status2 = pam_end(pamh, status)) == PAM_SUCCESS) { @@ -428,8 +430,15 @@ int fd[2]; pid_t pid; - service = module->service_name != NULL ? - module->service_name : request->service; + if (module->service_name != NULL) { + service = module->service_name; + } else { + if (!strncmp(request->service, "IMAP", strlen(request->service))) + service = "imap"; + else if (!strncmp(request->service, "POP3", strlen(request->service))) + service = "pop3"; + } + auth_request_log_debug(request, "pam", "lookup service=%s", service); if (worker) {

2 1

[Dovecot] vpopmail "last auth" question
by B. Cook 03 Apr '07

03 Apr '07

Hello, I run the domain for the school here with qmail and vpopmail on FreeBSD with dovecot from the ports. I'm running dovecot 1.0.r26 and everything is working great. I been noticing that dovecot isn't updating when the user last logged in.. and I can't seem to figure out why. I also can't seem to find anything in the archives about it.. so am I the only one? name: bcook passwd: $1$ clear passwd: comment/gecos: B. Cook uid: 0 gid: 0 flags: 0 gecos: B. Cook limits: No user limits set. dir: /usr/local/vpopmail/domains/poughkeepsieschools.org/bcook quota: 41943040S usage: 72% account created: Wed Oct 18 21:09:03 2006 last auth: Never logged in I'm wondering how I could get the 'last auth' to populate like it used to w/ courier. below is my config if it will help: protocols = imap imaps pop3 listen = * disable_plaintext_auth = no ssl_disable = no ssl_cert_file = /long/path/to/file.pem ssl_key_file = /long/path/to/file.pem verbose_ssl = yes login_user = dovecot login_process_size = 64 first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth default { mechanisms = plain passdb vpopmail { args = } userdb vpopmail { } user = root } plugin { quota = maildir } Thanks in advance. -- B. Cook Network Analyst Poughkeepsie City School District Mobile: 845.264.5827 | Desk: 845.451.4791

4 4

[Dovecot] Suggestion: mod_auth_dovecot
by David Anderson 03 Apr '07

03 Apr '07

Hello, I have a suggestion which might be a small and very useful project for a C coder (I'm not one!). As Dovecot makes its authentication interface available to other programs, I think that an Apache module to use it would be very useful. Currently I share an passwd-db file between Dovecot and Apache. However with Apache that means I have to give Apache read access. That means that websites with PHP could read that password file if they liked. If Apache could talk to the Dovecot authentication process instead, that would be a lot better. I'm sure there are lots of situations in which this would be useful - Dovecot's authentication settings are so flexible that it would be very handy to be able to use them more widely. If anyone produces one, I pledge to produce an RPM package and submit it to Fedora as my contribution. I would do it myself if I knew C... David

4 6

[Dovecot] prefetch + static + deliver
by Tom Bombadil 02 Apr '07

02 Apr '07

Hi all... The prefetch entry in the wiki says: "If you're using Dovecot's local delivery agent, you'll still need a valid userdb which it can use to locate the users. You can do this by adding a normal sql/ldap userdb after userdb prefetch." (http://wiki.dovecot.org/UserDatabase/Prefetch) My question is: Does it need to be a SQL/LDAP userdb? How about static or passwd? Thanks in advance :)

3 3