- dovecot - dovecot.org

file/folder perms permissions
by Jim Pazarena 05 Aug '16

05 Aug '16

Forgive me if I am blind, but I cannot find default folder permissions. For the home directories, with the sub of mail: and deeper, I see some files with 660, some with 600, some folders with 770 some with 660 I am a bit confused. I manually messed with some files, and my MUA complained about permissions. So I got that mess fixed, and in doing so I noticed the seemingly contradictory permissions. Thanks!

3 2

SSL connection reset by peer
by Vince42 04 Aug '16

04 Aug '16

Hi, I am running a dovecot server and have set up an external monitoring, where every five minutes a login with SSL on port 993 is done. I usually get once a day an error "connection reset by peer - SSL connect", which goes away until the next monitor is executed. Initially I thought that raising the mail_max_userip_connections in protocol imap in 20-imap.conf to 256 should do the trick - but the error stays. What could be the reason for this error and which configuration values could be changed in order to avoid this error? I read a lot of different suggestions - but did not find a plausible explanation and recommendation. Thanks in advance! -- Cheers, \\|// Vince (o o) ----------------------------ooO-(_)-Ooo------------------------- ''' (o)_(o) [ ][0][ ] ô¿ô (=°o°=) World Domination by Copy and Paste [ ][ ][0] - (")_(") [0][0][0] () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Ooo. ---------------------------.ooO----( )------------------------- ( ) (_/ \_)

5 11

Dovecot 2.2.25 test failure
by Michael A. Peters 04 Aug '16

04 Aug '16

Operating system - 64 bit CentOS 7 gcc-4.8.5-4.el7.x86_64 Building against LibreSSL which has been fine for other releases, but it is a crypto test that is fails. Tried with LibreSSL 2.4.2 and 2.3.6 - both the build completes but fails the make check Dovecot 2.2.24 passes make check on both. This is where it fails: Making check in lib-dcrypt make[2]: Entering directory `/home/alice/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt' for bin in test-crypto test-stream; do \ if ! /bin/sh ../../run-test.sh ../.. ./$bin; then exit 1; fi; \ done ../../run-test.sh: line 21: 22369 Segmentation fault (core dumped) valgrind -q --trace-children=yes --leak-check=full --suppressions="$supp_path" --log-file=test.out.$$ $* ==22369== Invalid read of size 8 ==22369== at 0x113A47: dcrypt_ctx_sym_create (dcrypt.c:61) ==22369== by 0x119194: test_cipher_test_vectors (test-crypto.c:60) ==22369== by 0x1196F0: test_run_funcs (test-common.c:354) ==22369== by 0x119FC0: test_run (test-common.c:404) ==22369== by 0x113461: main (test-crypto.c:554) ==22369== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==22369== ==22369== ==22369== Process terminating with default action of signal 11 (SIGSEGV) ==22369== Access not within mapped region at address 0x8 ==22369== at 0x113A47: dcrypt_ctx_sym_create (dcrypt.c:61) ==22369== by 0x119194: test_cipher_test_vectors (test-crypto.c:60) ==22369== by 0x1196F0: test_run_funcs (test-common.c:354) ==22369== by 0x119FC0: test_run (test-common.c:404) ==22369== by 0x113461: main (test-crypto.c:554) ==22369== If you believe this happened as a result of a stack ==22369== overflow in your program's main thread (unlikely but ==22369== possible), you can try to increase the size of the ==22369== main thread stack using the --main-stacksize= flag. ==22369== The main thread stack size used in this run was 8388608. Failed to run: ./test-crypto make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/home/alice/rpmbuild/BUILD/dovecot-2.2.25/src/lib-dcrypt' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/alice/rpmbuild/BUILD/dovecot-2.2.25/src' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.Il5fdU (%check) Thanks for suggestions.

3 7

Attachment Storage problems
by Daniel van Ham Colchete 04 Aug '16

04 Aug '16

Guys, I started using single instance attachment storage a while ago but I had too many problems with it. My logs are filled with errors like: Aug 03 18:41:38 imap(user@domain): Error: read(attachments-connector(zlib(/srv/dovecot/mdbox/domain/user/storage/m.2))) failed: read(/srv/dovecot/attach/domain/5f/03/5f03f1d7da846fe9268473cae5219ae31019fd540dc67f58596d8390be4a0f2256158b1e9ba327841c513a6d927dbe9b767b7ad94f8ae5772674cccb3124b69d-7be2ef0e97036457c52000009331bd36[base64:19 b/l]) failed: open(/srv/dovecot/attach/domain/5f/03/5f03f1d7da846fe9268473cae5219ae31019fd540dc67f58596d8390be4a0f2256158b1e9ba327841c513a6d927dbe9b767b7ad94f8ae5772674cccb3124b69d-7be2ef0e97036457c52000009331bd36) failed: No such file or directory (uid=23484, box=INBOX) The funny thing is that the directory /srv/dovecot/attach/domain/5f/03/ doesn't even exist! So, I would like to stop using it and my question is: how? First we would need to stop writting things there while still reading it. How can I tell dovecot to stop using it on new e-mail? Second would be a dsync-like migration reinserting the attachments on the messages back. How can I do that? Most importantly, what do I do with the messages that lost attachments? Thank you very much. Best, Daniel Colchete

1 0

service-specific userdb affecting lmtp, quota-service
by Michael Fox 03 Aug '16

03 Aug '16

The service specific passwd-file userdb is causing quota-status and lmtp to fail. Using: userdb { args = ... /etc/dovecot/auth.d/%d/userdb.%s } I'm getting the following in /var/log/mail.err when I try to send/receive mail: Aug 1 15:46:57 n6mef-gw dovecot: auth: Error: passwd-file(mefpop(a)email.n6mef.org): stat(/etc/dovecot/auth.d/email.n6mef.org/userdb.quota-status) failed: Address family not supported by protocol Aug 1 15:47:08 n6mef-gw dovecot: auth: Error: passwd-file(mefpop(a)email.n6mef.org): stat(/etc/dovecot/auth.d/email.n6mef.org/userdb.lmtp) failed: Address family not supported by protocol I don't have a userdb.quota-status or userdb.lmtp. Is there something else that needs to be in the configuration to prevent these services from needing their own userdb? Thanks, Michael $ doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-76-generic x86_64 Ubuntu 14.04.4 LTS auth_mechanisms = cram-md5 auth_verbose = yes mail_gid = vmail mail_location = maildir:~/Maildir mail_plugins = " quota" mail_uid = vmail 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 = } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = scheme=cram-md5 username_format=%n /etc/dovecot/auth.d/%d/passdb driver = passwd-file } plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=50MB quota_rule2 = Trash:storage=+10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_status_toolarge = 552 5.2.3 Message is too large quota_warning = storage=90%% quota-warning 90 %n %d quota_warning2 = storage=75%% quota-warning 75 %n %d } pop3_lock_session = yes protocols = pop3 imap lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { executable = pop3 postlogin process_limit = 25 } service postlogin { executable = script-login /etc/dovecot/postlogin.sh group = vmail user = vmail } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = /etc/dovecot/quota-warning.sh user = vmail } ssl = required ssl_cert = </opt/xsc/ssl/certs/n6mef-gw.crt ssl_key = </opt/xsc/ssl/private/n6mef-gw.key ssl_protocols = !SSLv2 !SSLv3 userdb { args = username_format=%n /etc/dovecot/auth.d/%d/userdb.%s default_fields = home=/var/vmail/%d/%n driver = passwd-file } verbose_ssl = yes protocol lmtp { postmaster_address = xxxxxxxxxxxxxxxxx } protocol imap { mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 1 } remote 192.168.7.0/24/24 { ssl = yes } remote 192.168.7.0/27/27 { ssl = no } $

2 4

"Plaintext authentication disallowed on non-secure (SSL/TLS) connections" despite correct configuration to allow this
by Christian Balzer 03 Aug '16

03 Aug '16

Hello, this is basically a repeat of this query from last year, which unfortunately got a deafening silence for replies: --- http://dovecot.org/pipermail/dovecot/2015-August/101720.html --- I have mostly 2.1.7 (Debian Wheezy) mailbox servers and the current proxies are also of that vintage. So with "ssl=yes" and "disable_plaintext_auth=no" plaintext logins work, as per the documentation (http://wiki2.dovecot.org/SSL/DovecotConfiguration) and historically expected. Trying to use a 2.2.24 (Debian Jessie backports) dovecot proy with the same parameters fails like this: --- Aug 2 15:45:57 smtp12 dovecot: pop3-login: proxy(chibixxx(a)gol.com): Login failed to mbxx.xxx.gol.com:110: Plaintext authentication disallowed on non-secure (SSL/TLS) connections.: user=<chibixxx(a)gol.com>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, pid=16066 --- Changing things to "ssl=no" doesn't help and setting trusted networks only changes the last bit to have "secured" appended but still fails the same otherwise. I really need 2.2.x to behave the same way as before and documented. Any ideas and feedback would be most welcome. Regards, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

1 1

Error: Timeout (180s) while waiting for lock for transaction log file dovecot.index.log
by Götz Reinicke - IT Koordinator 02 Aug '16

02 Aug '16

Hi, our maildir store is on a NFS share which was working fine for some time with the recommended setting from the dovecot wiki; suddenly today i got informed that one user has login problems to his mails and I have some messages in the logs: Error: Timeout (180s) while waiting for lock for transaction log file ....../Maildir/dovecot.index.log My current guess is a hick up in the network during a router configuration this weekend. My question: How to solve the problem? I can restart the nfs service/server later this day, as well as the mailserver ... as there is a kernel update too. Do I have to initiate some resync or deletion of index or whatsoever files? Thanks for any feedback and regards . Götz

1 0

auth_bind with "()" in username not working
by Matthias Lay 02 Aug '16

02 Aug '16

Hi all, I have an AD testsetup with auth_bind setting auth_bind_userdn = "spdev\\%Ln" I created a testuser "claasc (test)" which works fine in all ldapfilters but not for the auth_bind. the log shows everything correct just "invalid credentials" mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: auth client connected (pid=12202) mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=T6knVtc0wQB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=39873 mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: client passdb out: CONT 1 mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: client in: CONT<hidden> mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: passwd-file(claasc (test),127.0.0.1,<T6knVtc0wQB/AAAB>): cache miss mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: passwd-file(claasc (test),127.0.0.1,<T6knVtc0wQB/AAAB>): lookup: user=claasc (test) file=/etc/dovecot/passwd.postmaster mail.info: Jun 9 14:12:31 dovecot: auth: passwd-file(claasc (test),127.0.0.1,<T6knVtc0wQB/AAAB>): unknown user (given password: HubertHans99) mail.debug: Jun 9 14:12:31 dovecot: auth: Debug: ldap(claasc (test),127.0.0.1,<T6knVtc0wQB/AAAB>): cache miss mail.info: Jun 9 14:12:31 dovecot: auth: ldap(claasc (test),127.0.0.1,<T6knVtc0wQB/AAAB>): invalid credentials mail.debug: Jun 9 14:12:33 dovecot: auth: Debug: client passdb out: FAIL 1 user=claasc (test) mail.info: Jun 9 14:12:33 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<claasc (test)>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<T6knVtc0wQB/AAAB> So I guess its just a bind problem. strace output from auth process of imap login: write(26, "0-\2\1\4`(\2\1\3\4\25spdev\\claasc \$test\$\200\fHubertHans99", 47) = 47 the additional \\ in front of the brackets look strange to me and might be the reason. tested Version is 2.2.18 Greetz Matze

1 4

passwd-file extra-fields: inbox=yes
by Michael Fox 02 Aug '16

02 Aug '16

I'd like to implement the virtual plugin so that POP3 users can see emails in their own inbox and a public namespace. As I understand it, I need to set "inbox=yes" separately, depending on which service the user is using. With passwd-file flat files, this means: userdb { args = ... /path/userdb.%s } userdb.imap: set the extra fields for each user = userdb_namespace/inbox/inbox=yes userdb.pop3: set the extra fields for each user = userdb_namespace/virtual/inbox=yes But without even getting to the virtual namespace part, I'm having difficulty getting the extra fields setting to work for a regular IMAP user. Specifically: If I use the Dovecot default settings of namespace inbox, which includes inbox=yes, and do NOT include the extra_fields value shown above, then IMAP users can log in OK. But if I comment out inbox=yes within namespace inbox, and then add the extra fields to userdb.imap (as shown above), (and reload doveadm), then the IMAP user is no longer able to login. Thunderbird displays "Login to server ... failed." and I get the following in syslog (mail.err): Aug 1 13:56:13 n6mef-gw dovecot: imap(mefimp(a)email.n6mef.org): Error: user mefimp(a)email.n6mef.org: Initialization failed: namespace configuration error: Duplicate namespace prefix: "" Aug 1 13:56:13 n6mef-gw dovecot: imap(mefimp(a)email.n6mef.org): Error: Invalid user settings. Refer to server log for more information. I'm at a loss for what's wrong. Can someone help? Userdb.imap test entry and doveconf -n below. Thanks, Michael Userdb.imap: mefimp::::Michael E Fox - mefimp:::userdb_namespace=/namespace/inbox/inbox=yes $ doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-76-generic x86_64 Ubuntu 14.04.4 LTS auth_mechanisms = cram-md5 auth_verbose = yes mail_gid = vmail mail_location = maildir:~/Maildir mail_plugins = " quota" mail_uid = vmail namespace inbox { 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 = } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = scheme=cram-md5 username_format=%n /etc/dovecot/auth.d/%d/passdb driver = passwd-file } plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=50MB quota_rule2 = Trash:storage=+10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_status_toolarge = 552 5.2.3 Message is too large quota_warning = storage=90%% quota-warning 90 %n %d quota_warning2 = storage=75%% quota-warning 75 %n %d } pop3_lock_session = yes protocols = pop3 imap lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3 { executable = pop3 postlogin process_limit = 25 } service postlogin { executable = script-login /etc/dovecot/postlogin.sh group = vmail user = vmail } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = /etc/dovecot/quota-warning.sh user = vmail } ssl = required ssl_cert = </opt/xsc/ssl/certs/n6mef-gw.crt ssl_key = </opt/xsc/ssl/private/n6mef-gw.key ssl_protocols = !SSLv2 !SSLv3 userdb { args = username_format=%n /etc/dovecot/auth.d/%d/userdb.%s default_fields = home=/var/vmail/%d/%n driver = passwd-file } verbose_ssl = yes protocol lmtp { postmaster_address = xxxxxxxxxx } protocol imap { mail_max_userip_connections = 1 } protocol pop3 { mail_max_userip_connections = 1 } remote 192.168.7.0/24/24 { ssl = yes } remote 192.168.7.0/27/27 { ssl = no } $

1 0

IMAP flags and dovecot-keywords not working as expected
by Mark Foley 01 Aug '16

01 Aug '16

I've converted most of our users from Outlook to Thunderbird. One important feature of Thunderbird is that it pays attention to the IMAP non-standard message flags via the 'tags' feature (see http://wiki2.dovecot.org/MailboxFormat/Maildir) This is important because 2 users make extensive use of Outlook categories (Tags, in Thunderbird). I found that when I set a message to the 1st Tbird tag 0 (Important), the corresponding IMAP file got an 'a' suffix. Likewise, if I manually added an 'a' suffix to an IMAP file the corresponding tag was set displayed in Thunderbird. This made it easy for me to exports Outlook Categories and set IMAP messages flags accordingly. This worked perfectly on the user I was experimenting with (me). Recently, I converted one of these Outlook 'categories' users to Thunderbird. I added the appropriate flag letters to their IMAP messages, changed their tag names in Thunderbird, and created the following dovecot-keywords file as: 0 Board_and_Committee 1 Completed 2 Health_Care_meetings 3 Notifications 4 OSHP-DAS 5 personal_or_To_Do 6 Retirement_exits 7 $label5 8 Junk 9 $Forwarded 10 $MDNSent 11 $label2 However, none of the tags show up correctly in Thunderbird. If I manually set a message to have a tag of 0, the corresponding IMAP file gets a flag of 'm', not 'a' and the following is added to the dovecot-keywords files: 12 $label1 How can I fix this? Where is "$label1" text defined? Why did Thunderbird not snag the text for '0' from the dovecot-keywords file and give the IMAP file a tag of 'a'? My current theory is that the "Default" Thunderbird Tags corresponding to IMAP flags are not changeable and if new tags are create in Tbird, they get new flag letters. That would, of course, mean that if a user changes Thunderbird tag name, they would lose all tag settings on existing message. That doesn't seem right and I hope my theory is wrong. Any insight would be appreciated. --Mark

2 3