- dovecot - dovecot.org

[Dovecot] Dovecot security
by Jay Khashan 14 Aug '13

14 Aug '13

Hi, THIS IS URGENT I have Debian Linux machine which I installed as a mail server with postfix, and dovecot. my mail server is setup to use SMTP relay. I currently have ports 143, 995, 25 & SSMTP ports open. in the last few days I have been under attack where email is being sent to fake email address for example xxx(a)evg-mail.org which does not exist in the mysql db. I need to figure out and lock down dovecot, because I believe the attack is some kind of virus /spyware. I need to know what statement in dovecot.conf or main.cf (postfix) I can modify to lock it down. Also open to install software to combat this kind of attack. Let me know what configuration files, info do you need to help out Many Thanks ~Jay

4 3

[Dovecot] HG changes affecting received headers
by Thomas Leuxner 13 Aug '13

13 Aug '13

Let me say this is a rather cosmetic issue, but it appears with the latest commits (around 2.2.5 release) the scheme of 'Received' headers has changed for LMTP: 1) Inet socket: Return-Path: <dfn-adv-bounces(a)dfn-cert.de> Delivered-To: <tlx(a)leuxner.net> Received: from spectre.leuxner.net ([188.138.0.199]) by spectre.leuxner.net (Dovecot) with LMTP id 8AkXDF5cA1LvDgAAZ53dLw for <tlx(a)leuxner.net>; Thu, 08 Aug 2013 10:52:46 +0200 2) UNIX socket: Return-Path: <dfn-adv-bounces(a)dfn-cert.de> Delivered-To: <tlx(a)leuxner.net> Received: from spectre.leuxner.net ([]) by spectre.leuxner.net (Dovecot) with LMTP id q8WuGflcA1I3DwAAZ53dLw for <tlx(a)leuxner.net>; Thu, 08 Aug 2013 10:55:21 +0200 3) Old (Pre 2.2.5) build, UNIX socket: Return-Path: <dfn-adv-bounces(a)dfn-cert.de> Delivered-To: <tlx(a)leuxner.net> Received: from spectre.leuxner.net by spectre.leuxner.net (Dovecot) with LMTP id 8NiKKX0h+lFRIAAAZ53dLw for <tlx(a)leuxner.net>; Thu, 01 Aug 2013 10:51:09 +0200 While it probably should resolve the FQDN in 1) (Postfix does), not sure what it should do with a UNIX socket in 2). Previously as shown in 3) it had none of it... Thomas

2 5

[Dovecot] fail2ban
by Aldo Reset 13 Aug '13

13 Aug '13

hi dovecot filter for fail2ban do not match: dovecot: pop3-login: Aborted login (tried to use disallowed plaintext auth): user=<>, rip=67 dovecot filter: failregex = (?: pop3-login|imap-login): (?:Authentication failure|Aborted login \(auth failed|Aborted login \(tried to use disabled|Disconnected \(auth failed).*rip=(?P<host>\S*),.* bst regards.

2 2

[Dovecot] Can't take user info from an alternate file
by dave＠661.org 13 Aug '13

13 Aug '13

I'm positive I did everything right to get Dovecot to take usernames and passwords from /etc/dovecot/users, but it still goes for /etc/passwd and /etc/shadow. The format of /etc/dovecot/users is "alice:{PLAIN}plaintextpassword" Here's my "doveconf -n": # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-51-virtual x86_64 Ubuntu 12.04.2 LTS auth_debug = yes auth_verbose = yes auth_verbose_passwords = plain hostname = papasmurf.foobar.com listen = * mbox_write_locks = fcntl passdb { args = scheme=PLAIN-MD5 username_format=%n /etc/dovecot/users driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0664 user = postfix } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%n /etc/dovecot/users driver = passwd-file } I'm using Ubuntu Precise and version 2.0.19 of Dovecot. -- David Griffith dave(a)661.org

2 5

[Dovecot] Disconnected (no auth attempts)
by Eric Broch 12 Aug '13

12 Aug '13

Hello list, I have a user who is not able to 'get' email using the 'Get Mail' option in his Thunderbird Client. The error on the server is the following: [Dovecot] dovecot: imap-login: Disconnected (no auth attempts) : rip 192.168.7.7, lip 192.168.7.12, TLS This user is able to receive mail on his phone, however. What does this error mean? Eric <http://www.dovecot.org/list/dovecot/2012-January/062988.html>

2 1

Re: [Dovecot] Please HELP: how to delete all messages older than X days
by Răzvan Sandu 12 Aug '13

12 Aug '13

Pe 7 Aug 2013 11:35, Timo Sirainen a scris: >> Thank you, but doveadm expunge will ask for the mailbox name: >> >> [root@mail1 ~]# doveadm expunge -u john.doe(a)example.com ON >> 2013-08-07 doveadm(root): Fatal: expunge: To avoid accidents, >> search query must contain MAILBOX in all search branches > > Add: mailbox '*' Thank you, it works! May I use the same wildcard syntax ('*') when configuring the expire plugin? Something like: mail_plugins = $mail_plugins expire plugin { expire = * } or plugin { expire = '*' } ? Best regards, Răzvan

3 2

[Dovecot] Unlock non existent locks
by Thomas Hummel 12 Aug '13

12 Aug '13

Hello Timo, I'm running a single instance of dovecot-2.1.15 on a single host running 8.3-RELEASE-p3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and fsync_disable=no. mail_nfs_index = yes served by an Isilon s200 node (OneFS 6.5.5.22) procmail delivers in the same location through postfix-2.8.7 The filer shows *a lot* of such messages : 2013-08-02T14:12:29+02:00 <0.5> XXXX-10(id10) /boot/kernel.amd64/kernel: [lkf_delegate.c:2752](pid 46390="kt: dwt3")(tid=101282) dev_local_lkf_unlock(): no lock entry present to unlock for resource: 1:19d5:fdbe ;client: 0xa51cc3f444107 Corresponding file may be a message, a maildir, an index, ... I can experience the same message with a simple fcntl C program which tries to unlock an NFS file without prior locking of it. However, the problem occurs only on a FreeBSD client (I tried the old nfs client and the new (mount_newnfs), not on a 2.6.32-358.11.1.el6.x86_64 CentOS release 6.4 (Final) Linux release. So my guess is that dovecot has some safety mechanism which tries to unlock locked files, maybe after some timeout and that, in the case of a an already unlocked file, the FreeBSD client sends the unlock RPC request to the server anyway whereas the linux client does not, noticing there isn't anything to unlock. Can you help me explaining such a behavior ? Are those "unlock a file with no prior lock" made on purpose or is it a bug ? Would it be an application or a RPC bug ? Can you think of another reason ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Groupe Exploitation et Infrastructure

2 5

[Dovecot] Error: Threading lost Message ID?
by Ralf Hildebrandt 12 Aug '13

12 Aug '13

QUERY: THREAD REFERENCES ISO-8859-1 ALL RESPONSE: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-08-09 15:42:34] Aug 9 15:41:48 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID Aug 9 15:42:34 postamt dovecot: imap(username) tTbs7oPjfACNKs4m: Error: Threading lost Message ID What does that mean? WHY has the Message-Id been lost? How can I find out WHICH MAIL caused this? This is the most recent dovecot 2.2.x -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 6

[Dovecot] GUID Mismatch Issue
by Jeff Geiger 12 Aug '13

12 Aug '13

Dovecot 2.1.7 While migrating mail from one server (Maildir) to another (mdbox), a config issue caused my dsync to fail on a few accounts. Those accounts received mail on the new server over night and it autocreated new inboxes with new GUIDs. Now dsync wants nothing to do with mirroring between the two (diff GUIDs). Is there a way to fix this? dsync(jeff(a)foo.bar): Error: Mailbox INBOX changed its GUID (0eee4b021dcadd5158550000eed085a1 -> 43f87412a8f00352ac340000be821591) dsync(jeff(a)foo.bar): Error: msg iteration failed: Couldn't open mailbox 0eee4b021dcadd5158550000eed085a1 dsync(jeff(a)foo.bar): Error: Mailbox INBOX changed its GUID (0eee4b021dcadd5158550000eed085a1 -> 43f87412a8f00352ac340000be821591) dsync(jeff(a)foo.bar): Error: Mailbox Trash changed its GUID (0fee4b021dcadd5158550000eed085a1 -> 6300df050ef10352e9350000be821591) dsync(jeff(a)foo.bar): Error: Mailbox Sent changed its GUID (832d1e3663cadd515f5d0000eed085a1 -> 855ef505c0f00352fc340000be821591) I need a way to merge the mailboxes, in either direction, so I can clear out one side and successfully migrate the mail accounts. Any tips or pointers are greatly appreciated.

2 1

[Dovecot] multiple passdbs and auth sockets
by md＠Linux.IT 12 Aug '13

12 Aug '13

I have a few systems which run dovecot 1.x as the authentication backend for Postfix, with multiple auth { } sections like this one, each one with a different passdb and its own socket: auth ldap-10 { passdb ldap { args = /etc/dovecot/dovecot-ldap-10.conf } socket listen { client { path = /var/spool/postfix/private/auth-10 mode = 0666 } } } I need multiple sockets tied to multiple dbs because there are duplicated accounts, but after switching to dovecot 2.1.7 apparently *all* passdbs are checked and dovecot reports this message: Warning: Obsolete setting in /etc/dovecot/conf.d/auth-local.conf.ext:91: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf shows that all my custom sockets are now part of a single "service auth { }" section, while all the passdbs appear at the top level. How can I update my configuration for dovecot 2.x? -- ciao, Marco

2 1