- dovecot - dovecot.org

Issue on install - file mbox-sync.c: line 1371 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2)
by Ian Turley 26 Jul '17

26 Jul '17

First of all apologies for using such an old version - I am trying to upgrade slowly and have had to go through this version first. As you can see I am getting an error in the log file as : file mbox-sync.c: line 1371 (mbox_sync_handle_eof_updates): assertion failed: (trailer_size <= 2) Raw backtrace: imap [0x80acdc1] -> imap [0x80accdc] -> imap(mbox_sync+0x14e9) [0x8079a29] -> imap(mbox_storage_sync_init+0x3e) [0x8079d8e] -> imap(imap_sync_nonselected+0x1c) [0x806183c] -> imap(_cmd_select_full+0xc3) [0x8059983] -> imap(cmd_select+0x19) [0x8059b49] -> imap [0x805afb8] -> imap [0x805b03c] -> imap(_client_input+0x6c) [0x805b71c] -> imap(io_loop_handler_run+0x110) [0x80b2a50] -> imap(io_loop_run+0x1c) [0x80b1f8c] -> imap(main+0x4c0) [0x8063640] -> /lib/libc.so.6(__libc_start_main+0xdc) [0xdd4edc] -> imap [0x80561a1] Is this some setting missing or corrupt mailbox? I only have very basic set up at this time to test. Version 1.0.7 # 1.0.7: /etc/dovecot.conf ssl_cert_file: /etc/postfix/certs/emma.turls.co.uk.crt ssl_key_file: /etc/postfix/certs/turls_csr.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail/:INBOX=/var/spool/mail mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd Regards Ian -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Re: under another kind of attack
by Joseph Tam 25 Jul '17

25 Jul '17

Olaf Hopp <Olaf.Hopp(a)kit.edu> writes: > I have dovecot shielded by fail2ban which works fine. But since a few > days I see many many IPs per day knocking on my doors with wron > password and/or users. But the rate at which they are knocking is very > very low. So fail2ban will never catch them. Slow roll distributed attacks. Really hard to stop. > And I see many many distinct IPs per day (a few hundred) trying many > many existing and non-existings accounts. As you see in the timestamps > in my examples, this can not be handled by fail2ban without affecting > regular users with typos. Is anybody observing something similar ? All the time, and to many services. If you need to be fault tolerant, you'll either have to set tolerant limits (allow reasonable number of failures), or timeout features. You could also track successful logins as whitelisting entries for future logins. > Anybody an idea against this ? Many of these observed IPs are chinese > mobile IPs, if this matters. But we have also chinese students and > researchers all abroad. Nearly an intractable problem, especially since your users are embedded in a notoriously infested network (as someone quipped, "like picking marshmallows out from a pile of sh*t"). Some ideas: - pre-emption (using third party RBLs that targets BFD) - immediate blacklisting of known bad users/passwords (e.g. "admin", "support", extinct users, etc.) - persistent tracking storage: tracking in SQL, or or large LRU list that can reach far enough back in time. (I think Aki mentioned weakforced which you can use instead if fail2ban to implement some of these things.) There are other solutions like alternate ports, port knocking, certificate authentication, or VPN, but they are hard/impossible to do with a large userbase, or have high setup/amortization costs. If you have a enforced strong password policy, these brute forcers have little chance of succeeding, so maybe the easiest cheapest policy is to ignore it. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: under another kind of attack
by Joseph Tam 25 Jul '17

25 Jul '17

"mourik jan c heupink" <lists(a)merit.unu.edu> writes: > On 07/24/2017 04:51 AM, Joseph Tam wrote:> You are essentially writing your own backend by taking over >> authentication. You'll be accepting user/password inputs into your >> checkpassword executable, then use the LDAP API (or some other system...snip >> and source address, which will be adversely affect performance on a >> busy server as authentication data cannot be cached. > > While this sounds awesome, it can do much more than what I was/am after, and appears lot more complicated to setup than what I had figured myself. > > Shouldn't I be able to do something like this: > > passdb { > driver = passwd-file > # application specific passwd-file should work from anywhere > # (so: no allow_nets) > args = /etc/dovecot/dovecot-application-specific > } > passdb { > # only allowed to use this from within local 192.168.1.0/24 > args = /etc/dovecot/dovecot-ldap.conf.ext allow_nets=192.168.1.0/24 > driver = ldap > } Yes, that would take care of *one* of the items on your wishlist (network specific passwords). You also wanted time specific passwords. And intelligent brute force detection. And blacklist lookups. Rather than cobbling together fail2ban, utility scripts, multiple passdbs, firewall rules and whatever other system you'll need to recruit, I'm suggesting you amortize the effort and pack it into one place, then you can extend this to incorporate whatever your heart desires. The complexity of implementing this reflects the complexity of your requirements. If you only had generic authentication needs, then the dovecot supplied facilities would be perfect. But you don't. > Where I would generate lines in dovecot-application-specific using a > script or some webpage, and generate lines like: > > username1:randomONE:vmail:vmail::/var/vmail/username1: > username1:randomTWO:vmail:vmail::/var/vmail/username1: > username2:randomTHREE:vmail:vmail::/var/vmail/username2: > username2:randomFOUR:vmail:vmail::/var/vmail/username2: > > And the result would be: username1 can login from anywhere, using > passwords "randomONE" & "randomTWO", plus the password in ldap when > coming from the internal network. You'll probably need 3 passdb, LDAP and 2 fallback passwd-file dbs. Joseph Tam <jtam.home(a)gmail.com>

1 0

SIEVE: handling of lineending in fields
by Ingo Thierack 25 Jul '17

25 Jul '17

Hello, migrated von the mailserver from centos to alpine linux. Most parts are run well. dovecot 2.2.31 sieve: 0.4.19 But i fight with on behavior. I have an sieve script which pipes a few fields to an external script which send this data to an telegram-bot. the part of the sieve-script. if header :matches "Subject" "*" { set "subject" "${1}"; } if header :matches "from" "*" { set "from" "${1}"; } if header :matches "to" "*" { set "to" "${1}"; } foreverypart { if header :mime :type :is "Content-Type" "text" { extracttext :first 30 "msgcontent"; break; } } pipe :copy :try "notify.sh" [ "", "(${from})#${to}#${subject}", "\"${msgcontent}\"" ]; What i get now is an error about looks like encoding of the linefeeds. default: line 107: error: specified :args item `"test 4??"' is invalid. Here is sent a mail which contains in subject "test 4". or default: line 107: error: specified :args item `"?? ?? ??? ??? Oracle Magazine "' is invalid. Here is sent a mail which contains in subject "test 4". On centos this was never an problem. With alpine-linux this process is complete broken. Any hints, where to look and maybee fix thie behavior? Mybe its ab problem with the libmusl which used in alpine. Regards Ingo

2 2

last_logon SQL mapping
by viper 25 Jul '17

25 Jul '17

Hi I have been attempting to do a mapping on the last_logon plugin. I have been reading the documentation on mapping. is there any way to customise a little more and create a individual SQL query for each of the functions SELECT and UPDATE, my current SQL setup has the username and domain in separate tables and my user_query and password_query are concat which I do not believe can be defined in the dictionary map process, I was also wanting to use datatime as the saved field but it seems only the unix timestamp is used. If there is any way to create a fully custom query that can be executed I believe this would allow me to preform the action am looking for in the same manner as the user_query and password_query If anyone has any suggestions please let me know Regards Craig

2 1

Core dumped when authenticating to managesieve
by Kristjan Eentsalu 25 Jul '17

25 Jul '17

Hey, I'm getting "Error in MANAGESIEVE command received by server." and service(managesieve-login) killed with signal 11 (core dumped) when doing two line autenticate(sogo) to managesieve(). # telnet localhost 4190 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "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 editheader" "NOTIFY" "mailto" "SASL" "PLAIN" "VERSION" "1.0" OK "Dovecot ready." AUTHENTICATE "PLAIN" {52+} XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX== NO "Error in MANAGESIEVE command received by server." AUTHENTICATE "PLAIN" {52+} <---- trying again Connection closed by foreign host. and after that in logs there is "dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 38748 killed with signal 11 (core dumped)" One line autenticate works. # telnet localhost 4190 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "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 editheader" "NOTIFY" "mailto" "SASL" "PLAIN" "VERSION" "1.0" OK "Dovecot ready." AUTHENTICATE "PLAIN" "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX==" OK "Logged in." OS: FreeBSD 11.1-RC3 Dovecot 2.2.31 , pigeonhole 0.4.19 Trace below GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... warning: core file may not match specified executable file. Core was generated by `dovecot/managesieve-login'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot-login.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot-login.so.0 Reading symbols from /usr/lib/libssl.so.8...done. Loaded symbols for /usr/lib/libssl.so.8 Reading symbols from /lib/libcrypto.so.8...done. Loaded symbols for /lib/libcrypto.so.8 Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /usr/lib/libkrb5.so.11...done. Loaded symbols for /usr/lib/libkrb5.so.11 Reading symbols from /usr/lib/libgssapi.so.10...done. Loaded symbols for /usr/lib/libgssapi.so.10 Reading symbols from /usr/lib/libgssapi_krb5.so.10...done. Loaded symbols for /usr/lib/libgssapi_krb5.so.10 Reading symbols from /lib/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/libasn1.so.11...done. Loaded symbols for /usr/lib/libasn1.so.11 Reading symbols from /usr/lib/libcom_err.so.5...done. Loaded symbols for /usr/lib/libcom_err.so.5 Reading symbols from /lib/libcrypt.so.5...done. Loaded symbols for /lib/libcrypt.so.5 Reading symbols from /usr/lib/libhx509.so.11...done. Loaded symbols for /usr/lib/libhx509.so.11 Reading symbols from /usr/lib/libroken.so.11...done. Loaded symbols for /usr/lib/libroken.so.11 Reading symbols from /usr/lib/libwind.so.11...done. Loaded symbols for /usr/lib/libwind.so.11 Reading symbols from /usr/lib/libheimbase.so.11...done. Loaded symbols for /usr/lib/libheimbase.so.11 Reading symbols from /usr/lib/libprivateheimipcc.so.11...done. Loaded symbols for /usr/lib/libprivateheimipcc.so.11 Reading symbols from /lib/libthr.so.3...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 i_stream_seek (stream=0x0, v_offset=80) at istream.c:296 296 istream.c: No such file or directory. in istream.c (gdb) bt full #0 i_stream_seek (stream=0x0, v_offset=80) at istream.c:296 _stream = (struct istream_private *) 0x5385e16 #1 0x000000000536937a in i_stream_limit_read (stream=0x767d540) at istream-limit.c:34 lstream = (struct limit_istream *) 0x767d540 left = 123848760 ret = 1 pos = 119265200 #2 0x000000000535f340 in i_stream_read (stream=0x767d5b0) at istream.c:174 _stream = (struct istream_private *) 0x767d540 old_size = 0 ret = 124244864 #3 0x00000000053607ae in i_stream_read_data (stream=0x767d5b0, data_r=0x7fffffffe868, size_r=0x7fffffffe878, threshold=0) at istream.c:569 ret = 0 read_more = false #4 0x00000000004038d1 in ?? () No symbol table info available. #5 0x0000000000403c1a in ?? () No symbol table info available. #6 0x00000000004030ad in ?? () No symbol table info available. #7 0x0000000000402eaa in ?? () No symbol table info available. #8 0x0000000004838435 in client_input (client=0x76c0c10) at client-common.c:920 No locals. #9 0x000000000537028d in io_loop_call_io (io=0x76a4300) at ioloop.c:599 ioloop = (struct ioloop *) 0x763a000 t_id = 2 #10 0x0000000005372f74 in io_loop_handler_run_internal (ioloop=0x763a000) at ioloop-poll.c:209 ctx = (struct ioloop_handler_context *) 0x76340e0 pollfd = (struct pollfd *) 0x7673840 tv = {tv_sec = 0, tv_usec = 895835} io = (struct io_file *) 0x76a4300 msecs = 896 ret = 0 call = true #11 0x00000000053707f8 in io_loop_handler_run (ioloop=0x763a000) at ioloop.c:648 No locals. #12 0x0000000005370621 in io_loop_run (ioloop=0x763a000) at ioloop.c:623 No locals. #13 0x00000000052ad15b in master_service_run (service=0x7635000, callback=0x4840630 <client_connected>) at master-service.c:666 No locals. #14 0x00000000048402f7 in login_binary_run (binary=0x4061b8, argc=1, argv=0x7fffffffeb40) at main.c:506 service_flags = 1608 set_pool = 0x7646020 login_socket = 0x48494c6 "login" c = -1 #15 0x000000000040288f in ?? () No symbol table info available. #16 0x000000000462c000 in ?? () No symbol table info available. #17 0x0000000000000000 in ?? () No symbol table info available. Current language: auto; currently minimal dovecot -n # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: FreeBSD 11.1-RC3 amd64 auth_master_user_separator = * auth_verbose_passwords = plain disable_plaintext_auth = no lmtp_save_to_detail_mailbox = yes mail_access_groups = imapmail mail_debug = yes mail_gid = imapmail mail_plugins = acl quota mail_uid = imapmail mailbox_list_index = yes 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 editheader namespace { hidden = no inbox = no list = no location = prefix = separator = / subscriptions = yes type = private } namespace public { hidden = no list = children location = maildir:/mail/imap/ localnet.net/shared:INDEXPVT=%h/public:LAYOUT=fs:DIRNAME=DlkfdewDSD prefix = shared/ separator = / subscriptions = no type = public } namespace inbox { alias_for = hidden = no inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = INBOX/ separator = / subscriptions = no type = private } namespace user { list = children location = maildir:%%h/Maildir:LAYOUT=fs:DIRNAME=DlkfdewDSD:INDEXPVT=%h/shared/%%n prefix = user/%%n/ separator = / subscriptions = no type = shared } passdb { args = /usr/local/etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/mail/dovecot/db/global-acls:cache_secs=300 acl_shared_dict = file:/mail/dovecot/db/shared-mailboxes quota = maildir:INBOX user/%u quota2 = maildir:Public quota:ns=shared/ quota2_rule = *:storage=100G quota_grace = 10%% quota_rule = *:storage=5G quota_rule2 = INBOX/Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = yes recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_extensions = +editheader } protocols = imap lmtp sieve service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { chroot = drop_priv_before_exec = yes inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 0 vsz_limit = 64 M } ssl = no ssl_cert = </etc/ssl/servercerts/cert.crt ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl quota sieve postmaster_address = postmaster(a)localnet.net } protocol imap { mail_plugins = acl quota imap_acl imap_quota }

3 2

Re: failed to store into mailbox 'INBOX/Junk': Permission denied
by Davide Marchi 25 Jul '17

25 Jul '17

> For more clarity I also attach the content of > "/etc/dovecot/conf.d/15-mailboxes.conf" > > > # mailbox Junk { > # special_use = \Junk > # } > # mailbox Trash { > # special_use = \Trash > # } > mailbox INBOX/Junk { > auto = subscribe > special_use = \Junk > } > mailbox INBOX/Trash { > auto = subscribe > special_use = \Trash > } > > Date: Mon, 24 Jul 2017 18:06:29 +0200 > From: Christian Kivalo <ml+dovecot(a)valo.at> > > Please also provide your doveconf -n Here my Dovecot configuration (I've commented out "mailbox Junk" and "mailbox Trash" above) # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 ext4 auth_mechanisms = plain login cram-md5 mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = acl 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 namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX/Junk { auto = subscribe special_use = \Junk } mailbox INBOX/Trash { auto = subscribe special_use = \Trash } 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/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/etc/dovecot/dovecot-acl sieve = ~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_dir = ~/sieve } protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/server.sio4.org/fullchain.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/letsencrypt/live/server.sio4.org/privkey.pem ssl_prefer_server_ciphers = yes userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = static } protocol imap { mail_plugins = acl imap_acl mail_log notify } protocol lmtp { mail_plugins = acl sieve } Many thanks Christian!

1 0

Strange Error: Password data is not valid for scheme SHA256. Please help me resolve it.
by david.madman2＠vfemail.net 24 Jul '17

24 Jul '17

Hello, I am using version 2.2.31 (65cde28) on an Ubuntu 16.04 VPS. I am attempting to setup a mail server using a flat file system as an experiment. I am able to send e-mail from external domain names and the messages land in my /var/mail/vmail/domain/user/ directories. I am trying to setup Thunderbird as an MUA using the information I generated on my VPS namely the IMAP server, username(a)domain.com, password, and SMTP server. IMAP server - www.domain.com SMTP server - www.domain.com Username - created in /etc/postfix/virtual-mailbox-users.db and /etc/dovecot/passwd.db Password - created by dovadm pw -s SHA256 and entered (along with the username) in /etc/dovecot/passwd.db I enter this information into "new accounts" in Thunderbird and select STARTTLS with ports 143 (IMAP) and 587 (SMTP). (I have experimented with a variety of other combinations too). I click "Done" which transmits the information to the domain server to verify the details. My /var/log/mail.log shows: Jul 22 18:40:48 www dovecot: auth: Error: passwd-file(test(a)domain.com,46.xxx.xxx.xxx,<wZoHUuxU6IAu9j4y>): Password data is not valid for scheme SHA256: Input length isn't valid (0 instead of 32) Jul 22 18:41:00 www dovecot: message repeated 2 times: [ auth: Error: passwd-file(test(a)domain.com,46.xxx.xxx.xxx,<fGoHUuxU6IAu9j4y>): Password data is not valid for scheme SHA256: Input length isn't valid (0 instead of 32)] Jul 22 18:41:02 www dovecot: imap-login: Disconnected (auth failed, 3 attempts in 14 secs): user=<test(a)domain.com>, method=PLAIN, rip=46.xxx.xxx.xxx, lip=139.xxx.xxx.xxx, TLS, session=<fGoHUuxU6IAu9j4y> What does "Password data is not valid for scheme SHA256: Input length isn't valid (0 instead of 32)]" mean? I assume that there is some kind of a mismatch between the way I generated the password with doveadm and entered it in passwd.db and the way I entered the non-hashed password into the password field in the new account section of Thunderbird. Is there a way to resolve this issue? My dovecot -n is below. You will note that the passdb section does have the scheme as SHA256. Many thanks. # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.4.0-83-generic x86_64 Ubuntu 16.04.2 LTS ext4 auth_mechanisms = plain login auth_verbose = yes mail_home = /var/mail/vmail/%d/%n mail_location = maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs 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 { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = username_format=%u scheme=SHA256 /etc/dovecot/passwd.db driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/letsencrypt/live/www.domain.com/fullchain.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = # hidden, use -P to show it userdb { args = uid=5000 gid=5000 home=/var/mail/vmail/%d/%n driver = static } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 10 } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster(a)domain.com quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 4

Re: under some kind of attack
by Joseph Tam 24 Jul '17

24 Jul '17

>> As per my post: checkpassword. You can then use one password on Mondays, >> Wednesdays, and Fridays, alternate passwords on Tuesdays and Thursday >> fetched from a rot-13 database, and only from prime numbered IP addresses >> on weekends, if that's what you want. > > Having read the wiki page on checkpassword, I am unsure how this would > work with an ldap backend. > > Could you elaborate on that? You are essentially writing your own backend by taking over authentication. You'll be accepting user/password inputs into your checkpassword executable, then use the LDAP API (or some other system that will do it for you) to authenticate. (You can Google around for code snippets.) You'll have direct control over all aspects of authentication (if/when/where/etc) that a generic backend can't provide. You can choose do implement using shell/PERL/etc script, or compile to executable from C sources. It's more work, but if you need to do everything on your wish list, I can't see any eaiser option. One of the drawbacks is that a working password depends on both time and source address, which will be adversely affect performance on a busy server as authentication data cannot be cached. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: failed to store into mailbox 'INBOX/Junk': Permission denied
by Davide Marchi 24 Jul '17

24 Jul '17

For more clarity I also attach the content of "/etc/dovecot/conf.d/15-mailboxes.conf" # mailbox Junk { # special_use = \Junk # } # mailbox Trash { # special_use = \Trash # } mailbox INBOX/Junk { auto = subscribe special_use = \Junk } mailbox INBOX/Trash { auto = subscribe special_use = \Trash } Thanks again

2 1

failed to store into mailbox 'INBOX/Junk': Permission denied
by Davide Marchi 24 Jul '17

24 Jul '17

Hello to everyone, On Debian Jessie (no SElinux) and "dovecot-sieve 1:2.2.13-12~deb8u1" I've changed the sieve (sieve_after) Junk and Trash path, from: "INBOX.Junk" to "INBOX/Junk" compiled it: sievec /etc/dovecot/sieve-after/spam-to-folder.sieve but now if i look into mail.err log, found this: Jul 24 07:22:01 server dovecot: lmtp(6823, info(a)hotelsangiorgioriccione.com) Error: p/3kL/mDdVmnGgAAS3B7vQ: sieve: msgid=<887291195.6699.1500873334921.JavaMail.trend@backend-prod-003>: failed to store into mailbox 'INBOX/Junk': Permission denied Jul 24 07:22:02 server dovecot: lmtp(6823, info(a)hotelsangiorgioriccione.com) Error: p/3kL/mDdVmnGgAAS3B7vQ: sieve: execution of script /etc/dovecot/sieve-after/spam-to-folder.sieve failed, but implicit keep was successful and many others.. This is the "spam-to-folder.sieve content": require ["fileinto","mailbox"]; if header :contains "X-Spam-Flag" "YES" { fileinto :create "INBOX/Junk"; stop; } where I'm wrong? many thanks!

1 0

dovecot/pigeonhole and sogo
by Thomas Robers 24 Jul '17

24 Jul '17

Hello, I have two systems one with dovecot 2.2.31/Pigeonhole 0.4.19 selfcompiled through the src.rpms from ghettoforge on a CentOS 6.9 server and a second system of SOGo (3.2.9, nightly) on CentOS 7. Everything worked together until I made the update to Dovecot 2.2.31 Pigeonhole 0.4.19. Since then I get an error message when I try to upload a sieve-script. SOGo shows a message popup that "the service is temporarily not available" and in the log file of Dovecot i get: > Jul 12 15:26:41 mail2 dovecot: managesieve-login: Disconnected (no auth attempts in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138, lip=192.168.1.135, TLS: Disconnected, session=<25U/xB5U/KLCw8GK> > Jul 12 15:26:41 mail2 dovecot: auth: Debug: auth client connected (pid=12182) > Jul 12 15:26:41 mail2 dovecot: managesieve-login: Disconnected (no auth attempts in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138, lip=192.168.1.135, TLS: Disconnected, session=<4zxBxB5U/qLCw8GK> > Jul 12 15:34:35 mail2 dovecot: auth: Debug: auth client connected (pid=12263) > Jul 12 15:34:35 mail2 dovecot: managesieve-login: Disconnected (no auth attempts in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138, lip=192.168.1.135, TLS: Disconnected, session=<uiR64B5UDKPCw8GK> > Jul 12 15:34:35 mail2 dovecot: auth: Debug: auth client connected (pid=12264) > Jul 12 15:34:35 mail2 dovecot: managesieve-login: Disconnected (no auth attempts in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138, lip=1192.168.1.135, TLS: Disconnected, session=<LeJ74B5UDqPCw8GK> Does this mean that managesieve-login doesn't get authentication data from SOGo? SOGo logs for this error: > S[0x7f368f2bab60]: "IMPLEMENTATION" "Dovecot Pigeonhole" > S[0x7f368f2bab60]: "SIEVE" "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" > S[0x7f368f2bab60]: "NOTIFY" "mailto" > S[0x7f368f2bab60]: "SASL" "PLAIN" > S[0x7f368f2bab60]: "VERSION" "1.0" > S[0x7f368f2bab60]: OK "Dovecot ready." > C: AUTHENTICATE "PLAIN" {%d+} > LOGIN:PASSWORD > > S[0x7f368f2bab60]: NO "Error in MANAGESIEVE command received by server." > C: AUTHENTICATE "PLAIN" {%d+} > LOGIN:PASSWORD Than I compiled Dovecot 2.2.31 together with Pigeonhole 0.4.18 and than everything works again as expected. I can upload and activate sieve-scripts from the SOGo webinterface. After that I tried to disable TLS for sieve with ssl = no in the 20-managesieve.conf: [...] protocol sieve { ssl = no [...] to capture the traffic between SOGo and Dovecot/Pigeonhole but then the managesieve-login process crashes: > Jul 12 16:28:32 mail2 dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 12941 killed with signal 11 (core dumps disabled) [last ip=192.168.1.138] Why isn't it possible to disable TLS for sieve and what changes between Pigeonhole 0.4.19 and 0.4.18 could be responsible for the disharmony between SOGo and Pigeonhole. I looked for 'changes' but could not find any hints regarding this problem. Is there a chance to get both work together again? And is it possible to disable TLS for sieve or why crashes the managesieve-login daemon? Any help would be welcome. TIA Thomas Robers

2 2

Modify stored mail contents?
by Evan Martin 23 Jul '17

23 Jul '17

Is there a safe way to modify the contents of emails stored by Dovecot? I'll probably only want to change the message bodies, not the headers, if that matters. Looking for ways to do this both for existing emails and new emails as they are received (though anything that works for existing emails can probably just be run again for new emails.) My mail storage is currently mdbox, but I could migrate to another format if that helps.

5 8

10-ssl ssl = no but dovecot still reads certs
by lists＠lazygranch.com 22 Jul '17

22 Jul '17

I'm bringing up a new email server starting without TLS initially. In 10-ssl.conf I set ssl = no, but the default ssl_cert and ssl_key lines are not commented out. I got the obvious error message: ------------------------------ doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file /etc/ssl/certs/dovecot.pem: No such file or directory /usr/local/etc/rc.d/dovecot: WARNING: failed to start dovecot -------------------------- No big deal, but I don't remember this being an issue the last time I set up a server. You would think if ssl=no, the ssl_cert and ssl_key files would not be opened.

3 2

Re: under some kind of attack
by Joseph Tam 22 Jul '17

22 Jul '17

mj <lists(a)merit.unu.edu> wrote: > - for external users, to ONLY be allowed to use an application specific > password. (or username and password, fine as well) > > Step one: making ldap password authentication valid only from our > internal network. I though: using allow_nets=192.168.1.0/24 for that passdb > > But I can't get that to work. :-( Unsure where exactly to define the > allow_nets, tried many variations on the theme already. > > Perhaps someone can help with the step one, and also tell me if the > approach outlined above is smart, valid and do-able in dovecot. As per my post: checkpassword. You can then use one password on Mondays, Wednesdays, and Fridays, alternate passwords on Tuesdays and Thursday fetched from a rot-13 database, and only from prime numbered IP addresses on weekends, if that's what you want. Gary Sellani <lists(a)lazygranch.com> writes: > Not applicable to most installations, but I use geographical filtering > on all ports other than 25. Fine if you are the only user of the email > system. If you're the only user, moving the IMAP/POP service to a nonstandard port will do most of that with much less bother, and you won't lock yourself out, requiring a ssh/edit firewall/reconnect. Been there, done that. > I get one hacker a week trying to guess passwords, and always from Digital Ocean VPS. abuse(a)digitalocean.com is fairly responsive. They usually nuke them pretty quickly. > I would like to see statistics on the success of such brute force > attacks. They can't be very successful these days. Even if the success rate is 0.00001%, you can do the arithmetic to see that's still a huge number of accounts. But you're right, if you have anything resembling a sensible password policy, they're just a log bloating nuisance. Joseph Tam <jtam.home(a)gmail.com>

2 1

FTS error Unknown user
by azurit＠pobox.sk 21 Jul '17

21 Jul '17

Hi, sorry for previous message, i accidentaly send it before it was complete. Recently, i was configuring a setup with one proxy, which is doing authentication and multiple backends, which doesn't have access to user database (see https://www.mail-archive.com/dovecot@dovecot.org/msg70123.html ). Now i wanted to use FTS (solr) on backends but i'm getting this error everytime a email is received (and FTS is not working, of course): dovecot: indexer-worker: Error: User [censored] lookup failed: Unknown user I don't fully understand why FTS needs to do any user lookup during indexing but, anyway, how can i workaround it? This is relevant config: passdb { driver = static args = password=[censored] allow_nets=[censored] } userdb { driver = static args = home=/var/mail/vhosts/%d/%n/home master_user=%u } plugin { fts = solr fts_solr = url=http://[censored]:8080/solr/ fts_autoindex = yes fts_autoindex_max_recent_msgs = 1000 } FTS is fully configured and working on proxy side (which is, currently, also a backend for most of the users - i will split it in stages, just wanted to say that i have FTS already working). azur

1 1

FTS
by azurit＠pobox.sk 21 Jul '17

21 Jul '17

Hi, recently, i was configuring a setup with one proxy, which is doing authentication and multiple backends, which doesn't have access to user database (see https://www.mail-archive.com/dovecot@dovecot.org/msg70123.html ). Now i wanted to use FTS (solr) on backends but i'm getting this error after every email is received:

1 0

Problem compiling dovecot 2.2.31 on Solaris
by Luciano Mannucci 21 Jul '17

21 Jul '17

I'm trying to compile under SunOS 5.8 Generic_117350-28 sun4u sparc SUNW,Ultra-5_10 (I know it's a bit oldish :-) and I get this error: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT pkcs5.lo -MD -MP -MF .deps/pkcs5.Tpo -c -o pkcs5.lo pkcs5.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT pkcs5.lo -MD -MP -MF .deps/pkcs5.Tpo -c pkcs5.c -fPIC -DPIC -o .libs/pkcs5.o pkcs5.c:9:20: error: stdint.h: No such file or directory make[4]: *** [pkcs5.lo] Error 1 What have I missed? I did: ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var\ --mandir=/usr/share/man --docdir=/usr/share/doc/packages/dovecot\ --disable-ipv6 --enable-header-install\ make Is it reasonable? Thanks in advance, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

4 6

under some kind of attack
by mj 21 Jul '17

21 Jul '17

Hi all, It seems we are under some kind of password guessing attack: > Jul 18 21:33:33 auth: Info: ldap(username1,103.6.223.61,<W7wLl5xUfABnBt89>): invalid credentials (given password: 1q2w3e4r5t) > Jul 18 21:34:16 auth: Info: ldap(username1,221.4.61.180,<89WnmZxUrADdBD20>): invalid credentials (given password: 1q2w3e4r5t) > Jul 18 21:36:13 auth: Info: ldap(username2,117.243.180.225,<ESWBoJxUdQB187Th>): invalid credentials (given password: 1q2w3e4r) > Jul 18 21:36:50 auth: Info: ldap(username2,58.59.103.230,<j7fQopxUNgA6O2fm>): invalid credentials (given password: 1q2w3e4r) > Jul 18 21:36:56 auth: Info: ldap(username4,58.215.13.154,<gtY5o5xUlQA61w2a>): invalid credentials (given password: 1q2w3e4r5t) > Jul 18 21:37:18 auth: Info: ldap(username3,220.175.154.205,<lFxppJxUFADcr5rN>): invalid credentials (given password: 1q2w3e4r) > Jul 18 21:37:25 auth: Info: ldap(username5,14.142.29.142,<40zopJxUSgAOjh2O>): invalid credentials (given password: 1q2w3e4r) > Jul 18 21:37:27 auth: Info: ldap(username4,119.1.98.121,<JDQOpZxUCwB3AWJ5>): invalid credentials (given password: 1q2w3e4r5t) > Jul 18 21:37:54 auth: Info: ldap(username3,218.76.156.11,<OMqtppxUMADaTJwL>): invalid credentials (given password: 1q2w3e4r) Different IPs, different usernames, but all (almost) the same password. Any idea what we can do about this?? Any advice you could give us would be very much appreciated. MJ

7 18

application specific passwords
by mj 21 Jul '17

21 Jul '17

Hi, Further to the other thread about password guessing activities against our dovecot, I would like to implement application specific passwords on our dovecot. Googling results in some documents, but they are all a bit older: > https://www.happyassassin.net/2014/08/26/adding-application-specific-passwo… > https://www.dgsiegel.net/news/2013_05_21-application_specific_passwords_for… > http://www.justinbuchanan.com/blog/category/RoundCube > http://www.justinbuchanan.com/blog/post/2012/12/02/Application-Specific-Pas… Those articles are interesting, but also rather old. (I realse that this does not neccesarily mean: irrelevant or bad) Is there anone here with some additional notes, ideas, tips, trics on setting up application specific passwords with dovecot with virtual users? We are using samba AD as an authentication backend. MJ

3 5

Re: under some kind of attack
by Joseph Tam 21 Jul '17

21 Jul '17

> I would like to create a fail2ban filer, that scans for these lines: > >> Jul 20 11:10:09 auth: Info: ldap(user1,60.166.35.162,<cDFXHbxUQgA8piOi>): invalid credentials (given password: password) >> Jul 20 11:10:19 auth: Info: ldap(user2,61.53.66.4,<V+nyHbxU+wA9NUIE>): invalid credentials (given password: password) > > (as you can see, I have enabled auth_verbose_passwords to do this, > making me very uncomfortable...) > > Anyway: since there are only a few password variations, I would like to > block anyone using those passwords. With all the constraints and processing, I'll offer yet another option: use the checkpassword password authentication scheme. This will bypass post-authentcation log-sniffing and allow you direct access to username, password and client IP (the last I'm not positive about) at authentication time. Now you'll have everything you need to do any wild and crazy auth processing, including database searches and triggering firewall blocking based on whatever crietria you want (including common password use). As to how to integrate it into your dovecot, I'm not sure whether it's best to supplant the LDAP method and authenticate within the checkpassword script, or to put it as the first authentication method (ahead of LDAP) to get first crack at inspect at authentication data, or the fallback authentication method (after LDAP) to pick up all the failures. However, after running honeypots, I can tell you that although BFD attackers will common use passwords, any static list of abused passwords will miss a lot. (A common one they use is $password=variations($user) or variation($domain)). Number of auth failure limits should also be a criteria for banning. Extinct users are also good candidates for instant banning. Joseph Tam <jtam.home(a)gmail.com>

2 1

2.2.devel (0bee280) crashdump virtual plugin
by Thomas Leuxner 20 Jul '17

20 Jul '17

#0 0x00007f497ecdb067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 10092 selftid = 10092 #1 0x00007f497ecdc448 in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0xfffe, sa_sigaction = 0xfffe}, sa_mask = {__val = {1024, 140722499998576, 94791001010256, 513, 139953641023651, 140722499998368, 94791001010256, 513, 11573297580199803136, 139953644744448, 139953641204307, 94791001010256, 140722499998464, 0, 139953641204665, 94791001010256}}, sa_flags = 2131669786, sa_restorer = 0x7ffc829fd301} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007f497f0f05b6 in default_fatal_finish (type=<optimized out>, status=status@entry=0) at failures.c:201 backtrace = 0x56363ff17088 "/usr/lib/dovecot/libdovecot.so.0(+0x9f5be) [0x7f497f0f05be] -> /usr/lib/dovecot/libdovecot.so.0(+0x9f6ac) [0x7f497f0f06ac] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f497f080fde] -> /usr/lib/d"... #3 0x00007f497f0f06ac in i_internal_fatal_handler (ctx=0x7ffc829fd350, format=<optimized out>, args=<optimized out>) at failures.c:670 status = 0 #4 0x00007f497f080fde in i_panic (format=format@entry=0x7f497f47af00 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0, timestamp_usecs = 0} args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffc829fd450, reg_save_area = 0x7ffc829fd390}} #5 0x00007f497f3cb6dc in mailbox_notify_changes_stop (box=<optimized out>) at mail-storage.c:1950 __FUNCTION__ = "mailbox_notify_changes_stop" #6 0x00007f497dc5aa6f in virtual_notify_changes (box=0x5636400cdbd8) at virtual-storage.c:696 bboxp_end = 0x563640015708 mbox = 0x5636400cdbd8 bboxp = 0x563640015180 #7 0x000056363f5e2652 in idle_finish (ctx=ctx@entry=0x56363ff64160, done_ok=<optimized out>, free_cmd=free_cmd@entry=true) at cmd-idle.c:46 client = 0x56363ff39e68 #8 0x000056363f5e2783 in idle_client_handle_input (ctx=ctx@entry=0x56363ff64160, free_cmd=free_cmd@entry=true) at cmd-idle.c:67 line = <optimized out> #9 0x000056363f5e284d in idle_client_input_more (ctx=0x56363ff64160) at cmd-idle.c:100 client = 0x56363ff39e68 #10 idle_client_input (ctx=0x56363ff64160) at cmd-idle.c:107 client = 0x56363ff39e68 #11 0x00007f497f105b22 in io_loop_call_io (io=0x56363ffae400) at ioloop.c:599 ioloop = 0x56363ff1f9b0 t_id = 2 __FUNCTION__ = "io_loop_call_io" #12 0x00007f497f10717a in io_loop_handler_run_internal (ioloop=ioloop@entry=0x56363ff1f9b0) at ioloop-epoll.c:223 ctx = 0x56363ff214d0 io = <optimized out> tv = {tv_sec = 3, tv_usec = 496715} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #13 0x00007f497f105bbc in io_loop_handler_run (ioloop=ioloop@entry=0x56363ff1f9b0) at ioloop.c:648 No locals. #14 0x00007f497f105d68 in io_loop_run (ioloop=0x56363ff1f9b0) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #15 0x00007f497f08b6d3 in master_service_run (service=0x56363ff1f850, callback=<optimized out>) at master-service.c:666 No locals. #16 0x000056363f5de1d3 in main (argc=1, argv=0x56363ff1f5e0) at main.c:491 set_roots = {0x56363f8096c0 <imap_setting_parser_info>, 0x7f497f8d5540 <lda_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x56363ff17048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x56363f5f92b0 <login_client_connected>, failure_callback = 0x56363f5f8bf0 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 auth_socket_path = 0x56363f602074 "auth-master" c = <optimized out>

2 13

SRS and vacation message
by Kacper Guzik 20 Jul '17

20 Jul '17

Hi i have similiar problem like here: http://www.iredmail.org/forum/topic11833-iredmail-support-vocation-respone-… email send : from : web123(a)gmail.com to : jacka(a)mail.com vocation sent back from : jacka(a)mail.com to : srs0=hmc8=v7=gmail.com=web123(a)mail.com postsrsd changing return-path from web123(a)gmail.com to srs0=hmc8=v7= gmail.com=web123(a)mail.com this is no problem for me but sieve: Vacation's messages are always addressed to the Return-Path address it is possible some how change this ugly to header to normal? dovecot --version 2.2.29.1 (e0b76e3) # 2.2.29.1 (e0b76e3): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) doveconf: Warning: service auth { client_limit=125000 } is lower than required under max. load (150000) # OS: Linux 3.10.0-514.16.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_master_user_separator = * auth_mechanisms = plain login auth_worker_max_count = 60 default_client_limit = 125000 default_process_limit = 25000 dict { quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log login_trusted_networks = xxx mail_fsync = never mail_gid = 2000 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_max_userip_connections = 128 mail_plugins = quota zlib expire mail_uid = 2000 maildir_broken_filename_sizes = yes 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master quota = dict:user::proxy::quotadict sieve = /home/sieve/%Ld/%Ln/dovecot.sieve sieve_after = /home/sieve/dovecot.sieve sieve_default = /home/sieve/dovecot.sieve sieve_dir = /home/sieve/%Ld/%Ln sieve_global_dir = /home/sieve sieve_global_path = /home/sieve/dovecot.sieve sieve_max_redirects = 25 zlib_save = gz zlib_save_level = 9 } protocols = pop3 imap sieve lmtp service auth { service_count = 0 unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0777 user = vmail } } service imap-login { process_min_avail = 16 service_count = 0 vsz_limit = 64 M } service imap { process_limit = 4096 } service lmtp { executable = lmtp -L inet_listener lmtp { port = 24 } user = vmail } service pop3-login { process_min_avail = 16 service_count = 0 } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = root mode = 0666 user = root } user = root } ssl_ca = </etc/ssl/ca-bundle.crt ssl_cert = </etc/ssl/xxx.crt ssl_key = # hidden, use -P to show it submission_host = xxx userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota imap_quota mail_log notify zlib } protocol pop3 { mail_plugins = quota zlib expire pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_fsync = optimized mail_plugins = quota sieve zlib postmaster_address = xxx } remote xxx { mail_max_userip_connections = 51200 }

1 0

Dovecot imap
by nlekkas＠gmail.com 20 Jul '17

20 Jul '17

Hello there to all ! Here is the doveconf - a as asked by Aki Tuomi.. Do you see anything wrong..? I would appreciate mush in anyone could help ... # OS: Linux 2.6.32-696.1.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) auth_mechanisms = plain login disable_plaintext_auth = no mail_location = maildir:~/Maildir mail_plugins = " quota" mbox_write_locks = fcntl passdb { driver = pam } plugin { quota = fs:User quota quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap pop3 userdb { driver = passwd } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

2 1

Re: under some kind of attack
by Joseph Tam 20 Jul '17

20 Jul '17

mj <lists(a)merit.unu.edu> writes: >>> However, it seems almost all IPs are different, and I don't think I can >>> keep the above settings permanently. >> >> Why not? Limited by firewall rules overload? You could probably use >> a persistent DB, can't you? > > I meant: keep the "block after the first failed attempt" setting. People > need the chance to change their password, so I have increased it to two. A timeout feature is handy here; even though you allow attackers several kicks at the can, it will allow your users to eventually gain control to their accounts again after a suitable penalty period. >> You can also use a third party RBL that specialized in brute forcers like >> blocklist.de. You can also feed back fail2ban data and crowdsource BFD >> data to them. > > Yes, I will look into that now. > ... > > Anyone aware of other blocklists that are worth bocking? Because the > list.blocklist.de/lists/all.txt blocks some, but not anywhere near all. There are other RBLs that overlap with this (like CBL), but they include entries will produce false positives. There was OpenBL but that is defunct. The different lists at blocklist.de have varying efficacy: the ssh and smtp BFD detection are fairly good (they have a 90+% hit rate at my site), but the IMAP/POP BFD detection not as good (maybe 20%). However, if people start feeding IMAP/POP fail2ban data back to blocklist.de, that will get better. > I now know how to block large lists of ips, so if anyone has additional > lists to block? Yeah, all of ChinaNet. May produce false positives. Joseph Tam <jtam.home(a)gmail.com>

1 0