- dovecot - dovecot.org

[Dovecot] Pam authentication failure message but it works
by Wayne Andersen 14 Jun '13

14 Jun '13

I am running Centos 6.4 64bit. Dovecot 2.0.9 I am getting the following messages in /var/log/secure, which looks like the pam authentication is not working but the users are allowed to login and the system works great. I am wondering if pam is actually failing and yet the system is getting the login info from elsewhere, or is this just a nuisance message? /var/log/secure Jun 12 23:11:29 smtp auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=christineg rhost=65.13.54.123 user=christineg Jun 12 23:11:45 smtp auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=susieg rhost=70.208.29.109 user=susieg Jun 12 23:12:03 smtp auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=bobs rhost=70.59.189.210 user=bobs In the debug log file I see what looks like a successful connection, but don't know how to read the two pam lines. /var/log/dovecot.debug.log Jun 12 23:11:29 auth: Debug: auth client connected (pid=10098) Jun 12 23:11:29 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=206.169.228.24 rip=65.13.54.123 lport=143 rport=54049 resp=AGNocmlzZwBjZzQ4MjU= Jun 12 23:11:29 auth: Debug: pam(christineg,65.13.54.123): lookup service=dovecot Jun 12 23:11:29 auth: Debug: pam(christineg,65.13.54.123): #1/1 style=1 msg=Password: Jun 12 23:11:29 auth: Debug: client out: OK 1 user=christineg Jun 12 23:11:29 auth: Debug: master in: REQUEST 4079353857 10098 1 0229474c9c1038e161328ecd28884af2 Jun 12 23:11:29 auth: Debug: passwd(christineg,65.13.54.123): lookup Jun 12 23:11:29 auth: Debug: master out: USER 4079353857 christineg system_groups_user=christineg uid=1116 gid=100 home=/home/christineg Jun 12 23:11:29 imap(christineg): Debug: Effective uid=1116, gid=100, home=/home/christineg Jun 12 23:11:29 imap(christineg): Debug: maildir++: root=/home/christineg/Maildir, index=, control=, inbox=/home/christineg/Maildir Jun 12 23:11:44 auth: Debug: auth client connected (pid=10100) Jun 12 23:11:45 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=206.169.228.24 rip=70.208.29.109 lport=143 rport=14107 Jun 12 23:11:45 auth: Debug: client out: CONT 1 Jun 12 23:11:45 auth: Debug: client in: CONT 1 AHJpY2hhcmRnQGNsaW1hLXRlY2guY29tAHJnMzgyMg== Jun 12 23:11:45 auth: Debug: pam(susieg,70.208.29.109): lookup service=dovecot Jun 12 23:11:45 auth: Debug: pam(susieg,70.208.29.109): #1/1 style=1 msg=Password: Jun 12 23:11:45 auth: Debug: client out: OK 1 user=susieg Jun 12 23:11:45 auth: Debug: master in: REQUEST 3368157185 10100 1 5a8d4b15a417d0bc4d2f818c5a5710f0 Jun 12 23:11:45 auth: Debug: passwd(susieg,70.208.29.109): lookup Jun 12 23:11:45 auth: Debug: master out: USER 3368157185 susieg system_groups_user=susieg uid=1087 gid=100 home=/home/susieg Jun 12 23:11:45 imap(susieg): Debug: Effective uid=1087, gid=100, home=/home/susieg Jun 12 23:11:45 imap(susieg): Debug: maildir++: root=/home/susieg/Maildir, index=, control=, inbox=/home/susieg/Maildir Jun 12 23:12:03 auth: Debug: auth client connected (pid=10104) Jun 12 23:12:03 auth: Debug: auth client connected (pid=10105) Jun 12 23:12:03 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=206.169.228.24 rip=70.59.189.210 lport=143 rport=38705 Jun 12 23:12:03 auth: Debug: client out: CONT 1 Jun 12 23:12:03 auth: Debug: client in: CONT 1 AGJyZW5kb25jQGNsaW1hLXRlY2guY29tAGJjMTU1NA== Jun 12 23:12:03 auth: Debug: pam(bobs,70.59.189.210): lookup service=dovecot Jun 12 23:12:03 auth: Debug: pam(bobs,70.59.189.210): #1/1 style=1 msg=Password: Jun 12 23:12:03 auth: Debug: client out: OK 1 user=bobs Jun 12 23:12:03 auth: Debug: master in: REQUEST 709623809 10104 1 0c261d849b956bf9cb5c0833b498bb97 Jun 12 23:12:03 auth: Debug: passwd(bobs,70.59.189.210): lookup Jun 12 23:12:03 auth: Debug: master out: USER 709623809 bobs system_groups_user=bobs uid=1188 gid=100 home=/home/bobs Jun 12 23:12:03 imap(bobs): Debug: Effective uid=1188, gid=100, home=/home/bobs Jun 12 23:12:03 imap(bobs): Debug: maildir++: root=/home/bobs/Maildir, index=, control=, inbox=/home/bobs/Maildir /etc/pam.d/dovecot #%PAM-1.0 auth required pam_nologin.so auth include password-auth account include password-auth session include password-auth # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.22.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %n auth_verbose = yes debug_log_path = /var/log/dovecot.debug.log disable_plaintext_auth = no hostname = mail.mydomain.com lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mbox_write_locks = fcntl passdb { args = failure_show_msg=yes driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /var/lib/dovecot/sieve/default.sieve } postmaster_address = postmaster(a)mydomain.com protocols = imap pop3 lmtp sieve sendmail_path = /usr/sbin/sendmail.postfix service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/postfix/mail.mydomain.crt ssl_key = </etc/postfix/mail.mydomain.key userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol pop3 { pop3_save_uidl = no pop3_uidl_format = %08Xu%08Xv }

1 0

[Dovecot] Autocreation the home folder
by Joan 14 Jun '13

14 Jun '13

Sorry if this has been already asked, but I haven't been able to find a solution, I am trying to migrate a dovecot 1.2 config to 2.1, the 'dovecot -n > dovecot.conf' migrated all the setup without issues, and the mail is working as expected. The only issue I've had is with the change with the mail_location, mail_home, that in the 2.1 versions can't be on the same path. After reading in the wiki the various config options ( http://wiki2.dovecot.org/VirtualUsers/Home) I opted to use the 3rd: Home directory under mail, for example: Maildir: home=/var/vmail/domain/user/home/ mail=/var/vmail/domain/user/ mbox: There's really no good and safe way to do it. So I changed from: mail_location = maildir:/home/vmail/%d/%n mail_home = /var/vmail/%d/%n To: mail_location = maildir:/home/vmail/%d/%n mail_home = /var/vmail/%d/%n/home The problem is that those home directories are not created (the mailboxes already existed) automatically, and I am getting these errors: ========================================================== May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Home dir not found: /var/vmail/example.com/username/home May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=20480000000 messages=0 May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota rule: root=User quota mailbox=Trash ignored May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota warning: bytes=15360000000 (75%) messages=0 reverse=no command=/etc/dovecot/quota-warning.sh 75 May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota warning: bytes=17408000000 (85%) messages=0 reverse=no command=/etc/dovecot/quota-warning.sh 85 May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: maildir++: root=/home/vmail/example.com/username, index=, control=, inbox=/home/vmail/example.com/username, alt= May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 May 10 17:08:59 server dovecot: lda(username(a)example.com): Debug: Quota warning: bytes=805306368 (75%) messages=0 reverse=no command=/etc/dovecot/quota-warning.sh 75 ======================================================== Am I supposed to create the folders via an external script? Or is there any option to make this automatic. Regards, Joan

4 10

[Dovecot] dovecot segfaults after upgrade
by Thomas Blomenkamp 14 Jun '13

14 Jun '13

Using dovecot on debian oldstable (squeeze) with daily builded repository, after an upgrade this morning, dovecot always shows the following error: 2013 Jun 10 11:07:22 mailstore imap(tblomenk): Fatal: master: service(imap): child 3016 killed with signal 11 (core dumps disabled) Jun 10 11:07:22 mailstore kernel: [ 1589.400741] imap[3016]: segfault at 7fffd9048ff8 ip 00007f91417e2c3b sp 00007fffd9049000 error 6 in libdovecot.so.0.0.0[7f9141796000+bc000] Please notice: I can reproduce the error by trying to access my mailbox with alpine or mutt, while alpine only can access my inbox. If I try to access my other folders, the error happens. Mutt always closes the connection after trying to login. It is a little bit strange because with a newer client like roundcube I can access all my folders successfully. In all kernel error messages it seems that error 6 in libdovecot.so.0.0.0[7f9141796000+bc000] is always the same. Also notice that dovecot is still running, it is just that you cannot access other folders than your inbox with pine. mailstore:~# dovecot --version 2.2.2 (45399357008a) mailstore:~# dovecot -n # 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1324) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1227) # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 auth_debug = yes auth_gssapi_hostname = mailstore.math.uni-bielefeld.de auth_mechanisms = plain login auth_username_format = %n auth_verbose = yes lmtp_save_to_detail_mailbox = yes log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Hi, the IMAP Mail-System on mailstore.math.uni-bielefeld.de is ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = mdbox:~/mdbox mail_plugins = acl mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave spamtest spamtestplus imapflags notify namespace { list = children location = mdbox:%%h/mdbox prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes.db mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_log_group_events = no quota = maildir:User quota quota_rule = *:storage=0 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +imapflags +notify +spamtest +spamtestplus sieve_spamtest_max_value = 100 sieve_spamtest_status_header = X-PMX-Spam: \.*Probability=([[:digit:]]+)%+\.* sieve_spamtest_status_type = score } protocols = imap lmtp sieve service auth { unix_listener auth-master { mode = 0600 user = vmail } unix_listener auth-userdb { user = vmail } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } process_limit = 1024 process_min_avail = 10 service_count = 1 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 vsz_limit = 64 M } ssl_cert = </etc/dovecot/mailstore_cert_chain.pem ssl_key = </etc/ssl/private/mcl_key.pem userdb { args = uid=vmail gid=vmail home=/var/vmail_san2/dovecot/%1Lu/%Lu driver = static } protocol imap { mail_plugins = acl imap_acl } protocol lmtp { mail_plugins = acl sieve } protocol sieve { mail_max_userip_connections = 50 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } Regards, Thomas

2 3

[Dovecot] IMAPC feature description
by Yonatan Broza 13 Jun '13

13 Jun '13

Hi, I couldn't find any decent documentation about the IMAPC feature. Could someone please explain the purpose of this feature? In particular, what are the differences between IMAPC and reverse proxying? Thanks.

2 1

[Dovecot] crash/mem violation in auth_worker + 50G logs in 2.1.7
by Mrten 13 Jun '13

13 Jun '13

Hi, This morning I discovered what seemed to be a deliberate crash in auth_worker: Jun 7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2) Jun 7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in defaults handling. Program aborted Jun 7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc detected *** dovecot/auth worker: waiting for connection: free(): invalid pointer: 0x00007fffa0863160 *** Jun 7 23:02:09 localhost dovecot: auth-worker: Error: ======= Backtrace: ========= Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f22d42f9b96] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /usr/lib/libmysqlclient.so.18(free_root+0x90)[0x7f22d37988c0] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /usr/lib/libmysqlclient.so.18(free_defaults+0x4b)[0x7f22d3796e6b] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /usr/lib/libmysqlclient.so.18(mysql_read_default_options+0x13c)[0x7f22d377d00c] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /usr/lib/libmysqlclient.so.18(mysql_real_connect+0x8e)[0x7f22d377eb4e] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /usr/lib/dovecot/modules/auth/libdriver_mysql.so(+0x1fc6)[0x7f22d3c52fc6] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(+0x2be1d)[0x7f22d515be1d] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(db_sql_connect+0xd)[0x7f22d514aedd] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(+0x23d70)[0x7f22d5153d70] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(passdb_init+0x2a)[0x7f22d515158a] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(auths_init+0x59)[0x7f22d513dfe9] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(main+0x345)[0x7f22d513d5f5] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f22d429c76d] Jun 7 23:02:09 localhost dovecot: auth-worker: Error: dovecot/auth worker: waiting for connection(+0xd7d9)[0x7f22d513d7d9] There follows a memory map but I snipped that. This repeated until I killed dovecot (12 hours later), by then 54GB of logs had accumulated. Besides leaving me impressed with the logserver :), I was wondering if this is a known problem. I don't know what triggered this at 23:02 (shown above is the first set of problem logentries). Can't really have been an upgrade, since I backported the raring dovecot Ubuntu package for my precise server, no automated upgrades there. I did go look for the /etc/mysql/conf.d directory mentioned, it wasn't there, but there was a /etc/mysql/my.cnf trying to !includedir it. Since there is no mysql on the server besides libmysqlclient I removed the directory and haven't seen the problem return yet. Sounds like the reason for happening, however, the memory error after that probably warrants research? If it is in libmysqlclient, that's another non-default snag because that's the lib I get from Percona, not the Ubuntu default one. Shouldn't dovecot recognize that the auth worker is crashing? One more thing, this is (one line from many) from audit.log (I have auditd logging audit records) type=ANOM_ABEND msg=audit(1370682566.377:3499876): auid=4294967295 uid=108 gid=115 ses=4294967295 pid=23187 comm="auth" reason="memory violation" sig=6 108 is the dovecot user, so it probably is related. I realise I'm way off defaults here but I wanted to report anyway. (dovecot -n attached) thanks for any insight, Maarten.

2 2

[Dovecot] CATENATE/literal8 issue
by Michael M Slusarz 13 Jun '13

13 Jun '13

Using 2.2.2, I see this: C: 6 APPEND "INBOX" (\seen) "16-May-2013 22:05:14 -0600" CATENATE (URL "/INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER" TEXT ~{40} S: 6 NO [UNKNOWN-CTE] Binary input allowed only when the first part is binary. Why is there this limitation? It seems to me that CATENATE is confusing the content-type encoding of the data/part itself with the encoding of the IMAP literal. A literal 8 is nothing more than a series of OCTET's that *may* contain nulls, but not necessarily. i.e., in the above example the 40 octets of data are US-ASCII text, which is perfectly acceptable to send as a literal8. (Client rationale: If BINARY exists on the server, we don't bother to scan IMAP literal's for null data -- we just send them as literal8's. It's an optimization that I would hate to get rid of.) michael

2 8

[Dovecot] Replication and LAYOUT=fs
by Simon Fraser 13 Jun '13

13 Jun '13

Hello folks, I have a problem with replication and mail_location with LAYOUT=fs set. If I set "mail_location = maildir:~/mail" (leaving out the :LAYOUT=fs), create and populate some mailboxes and subfolders, they all get replicated. If I start with a clean mail spool and LAYOUT=fs, I can create some new mailboxes and subfolders but only the inbox is replicated. Subfolders are ignored. The users are all in LDAP, and virtual, hence the generic mail_home format and mail_location being set. The userdb lookup has been told to return no attributes ("user_attrs = "), but I have also tried it with requesting 'home' and specifying a default of /mail/spool/%u in the userdb config. The service is perfectly functional as far as a mail client is concerned: it can access all the folders and messages it expects on the server that had them added. It's only the replication using LAYOUT=fs that seems to be troublesome. Here is `doveconf -n` for the first of the pair of servers (dcot1a and dcot1b). The configuration on the other is identical except for the hostname differences. Simon # 2.2.2: /mail/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-27-virtual x86_64 Ubuntu 12.04.2 LTS disable_plaintext_auth = no doveadm_password = secret first_valid_uid = 100 mail_gid = dovecot mail_home = /mail/spool/%u mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = notify replication mail_uid = dovecot namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = /mail/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_replica = tcp:dcot1b:12345 } protocols = imap lmtp service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = dovecot } unix_listener replication-notify { mode = 0600 user = dovecot } } service config { unix_listener config { user = dovecot } } service doveadm { inet_listener { port = 12345 } user = dovecot } service replicator { process_min_avail = 1 } shutdown_clients = no ssl_cert = </etc/ssl/certs/dcot1a-cert.pem ssl_key = </etc/ssl/private/dcot1a-key.pem userdb { args = /mail/etc/dovecot/dovecot-ldap.userdb.conf.ext driver = ldap } -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.

2 2

Re: [Dovecot] Dovecot 2 + IMAP
by Alex Dubinin 13 Jun '13

13 Jun '13

12.06.2013 22:34, Michael Kliewe пишет: > Hello Alex, > you asked exactly the same question 5 days ago and already got the > answer (from 2 people). Why did you ask again, didn't you receive the > answers? Thank you for your answer. Yes, i didn't receive answer ((((

1 0

[Dovecot] post-login script and original remote ip in proxy mode
by Ibrahim Harrani 13 Jun '13

13 Jun '13

Hi, I am running dovecot on 3 qmail-ldap server backend. dovecot configured to use auth_pop3 wrapper for authentication. Users logins to the qmail-ldap pop3&imap pools randomly. If a user is mailhost is not the connected server, dovecot proxies the connection to the user mailhost. In this case, I can not get the original client IP address via post-logins script on user host. I see only the first connected server IP as $IP environment. Any idea to get original client IP in this setup with postlogin scripts? Thanks

2 1

[Dovecot] Question about directory hash function.
by Evgeny Basov 13 Jun '13

13 Jun '13

Hello, Timo. I have a question about %H in http://wiki2.dovecot.org/Variables : what the hash function uses for calculations and how to get this value manually? This is need for bypass way getting home directory. With best regards, Evgeny Basov.

2 1