- dovecot - dovecot.org

zlib plugin aborts without zlib_save
by Adam Weinberger 26 Dec '17

26 Dec '17

This is in follow-up to https://dovecot.org/pipermail/dovecot/2017-December/110443.html I had mail_plugins = "zlib", but zlib_save wasn't set (my mailboxes were not compressed). It seems that when the zlib plugin is enabled, but zlib_save isn't set, the zlib plugin aborts on a regular basis---on a single-user system, I was seeing it about 150 times a day. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal: master: service(imap): child 80128 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Removing the (unused) zlib plugin made the errors disappear, at least. # Adam -- Adam Weinberger adamw(a)adamw.org http://www.adamw.org

1 0

Sieve 0.5.0/Dovecot 2.3.0
by Larry Rosenman 26 Dec '17

26 Dec '17

Using 2.3.0/0.5 and the below scripts/config, why doesn’t a mail addressed to ler_freebsd(a)lerctr.org get the FreeBSD flag? .dovecot.sieve points to master.sieve. Scripts: http://www.lerctr.org/~ler/sieve/ doveconf -n: thebighonker.lerctr.org /home/ler/sieve $ doveconf -n # 2.3.0 (c8b89eb): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0 (d68c23a1) # OS: FreeBSD 11.1-STABLE amd64 auth_mechanisms = plain login auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org thejonesonair.com thejonesonair.net default_vsz_limit = 1 G deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w) doveadm_password = # hidden, use -P to show it first_valid_gid = 0 first_valid_uid = 0 lda_mailbox_autocreate = yes listen = 192.147.25.65, :: lmtp_save_to_detail_mailbox = yes login_access_sockets = tcpwrap mail_attribute_dict = file:%h/mail/.imap/dovecot-mail-attributes mail_location = mbox:~/mail:INBOX=~/mail/INBOX mail_log_prefix = "%s(%u/%p): " mail_plugins = " fts fts_solr notify virtual" mail_privileged_group = mail mail_server_admin = mailto:ler@lerctr.org mail_server_comment = LERCTR Mail Server 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 index ihave duplicate mime foreverypart extracttext vacation-seconds editheader mboxmetadata servermetadata imapsieve vnd.dovecot.imapsieve namespace archive { hidden = no list = no location = mbox:~/MAIL-ARCHIVE prefix = ARCHIVE/ separator = / } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX { auto = create } mailbox SENT { special_use = \Sent } mailbox SPAM { special_use = \Junk } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } mailbox virtual/Flagged { special_use = \Flagged } mailbox virtual/all { special_use = \All } prefix = separator = / } namespace virtual { hidden = no list = yes location = virtual:~/MAIL-VIRTUAL:INDEX=MEMORY prefix = Virtual/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = user=%Ln noauthenticate driver = static skip = authenticated } passdb { args = failure_show_msg=yes session=yes max_requests=20 driver = pam skip = authenticated } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://thebighonker.lerctr.org:8983/solr/dovecot/ fts_tika = http://localhost:9998/tika/ imapsieve_mailbox1_before = file:/usr/local/share/dovecot-pigeonhole/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = SPAM imapsieve_mailbox2_before = file:/usr/local/share/dovecot-pigeonhole/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = SPAM imapsieve_mailbox2_name = * imapsieve_url = sieve://thebighonker.lerctr.org mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid size from subject vsize flags sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve sieve_extensions = +editheader +vacation-seconds +mboxmetadata +servermetadata sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap pop3 lmtp sieve recipient_delimiter = +-_ service anvil { unix_listener anvil { group = mail mode = 0660 } } service auth { unix_listener auth-client { mode = 0666 } unix_listener auth-master { mode = 0666 } } service doveadm { inet_listener http { port = 8080 ssl = yes } } service indexer-worker { drop_priv_before_exec = yes } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service stats { unix_listener stats-reader { group = mail mode = 0660 user = } unix_listener stats-writer { group = mail mode = 0660 user = } } service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } ssl_cert = </home/ler/letsencrypt-home/lerctr.org/fullchain.cer ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+AESGCM:EECDH:EDH+AESGCM:EDH+aRSA:HIGH:!MEDIUM:!LOW:!aNULL:!eNULL:!LOW:!RC4:!MD5:!EXP:!PSK:!SRP:!DSS ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { args = username_format=%Ln /etc/passwd driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = " fts fts_solr notify virtual sieve mail_log" } protocol lda { mail_plugins = " fts fts_solr notify virtual sieve mail_log" } protocol pop3 { mail_plugins = " fts fts_solr notify virtual mail_log" } protocol !doveadm { mail_plugins = " fts fts_solr notify virtual mail_log" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags imap_logout_format = in=%i out=%o fhc=%{fetch_hdr_count} fhb=%{fetch_hdr_bytes} fbc=%{fetch_body_count} fbb=%{fetch_body_bytes} del=%{deleted} exp=%{expunged} trash=%{trashed} imap_metadata = yes mail_max_userip_connections = 50 mail_plugins = " fts fts_solr notify virtual mail_log imap_sieve" } thebighonker.lerctr.org /home/ler/sieve $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

2 5

Crash in sieve_extprogram_create() after dovecot/pigeonhole update
by Oleksandr Natalenko 25 Dec '17

25 Dec '17

Hi all. My dovecot setup: pf@vulcan:~ » dovecot --version 2.3.0 (c8b89eb) on Arch Linux, x86_64 (full config here: [0]) uses sieve plugin to train rspamd system as described in the wiki [1]. It used to work fine prior to 2.3.0/0.5.0 update, but now "imap" process crashes when I move spam letters from the inbox to the junk folder. I've recompiled both dovecot and pigeonhole with debug symbols and got this stacktrace [2]. As you can see, it fails (with a SIGSEGV) in sieve_extprogram_create(), sieve- extprograms-common.c:562, which corresponds to this code: === 562 if ( !smtp_address_isnull(msgdata->envelope.rcpt_params->orcpt.addr) ) { 563 program_client_set_env 564 (sprog->program_client, "ORIG_RECIPIENT", 565 smtp_address_encode(msgdata->envelope.rcpt_params- >orcpt.addr)); 566 } === When I dump msgdata structure, I see that rcpt_params is NULL: [3]. Thus, NULL pointer dereference occurs. Here is my report-spam.sieve file: [4] What I'm doing wrong here? Or is this some bug within pigeonhole? Could you please help me with resolving this? Thanks. [0] https://gist.github.com/92be2a4abe04149fd4b6971b6b4fa38d [1] https://wiki2.dovecot.org/HowTo/AntispamWithSieve [2] https://gist.github.com/8b202ebe9310845b59bcdeed7567026e [3] https://gist.github.com/a7e30b9e7a6c315d729bdcfe7142f532 [4] https://gist.github.com/fd1aa8943af106408a30155dffe052ab

1 1

ssl_curve_list seems to be ignored with Dovecot 2.3
by Marcel Menzel 25 Dec '17

25 Dec '17

Hi all, after upgrading to Dovecot 2.3, I've noticed the new "ssl_curve_list" TLS option in 10-ssl.conf. Setting it to "ssl_curve_list = X25519:P-256" or leaving it blank (auto) does not change anything, Dovecot keeps on negotiating P-384: Server Temp Key: ECDH, P-384, 384 bits When using "-curves X25519" in s_client, it does a fallback to DH: Server Temp Key: DH, 4096 bits I'm on Dovecot 2.3.0 (c8b89eb) with OpenSSL 1.1.0g 2 Nov 2017 on Arch Linux 4.14.8-1-ARCH. Am I missing something here? OpenSSL 1.1 defaults to Curve25519 when leaving it on auto. Greetings, Marcel Menzel

1 0

Dovecot 2.3.0 generates all index files at once
by Andreas M. Kirchwitz 25 Dec '17

25 Dec '17

Merry Christmas! The brandnew Dovecot 2.3.0 seems to generate index (cache) files for all IMAP folders at once when a user logs in the first time. (Those "dovecot.index" files that live in ".imap" directories.) Previous versions generated these index files on demand when a folder was actually accessed (so if a folder was never used, no resources were wasted to ever generate an index file for it). For large mailboxes with lots of mail this may take hours, and during this time the user's mail client hangs (like Mutt) or exits with a timeout (like Thunderbird). Access to this user's mailbox hangs/fails with locking errors for obvious reasons. For fresh installations with pre-existing folders (but no index files yet) this kind of brings down the machine running Dovecot as soon as multiple users try to access their mail. I haven't analyzed the IMAP commands in detail. Just tried with Mutt and Thunderbird and they both trigger the issue. However, maybe Dovecot is just fine and the clients do something wrong which was just tolerated by Dovecot until now. My configuration is pretty simple: # 2.3.0 (c8b89eb): /usr/local/Dovecot-2.3.0/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab124.2 i686 CentOS release 6.9 (Final) auth_mechanisms = plain login digest-md5 cram-md5 first_valid_gid = 1000 first_valid_uid = 1000 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u passdb { args = /usr/local/dovecot/etc/dovecot/dovecot.passwd driver = passwd-file } protocols = imap ssl_cert = </usr/local/dovecot/etc/dovecot/certs/server.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/dovecot/etc/dovecot/dovecot.passwd driver = passwd-file } verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 20 } Good news is, Dovecot 2.3.0 compiles without errors and it also runs fine once all index files have been created. Maybe there's a new configuration option to toggle this behaviour but I haven't spotted anything obvious yet. Any help is appreciated. Thanks a lot and keep up the good work, Andreas

1 0

Disable ssl validation for replication?
by Joseph Ward 24 Dec '17

24 Dec '17

Hi, I have two servers (HA configuration) on which I'm attempting to get replication working over SSL. They're at two different sites, but connected via a site-site VPN. Everything seems to be fine, except that the certificates are not validating as I'm using IP addresses for the sync, as opposed to the public hostnames for which the certificates are valid, and so I get the following error: doveadm(user@domain): Error: doveadm server disconnected before handshake: SSL certificate doesn't match expected host name 10.x.x.x I'm on Dovecot 2.2.33. Is there any way to disable the certificate checking/validation for the sync engine? ( I'm aware of at least a couple of fallback options: -have a self-signed cert for replication and use the Let's Encrypt one for IMAP/POP - create firewall rules allowing them to connect to each other over the public internet so that it can validate the proper cert These are both much less palatable than simply disabling the cert validation if it's possible. ) Thank you in advance for any assistance, Joseph

3 3

sieve_pipe_socket_dir not created at startup for configured pipe service
by Garth Corral 24 Dec '17

24 Dec '17

Hi, all I’m new to the list but not to dovecot. I’ve been using it in a basic configuration for some time, but finally decided to tweak my deployed system to take advantage of some more dovecot features. In particular I’m trying to set up pigeonhole to implement spam retraining with imapsieve. All of this is with dovecot 2.2.31 (65cde28) and pigeonhole 0.4.19. Before going any further let me start by saying that I have gotten all of this to work. It works when I can get dovecot to start up, that is. My configuration is pretty much straight from the docs, with a few tweaks for my particular needs. I’m trying to set up a pipe service using sieve-extprograms, and the relevant part of my config looks like this: plugin { sieve_pipe_input_eol = lf sieve_pipe_socket_dir = sieve-pipe sieve_filter_socket_dir = sieve-filter sieve_execute_socket_dir = sieve-execute sieve_pipe_bin_dir = /usr/local/libexec/dovecot/sieve-pipe sieve_filter_bin_dir = /usr/local/libexec/dovecot/sieve-filter sieve_execute_bin_dir = /usr/local/libexec/dovecot/sieve-execute } service sieve-train-ham { executable = script /usr/local/libexec/dovecot/sieve-pipe/train-ham.sh # Needs access to dspam config and lockfiles. user = dspam # socket name is program-name in Sieve (without sieve-pipe/ prefix) unix_listener sieve-pipe/train-ham { } } It’s my understanding from reading the docs that the sieve_pipe_socket_dir specifies a directory that is relative to base_dir, which is the default /var/run/dovecot in my case. The issue I’m having is that dovecot will not start, and spews the following errors: dovecot: master: Error: bind(/var/run/dovecot/sieve-pipe/train-ham) failed: No such file or directory dovecot: master: Fatal: Failed to start listeners Once dovecot fails startup, it leaves /var/run/dovecot around and if I manually create the sieve-pipe directory there it will start up, create the sockets there and everything works as intended subsequently. The problem, though, is that on normal shutdown all of /var/run/dovecot goes away and the at the next startup it fails to start again. Needless to say this isn’t great for unintended reboots, etc. So, can anyone see anything obvious that I’m doing wrong? I’m just assuming that dovecot should create the needed subdir since I can’t find anything in the docs to suggest a way to create it otherwise. I’ve tried all I can think of at the moment to try to remedy this without success. I’m happy to provide additional details as needed to try to track this down. Thanks in advance, Garth

3 3

Dovecot 2.3-rc Logging Format
by Thomas Leuxner 24 Dec '17

24 Dec '17

Hi, the release candidate defaults to a log format with session IDs. mail_log_prefix = "%s(%u)<%{pid}><%{session}>: " As the LMTP service seems to have the session ID hardcoded, the IDs get duplicated in the logs: Dec 21 08:48:03 edi dovecot: lmtp(26573): Connect from local Dec 21 08:48:03 edi dovecot: lmtp(tlx(a)leuxner.net)[26573]: <fCVaBjNnO1rNZwAAIROLbg>: fCVaBjNnO1rNZwAAIROLbg: sieve: msgid=<2323281.OorJHhdMHM@ylum>, time=158ms, status=stored mail into mailbox ':public/Mailing-Lists/Debian-User' Dec 21 08:48:03 edi dovecot: lmtp(26573): Disconnect from local: Client has quit the connection (state = READY) Regards Thomas

3 2

Released Pigeonhole v0.5.0 for Dovecot v2.3.0.
by Stephan Bosch 24 Dec '17

24 Dec '17

Hello Dovecot users, Here's the definitive 0.5.0 release. There is one RC fix regarding the duplicate presence of the session ID in the LMTP/LDA log lines produced by the Sieve interpreter. Since this change is relative to the RC, it is not in the change log below. Changelog v0.5.0: * editheader extension: The implementation of header modifications is heavily updated. Although the functionality has not changed, the underlying code was updated to address several static analysis warnings, runtime integer arithmetic warnings (Clang), and to match updates in the Dovecot stream API. + variables extension: Made the maximum scope and variable size configurable. + subaddress: Support multiple recipient_delimiters. - enotify extension: mailto method: Fixed parsing of mailto URI with only a header part. - enotify plugin: mailto method: Make sure the "From:" header is set to a usable address and not "(null)". - Fixed writing address headers to outgoing messages. Sometimes headers were MIME-encoded twice, yielding invalid results. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.0.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.0.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Dovecot 2.3-rc1 SMTP submission proxy always gives TLS required error even when already using TLS
by Michael Marley 23 Dec '17

23 Dec '17

First of all, I apologize for my accidental empty message earlier. I just set up the SMTP submission proxy in Dovecot 2.3, but whenever I try to connect to it, it always returns "530 5.7.0 TLS required." for any sort of AUTH or MAIL command. This occurs even if TLS is being used. It also occurs regardless of whether I connect with a real client (Thunderbird) or manually with openssl s_client and regardless of whether a loopback connection or a remote connection is used. Here is the output of "dovecot -n". Please let me know if I can provide any other data. Thanks! # 2.3.0.rc1 (12aba5948): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.alpha1 (f60f2785) # OS: Linux 4.14.7-041407-generic x86_64 Ubuntu Bionic Beaver (development branch) auth_mechanisms = plain login auth_username_format = %Ln mail_location = mdbox:~/mdbox 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 index ihave duplicate mime foreverypart extracttext 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 { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = michael(a)michaelmarley.com protocols = imap sieve lmtp submission service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 0 } } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/private/michaelmarley.com.pem ssl_cipher_list = HIGH !RC4 !aNULL !eNULL !3DES @STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes submission_relay_host = localhost submission_relay_port = 24 submission_relay_trusted = yes userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } local_name matthewtmarley.com { ssl_cert = </etc/ssl/private/matthewtmarley.com.pem ssl_key = # hidden, use -P to show it }

2 4

Pigeonhole implicit keep gets unfiltered message
by Adam Weinberger 23 Dec '17

23 Dec '17

I'm getting a behaviour with pigeonhole that I wasn't expecting. Am I misunderstanding the design? I run my messages through a vnd.dovecot.filter. It's essentially this: filter "spam_filter"; if spamheaders { fileinto "spam"; stop; } Mail stored in the spam folder is the filtered version, but the implicit-keep message is the original, unfiltered message. If I add an explicit `keep;` to the end, it stores the filtered version into my inbox. Based on the filter RFC, I was expecting the implicit keep to retain the filtered version. Am I misinterpreting the spec? # Adam -- Adam Weinberger adamw(a)adamw.org http://www.adamw.org

2 4

Re: Lua Auth
by Mark Moseley 23 Dec '17

23 Dec '17

> > > > > 2) Is there an appropriate way to return data with spaces in it (or > presumably other non-alphanum chars. My quota name had a space in it, > which > somehow got interpreted as 'yes' , i.e.: > > imap: Error: Failed to initialize quota: Invalid quota root quota: Unknown > quota backend: yes > > I simply changed the space to an underscore as a workaround, but I'm > curious if there's a better way. I tried various quoting without success. > Didn't try escaping yet. > > > 2) Instead of string, return a key value table. you can have spaces in > values. > > > Does this work for auth_passdb_lookup too, or just auth_userdb_lookup? I've been returning a table with auth_userdb_lookup just fine. But when I try using it with passdb (and despite being very very sure that a 'password' key exists in the table I'm returning from auth_passdb_lookup() -- I'm logging it one line above the return), the passdb auth fails with this log entry: Dec 21 23:29:22 auth-worker(7779): Info: lua(test1(a)test.com,10.20.103.32,<dSvLQuZg+uIKFGcg>): No password returned (and no nopassword) I guess it's not seeing the password key in the table I'm returning. If I return a concat'd string ("password=... user=...") from auth_passdb_lookup(), it works just fine. I was also curious if there's a way to pass info between auth_userdb_lookup and auth_passdb_lookup. I was trying to use a table with auth_passdb_lookup() so I could take advantage of prefetch and thought that if auth_passdb_lookup didn't take a table, I could stash data away and then un-stash it in auth_userdb_lookup Thanks! > 3) response_from_template expands a key=value string into table by var > expanding values. > > > var_expand can be used to interpolation for any purposes. it returns a > string. see https://wiki.dovecot.org/Variables for details on how to use > it. > > > Individual variable access is more efficient to do directly. > > > --- > Aki Tuomi >

3 5

ot: how to block persistent same invalid account, different IPs
by Joseph Tam 22 Dec '17

22 Dec '17

"Voytek Eymont" <voytek(a)sbt.net.au> > I've installed fail2ban, it seems to be working as it identified my failed > test logins, BUT, my question is: > > what can I do when I see same invalid name trying to login to dovecot, > different IP each time, how can I say block each IP as used by this name ? If each IP is only used once in a long while, what would be the point? In general, distributed attacks are very hard to stop if you have a default accept stance. I've observed that most of the attacks to my site are from the enormous Chinese stated owned public network superblocks. I finally got sick of them so I now spiral these IMAP/POP connections into the Scharwzschild radius of my firewall. It's a prophylactic measure and not a reactive system like fail2ban, and may not work for you if you got road warriors that frequent that part of the world. However, it did get rid of a metric ton of BFD connections. Joseph Tam <jtam.home(a)gmail.com>

1 0

ot: how to block persistent same invalid account, different IPs
by Voytek Eymont 22 Dec '17

22 Dec '17

I've installed fail2ban, it seems to be working as it identified my failed test logins, BUT, my question is: what can I do when I see same invalid name trying to login to dovecot, different IP each time, how can I say block each IP as used by this name ? or it that a bad idea ? I can see two persistent attempts as so: I don't have such user 'ignacio' or 'julian' # grep ignacio.munoz /var/log/dovecot.log | wc 178 3436 35624 # grep ignacio.munoz /var/log/dovecot.log | grep 'auth fail' | wc 178 3436 35624 # grep julian /var/log/dovecot.log | wc 178 3432 34321 # grep julian /var/log/dovecot.log | grep 'auth fail' | wc 178 3432 34321 last 6 tries, sometimes have just : <ignacio.munoz>, sometimes, with tld Dec 22 17:00:33 imap-login: Info: Disconnected (auth failed, 1 attempts in 8 secs): user=<ignacio.munoz(a)aaa.com>, method=PLAIN, rip=157.122.183.218, lip=163.47.110.6, TLS, session=<Z4JniOdgkgCderfa> Dec 22 17:01:06 imap-login: Info: Disconnected (auth failed, 1 attempts in 7 secs): user=<ignacio.munoz>, method=PLAIN, rip=60.172.162.2, lip=163.47.110.6, TLS, session=<CsdriudgWAA8rKIC> Dec 22 18:58:26 imap-login: Info: Disconnected (auth failed, 1 attempts in 10 secs): user=<ignacio.munoz(a)aaa.com>, method=PLAIN, rip=60.30.224.189, lip=163.47.110.6, TLS: Disconnected, session=<kvLWLelg0QA8HuC9> Dec 22 18:58:59 imap-login: Info: Disconnected (auth failed, 1 attempts in 7 secs): user=<ignacio.munoz>, method=PLAIN, rip=220.164.2.138, lip=163.47.110.6, TLS: Disconnected, session=<T7T5L+lgRADcpAKK> Dec 22 19:30:28 imap-login: Info: Disconnected (auth failed, 1 attempts in 6 secs): user=<ignacio.munoz(a)aaa.com>, method=PLAIN, rip=113.8.194.3, lip=163.47.110.6, TLS, session=<jfSgoOlgswBxCMID> Dec 22 19:31:09 imap-login: Info: Disconnected (auth failed, 1 attempts in 6 secs): user=<ignacio.munoz>, method=PLAIN, rip=58.210.119.226, lip=163.47.110.6, TLS, session=<moAVo+lg8gA60nfi> -- Voytek

3 2

New Dovecot service: SMTP Submission (RFC6409)
by Stephan Bosch 22 Dec '17

22 Dec '17

Hi, As some of you know, I started implementing the SMTP submission proxy a few years ago. It acts as a front-end for any MTA, adding the necessary functionality for an SMTP submission service, also known as a Mail Submission Agent (MSA) (https://tools.ietf.org/html/rfc6409) The main reason I created this, back then, was implementing the BURL capability (https://tools.ietf.org/html/rfc4468) The main application of that capability -- together with IMAP URLAUTH -- is avoiding a duplicate upload of submitted e-mail messages; normally the message is both sent through SMTP and uploaded to the "Sent" folder through IMAP. Using BURL, the client can first upload the message to IMAP and then use BURL to make the SMTP server fetch the message from IMAP for submission, thereby avoiding a second upload. Apart from BURL, the submission proxy service also adds the required AUTH support, avoiding the need to configure the MTA for SASL authentication. More SMTP capabilities like CHUNKING and SIZE are supported, without requiring the backend MTA supporting these extensions. Other capabilities like DSN currently require support from the backend/relay MTA. At this point, the submission proxy is still pretty basic. However, it will provide a basis for adding all kinds of functionality in the (not so distant) future. For the first time, it will be possible to act upon message submission, rather than only message retrieval; e.g. plugins can be devised that process outgoing messages somehow. Examples of the things we could do are adding Sieve filtering support for outgoing messages, or implicitly storing submitted messages to the Sent folder. Once a plugin API is devised, you can create your own plugins. The reason I send this message now, is that this code is finally merged into the Dovecot master repository. This means that it is part of the upcoming 2.3 release. Now that it is merged, you can install and test it from Github if you like. Feedback is of course appreciated. The documentation is still pretty sparse, but there is currently not much to configure. Just add "submission" to the protocols and configure the relay MTA server. The configuration is currently only documented in the example configuration in doc/example-config/conf.d/20-submission.conf. The submission service is a login service, just like IMAP, POP3 and ManageSieve, so clients are required to authenticate. The same authentication configuration will also apply to submission, unless you're doing protocol-specific things, in which case you may need to amend your configuration for the new protocol. BURL support requires a working IMAP URLAUTH implementation. I've updated the automated Xi Debian package builder to create an additional dovecot-submissiond package. So, if you're using the Xi packages, you only need to install that package and configure the relay MTA. Regards, Stephan.

7 16

v2.3.0 released
by Timo Sirainen 22 Dec '17

22 Dec '17

https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz.sig Some random notes: - This release is signed with a new PGP key 0x18A348AEED409DA1 (which is signed by the old key). - This fixes several compiling issues reported for the 2.3 release candidate. Also a few other fixes mainly for submission server and doveadm server. - We're still planning to make at least one (or two) more v2.2.x release before retiring it. It's now time for Christmas holidays though, so the next release will have to wait until the end of January. - We'll start distributing v2.3.x releases in apt/yum repositories in near future. There will be a separate email about it. Some repetition from the release candidate's announcement: There are several new and exciting features in v2.3.0. I'm especially happy about the new logging and statistics code, which will allow us to generate statistics for just about everything. We didn't have time to implement everything we wanted for them yet, and there especially aren't all that many logging events yet that can be used for statistics. We'll implement those to v2.3.1, which might also mean that some of the APIs might still change in v2.3.1 if that's required. We also have new lib-smtp server code, which was used to implement SMTP submission server and do a partial rewrite for LMTP server. Some of the larger changes: * Various setting changes, see https://wiki2.dovecot.org/Upgrading/2.3 * Logging rewrite started: Logging is now based on hierarchical events. This makes it possible to do various things, like: 1) giving consistent log prefixes, 2) enabling debug logging with finer granularity, 3) provide logs in more machine readable formats (e.g. json). Everything isn't finished yet, especially a lot of the old logging code still needs to be translated to the new way. * Statistics rewrite started: Stats are now based on (log) events. It's possible to gather statistics about any event that is logged. See http://wiki2.dovecot.org/Statistics for details * ssl_dh setting replaces the old generated ssl-parameters.dat * IMAP: When BINARY FETCH finds a broken mails, send [PARSE] error instead of [UNKNOWNCTE] * Linux: core dumping via PR_SET_DUMPABLE is no longer enabled by default due to potential security reasons (found by cPanel Security Team). + Added support for SMTP submission proxy server, which includes support for BURL and CHUNKING extension. + LMTP rewrite. Supports now CHUNKING extension and mixing of local/proxy recipients. + auth: Support libsodium to add support for ARGON2I and ARGON2ID password schemes. + auth: Support BLF-CRYPT password scheme in all platforms + auth: Added LUA scripting support for passdb/userdb. See https://wiki2.dovecot.org/AuthDatabase/Lua - Input streams are more reliable now when there are errors or when the maximum buffer size is reached. Previously in some situations this could have caused Dovecot to try to read already freed memory. - Output streams weren't previously handling failures when writing a trailer at the end of the stream. This mainly affected encrypt and zlib compress ostreams, which could have silently written truncated files if the last write happened to fail (which shouldn't normally have ever happened). - virtual plugin: Fixed panic when fetching mails from virtual mailboxes with IMAP BINARY extension. - doveadm-server: Fix potential hangs with SSL connections - doveadm proxy: Reading commands' output from v2.2.33+ servers could have caused the output to be corrupted or caused a crash. - Many other smaller fixes

1 0

detect suspicious logins
by Matthew Broadhead 22 Dec '17

22 Dec '17

does anyone know of a linux module (maybe similar to fail2ban) that could be installed which would monitor email logs (sign ins) and alert the user to any suspicious activity on their account? i suspect it would need to log geo location, device type and ip address to a database. it seems like a module like this would be very useful and should exist already? thanks in advance

4 3

Re: Disable ssl validation for replication?
by Joseph Tam 22 Dec '17

22 Dec '17

Joseph Ward writes: > I'm aware of at least a couple of fallback options: > ??? -have a self-signed cert for replication and use the Let's Encrypt > one for IMAP/POP > ??? - create firewall rules allowing them to connect to each other over > the public internet so that it can validate the proper cert > ? > These are both much less palatable than simply disabling the cert > validation if it's possible. Maybe instead of disabling the check, appease it by supplying (in /etc/hosts) an alternate mapping of the FQDN subject of your certificate to your internal IP: 10.x.x.x your.sync.target Joseph Tam <jtam.home(a)gmail.com>

3 2

Re: detect suspicious logins
by Joseph Tam 21 Dec '17

21 Dec '17

Matthew Broadhead <matthew.broadhead(a)nbmlaw.co.uk> wrote: >> does anyone know of a linux module (maybe similar to fail2ban) that >> could be installed which would monitor email logs (sign ins) and alert >> the user to any suspicious activity on their account? I just monitor straight from the logs using homebrew utilties. @lbutlr" <kremels(a)kreme.com> > Fail2ban can protect email logins. Alerting a user because random IP > in Korean Middle School tried to login seems no helpful. > >> i suspect it would need to log geo location, device type and ip >> address to a database. it seems like a module like this would be very >> useful > > How? > > Blacklist failed logins. That protects everyone and doesn't induce panic. I just went through a long thread elsewhere on this topic. Fail2ban is mainly a counter brute force measure. If you have a strong password policy, the net result of using it is that it makes your logs smaller, and maybe saves some CPU cycles or from DoS for really intense bouts, but otherwise, does not add to security as good passwords makes BFD infeasible. *However*, if the attacker knows the approximate password (e.g. shoulder surfing), this may help, but eventually, the password will succumb to a patient diligent attack. What the OP is considering is if the password is divulged e.g. phishing attack or snarfed from another source. In this case, an intruder's authentication will succeed immediately. If a monitor spots someone authenticating from another continent than where the owner is supposed to be, or from 2 locations thousands of miles apart, or from 5 different location simultaneously, or tried to send a huge number of messages with many bounces, or was using a different mail clients that one historically used), it can signal the admin/user for further investigation. For users, I think reporting a login origin audit will be helpful, regardless of circumstances. However, it should be done out of band, if the assumption is someone else has control of the account. Joseph Tam <jtam.home(a)gmail.com>

1 0

Logouts/disconnections not being logged?
by Joseph Tam 21 Dec '17

21 Dec '17

In a previous thread Subject: Re: iPhone/iPad IMAP connection bursts causes user+IP exceeded I reported the behaviour of MacOSX/iOS IMAP readers whereby it would use up all available connections (up to the mail_max_userip_connections setting) for mailbox searches, then log them all out, then repeat the cycle with another batch of mailbox searches, until all mailboxes were scanned. However, login/logout log counts don't square up. I would observe (for a particular user+ip) mail_max_userip_connections login entries, followed by *fewer* than mail_max_userip_connections logout entries. (I could not find any disconnections or other forms of termination.) The next peak connection count happened after another mail_max_userip_connections logins (implying the total connection count > mail_max_userip_connections), then another strings of logouts fewer than mail_max_userip_connections. For example, if mail_max_userip_connections=100, I would see 0 -> 100 logins -> 87 logouts -> 100 logins -> 87 logouts -> 100 logins -> 94 logouts -> 100 logins -> ... It appears that somewhere, somehow, IMAP session exits are not being logged. Is there a reason to explain this discrepancy? Joseph Tam <jtam.home(a)gmail.com>

1 0

Virtual folders: Panic: file mail-index-sync.c
by Andreas Tauscher 21 Dec '17

21 Dec '17

Hi! I have compiled Dovecot 2.33.2 and crated some virtual folders. When I create a virtual folder for all flagged mails with dovecot-virtual containing * flagged and I set in 15-mailboxes.conf mailbox virtual/Flagged { special_use = \Flagged comment = All flagged messages auto = subscribe } The dovecot is crashing when any virtual folder is accessed: Dec 21 01:07:59 mail dovecot: imap(transfer1(a)shidolya.co.tz): Panic: file mail-index-sync.c: line 413 (mail_index_sync_begin_to2): asserti on failed: (!index->syncing) Dec 21 01:07:59 mail dovecot: imap(test(a)test.local): Error: Raw backtrace:/usr/lib/dovecot/libdovecot.so.0(+0x935c2) [0x7f4ead13 95c2] -> /usr/lib/dovecot/libdovecot.so.0(+0x936ad) [0x7f4ead1396ad] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4ead0c9f61] -> /u sr/lib/dovecot/libdovecot-storage.so.0(+0xd4d4c) [0x7f4ead49ed4c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x4 f) [0x7f4ead49ee2f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1c) [0x7f4ead49eecc] -> /usr/lib/dovecot/modules/l ib20_virtual_plugin.so(virtual_storage_sync_init+0x20e) [0x7f4eabe9904e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x4 4) [0x7f4ead4076a4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f4ead407747] -> /usr/lib/dovecot/libdovecot-storage .so.0(index_storage_get_status+0x31) [0x7f4ead481dd1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x916d) [0x7f4eabe9616d] -> /us r/lib/dovecot/libdovecot-storage.so.0(+0x9ce81) [0x7f4ead466e81] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xd825) [0x7f4eac8d0825] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f4ead407ae1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so (virtual_storage_sync_init+0x1096) [0x7f4eabe99ed6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) [0x7f4ead4076a4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f4ead407747] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7f4ead481dd1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x916d) [0x7f4eabe9616d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x9ce81) [0x7f4ead466e81] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xd825) [0x7f4eac8d0825] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f4ead407ae1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x1096) [0x7f4eabe99ed6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) [0x7f4ead4076a4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f4ead407747] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7f4ead481dd1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x916d) [0x7f4eabe9616d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x9ce81) [0x7f4ead466e81] When I remove "auto = subscribe" everything working like expected. I got this crash only if I use "flagged" in the virtual folder. Other virtual folders like a unseen folder is working fine with "auto = subscribe" Andreas

1 0

ot: fail2ban dovecot setup
by voytek＠sbt.net.au 20 Dec '17

20 Dec '17

I'm trying to setup and test fail2ban with dovecot I've installed fail2ban, I've copied config from https://wiki2.dovecot.org/HowTo/Fail2Ban, and, trying to test it, attempted multiple mail access with wrong password, but, get this: # fail2ban-client status dovecot-pop3imap Status for the jail: dovecot-pop3imap |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- File list: /var/log/dovecot.log `- Actions |- Currently banned: 0 |- Total banned: 0 `- Banned IP list: # grep 'auth fail' /var/log/dovecot.log | grep voytek@k | wc 19 367 3749 and Dec 17 09:55:03 imap-login: Info: Disconnected (auth failed, 2 attempts in 5 secs): user=<voytek@k..au>, method=PLAIN, rip=110.175.246.167, lip=163.47.110.7, TLS, session=<bQ6mAX1gHcRur/an> Dec 17 09:55:12 imap-login: Info: Disconnected (auth failed, 2 attempts in 4 secs): user=<voytek@k..au>, method=PLAIN, rip=110.175.246.167, lip=163.47.110.7, TLS, session=<Osk5An1gAKVur/an> Dec 17 09:55:20 imap-login: Info: Disconnected (auth failed, 2 attempts in 4 secs): user=<voytek@k..au>, method=PLAIN, rip=110.175.246.167, lip=163.47.110.7, TLS, session=<xsq/An1gDN1ur/an> Dec 17 09:55:27 imap-login: Info: Disconnected (auth failed, 2 attempts in 4 secs): user=<voytek@k..au>, method=PLAIN, rip=110.175.246.167, lip=163.47.110.7, TLS, session=<RVUkA31gm4xur/an> # cat dovecot-pop3imap.conf [Definition] failregex = (?: pop3-login|imap-login): (?:Authentication failure|Aborted login \(auth failed|Aborted login \(tried to use disabled|Disconnected \(auth failed).*rip=(?P<host>\S*),.* ignoreregex = # systemctl status fail2ban ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2017-12-16 22:35:14 AEDT; 12h ago Docs: man:fail2ban(1) Process: 2034 ExecStop=/usr/bin/fail2ban-client stop (code=exited, status=0/SUCCESS) Process: 6024 ExecReload=/usr/bin/fail2ban-client reload (code=exited, status=0/SUCCESS) Process: 2036 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=0/SUCCESS) Main PID: 2039 (fail2ban-server) CGroup: /system.slice/fail2ban.service └─2039 /usr/bin/python2 -s /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/ru... Dec 16 22:35:14 systemd[1]: Starting Fail2Ban Service... Dec 16 22:35:14 fail2ban-client[2036]: 2017-12-16 22:35:14,657 fail2ban.server [2...9.7 Dec 16 22:35:14 fail2ban-client[2036]: 2017-12-16 22:35:14,657 fail2ban.server [2...ode Dec 16 22:35:14 systemd[1]: Started Fail2Ban Service. Dec 17 09:21:51 systemd[1]: Reloaded Fail2Ban Service. Dec 17 09:22:52 systemd[1]: Reloaded Fail2Ban Service. Dec 17 09:31:40 systemd[1]: Reloaded Fail2Ban Service. Hint: Some lines were ellipsized, use -l to show in full.

4 8

Shared mailboxes ACL's in MySQL, mailboxes in LDAP
by Matt . 20 Dec '17

20 Dec '17

Hi Guys, I'm having a situation that I want to autocreate my mailboxes using ldap auth as my mailboxes are in there. But as I need to share some mailboxes as shared folder is it possible to have that information in MySQL ? Maybe it even better to put everything in MySQL but designwise it's actually not. I f someone has an example how to accomplish this as I'm reading about ACL's as well and I'm wondering if this is actually going to work. Thanks! Matt

1 0

POP3 lock
by The Doctor 19 Dec '17

19 Dec '17

This might be trivial or not. I have a customer access his e-mail via POP3 using multiple devs. I recommend they switch to IMAP , however, How can the POP3 locking be made into a non-issue? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism Happy Christmas 2017 and Merry New Year 2018

2 1

IMAP proxy
by Gandalf Corvotempesta 19 Dec '17

19 Dec '17

I'm migrating an old server to another old server (same dovecot version in both servers) The migration itself is straightforward, stop dovecot on the old server, migrate everything via rsync, start dovecot to the new server. There is only one step left: change the dns configuration, pointing from the old server to the newer one. As most of domains are not managed by me and some other domains are pointing to our server via IP, I can't simply change the A record or wait for all users to change their domain configuration. TL;DR: is possible to use dovecot as IMAP proxy so that even after changing our dns records, any user directly connecting to my old server would be proxied to the newer one automatically ? Any additional software or only a configuration change is required ?

3 3