- dovecot - dovecot.org

[Dovecot] LDAP authentication via PAM
by Oscar A. Valdez 09 Apr '06

09 Apr '06

I've configured dovecot to authenticate against a Fedora Directory Server. The mail server on which dovecot is installed has the nss_ldap and pam_ldap packages installed, and /etc/dovecot.conf has the following two lines: auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = pam In other words, I want dovecot to use LDAP to access the user database, but PAM for authentication. This part is working, since users authenticate and get their mails correctly through dovecot. /etc/dovecot-ldap.conf contains the following: hosts = 192.168.0.2 ldap_version = 3 base = ou=People, dc=duraflex, dc=com, dc=sv deref = never scope = subtree user_attrs = uid,homeDirectory,,,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(uid=%u)) I haven't specified a dn or dnpass, since all I need is that dovecot perform an anonymous query for the uid, homeDirectory, uidNumber and gidNumber fields of its users, which are publically viewable. However, my FDS server's access log has entries like these: conn=3266227 fd=138 slot=138 connection from 192.168.0.100 to 192.168.0.2 conn=3266227 op=0 BIND dn="" method=128 version=3 conn=3266227 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="" conn=3266227 op=1 SRCH base="ou=People,dc=duraflex,dc=com,dc=sv" scope=1 filter="(&(objectClass=posixAccount)(uid=dovecot))" attrs=ALL conn=3266227 op=1 RESULT err=0 tag=101 nentries=0 etime=0 conn=3266227 op=2 SRCH base="ou=Groups,dc=duraflex,dc=com,dc=sv" scope=1 filter="(&(objectClass=posixGroup)(memberUid=dovecot))" attrs="gidNumber" conn=3266227 op=2 RESULT err=0 tag=101 nentries=0 etime=0 conn=3266227 op=-1 fd=138 closed - B1 Dovecot binds anonimously with an empty dn, then queries FDS for a user and a group called dovecot (which don't exist on the DS), and finds 0 entries. Is it possible to access the user database through PAM (auth_userdb = pam)? Since I'm running the nss_ldap and pam_ldap modules, it'd really be an LDAP query for users, and a query in /etc/passwd and /etc/group for dovecot (since it's a local user and group on the mail server). -- Oscar A. Valdez

2 1

[Dovecot] auth problem with dovecot-1.0.beta5
by Alan McKay 09 Apr '06

09 Apr '06

Hey folks, Let me start by saying I really love what I see so far! Dovecot seems to be extremely feature-rich, and unlike a lot of free software the documentation is extremely good! I gave up on courier IMAP because of the poor documentation, and I have to say Dovecot sure differentiates itself in that area! Unfortunately I still can't get it going :-/ First thing I noticed is that --with-shadow does not appear to be working on my FreeBSD 6.0 system. Here is what I built with : ./configure --prefix=/usr/local --enable-shared --enable-static --disable-ipv6 --with-ioloop =poll --with-passwd --with-shadow --with-pam --with-passwd-file --without-checkpassword --wit hout-bsdauth --without-gssapi --without-ldap --with-static-userdb --without-prefetch-userdb --without-sql --without-mysql --without-ssl --with-rundir=/var/run/dovecot --with-storages=mb ox --without-sql-drivers However : root@heimat# dovecot --build-options Build options: ioloop=poll Passdb: checkpassword pam passwd passwd-file vpopmail Userdb: checkpassword passwd passwd-file static vpopmail And when I try to include the shadow options in the config file I get this in the log file : Apr 8 17:07:38 heimat dovecot: auth(default): Unknown passdb driver 'shadow' (typo, or Dovecot was built without support for it? Check with dovecot --build-options) No big deal. I've never used PAM, but I'll have a go at it. My config file looks like this : base_dir = /var/run/dovecot/ protocols = imap listen = 127.0.0.1 ssl_disable = yes first_valid_uid = 1000 last_valid_uid = 2000 first_valid_gid = 1000 last_valid_gid = 2000 default_mail_env = mbox:~/IMAP/:INBOX=/var/mail/%u mail_extra_groups = mail protocol imap { } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 auth default { mechanisms = plain userdb passwd { } passdb pam { # args = session=yes * args = * } #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} user = root } And I cannot get my webmail to auth. So I decided to "telnet localhost 143" and try typing the login command like the docs suggest. But here's what I get : telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost.dmz.alanmckay.com. Escape character is '^]'. * OK Dovecot ready. LOGIN amckay XXXXXX LOGIN BAD Error in IMAP command received by server. Something tells me there is a big problem here :-/ Which brings me to my next question : is there a "latest stable" release? I didn't see anything obvious on the website. thanks! -Alan -- "True Budo is done for the sake of building peace. Train every day so as to make peace between this spirit and all things manifested on the face of the Earth" - Ueshiba Morihei

4 6

[Dovecot] looking for headway on Timeout leak
by David Powers 09 Apr '06

09 Apr '06

mail1 dovecot: imap(smith(a)willcapmanagement.com): Timeout leak: 0x807fad0 Can anyone give me a heads up on what might cause the above message? I am working on polishing a plugin and it continues to throw this error with no seeming consequences. -David

2 1

[Dovecot] beta5: Solaris, IMAP, DOA
by Jeff A. Earickson 09 Apr '06

09 Apr '06

Help... Both beta4 and now beta5 die immediately at startup for me: Apr 7 14:29:32 emerald dovecot: [ID 474997 mail.info] Dovecot v1.0.beta5 starting up Apr 7 14:29:33 emerald dovecot: [ID 128275 mail.error] Auth process died too early - shutting down My setup: Solaris 9, built with gcc 4.1.0, IMAP only, mbox format, INBOXes NFS mounted, index and other mail folders local disk. Beta3 continues to work great for me; imap-login for it notes "method=PLAIN, TLS" in the syslogs. There were no real changes in my dovecot.conf between beta3 and beta5. What broke? What to look for to fix this problem? Jeff Earickson Colby College

2 1

[Dovecot] One dovecot, multiple addresses
by Nick Plante 09 Apr '06

09 Apr '06

There was a thread in February called "One dovecot, multiple domains" that I'd like to follow up on... I have a similar need; a hosted system with a couple IP aliases currently running dovecot for users at imap.domain1.com on one of those addresses. Now I need to also make it accessible via the name imap.domain2.com on a different address. Both "hosts" require SSL certs. They'll be using the same user auth source and have access to the same mailspools (although certain users will access theirs through domain1 and others through domain2). It sounds like dovecot doesn't support this sort of ip-based virtual hosting scheme right now. Is it possible to just configure two separate instances of the server, one bound to each virtual interface with their separate certs? Or are there issues with this poor man approach (contention, etc)? TIA; nap.

3 2

[Dovecot] problem authenticating passwd
by richard＠richard-brouwer.nl 08 Apr '06

08 Apr '06

Maybe you guys seen this question a thousand times but really I can't find a solution. So is there anybody who can give me a direction or a clue to solve my problem. I configured my dovecot as follows: protocols = imap pop3 imaps pop3s login_chroot = yes login_user = dovecot auth_verbose = yes auth default { mechanisms = plain passdb passwd { args = /etc/passwd } userdb passwd { args = /etc/passwd } user = root } The maillog gives me that there is password mismatch, but I'm 100 % sure that the password is correct. I allso looked in my /etc/passwd file and the user is there. The user is all so able to login the Linux system. My system is Fedora redhat RC 5. Dovecot is v1.0.beta2. I attached the last rules of my maillog. Is there anybody who can please help me. Thx in advance richard This is the tail of the maillog: Apr 8 10:58:12 host dovecot: Killed with signal 15 Apr 8 10:58:34 host dovecot: Dovecot v1.0.beta2 starting up Apr 8 10:59:09 host dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.0.200 rip=192.168.0.104 resp=AHJpY2hhcmRAcmljaGFyZC1icm91d2VyLmNvbQBoYWxsbzUzOA== Apr 8 10:59:09 host dovecot: auth(default): passwd(richard(a)richard-brouwer.com,192.168.0.104): unknown user Apr 8 10:59:11 host dovecot: auth(default): client out: FAIL 1 user=richard(a)richard-brouwer.com Apr 8 11:00:00 host dovecot: auth(default): client in: AUTH 2 PLAIN service=POP3 lip=192.168.0.200 rip=192.168.0.104 resp=AHJpY2hhcmRAcmljaGFyZC1icm91d2VyLm5sAGhhbGxvNTM4 Apr 8 11:00:00 host dovecot: auth(default): passwd(richard(a)richard-brouwer.nl,192.168.0.104): password mismatch Apr 8 11:00:01 host dovecot: auth(default): client out: FAIL 2 user=richard(a)richard-brouwer.nl

2 1

[Dovecot] pop-before-smtp Dovecot pattern
by Bjorn Patterson 08 Apr '06

08 Apr '06

Hi, Having some problems with the default pattern in the pop-before-smtp.pl.conf file for dovecot. Also the one off the dovecot wiki doesn't seem to work and since I can't seem to figure out how these patterns work I hoping someone could help me out with a custom pattern. This is what my mail log looks like: Apr 8 23:30:40 nemesis dovecot: pop3-login: Login: user=<bjorn>, method=PLAIN, rip=::ffff:203.109.208.111, lip=::ffff:192.168.0.253 Any help would be much appreciated _________________________________________________ Regards: Bjorn Patterson Digitalsouth Networks ICC Technician HYPERLINK "http://www.digitalsouth.net.nz/"http://www.digitalsouth.net.nz [ When replying to this, please include a copy of the original message. ] -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/304 - Release Date: 7/04/2006

2 1

[Dovecot] where do i get updates from? (one for Timo?)
by Obantec Support 08 Apr '06

08 Apr '06

Hi i am on FC3 and ran yum update dovecot and it offers dovecot.i386 0:0.99.13-3.FC3 i thought there was a 1.X beta4 which i should be using? (i have 1.0 stable running from a while back) Mark

4 4

[Dovecot] plain auth problem with beta4
by Mark Davies 08 Apr '06

08 Apr '06

Using kmail with PLAIN authentication worked fine with beta3 but trying it with beta4 authentication fails. This is because kmail sends "username \0 username \0 password" in the authorization token and the new code to call auth_request_set_login_username() when supplied an authid must be returning failure (certainly commenting this code out returns to the beta3 behaviour of successfully authenticating). I had a quick look at the routine to see why it might be failing but didn't really work out what its supposed to do. cheers mark

2 3

[Dovecot] Dovecot article @ Linux.com
by Thomas Zajic 07 Apr '06

07 Apr '06

There's a short article up on Linux.com introducing Dovecot. Just thought I'd let you know. ;-) http://applications.linux.com/article.pl?sid=06/03/28/1919226&from=rss Thomas -- =-------------------------------------------------------------------------= - Thomas "ZlatkO" Zajic <zlatko(a)gmx.at> Linux-2.6.16 & Thunderbird-1.5 - - "It is not easy to cut through a human head with a hacksaw." (M. C.) - =-------------------------------------------------------------------------=

1 0