August 2006 - dovecot

[Dovecot] dovecot 1.0rc6 and LDAP problem
by Marcin Deranek 16 Aug '06

16 Aug '06

Hi, I have been using Dovecot with LDAP support (only for password authentication) for a couple of weeks already and everything was running smoothly so far.. till last week when discovered interesting thing: whenever I start LDAP server (openldap 2.3.24) before I start Dovecot everything is fine.. however when Dovecot is started first and then LDAP server it's not possible to authenticate :-( My dovecot-ldap.conf file: hosts = 127.0.0.1 auth_bind = yes auth_bind_userdn = uid=%u,ou=Users,dc=domain,dc=tld ldap_version = 3 base = ou=Users,dc=domain,dc=tld These are messages I get in syslog: slapd is down Aug 15 18:56:55 ftp dovecot: Dovecot v1.0.rc6 starting up Aug 15 18:56:56 ftp dovecot: auth(default): LDAP: Can't connect to server: 127.0.0.1 slapd is started Aug 15 18:58:36 ftp dovecot: imap-login: Disconnected: Inactivity: method=plain, rip=192.168.1.3, lip=192.168.1.2, TLS Aug 15 18:58:36 ftp dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see src/lib/fdpass.c) slapd messages: Aug 15 18:57:19 ftp slapd[20544]: slapd starting Aug 15 18:57:36 ftp slapd[20544]: conn=0 fd=11 ACCEPT from IP=127.0.0.1:37703 (IP=0.0.0.0:389) Aug 15 18:57:36 ftp slapd[20544]: conn=0 op=0 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" method=128 Aug 15 18:57:36 ftp slapd[20544]: conn=0 op=0 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" mech=SIMPLE ssf=0 Aug 15 18:57:36 ftp slapd[20544]: conn=0 op=0 RESULT tag=97 err=0 text= Aug 15 18:58:39 ftp slapd[20544]: conn=0 op=1 BIND anonymous mech=implicit ssf=0 Aug 15 18:58:39 ftp slapd[20544]: conn=0 op=1 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" method=128 Aug 15 18:58:39 ftp slapd[20544]: conn=0 op=1 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" mech=SIMPLE ssf=0 Aug 15 18:58:39 ftp slapd[20544]: conn=0 op=1 RESULT tag=97 err=0 text= Aug 15 18:59:41 ftp slapd[20544]: conn=0 op=2 BIND anonymous mech=implicit ssf=0 Aug 15 18:59:41 ftp slapd[20544]: conn=0 op=2 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" method=128 Aug 15 18:59:41 ftp slapd[20544]: conn=0 op=2 BIND dn="uid=user,ou=Users,dc=domain,dc=tld" mech=SIMPLE ssf=0 Aug 15 18:59:41 ftp slapd[20544]: conn=0 op=2 RESULT tag=97 err=0 text= Has anyone else has the same problem ? Regards, Marcin

2 2

[Dovecot] stale imap processes with 1.0.rc6 on FreeBSD
by Jeremy C. Reed 16 Aug '06

16 Aug '06

Was running dovecot-1.0.rc2 but many stale imap processes (only one user of IMAP). Switched to dovecot-1.0.rc6 but problem continued. This is on FreeBSD 4 something. Maybe it has bug with kqueue?? I read messages about the stale imap processes on the list. It seems to hit *BSD systems. But email about new release candidate indicated it should be fixed. I read on the pkgsrc commit list about --with-ioloop=best So I configured with that and saw that the I/O loop method is now kqueue. (I saved configure output and it was poll before). But the stale imap processes problem continues. For one user over past couple hours I have eight imap processes in "I" state. I have: File offsets ........................ : 64bit I/O loop method ..................... : kqueue File change notification method ..... : kqueue Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword (modules) Building with password lookup modules : passwd passwd-file pam checkpassword (modules) Building with SQL drivers ............: And I have: protocols = imap pop3 protocol imap { imap_client_workarounds = outlook-idle delay-newmail } (Just started using delay-newmail today.) My maillogs don't show any problems. The IMAP user tells me that Outlook says it has reset connections often. I see multiple imap-login Login within a few minutes for this same user who said received a connection reset in outlook at the same time. Just received a screenshot that said: Microsoft Office Outlook Failed to update headers. The TCP/IP connection unexpectedly terminated by the server. Then also received an error (in Outlook I think), like: imap session idle too long, connection reset (I don't have or use Outlook myself so can't test myself.) It is used for a lot of pop3 and seems fine with that. (It uses stunnel for pop3s but not imaps for over a week to eliminate stunnel from our troubleshooting). Any ideas on troubleshooting this would be appreciated. Jeremy C. Reed

4 13

[Dovecot] problem with sieve implementation
by Amadou Toure 16 Aug '06

16 Aug '06

Hello, I follow the instruction of this link (http://wiki.dovecot.org/LDA) to implement sieve with my dovecot installation (dovecot-1.0rc2) and i'm running the timsieve daemon of my cyrus-imapd installation but i got the following error message when the sieve daemon try to formward message : entered bc_action_emit with filelen: 16 Aug 13 14:53:27 ldap sieve[3870]: entered bc_action_emit with filelen: 36 Thank you for your help regards Amadou TOURE

2 2

[Dovecot] cleartext password logging
by Imre Gergely 16 Aug '06

16 Aug '06

hi is it possible to somehow log cleartext passwords (preferably after the authentication is done, and the user logged in)? 'auth_verbose = yes' doesn't seem to be enough. i have dovecot 0.99. thx.

2 1

[Dovecot] Dovecot - Issue with Maildir++ quotas
by Andrew Richards 16 Aug '06

16 Aug '06

Hi, I've been bitten by an issue running Squirrelmail on top of Dovecot using Maildir++ quotas. Having configured these quotas in Dovecot, I notice that Dovecot appears not to exclude the 'Trash' folder from its quota calculation (which it should do, according to the Maildir++ spec). Unfortunately this breaks Squirrelmail if I try to delete a message from a close-to-quota mailbox - as per July's thread: "Maildir++ quota - how to handle a full mailbox" Which unfortunately means that a fairly full mailbox can become 'Wedged' with Dovecot/Squirrelmail in this situation with its owner unable to delete messages if that's the only way they access their mailbox. I took a look at the source and found the 'Quota exceeded' lines in src/plugins/quota/quota-storage.c but didn't understand it well enough to dive in... except to notice that the 'Trash' folder doesn't appear to get excluded from the calculations. cheers, Andrew.

5 8

[Dovecot] multiple Authentication
by Marc Perkel 16 Aug '06

16 Aug '06

I'm using the following authentication passing the full email address user(a)domain.com auth default { mechanisms = plain # Linuxconf passwd-like file with specified location passdb passwd-file { args = /etc/vmail/shadow.%d } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d } user = root } But - what I want to do is if the user doesn't enter the domain part I want it to assume one specific domain. How would I do that?

2 1

[Dovecot] POP3 and TLS don't work (dovecot 1.0 rc6)
by kaspars.bogdanovs＠awtech.lv 16 Aug '06

16 Aug '06

Hi! It seems there are problem with POP3 connection when TLS enabled. Previously it worked fine, but for now it doesn't... Plain & SSL POP3 works. Plain, TLS & SSL IMAP works too. In logs nothing than: dovecot: Aug 16 10:36:23 Warning: pop3-login: SSL_accept() failed: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [xxx.xxx.xxx.xx] xxx.. - remote ip address On client side: KMail - Could not connect to host Your POP3 server claims to support TLS but negotiation was unsuccessful. You can disable TSL in KDE using the crypto settings module. Thunderbird (on Windows) - nothing special, but can't connect. OS: Debian Linux __ Kaspars P.S. sorry for bad english

2 1

[Dovecot] default_realm problem
by Anton Martchukov 16 Aug '06

16 Aug '06

Hello List, I've upgraded to dovecot from FreeBSD ports, changed the config from previous 0.99 version, but meet a problem with %d variable beeing empty in userdb static configuration directive. Our server supports multiple domains, e.g. 'mxc.ru' and 'mail.mxc.ru'. Users can log into using their full e-mail address like antonm(a)mxc.ru or antonm(a)mail.mxc.ru, but the feature of adding default domain should also be present, e.g. when logging with user name 'antonm' server should assume username to be 'antonm(a)mxc.ru' cause 'mxc.ru' is the default domain. This wroked fine in 0.99 version, but, alas, I can't get it working in newer version. I've tried different settings combination, but all of them results in '%d' beeing empty Debug authentication log is: dovecot: Aug 16 10:59:46 Info: auth(default): auth(antonm(a)mxc.ru,10.3.1.192): username changed antonm(a)mxc.ru -> antonm dovecot: Aug 16 10:59:46 Info: auth(default): ldap(antonm,10.3.1.192): uid(user)=antonm userPassword(password)=<hidden> dovecot: Aug 16 10:59:46 Info: auth(default): client out: OK 1 user=antonm dovecot: Aug 16 10:59:46 Info: auth(default): master in: REQUEST 11 97887 1 dovecot: Aug 16 10:59:46 Info: auth(default): master out: USER 11 antonm uid=1004 gid=1004 home=/data/mai lspool//antonm The problem here seems to be with "username changed antonm(a)mxc.ru -> antonm", but I do not know how to switch it off. The relevant config file parts are: dovecot.conf: auth_default_realm = mxc.ru auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth default { mechanisms = plain digest-md5 passdb ldap { args = /usr/local/etc/dovecot-ldap.conf } userdb static { args = uid=1004 gid=1004 mail=maildir:/data/mailspool/%d/%n } } dovecot-ldap.conf: #all user attrs here are commented, since we don't get any user info from ldap, but checking a password #user_attrs = uid,homeDirectory,,,uidNumber,gidNumber #user_attrs = ,,,,,,, #user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_filter = (&(objectClass=mailUser)(dc=%d)(uid=%n)(accountActive=TRUE)) default_pass_scheme = PLAIN The authentication is working, so on the pass_filter in dovecot-ldap.conf '%d' is resolved properly, but in userdb static's mail argument it's empty whatever I do. Thank you for your help! -- Anton Martchukov - http://www.martchukov.com

2 1

[Dovecot] Problems after upgrade (0.99.x -> 1.0.x)
by fazer69＠o2.pl 16 Aug '06

16 Aug '06

Hello :) I had a working Dovecot 0.99.x with the following dovecot.conf: ### ssl_disable = yes disable_plaintext_auth = no login = imap verbose_proctitle = yes default_mail_env = maildir:%h/Maildir auth = default auth_mechanisms = plain auth_userdb = passwd /etc/passwd auth_passdb = shadow /etc/shadow auth_user = root protocols = imap pop3 ### Then I've downloaded, compiled and installed Doveot 1.0.rc6, I tried lot of "possibilities" in the new dovecot.conf but I always get : dovecot: Dovecot v1.0.rc6 starting up dovecot: Login process died too early - shutting down dovecot: child 15288 (login) killed with signal 11 dovecot: child 15289 (login) killed with signal 11 dovecot: child 15290 (login) killed with signal 11 Some add. info: # dovecot -n # /usr/local/etc/dovecot.conf ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login auth default: passdb: driver: shadow args: /etc/shadow userdb: driver: passwd How can I get the new Dovecot acting as the old one? I don't use pam (which seems to be default now), simply shadow passwords (Slackware). http://wiki.dovecot.org/UpgradingDovecot did not help me. TIA, websafe

6 7

[Dovecot] Migrating from qpopper to dovecot
by asko 16 Aug '06

16 Aug '06

Hi, I am planning a migration from Qpopper 4.0.5 to Dovecot.. I need to use mbox format (because Openwebmail does not have native Maildir support yet) and pop3. The system will have about 1500 users, once migrating is complete. To avoid users downloading their mailboxes all over again, i need to set "pop3_reuse_xuidl = yes".. But that option works since Dovecot 1.0alpha1. RHEL has latest stable version 0.99.11-2. So let me rephrase my question: is latest dovecot (1.0.rc6) stable enough to handle the load (mbox with pop3) or should I wait for the stable version to come out.. I want to avoid trouble under heavy load and/or with different pop3 clients. I found some problem reports of mbox related issues from dovecot mailing list. I could go with latest Qpopper 4.0.8, trading speed to safety.. If you have any similar experiences, please share your knowledge ;-) -- asko

1 0