- dovecot - dovecot.org

[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

[Dovecot] LDAP: bind to LDAP server instead of retreiving a password from it?
by Geert Hendrickx 10 Jul '06

10 Jul '06

Hi, Dovecot currently treats an LDAP user/password database the same way as a text or SQL based database: it just tries to retreive the (hashed) password for a given username. LDAP however has the capability to authenticate the user itself: dovecot could try to bind to LDAP with the given username and password, and if authentication succeeded, the LDAP server returns the other info (uid, homedir, ...), but not the password. I know at least qmail's pop3 server uses LDAP this way. Could this authentication mechanism be implemented in Dovecot as well? Geert

2 2

[Dovecot] Damnitall
by nick 10 Jul '06

10 Jul '06

Today I upgraded to dovecot 1.0 rc1 (before I was using a 1.0 beta, as it had functions no one else had), the beta worked fairly well, no crashes, and the bugs were few and far between. I had a few issues with thunderbird 1.5, so I decided to upgrade. My problem is this, before, I had configured procmail to deliver SPAM to a subdirectory of the users home directory, (not mail/) and everything worked fine, new directories were creatable, and IMP seemed to be happy with everything as it was. With the new version though, dovecot refuses to see the folders in the base of the home directory, and all of this with absolutely no change to my conf file (except for the passdb and userdb options). my dovecot.conf file looks like this: default_mail_env = mbox:/ha/home/%u:INBOX=/ha/mail/%u:INDEX=/ha/home/%u ha is my drbd directory, for high availability. I've tried modifying the private namespaces, but without much luck, and I'm really not looking forward to moving all those folders to under the mail/ directory. Do I have any other options?? thanks, Nick

5 8

[Dovecot] Dovecot and MS Active Directory.
by Sysadmin 10 Jul '06

10 Jul '06

Hello. We are using dovecot right now, but the boss pushes the MS based system (Exchange, Sharepoint, Active Directory etc) to use. However, skipping the other parts I'd like to keep open source based mail server and the question is - can the dovecot authenticate against the MS Active Directory without any problems? -- Sysadmin

2 1

[Dovecot] Oops, forgot about apop...
by Bruce Lane 10 Jul '06

10 Jul '06

How does one go about generating a local password database for apop authentication? Or can it simply run against /etc/passwd, using a PAM entry? (I forgot to append this to my last message... sorry...). Thanks much. -=-=-=-=-=-=-=-=-=-=-=- 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 1

[Dovecot] New User: POP3 issues
by kyrrin＠bluefeathertech.com 10 Jul '06

10 Jul '06

Fellow dovecot'ers, I'm just getting started with Dovecot, and I'm not a programmer, so please be gentle. ;-) THE PLATFORM: NetBSD 3.0/SPARC, Postfix 2.3-RC8, current Dovecot RC (I forgot the number). Maildir-type directories. THE GOAL: To accommodate authenticated (remote) POP3 users with APOP or SSL/TLS, and allow users on the internal network (192.168.x.x) to just use basic POP3 without worrying about authentication. QUESTIONS: (1) Does the dovecot master daemon have to be running in order to call pop3- login from inetd, in response to POP connection attempts? If so, it could be a problem. I'm getting this error when I try to start the thing. featherweb: {339} /usr/local/sbin/dovecot Fatal: listen(110) failed: Address already in use featherweb: {340} (2) For apop authentication, how do I go about generating the shared secret file locally, for each user? Is there a script that came with dovecot or...? (3) Is there a trick, similar to postfix's 'postconf -n,' that will give a condensed output of dovecot's configuration file? (4) I'm currently using sasl auth for Postfix's SMTP auth function. How difficult is it to use Dovecot for the same thing? (5) GAAAAHHHHH! (Just on general principles, based on the hours I've spent trying to get everything working). Thanks in advance. --- Bruce 'Quietly Making Noise' Lane Blue Feather Technologies

3 2

[Dovecot] /var/dovecot /var/spool/mail permissions, setup help (w/ config info)
by Jeff Kowalczyk 08 Jul '06

08 Jul '06

(repost gmane message as list member) I need some help with Dovecot-1.0rc2 on Gentoo Linux. My test harness is one Thunderbird-1.5.0.4 client, storage using legacy mbox directories ported over from an old UW-IMAP/sendmail combo running on RHL 8. Config is intended to be passwd/pam, plaintext login allowed (until I migrate everyone to ssl). After this is working, postfix and dspam are to be added, unless someone can recommend a 'dovecot of smtp' to use. I'll tail the mail.log to illustrate the problem, then excerpt what I think are the relevant directory and config file listings. I'm paying particular attention to file ownership, but am loathe to just chown dovecot things unless I know why. Let me know if you want to see any other config info to help spot the problem. Thanks! # tail -n 30 /var/log/mail.log dovecot: Jul 05 18:35:25 Info: Dovecot v1.0.rc2 starting up dovecot: Jul 05 18:36:10 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=123.456.789.012 rip=098.765.432.109 dovecot: Jul 05 18:36:10 Info: auth(default): client out: CONT 1 dovecot: Jul 05 18:36:10 Info: auth(default): client in: CONT 1 AGplZmYua293YWxjenlrAHdvcmRwYXNzMQ== dovecot: Jul 05 18:36:10 Info: auth(default): client out: OK 1 user=namefirst.namelast dovecot: Jul 05 18:36:10 Info: auth(default): master in: REQUEST 1 25692 1 dovecot: Jul 05 18:36:10 Info: auth(default): master out: USER 1 namefirst.namelast system_user=namefirst.namelast uid=501 gid=12 home=/home/namefirst.namelast dovecot: Jul 05 18:36:10 Error: stat(/var/dovecot/namefirst.namelast) failed: No such file or directory dovecot: Jul 05 18:36:10 Info: IMAP(namefirst.namelast): Effective uid=501, gid=12 dovecot: Jul 05 18:36:10 Info: IMAP(namefirst.namelast): mbox: data=/var/spool/mail/namefirst.namelast:INDEX=/var/dovecot/namefirst.namelast dovecot: Jul 05 18:36:10 Info: IMAP(namefirst.namelast): mbox: INBOX defaulted to /var/spool/mail/namefirst.namelast/inbox dovecot: Jul 05 18:36:10 Info: IMAP(namefirst.namelast): mbox: root=/var/spool/mail/namefirst.namelast, index=/var/dovecot/namefirst.namelast, inbox=/var/spool/mail/namefirst.namelast/inbox dovecot: Jul 05 18:36:10 Info: imap-login: Login: user=<namefirst.namelast>, method=plain, rip=098.765.432.109, lip=123.456.789.012 dovecot: Jul 05 18:36:10 Error: IMAP(namefirst.namelast): open() failed with subscription file /var/spool/mail/namefirst.namelast/.subscriptions: Not a directory dovecot: Jul 05 18:36:12 Error: IMAP(namefirst.namelast): open(/var/spool/mail/namefirst.namelast/inbox, O_CREAT) failed: Not a directory dovecot: Jul 05 18:36:12 Error: IMAP(namefirst.namelast): mkdir_parents(/var/dovecot/namefirst.namelast/.imap/INBOX) failed: Permission denied dovecot: Jul 05 18:36:14 Info: IMAP(namefirst.namelast): Disconnected: Logged out # ls -al /var/spool/mail drwxrwxr-x 2 root mail 1472 Jul 2 19:20 . drwxr-xr-x 6 root root 168 Jul 3 14:19 .. -rw-r--r-- 1 root root 0 Jun 27 18:46 .keep -rw------- 1 namefirst.namelast mail 36243879 Jul 1 17:52 namefirst.namelast (...) # ls -al /var/dovecot/ total 0 drwxr-xr-x 2 root root 72 Jul 5 10:30 . drwxr-xr-x 14 root root 360 Jun 29 09:45 .. -rw-r--r-- 1 root root 0 Jul 5 10:30 .keep # ls -al /var/run/dovecot/ total 5 drwxr-xr-x 3 root root 176 Jul 5 18:35 . drwxr-xr-x 9 root root 504 Jul 3 14:45 .. srw------- 1 root root 0 Jul 5 18:35 auth-worker.25687 srwxrwxrwx 1 root root 0 Jul 5 18:35 dict-server drwxr-x--- 2 root dovecot 136 Jul 5 18:35 login -rw------- 1 root root 6 Jul 5 18:35 master.pid # ls -al /home/namefirst.namelast/ total 17791 drwxr-xr-x 2 namefirst.namelast mail 248 Jul 5 18:29 . drwxr-xr-x 76 root root 2512 Jul 2 20:21 .. -rw------- 1 namefirst.namelast mail 3293785 Sep 23 2005 Sent # grep dovecot /etc/group dovecot:x:97: # grep dovecot /etc/passwd dovecot:x:97:97:added by portage for dovecot:/dev/null:/usr/sbin/nologin # grep mail /etc/passwd mail:x:8:12:mail:/var/spool/mail:/bin/false postmaster:x:14:12:postmaster:/var/spool/mail:/bin/false # grep mail /etc/group mail::12:mail # grep namefirst.namelast /etc/passwd namefirst.namelast:x:501:12:First Last:/home/namefirst.namelast:/bin/bash # cat /etc/pam.d/dovecot auth required pam_unix.so account required pam_unix.so # cat /etc/dovecot.conf base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s listen = * shutdown_clients = yes log_path = /var/log/mail.log info_log_path = /var/log/mail.log log_timestamp = "%b %d %H:%M:%S " syslog_facility = mail disable_plaintext_auth = no ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem login_chroot = yes login_user = dovecot default_mail_env = mbox:/var/spool/mail/%u:INDEX=/var/dovecot/%u mail_extra_groups = mail mail_debug = yes protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain login passdb pam { args = dovecot } userdb passwd { } user = root } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

[Dovecot] FYI: timosieved
by John Peacock 07 Jul '06

07 Jul '06

Just a heads up for all interested in using the Dovecot LDA with SIEVE scripting: I've started work on a proof-of-concept managesieve daemon, since the only one available right now is dependent on Cyrus. It appears that the only choice available for sites not using timsieved is the Ingo component of Horde, which is way too fat to install by itself (plus it uses FTP for a transport, which I make it a rule not to install). For testing purposes, I am hacking together a Perl module based on the Net::Server model (which is not suitable for production). If this goes well (the managesieve protocol is painfully stupid and the only tricky part is linking in libsieve), then I'll do a rewrite in C. It will authenticate directly to Dovecot through the auth-client (or auth-master) mechanism, so whatever SASL methods that Dovecot supports, it will support. I've decided that the eventual server will be called timosieved, in honor of our host, and echoing the original Cyrus timsieved. Don't bug me about when it'll be done... :) John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748

3 2

[Dovecot] default_mail_env and IMAP server directory in client
by Dirk Essl 07 Jul '06

07 Jul '06

Hi, I'm currently installing a dovecot Server to be a replacement for an uw-imapd. I dont want to touch the clients configuration, because I have too much users... Situation is the following: the mbox files are in the users homedirectory (~/MailImap), automounted via nfs In dovecot.conf I've set default_mail_env = mbox:%h/MailImap:INBOX=/var/mail/%u It works perfect without a value in Firefox' setting 'IMAP server directory' but in all clients tis is set to '~/MailImap' so it doesnt show subfolders I already tried to symlink various things in the MailImap directory and different values of default_mail_env, but I cannot mak it work. Any suggestions? It would help if dovecot could discard the IMAP server directory setting of the client, but I am not a programmer and dont know where to look in the source :-( -- TIA dirk

2 1

[Dovecot] 1.0.rc2 ldap in Solaris
by Tomi Vainio 07 Jul '06

07 Jul '06

Hi, Earlier it was possible to compile ldap support in Solaris 10 but currently it fails in src/auth/db-ldap.c line 341 because LDAP_SASL_QUIET is missing. I can found eg. LDAP_SASL_INTERACTIVE from headers. Tomppa

1 0