- dovecot - dovecot.org

[Dovecot] Auth error in log
by Per-Henrik Lundblom 03 Sep '13

03 Sep '13

Hi, I have a setup with Dovecot handling a few virtual domains delivering mails to both local Unix account mailboxes and seperate mailboxes for virtual users defined in a MySQL database. A quick overview of the configuration shows two passdb definitions: auth default { mechanisms = plain login passdb pam { args = dovecot } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { args = mail=maildir:~/Maildir blocking=yes } userdb static { args = uid=vmail gid=mail home=/var/spool/vmail/%d/%n allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } !include_try /etc/dovecot/auth.d/*.auth } When a virtual user defined in the MySQL database tries to log in using IMAP or SMTP I always get auth failures logged in the system logs. Entries are like this: Aug 21 06:25:36 roadrunner dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=luser(a)mydomain.com rhost=85.224.xx.xx I assume these failures comes form the fact that PAM doesn't recognize the virtual users and Dovecot continues to the SQL passdb entry. As a result I get a _lot_ of auth failures in the logs. I have tried to come up with a way where the auth failures from PAM arent't logged if the the SQL authenication is successful. Is this possible or are there any other recommended ways to handle this? /PH -- Per-Henrik Lundblom email: ph(a)whatever.nu phone: +46 733 207126 webpage: www.whatever.nu

2 3

[Dovecot] local AND virtual mail locations ?
by Pierre-Philipp Braun 02 Sep '13

02 Sep '13

Hi, I would like to use Dovecot not only for virtual mboxes, but also for local users. In other words, I would like to use different "mail_location"s depending on "passdb" "passwd-file" versus "passwd". I need that as the smtp daemon I am using (david parsons' postoffice smtp server) serves both but is only able to process messages through procmail on local users. Here are the two mail_locations I would like to use: mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n depending on those passdb stanzas, respectively: passdb passwd-file { args = username_format=%n /etc/virtual/%d/passwd } passdb passwd { } Any help would be appreciated. Here's my Dovecot version and current working configuration for virtual users only: # dovecot -n dovecot -n # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.3-RELEASE amd64 ufs protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 6 first_valid_gid: 6 mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n imap_client_workarounds: tb-extra-mailbox-sep auth default: user: mail passdb: driver: passwd-file args: username_format=%n /etc/virtual/%d/passwd userdb: driver: static args: uid=6 gid=6 I find that first_valid_uid and first_valid_gid don't look pretty but it seems mandatory for the standard 'mail' user and group ownerships to work on the virtual mbox files and folders. I created the user while the group already existed. If you have any advices on that too, I would be pleased. Thanks Pierre-Philipp

3 7

[Dovecot] migration from IMAP/POP3 courier server to a remote dovecot server
by nik600 02 Sep '13

02 Sep '13

Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read http://wiki2.dovecot.org/Migration and http://wiki2.dovecot.org/Migration/Courier and http://wiki2.dovecot.org/Migration/Dsync And decided that probably the best tool to use is Dsync, as the courier-dovecot-migrate.pl<http://www.dovecot.org/tools/courier-dovecot-migrate.pl> script works only locally. I've tested the dsync following instructions reported above but after the migration of one test-account the client re-download messages. If i want to keep both IMAP UIDs and POP3 UIDs i have to sync both imapc and pop3c with two commands? doveadm -o imapc_user=foo -o pop3c_user=foo -o imapc_password=bar -o pop3c_password=bar backup -R -u user@domain imapc: doveadm -o imapc_user=foo -o pop3c_user=foo -o imapc_password=bar -o pop3c_password=bar backup -R -u user@domain pop3c: Or imapc is enough? Do you have any suggestion? Thanks -- /*************/ nik600 http://www.kumbe.it

1 2

[Dovecot] Getting back into Dovecot 2.2.5
by Kai Hendry 02 Sep '13

02 Sep '13

Hi there, I'm prompted to get into running my own mail server again with Gmail going bad. However I found /usr/share/doc/dovecot/example-config/conf.d/ a little scary, since I like to have my configs as minimalistic as possible, e.g. http://dabase.com/blog/Minimal_squid3_proxy_configuration/ So far I have: https://github.com/Webconverger/sg.webconverger.com/blob/master/dovecot/dov… I was kinda hoping for a Maildir, but this doesn't work: mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=/var/mail/%u I do realise /var/mail/%u is a mbox, but I was wondering if there could be some clever conversion. I was surprised something like INBOX=/var/mail/%u wasn't the default btw. Also surprised dovecot seems to choke on single line syntax like `passdb { driver = pam }` :-) Next thing I'm confused about is the `namespace inbox {` stuff. Is it really needed? I was expecting Dovecot to create the folders once I defined them, but mutt couldn't see them until I created them myself. The mail server is just for myself and a few colleagues. We will probably use mutt as our MUA and Apple Mail on IOS when we are out & about. I next plan to integrate dspam, and work out how to sort mails into folders like I previously effectively had with Gmail's labels. I was confused to which mechanism I should be using to sort mail into folders with rules. Sieve? Back to Procmail? Pigeonhole? I'm looking to avoid complexity here. On the topic of search, can I get away with not running a Solr server? Since I shudder at the thought of running Tomcat. http://wiki2.dovecot.org/Plugins/FTS Kiitos paljon for any pointers!

3 4

[Dovecot] Auto-blocking faulty login attempts
by Jos Chrispijn 01 Sep '13

01 Sep '13

Dear group, How can I block login attempts to dovecot after trying 5 times in error? -- Best regards, Jos Chrispijn --- Artificial intelligence is no match for natural stupidity

3 2

[Dovecot] Dovecot and Postfix Authentication
by Christopher Trom 31 Aug '13

31 Aug '13

I am a student and am trying to get a mail server setup for a project. I have all of the Postfix configuration taken care of, but I am confused by the way that authentication works with Dovecot in the mix. As a user of the system, am I supposed to authenticate myself to Postfix, Dovecot, both individually, or both together? My Postfix users are stored in a PostgreSQL database, should Dovecot also be connected to this db? Some basic pointers on how this setup ought to look is all that I'm hoping for. Thank you, Christopher

2 1

Re: [Dovecot] Bizarre permissions problem
by Joseph Tam 31 Aug '13

31 Aug '13

Bill Oliver writes: > There's *one* user I can't get it to work on without a > workaround. The user is "newuser" and the uid is 1111 (actual name and > number changed to protect the innocent). The error I get in my maillog > is: > > The error I get in may maillog is: > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > > Now, it looks to me like dovecot is saying that the user newuser can't > get to the /home/newuser/mail/.imap directory because it doesn't have > permission. However, the user newuser has all the permissions it needs: > > $ ls -la /home/newuser/mail > > total 20 > drwxrw---- 3 newuser newuser 4096 Aug 29 15:01 . > drwxrw---- 6 newuser newuser 4096 Aug 29 12:16 .. > drwxrwx--- 2 newuser newuser 4096 Aug 29 16:05 .imap > -rw-rw---- 1 newuser newuser 499 Aug 13 07:56 saved-messages > -rw-rw---- 1 newuser newuser 1756 Aug 16 11:15 sent-mail The output of doveconf -n would have been useful, especially as it relates to your mail_location value, but I can make a pretty good guess at what is happening. Dovecot is trying to create indices with analogous permissions to your mailbox files. Your user's INBOX (/var/mail/newuser) has permission user:group:mode = 1111:12:0660 *but* newuser is not in group "mail" (GID 12), hence it cannot do the required chown operations. (Notice the mode of .imap/: the group write is on so the chmod worked.) Your INBOX ended up this way because some LDA's auto-create new INBOX's with these permissions (to allow access to other part of the mail sysyem that are set-gid "mail"). Options: 1) chmod g-rwx /var/mail/newuser - assumes you have no other parts of your mailsystem that needs access to all user INBOX by assuming group "mail". - dovecot is smart enough to figure out group membersip is irrelevant is groups access is nil. 2) chgrp newuser /var/mail/newuser 3) To avoid future problems: make sure new mailboxes are created with workable permissions. There are also dovecot configs that loosen up some group access, but you'll have to investigate that yourself. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] kqueue bug?
by Timo Sirainen 31 Aug '13

31 Aug '13

Apparently Dovecot with kqueue ioloop enabled causes random crashes in FreeBSD 9.1. Anyone else noticed something like that? I'm wondering if Dovecot's kqueue code has a bug somewhere (I can't find it) or could it be that FreeBSD itself has a bug? Anyway it seems to be returning events for filters that have already been removed.

4 3

[Dovecot] Log successful login plain text password
by Marco Fretz 30 Aug '13

30 Aug '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I want to use dovecot as a IMAP and POP3 proxy in front of our current E-Mail hosting server to log the plain text passwords of all successful logins for migration reasons. Actually I don't need the password to see in plain text, storing them as SHA256-CRYPT (or something dovecot can use later for auth) hash in a file or DB would be fine, too. I need this for the migration from the current mail server (using proprietary hashing to store passwords) to a new postfix / dovecot base mail system. I played around with "auth_debug_passwords" and all debug / logging options I found in the manual. Nothing logs successful login plaintext passwords. Any hint welcome. Thanks a lot, Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSHZ9tAAoJEKxm7Ju3UATui2cP/A3cf2TrNvOjjtP1TCgZZ5EC igsgngPlKiXU/RwHO9shBLXUyhKDHPGihNf9KL/RjoFnrgX1asPd/RF/2b080IU3 bNO49BLs8QqoroKz5E+TL8UNixlO5YQjnerKfJ5GIJbSUTC3MaxmN62Cl9jEaTWu 4dX3MXoB3ghoxt6FETSLXz6cEXsGd6KvqxolQC13NYtvpZED+qk7z3RywK8Xp/Au Ipx3xEnDRc/YvG3PeJlsjF9Ge80GxVVH0nudNOV/zmyuNfh4PkPRerk1R4Px01zI sxnXvcNjjenCJ6DMKBmOCyBii9Wl9i4opw9k4X4Z6MFEZGiodRz1usKWJMT0VqUG NBEJDOWsoWpasWMCtduBRrNQS3JI+o1tebDAI5n3K4lJ2d27+nosDvdQ8vNlVszM 8nhSn228RQNy9SJZNAvspOYQBM2gt5IQyWGA4jhrMUkwKeTfHZik8vh8lEcwbK9q H6Myue+i+G8wVa57F1V7/7x2LNGn56BWxTDlBrtKdK3KphCgEoCny/f5VYerO8It MnCMLPXI2oCC8qqkK7x45SYSe/eQhgV93LHpI5z25TqyeJ6R+7dglderRDQcNN0n OtbYMYkqlF8xJ4k+rVFwOC5VD7Bq+S2Q4LyLEf7wFH32Dc12pI/SnAL8DPvkNgbL FshgaVOXUEkb0WhnvROl =oEzx -----END PGP SIGNATURE-----

2 5

[Dovecot] Pigeonhole Sieve - sent message to xmpp account
by Ingo Thierack 30 Aug '13

30 Aug '13

Hello, does someone know, how far the implementation of enotify - xmpp is. Would be nice to push notifications to an jabber account for specific filtered mails. Regards, Ingo

2 1