- dovecot - dovecot.org

pam authentication error?
by unknown＠example.com 28 May '19

28 May '19

Getting this: auth-worker(5045): Error: pam(kremels,xxx.xxx.xxx.xxx: pam_authenticate() failed: authentication error (/etc/pam.d/dovecot missing?) # cat /etc/pam.d/dovcot auth required pam_unix.so nullok account required pam_unix.so (file was last updated in April of 2018) passdb { username_filter = "!*@*" driver = pam } userdb { driver = passwd } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } # ls -ls /var/spool/postfix/private/auth 0 srw-rw-rw- 1 root wheel 0 May 27 13:57 /var/spool/postfix/private/auth postfix/main.cf: smtpd_sasl_authenticated_header = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_starttls_timeout = 20s smtpd_tls_cert_file = /usr/local/etc/dehydrated/certs/covisp.net/fullchain.pem smtpd_tls_key_file = /usr/local/etc/dehydrated/certs/covisp.net/privkey.pem smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_security_level = may 16 -rw------- 1 root 443 4152 May 20 21:08 fullchain-1558408117.pem 0 lrwx------ 1 root 443 24 May 20 21:08 fullchain.pem -> fullchain-1558408117.pem 8 -rw------- 1 root 443 3243 May 20 21:08 privkey-1558408117.pem 0 lrwx------ 1 root 443 22 May 20 21:08 privkey.pem -> privkey-1558408117.pem

2 1

Re: Hello some help on login users saying it's disabled
by Joseph Tam 27 May '19

27 May '19

> Hello I am experiencing some strange issue with the dovecot, the web > round cube works fine but when I try to connect with an iPhone over > IMAP IMAPs it tells me that the account is disabled. > > May 25 14:30:32 imap-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=... > ... It's probably the iPhone mail app trying to be clever and auto-configuring the settings for IMAP (and getting it wrong). To stop this behaviour, hardwire the iPhone IMAP parameters, then disable "Automatic manage connection". If you use SSL/TLS, this will also secure you from plaintext MITM attacks. Other oddities I've seen from Apple mail readers: 1) If you don't disable "Automatic manage connection", it will also hunt around for outgoing mail settings. 2) Once in a while, it initiates an idle authenticated SMTP session (i.e. authenticates, but does nothing). 3) Roofs your user IMAP connection limit when the client does global mail searches. Joseph Tam <jtam.home(a)gmail.com>

1 0

SIGABRT on fetching mail
by Peter Nabbefeld 27 May '19

27 May '19

Hello, I still cannot fetch my mails, relying on my smartphone (which makes it a burden to read my mails ...) - could probably somebody help me? Kind regards, Peter

2 2

Error suggestions please
by Remo Mattei 27 May '19

27 May '19

May 25 15:01:27 imap(xxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Mailbox INBOX: UID=208: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) (read reason=mail stream) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Error: Corrupted record in index cache file /home/vpopmail/domains/italy1.com/xxxxx/Maildir/dovecot.index.cache: UID 208: Broken physical size in mailbox INBOX: read(/home/vpopmail/domains/italy1.com/xxxxx/Maildir/cur/1154731221.9257.az… failed: Cached message size smaller than expected (26421 < 26511, box=INBOX, UID=208) May 25 15:01:27 imap(xxxxxx(a)italy1.com)<10256><LsrOdL2J3uisCqP7>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) Can someone tell help on how to fix this issue. Thanks

3 3

Unknown error message
by Jerry 26 May '19

26 May '19

dovecot 2.3.6 (7eab80676) FreeBSD 12.0-RELEASE-p5 amd64 I have recently been finding error messages similar to the following in my Dovecot log file: May 26 06:58:32 imap(gerard(a)seibercom.net)<87791><WvXT+LyJHBCubeH6>: Error: stat(/var/mail/vmail/seibercom.net/gerard/.dovecot.sieve/tmp) failed: Not a directory The message is correct as there is no such directory. The question is why has it suddenly started appearing? I checked my maillog file, and there are no messages being transmitted to Dovecot when that error message is created. Neither is there any mail with that ID number either. Could this be someone attempting to hack into my system? Thanks! -- Jerry

2 1

Automatically subscribe to the INBOX folder
by glts 26 May '19

26 May '19

Hello, I am using the ‘auto = subscribe’ feature in the mailbox configuration section in the usual fashion (as shown in conf.d/15-mailboxes.conf): namespace inbox { inbox = yes mailbox Drafts { special_use = \Drafts auto = subscribe } ... } When I connect to an account with the Thunderbird mail client, those mailboxes/folders get autocreated and autosubscribed. Good! INBOX, however, does not get subscribed to automatically. When I look at the account’s subscriptions in Thunderbird, all folders are subscribed, except INBOX. How can I enable autosubscribe for the INBOX folder (like the other folders)? Is there an option for this? This is in Dovecot 2.2.22. Cheers, David

2 1

Workaround for infinite loop in XCLIENT command bug
by mabi 26 May '19

26 May '19

Hello, I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug which has been fixed in 2.3.6 is hitting me: lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server https://github.com/dovecot/core/commit/5d03f39b345127b80d145ee90772739baa7a… so I was wondering if there is any workarounds? Maybe like disabling the XCLIENT command from the config file or something similar? My original post regarding this issue is here: https://www.mail-archive.com/misc@opensmtpd.org/msg04362.html I first thought this was an OpenSMTPD issue but it seems to be that Dovecot bug. Cheers, Mabi

3 6

Dovecot multiple passdb and fail2ban
by Joaquin F 26 May '19

26 May '19

Objective: different password for remote and local imap login Version: 2.2.36 (1f10bfa63) on CentOS 7 Users are from Active Directory, mapped to local users via sssd After much experimentation, I have configured this way: doveconf -n passdb userdb passdb { args = username_format=%Ln /etc/dovecot/remote driver = passwd-file skip = authenticated username_filter = user01 user02 } passdb { driver = pam override_fields = allow_nets=127.0.0.0/8,192.168.1.0/24 skip = authenticated } userdb { driver = passwd } If I put the passdb's in the reverse order, I would get failure messages (when logging in remotely) in /var/log/secure, such as: auth: pam_sss(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user02 rhost=xx.xx.xx.xx user=user02 Which caused fail2ban to ban that ip /etc/fail2ban/jail.local [dovecot] enabled = true port = imap,imaps If I set "auth_verbose = yes", then I can see messages in (when logging in locally) in /var/log/maillog dovecot: auth: passwd-file(user02,192.168.1.20,<Na/7f8WJC8HAqAEU>): Password mismatch which is probably not a big deal... but seems inefficient? Question: is there a more elegant way to use different passdb depending on ip? Thanks in advance.

1 0

Imap reverse / proxy in front of our clients machines.
by Brent Clark 25 May '19

25 May '19

Good day Guys I have a user story have an imap reverse / proxy in front of our clients servers. Im currently using the following sources for information. https://wiki.failover.de/Email/Dovecot/IMAP/Proxy/ https://gist.github.com/rplessl/dd56d05c84f988706418 https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy In my vagrant instance, dovecot can connect to the the remote server You can see my debugging and conf: https://pastebin.com/raw/H2AL53Fz https://pastebin.com/raw/hZHSHvcu If anyone can assist it would be greatly appreciated. Many thanks Regards Brent

1 0

Race condition in IMAP NOTIFY for events received NOTIFY_DELAY_MSECS apart
by Guilhem Moulin 25 May '19

25 May '19

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $ sed -r 's/^\s*//; s/\s+/ /g' >/tmp/dovecot.conf <<-EOF log_path = /tmp/dovecot.log mailbox_list_index = yes mail_home = /dev/shm/dovecot-test/%u mail_location = dbox:~/mail ssl = no EOF (`doveconf -c /tmp/dovecot.conf -n` output enclosed.) $ rm -rf /dev/shm/dovecot-test && mkdir -m0700 /dev/shm/dovecot-test $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin \ doveadm -c /tmp/dovecot.conf exec imap S: * PREAUTH [CAPABILITY IMAP4rev1 … NOTIFY] Logged in as user C: a NOTIFY SET STATUS (SELECTED (MessageNew MessageExpunge FlagChange)) (MAILBOXES (INBOX test) (MessageNew MessageExpunge FlagChange)) S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) S: a OK NOTIFY completed (0.004 + 0.000 + 0.003 secs). S: * STATUS INBOX (MESSAGES 0 UIDNEXT 1 UIDVALIDITY 1558785754 UNSEEN 0 HIGHESTMODSEQ 1) C: b SELECT INBOX […] S: b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). Now deliver two messages to INBOX with ~500ms in between: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m INBOX' Only the the first message is reported in the above IMAP session: S: * 1 EXISTS S: * 1 RECENT An UNSELECT doesn't trigger the notification, but (of course) a NOOP does: C: c NOOP S: * 2 EXISTS S: * 2 RECENT S: c OK NOOP completed (0.001 + 0.000 secs). Similarly, for two flag changes within 0.5s only the first is recorded: $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'doveadm -c /tmp/dovecot.conf flags add "\\Seen" mailbox INBOX 1; \ sleep 0.500; \ doveadm -c /tmp/dovecot.conf flags add "\\Answered" mailbox INBOX 2' yields a single unsolicited FETCH response: S: * 1 FETCH (MODSEQ (4) FLAGS (\Seen \Recent)) AFAICT this is only reproducible in the ‘SELECTED’ mailbox specifier: after creating a mailbox "test", $ env -i USER=user HOME=/dev/shm/dovecot-test/user PATH=/usr/bin:/bin sh -c \ 'echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test; \ sleep 0.500; \ echo -n . | doveadm -c /tmp/dovecot.conf exec dovecot-lda -e -m test' yields two unsolicited STATUS responses as expected: * STATUS test (MESSAGES 1 UIDNEXT 2 UIDVALIDITY 1558787038 UNSEEN 1 HIGHESTMODSEQ 2) * STATUS test (MESSAGES 2 UIDNEXT 3 UIDVALIDITY 1558787038 UNSEEN 2 HIGHESTMODSEQ 3) (And same thing for two flag updates in the "test" mailbox.) This is not specific to INBOX as once "test" is selected the same problem arises. AFAICT the race is in ‘src/lib-storage/list/mailbox-list-index-notify.c’ which for some reason doesn't acknowledge ST_CHANGED() after inotify_rm_watch(), but I couldn't get my head around that file. Cheers, -- Guilhem.

1 0