- dovecot - dovecot.org

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

Panic: file-lock.c
by Ricardo Branco 19 Dec '17

19 Dec '17

Today we had an unclean shutdown of our NFS filler and have had lots of issues with mailboxes being re-synced, mostly all the issues are now resolved but we are seeing the following appear for one user on our system. Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Panic: file file-lock.c: line 287: unreached Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x9ceda) [0x7f2b45209eda] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x9cf46) [0x7f2b45209f46] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f2b4519cc5f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xa150a) [0x7f2b4520e50a] -> /usr/local/lib/dovecot/libdovecot.so.0(file_wait_lock_error+0x39) [0x7f2b4520e789] -> /usr/local/lib/dovecot/libdovecot.so.0(file_try_lock_error+0x13) [0x7f2b4520e873] -> /usr/local/lib/dovecot/libdovecot.so.0(file_create_locked+0x29e) [0x7f2b4520b7de] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_lock_file_create+0x125) [0x7f2b454dc345] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xba1fd) [0x7f2b4554f1fd] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mailbox_vsize_update_appends+0x63) [0x7f2b4554f363] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mailbox_sync_deinit+0x197) [0x7f2b4555c327] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0xebd1) [0x7f2b4416bbd1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_deinit+0x30) [0x7f2b454de750] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3b) [0x7f2b454e0b4b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) [0x7f2b45558402] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0xfbf4) [0x7f2b4416cbf4] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xe564) [0x7f2b445aa564] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x8c) [0x7f2b454e05cc] -> dovecot/imap(imap_status_get+0x7a) [0x42222a] -> dovecot/imap(cmd_status+0x15d) [0x41514d] -> dovecot/imap(command_exec+0x5d) [0x41a7fd] -> dovecot/imap() [0x417fb0] -> dovecot/imap() [0x418046] -> dovecot/imap(client_handle_input+0x165) [0x418385] -> dovecot/imap(client_input+0x6f) [0x41882f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x61) [0x7f2b4521db71] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbf) [0x7f2b4521f75f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f2b4521dc2c] Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Fatal: master: service(imap): child 30620 killed with signal 6 (core dumps disabled)

1 0

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

19 Dec '17

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will happen a little later. 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: http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.0.… http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.0.… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 3

nfs_flush_chown_uid errors over NFS
by Johan Hendriks 18 Dec '17

18 Dec '17

Hello all, We use an older version of dovecot 2.0.19 on Ubuntu 12.04 using an NFS share, also a linux box. Now we want to migrate the storage to a FreeBSD server and later on the mailservers them self. In the firsts test all looks fine, but we do see some errors some times. Error: nfs_flush_chown_uid: chown(/var/mail/virtual/domain.com/user/Maildir) failed: Invalid argument This does not happen all the time but sometimes it shows up. I can read all the mail using an mailclient and the uid shows the user vmail:vmail. Is this cosmetic or is there something wrong? Thanks for your time Regards johan

1 0

Sieve with LDA
by Doug Hardie 18 Dec '17

18 Dec '17

I found an email that sieve stored in Deleted Messages incorrectly. The log messages show sieve doing that, but don't give me any indication of which sieve rule caused the problem. I went through it manually, but didn't see anything that matched. I seem to recall that there was a way to use sieve-test to show the rules and how they were applied, but I can't seem to get it to do that now. -- Doug

3 4

ot: 2.2 ghettoforge install systemctl Q
by voytek＠sbt.net.au 16 Dec '17

16 Dec '17

I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used /etc/dovecot from current Centos 6 Dovecot 2.1 I can start/stop Dovecot with dovecot / doveadm stop BUT when I tried 'systemctl' I get # systemctl status dovecot ● dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:dovecot(1) http://wiki2.dovecot.org/ how do I fix this, or, do I need to fix it ? or maybe I need to pursue this on ghettoforge list

3 3

2.1 to 2.2 server migration Qs: sanity check, config ?
by voytek＠sbt.net.au 16 Dec '17

16 Dec '17

I have an old Centos 6 running dovecot 2.1.17 with Postfix 2.1x, mysql virtual domains, in the process of setting a new Centos 7 to migrate, copied /etc/dovecot, made some minor edits to get rid of errors, added Letsencrypt in place of self certified certs, it seems to work, using mail client I can log on StartSSL/110/143, TLS/995/993 with no visible errors when login on is there any other sanity checks I should do ? before I start putting users on it ? attaching dovecot.conf at the end, appreciate any suggestion or correction I see a lot of these warning, are they benign? #grep Warning /var/log/dovecot.log | wc 74 1102 6900 # wc /var/log/dovecot.log 174 2299 19716 /var/log/dovecot.log Dec 16 00:57:12 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Dec 16 00:57:52 auth: Warning: auth client 0 disconnected with 1 pending requests: EOF Dec 16 00:57:59 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer ( as I've re used an old host name, I can see some users already trying to connect, they must've never removed this server name when it was shut down, perhaps they're generating these errors, repeatedly logging on ?) # doveadm who username # proto (pids) (ips) five(a)aaa.com.au 1 imap (9047) (35.196.255.170) seven(a)aaa.com.au 1 imap (9056) (104.196.21.108) eight(a)aaa.com.au 1 imap (9062) (35.196.255.170) five(a)aa.com.au 2 imap (9240 9044) (203.194.43.48 35.196.255.170) six(a)aa.com.au 2 imap (9248 9063) (203.194.43.48 35.185.44.87) postbox(a)aa.com.au 1 imap (9057) (104.196.178.232) eight(a)aa.com.au 2 imap (9244 9050) (203.194.43.48 35.196.255.170) seven(a)aa.com.au 2 imap (9055 9242) (104.196.21.108 203.194.43.48) six(a)aaa.com.au 1 imap (9054) (35.185.44.87) doveconf -n -c /etc/dovecot/test/dovecot.conf > /etc/dovecot/test/dovecot.conf.new # cat dovecot.conf.new # 2.2.33.2 (d6601f4ec): /etc/dovecot/test/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 3.10.0-693.11.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 last_valid_uid = 2000 listen = * log_path = /var/log/dovecot.log mail_gid = 2000 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = quota mail_uid = 2000 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 = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users-password driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /var/vmail/sieve sieve_global_path = /var/vmail/sieve/dovecot.sieve } protocols = pop3 imap sieve service auth { unix_listener /var/spool/postfix/dovecot-auth { group = postfix mode = 0666 user = postfix } 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 = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service pop3-login { service_count = 1 } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/..fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/sieve.log mail_plugins = quota sieve autocreate postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 60 mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } #

2 3

Dovecot path separator clarification
by Davide Marchi 15 Dec '17

15 Dec '17

Hi Friends, On Debian Jessie and Dovecot 1:2.2.x using the default separator "/" (simply leave commented 10-mail.conf -> "#separator =") I've create for a vuser (from client) a subfolder Scuola/prova on server side, Dovecot create: ../Maildir/.Scuola.prova Here my question: why not ../Maildir/Scuola/prova ? Where I'm wrong? Many thanks! Davide

2 1

Re: sieve filter move wrong email to Junk folder
by Richard 15 Dec '17

15 Dec '17

> Date: Thursday, December 14, 2017 09:47:44 -0800 > From: Gao <gao(a)pztop.com> > > I use a sieve filter to move spam email to user's Junk folder: ># cat spam_to_junk.sieve > require "fileinto"; > if exists "X-Spam-Status" { > if header :contains "X-Spam-Status" "YES" { > fileinto "Junk"; > stop; > } else { > } > } > if header :contains "subject" ["SPAM?"] { > fileinto "Junk"; > stop; > } > > Most time this filter works fine but occasionally it move non-spam > in to Junk folder. Here is an example, this email is from dovecot > mailling list and it end up in my Junk folder. Mailllog and header > here. Would someone help me to figure out what went wrong here? > > Thanks. > > Gao > > X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 Because of the way you are bounding it, I suspect that the "YES" in BAYES_00, at the end of that line, is triggering the mis-filing. Why not make: contains "X-Spam-Status" "YES" a single string: contains "X-Spam-Status: YES" that would be more precise and avoid this issue.

5 7

Re: Recommended tool for migrating IMAP servers
by Davide Marchi 15 Dec '17

15 Dec '17

Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. Usually using imapc connector to connect to legacy > platform. > > Wqmi Many thanks Wqmi! Well, I've read the dsync documentation, but this warning has me a little worried: "Make sure destination is exactly as source, deleting/reverting any changes in destination if necessary" So I followed the Imapsync way, and all works fine. I seem to have understood thatImapsync works as a traditional client,for this reason also much easier to use and with less mistakes risk. And anyway a software done very well ;-) x9p wrote:> I do not believe imapsync has license issues. Its written in perl and its > hosted on github. You can pay for support if you want. and disable > stats > uploaded to their servers, via command line. Well, clear, many thanks x9p! Many thanks to all! Davide -- cosmogoniA cosmogoniA<https://www.cosmogonia.org/> n o p r o v a r e n o f a r e o n o n f a r e n o n c e p r o v a r e

2 2

Re: Mail-crypt plugin clarification
by Joseph Tam 15 Dec '17

15 Dec '17

Aki Tuomi writes: > Dovecot does support making it difficult to prevent access to the stored > mail. Those who have had problems understanding the documentation might find this unintended double-negative ironically funny. > You can, with suitable workflows, ensure that the user's emails are not > readable by anyone but the user. Of course the only way to be fully > sure is to use end-to-end encryption, ... "Ensure" (or OP: "impossible") are very high standards of privacy. If the OP really means it, then since a third party has control over the (virtual or real) hardware, the server should never have access to private keys or decrypted data. (We're in agreement I think.) If the OP lowers their standards to "inconvenient" to gain access, then the plugin is enough. It will keep the honest admin honest. > ... like PGP or S/MIME, but this does go a long way to prevent admin access > to user's email. Don't ignore metadata; who/when/where (and headers?) could reveal much information. Joseph Tam <jtam.home(a)gmail.com>

2 1

sieve filter move wrong email to Junk folder
by Gao 15 Dec '17

15 Dec '17

I use a sieve filter to move spam email to user's Junk folder: # cat spam_to_junk.sieve require "fileinto"; if exists "X-Spam-Status" { if header :contains "X-Spam-Status" "YES" { fileinto "Junk"; stop; } else { } } if header :contains "subject" ["SPAM?"] { fileinto "Junk"; stop; } Most time this filter works fine but occasionally it move non-spam in to Junk folder. Here is an example, this email is from dovecot mailling list and it end up in my Junk folder. Mailllog and header here. Would someone help me to figure out what went wrong here? Thanks. Gao =======Header========= Dovecot Mailing List <dovecot(a)dovecot.org> References: <c2562504-d5ae-cf3b-3e71-35ef0df15b79(a)rename-it.nl> <e804da79-6bdc-fb21-8ed4-7c1385ea8936(a)gmx.com> From: sender name <sender(a)rename-it.nl> Message-ID: <9100b497-7f3e-8129-9f8f-c675296e2bd7(a)rename-it.nl> Date: Thu, 14 Dec 2017 11:54:19 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <e804da79-6bdc-fb21-8ed4-7c1385ea8936(a)gmx.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-SA-Exim-Connect-IP: 217.119.239.130 X-SA-Exim-Mail-From: sender(a)rename-it.nl X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sogo.guto.nl X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2, No Subject: Re: New Dovecot service: SMTP Submission (RFC6409) X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on sogo.guto.nl) X-BeenThere: dovecot(a)dovecot.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Dovecot Mailing List <dovecot.dovecot.org> List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe> List-Archive: <https://dovecot.org/pipermail/dovecot/> List-Post: <mailto:dovecot@dovecot.org> List-Help: <mailto:dovecot-request@dovecot.org?subject=help> List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe> Errors-To: dovecot-bounces(a)dovecot.org Sender: "dovecot" <dovecot-bounces(a)dovecot.org> X-mydomain-MailScanner-Information: Please contact the administrator for more information X-mydomain-MailScanner-ID: D6773400AB09.ADBA7 X-mydomain-MailScanner: Found to be clean X-mydomain-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.598, required 5, autolearn=not spam, BAYES_00 -1.90, DCC_CHECK 1.10, HEADER_FROM_DIFFERENT_DOMAINS 0.00, KAM_LAZY_DOMAIN_SECURITY 1.00, KAM_SHORT 0.00, RCVD_IN_DNSWL_MED -2.30, RCVD_IN_HOSTKARMA_W -2.50) X-mydomain-MailScanner-From: dovecot-bounces(a)dovecot.org =====End of header======= =======Maillog========= Dec 14 02:54:51 mail postfix/postscreen[19236]: CONNECT from [94.237.32.243]:40818 to [10.11.22.68]:25 Dec 14 02:54:52 mail postfix/postscreen[19236]: PASS OLD [94.237.32.243]:40818 Dec 14 02:54:52 mail postfix/smtpd[19244]: connect from wursti.dovecot.fi[94.237.32.243] Dec 14 02:54:52 mail policyd-spf[19248]: None; identity=helo; client-ip=94.237.32.243; helo=mail.dovecot.fi; envelope-from=dovecot-bounces(a)dovecot.org; receiver=gao(a)pztop.com Dec 14 02:54:52 mail policyd-spf[19248]: None; identity=mailfrom; client-ip=94.237.32.243; helo=mail.dovecot.fi; envelope-from=dovecot-bounces(a)dovecot.org; receiver=gao(a)pztop.com Dec 14 02:54:52 mail postfix/smtpd[19244]: D6773400AB09: client=wursti.dovecot.fi[94.237.32.243] Dec 14 02:54:53 mail postfix/cleanup[19249]: D6773400AB09: hold: header Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243])??by mail.mydomain.com (Postfix) with ESMTP id D6773400AB09??for <gao(a)pztop.com>; Thu, 14 Dec 2017 02:54:52 -0800 (PST) from wursti.dovecot.fi[94.237.32.243]; from=<dovecot-bounces(a)dovecot.org> to=<gao(a)pztop.com> proto=ESMTP helo=<mail.dovecot.fi> Dec 14 02:54:53 mail postfix/cleanup[19249]: D6773400AB09: message-id=<9100b497-7f3e-8129-9f8f-c675296e2bd7(a)rename-it.nl> Dec 14 02:54:53 mail opendkim[1706]: D6773400AB09: wursti.dovecot.fi [94.237.32.243] not internal Dec 14 02:54:53 mail opendkim[1706]: D6773400AB09: not authenticated Dec 14 02:54:53 mail opendkim[1706]: D6773400AB09: no signature data Dec 14 02:54:53 mail postfix/smtpd[19244]: disconnect from wursti.dovecot.fi[94.237.32.243] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Dec 14 02:54:53 mail MailScanner[18700]: New Batch: Scanning 1 messages, 7572 bytes Dec 14 02:54:53 mail MailScanner[18700]: Virus and Content Scanning: Starting Dec 14 02:54:53 mail MailScanner[18700]: Spam Checks: Starting Dec 14 02:54:53 mail MailScanner[18700]: MailWatch: Blacklist refresh time reached Dec 14 02:54:53 mail MailScanner[18700]: MailWatch: Starting up MailWatch SQL Blacklist Dec 14 02:54:53 mail MailScanner[18700]: MailWatch: Read 0 blacklist entries Dec 14 02:54:56 mail MailScanner[18700]: Requeue: D6773400AB09.ADBA7 to 24EDE400AABD Dec 14 02:54:56 mail MailScanner[18700]: Uninfected: Delivered 1 messages Dec 14 02:54:56 mail postfix/qmgr[1756]: 24EDE400AABD: from=<dovecot-bounces(a)dovecot.org>, size=6784, nrcpt=1 (queue active) Dec 14 02:54:56 mail MailScanner[18700]: Deleted 1 messages from processing-database Dec 14 02:54:56 mail MailScanner[18700]: MailWatch: Logging message D6773400AB09.ADBA7 to SQL Dec 14 02:54:56 mail MailScanner[18962]: MailWatch: D6773400AB09.ADBA7: Logged to MailWatch SQL Dec 14 02:54:56 mail dovecot: lmtp(19259): Connect from local Dec 14 02:54:56 mail dovecot: lmtp(gao(a)pztop.com): AHqjGYBYMlo7SwAAlqGq+A: sieve: msgid=<9100b497-7f3e-8129-9f8f-c675296e2bd7(a)rename-it.nl>: stored mail into mailbox 'Junk' Dec 14 02:54:56 mail dovecot: lmtp(19259): Disconnect from local: Successful quit Dec 14 02:54:56 mail postfix/lmtp[19258]: 24EDE400AABD: to=<gao(a)pztop.com>, relay=mail.mydomain.com[private/dovecot-lmtp], delay=3.9, delays=3.8/0.01/0.01/0.06, dsn=2.0.0, status=sent (250 2.0.0 <gao(a)pztop.com> AHqjGYBYMlo7SwAAlqGq+A Saved) Dec 14 02:54:56 mail postfix/qmgr[1756]: 24EDE400AABD: removed Dec 14 02:54:56 mail dovecot: indexer-worker(gao(a)pztop.com): Indexed 1 messages in Junk (UIDs 11..11) ======End of Maillog======

3 2

doveadm log reopen not works with 2.2.33
by Alessio Cecchi 14 Dec '17

14 Dec '17

Hi, after the upgrade from dovecot 2.2.32 to 2.2.33 we notice that the /var/log/director/director.log was empty and the log are write in the logrotate file es. /var/log/director/director.log-20171201. Log path is dovecot is: log_path = /var/log/director/director.log Logrotate configuration is: /var/log/director/director.log { daily rotate 31 missingok notifempty compress delaycompress sharedscripts postrotate doveadm -i director log reopen endscript } and worked fine until the last dovecot upgrade. Now the only way to "reopen" the log file is doveadm reload. Is this a know bug? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output))
by Ralf Hildebrandt 14 Dec '17

14 Dec '17

Running Dovecot from the daily builds: 2:2.3.0~alpha0-1~auto+1287 in an proxy setup: auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = <redacted>.charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no listen = *,:: mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_plugins = mail_log notify mail_uid = imapproxy passdb { args = host=<redacted>.charite.de port=993 ssl=imaps ssl_ca_file=/etc/ssl/certs/ca-certificates.crt default_fields = userdb_imapc_user=%u userdb_imapc_password=%w userdb_imapc_host=<redacted>.charite.de userdb_imapc_ssl=imaps userdb_imapc_port=993 driver = imap } postmaster_address = postmaster(a)charite.de protocols = imap service auth { inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/dovecot/dovecot.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_client_ca_file = /etc/ssl/certs/ca-certificates.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = prefetch } verbose_proctitle = yes Error in my log: Dec 14 14:35:28 mproxy dovecot: imap(voxxxxea)<79275><dnC4tUxgZs3BrwIS>: Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output)) Dec 14 14:35:28 mproxy dovecot: imap(voxxxxea)<79305><taooukxgd83BrwIS>: Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output)) Dec 14 14:35:28 mproxy dovecot: imap(voxxxxea)<79275><dnC4tUxgZs3BrwIS>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xc3cd5) [0x7fe40d9cccd5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc3dbc) [0x7fe40d9ccdbc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe40d942f8e] -> dovecot/imap [voxxxxea 193.175.2.18](client_handle_input+0x2a8) [0x564f326e0e18] -> dovecot/imap [voxxxxea 193.175.2.18](client_continue_pending_input+0x80) [0x564f326e0f20] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fe40d9e48f9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7fe40d9e612a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7fe40d9e4a02] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fe40d9e4c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe40d965b63] -> dovecot/imap [voxxxxea 193.175.2.18](main+0x333) [0x564f326d3113] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fe40d5623f1] -> dovecot/imap [voxxxxea 193.175.2.18](+0xe2f1) [0x564f326d32f1] Dec 14 14:35:28 mproxy dovecot: imap(voxxxxea)<79305><taooukxgd83BrwIS>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xc3cd5) [0x7faa962d8cd5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc3dbc) [0x7faa962d8dbc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7faa9624ef8e] -> dovecot/imap [voxxxxea 193.175.2.18](client_handle_input+0x2a8) [0x5615124cde18] -> dovecot/imap [voxxxxea 193.175.2.18](client_continue_pending_input+0x80) [0x5615124cdf20] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7faa962f08f9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7faa962f212a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7faa962f0a02] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7faa962f0c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7faa96271b63] -> dovecot/imap [voxxxxea 193.175.2.18](main+0x333) [0x5615124c0113] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7faa95e6e3f1] -> dovecot/imap [voxxxxea 193.175.2.18](+0xe2f1) [0x5615124c02f1] -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | https://www.charite.de

1 0

dovecot (+sendmail) fails to get email into thunderbird
by jo land 14 Dec '17

14 Dec '17

I ain't able to get emails into my email application (thunderbird). I use 143 Imap to connect which i have tested with telnet and was able to login. But if i select the inbox with telnet it returns "0 EXISTS" like so: telnet 192.168.1.13 143 Trying 192.168.1.13... Connected to sub.domain.net. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. oper1 login update.site1 1234 oper1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE] Logged in oper2 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1513093097] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [NOMODSEQ] No permanent modsequences oper2 OK [READ-WRITE] Select completed. My dovecot -n gist.pastebin <https://gist.github.com/anonymous/db5c7d81e18cff8180f6484c8dcb2a54> https://gist.github.com/anonymous/db5c7d81e18cff8180f6484c8dcb2a54 Mail location set to: /var/mail/

2 2

dovecot crashing
by cheese＠nosuchhost.net 14 Dec '17

14 Dec '17

i have a system with panics/crashes and seem to be able to trigger the problem. dovecot version: 2.2.33.2 (from ius rpm-package-repository) maillog: Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 || block_idx+1 == block_count) Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7fa6768ef3de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7fa6768ef4be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa67688077c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xb50f7) [0x7fa676c370f7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_get_binary_stream+0x3c9) [0x7fa676c37569] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_get_binary_size+0x5b) [0x7fa676bbfa2b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(imap_msgpart_size+0x80) [0x7fa676c7a340] -> dovecot/imap(+0x207a9) [0x55b9589327a9] -> dovecot/imap(+0x1e63a) [0x55b95893063a] -> dovecot/imap(imap_fetch_more+0x35) [0x55b958931b45] -> dovecot/imap(cmd_fetch+0x34d) [0x55b95892336d] -> dovecot/imap(command_exec+0x5c) [0x55b95892ef0c] -> dovecot/imap(+0x1b48f) [0x55b95892d48f] -> dovecot/imap(+0x1b521) [0x55b95892d521] -> dovecot/imap(client_handle_input+0x195) [0x55b9589 2d8e5] -> dovecot/imap(client_input+0x85) [0x55b95892de05] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7fa676904cd2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fa6769063bf] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7fa676904d6c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa676904f28] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa67688afa3] -> dovecot/imap(main+0x333) [0x55b9589202e3] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa6764aec05] -> dovecot/imap(+0xe476) [0x55b958920476] Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Fatal: master: service(imap): child 5766 killed with signal 6 (core dumped) gdb backtrace is attached as file more infos/core-dump-file available if needed. yours josef

1 0

Re: Mail-crypt plugin clarification
by Joseph Tam 14 Dec '17

14 Dec '17

rje writes: > I'm looking into ways to encrypt the stored email on my server. The idea is > to make it impossible for my hosting provider (who has access to my VPS) to > read the mail from the disk. Just to be clear, if at any point your VPS has access to the plaintext mail (or keys that decrypt mail), then the VPS provider could access your decrypted mail. To make it unfeasible for your VPS to read your mail, it has to arrive at your VPS pre-encrypted. I can envision a system where you import encrypted mail into your mail store, then use client IMAP access to be decrypted locally by your mail reader. However, metadata is still accessible by your VPS provider. If your VPS is the MTA that directly handles SMTP from your correspondees sending you unencrypted messages, you can't lock out a sufficiently skilled platform admin. Joseph Tam <jtam.home(a)gmail.com>

2 1

Error: stat no such file or directory with 2.2.33.2
by María Arrea 14 Dec '17

14 Dec '17

We have upgraded today from Dovecot 2.2.31 to Dovecot 2.2.33.2 and modified our config to include ITERINDEX in mail_location and we are detecting some errors like this: /Dec 13 08:17:31 buzon_rhel7 dovecot: imap(rboloix): Error: stat(/buzones/location/18/48/rboloix/mailboxes/SIT - Pra&AwE-cticas 2014/dbox-Mails) failed: No such file or directory// //Dec 13 08:40:24 buzon_rhel7 dovecot: imap(espi): Error: stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) failed: No such file or directory// //Dec 13 08:40:25 buzon_rhel7 dovecot: imap(espi: Error: stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) failed: No such file or directory// //Dec 13 08:41:59 buzon_rhel7 dovecot: imap(espi): Error: stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) failed: No such file or directory/ I have grepped logs of past 4 weeks and have not found this errors with Dovecot 2.2.31. Any idea of what is going on? Full doveconf -n output below: /# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 3.10.0-693.11.1.el7.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.4 (Maipo) xfs auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_mechanisms = plain login auth_worker_max_count = 5500 base_dir = /var/run/dovecot/ default_client_limit = 5000 default_process_limit = 6500 disable_plaintext_auth = no imap_capability = +XLIST imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_fsync = never mail_gid = entrega mail_home = /buzones/location/%2.26Hn/%2.200Hn/%n/home_usuario/ mail_location = mdbox:/buzones////location//%2.26Hn/%2.200Hn/%n:ITERINDEX:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo////location//%2.26Hn/%2.200Hn/%n mail_max_userip_connections = 15000 mail_plugins = " zlib acl quota virtual mail_log notify" mail_uid = entrega 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 mdbox_purge_preserve_alt = yes mdbox_rotate_interval = 1 days mdbox_rotate_size = 60 M namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox SPAM { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } namespace { list = yes location = mdbox:/buzones////location//%%2.26Hn/%%2.200Hn/%%n:ALT=/buzones/alternativo////location//%%2.26Hn/%%2.200Hn/%%n:INDEX=/indices_dovecot/indices/%%2.26Hn/%%2.200Hn/%%n:INDEXPVT=~/mdbox/carpeta_compartida/%%u prefix = carpeta_compartida/%%u/ separator = / subscriptions = no type = shared } namespace { list = yes location = virtual:/etc/dovecot/virtual:INDEX=~/mdbox/virtual:CONTROL=~/mdbox/virtual prefix = Carpetas_virtuales/ separator = / } passdb { args = /etc/dovecot/deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile acl_shared_dict = file:/buzones////location//acls_compartidas.db lda_mailbox_autosubscribe = yes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size subject from quota = dict:Cuota de usuario::file:/buzones/cuotas/%n quota_rule2 = Trash:storage=+10%% quota_warning = storage=90%% aviso_cuota 90 %u sieve = /buzones////location//%2.26Hn/%2.200Hn/%n/home_usuario/dovecot.sieve sieve_dir = /buzones////location//%2.26Hn/%2.200Hn/%n/home_usuario/sieve/ zlib_save = gz zlib_save_level = 9 } pop3_no_flag_updates = yes protocols = pop3 imap sieve service anvil { client_limit = 25000 } service auth { client_limit = 32000 unix_listener auth-master { user = entrega } unix_listener auth-userdb { user = entrega } user = root } service aviso_cuota { executable = script /usr/local/bin/quota-warning.sh unix_listener aviso_cuota { mode = 0666 } user = entrega } service config { process_min_avail = 4 } service imap-login { executable = /usr/libexec/dovecot/imap-login group = dovenull process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service imap { executable = /usr/libexec/dovecot/imap process_limit = 8000 process_min_avail = 12 vsz_limit = 1 G } service managesieve-login { executable = /usr/libexec/dovecot/managesieve-login inet_listener sieve { port = 2000 } process_limit = 2000 vsz_limit = 1 G } service managesieve { executable = /usr/libexec/dovecot/managesieve process_limit = 5000 } service pop3-login { executable = /usr/libexec/dovecot/pop3-login process_limit = 5000 process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service pop3 { executable = /usr/libexec/dovecot/pop3 process_limit = 5000 } ssl_ca = </etc/pki/SCS2016/cadena_Terena.crt ssl_cert = </etc/pki/SCS2016/buzonus_us_es.crt ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } protocol lda { hostname = location info_log_path = log_path = mail_fsync = optimized mail_plugins = sieve zlib quota virtual acl postmaster_address = me(a)xxxxx.com syslog_facility = mail } protocol imap { mail_plugins = zlib quota imap_quota virtual acl imap_acl notify mail_log } protocol pop3 { mail_plugins = zlib quota virtual pop3_enable_last = yes pop3_uidl_format = %g }/

2 2

TLS Error and not working lmtp
by Jakob Schürz 13 Dec '17

13 Dec '17

Hi! I have some troubles with the virtual plugin. I run a self-compiled dovecot 2.2.33.2 from debian testing. I patched this version with the QRESYNC-Patch from a few weeks ago. But i always get an errormessage, when i try to open an email from a virtual mailbox. So i cloned the actual git-Repo and compiled dovecot and pigonehole-sieve. The problem with the virtual plugin seems gone away. But there are some other problems. I use ssl=required and with dovecot from debian TLS/SSL and STARTTLS works fine. With the selfcompiled from git, i get this error: dovecot[1284]: imap-login: Error: Failed to initialize SSL server context: Couldn't parse DH parameters: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: DH PARAMETERS: user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<D6bC4Rlg8ut/AAAB> The key and crt are exactly the same files as before. The second problem is, lmtp is not working. I use exactly the same config for the debians dovecot and dovecot from git. But in the gitversion the error in exim is: Failed to connect to socket /var/run/dovecot/lmtp for dovecot_lmtp transport: Connection refused My config is: # dovecot -n # 2.3.devel (b1aac3a1d): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (624e1769) # OS: Linux 4.13.0-trunk-amd64 x86_64 Debian 9.3 btrfs auth_debug = yes auth_mechanisms = plain login cram-md5 digest-md5 auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes first_valid_uid = 1000 imap_capability = +XDOVECOT imap_client_workarounds = tb-extra-mailbox-sep lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = *, ::1 login_trusted_networks = 127.0.0.1/8 192.168.0.0/24 192.168.1.0/24 172.17.0.0/24 172.18.0.0/24 mail_debug = yes mail_gid = vmail mail_home = /var/mail/%u mail_location = maildir:/var/mail/%u/Maildir:LAYOUT=fs:INDEX=/var/lib/dovecot/db/indexes/Maildir/%u:INDEXPVT=/var/lib/dovecot/db/indexes/Maildir/%u:CONTROL=/var/lib/dovecot/db/control/Maildir/%u mail_plugins = zlib quota acl listescape mail_log notify virtual mail_privileged_group = vmail mail_server_admin = mailto:jakob@xundeenergie.at mail_shared_explicit_inbox = yes mail_uid = vmail 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 mmap_disable = yes namespace { hidden = no inbox = no list = children location = maildir:/var/mail/mailarchiv/%u/:LAYOUT=fs:INDEX=/var/lib/dovecot/db/indexes/mailarchiv/%u:INDEXPVT=/var/lib/dovecot/db/indexes/mailarchiv/%u mailbox incoming { auto = create } mailbox outgoing { auto = create } prefix = Mailarchiv/ separator = / subscriptions = no type = private } namespace { list = children location = maildir:/var/mail/public/:LAYOUT=fs:INDEX=/var/lib/dovecot/db/indexes/public/%u:INDEXPVT=/var/lib/dovecot/db/indexes/public/%u prefix = Roseggergasse/ separator = / subscriptions = no type = public } namespace Geteilt { hidden = no inbox = no list = children location = maildir:/var/mail/%%u/Maildir:LAYOUT=fs:INDEXPVT=/var/lib/dovecot/db/indexes/shared/%u/%%u:INDEX=/var/lib/dovecot/db/indexes/shared/%u/%%u prefix = Geteilt/%%n/ separator = / subscriptions = no type = shared } namespace Real { hidden = yes list = no location = virtual:/var/mail/real:INDEX=/var/lib/dovecot/db/indexes/real/%u prefix = Real/ separator = / subscriptions = no } namespace Synoptic { hidden = no list = children location = virtual:/var/mail/virtual:INDEX=/var/lib/dovecot/db/indexes/virtual/%u mailbox INBOX/Archives { auto = no special_use = \Archive } mailbox INBOX/Drafts { auto = no special_use = \Drafts } mailbox INBOX/Entwürfe { auto = no special_use = \Drafts } mailbox INBOX/Junk { auto = no special_use = \Junk } mailbox INBOX/Sent { auto = no special_use = \Sent } mailbox INBOX/Spam { auto = no special_use = \Junk } prefix = Synoptic/ separator = / subscriptions = no } namespace inbox { hidden = no inbox = yes location = mailbox Archiv { auto = no special_use = \Archive } mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Entwürfe { auto = no special_use = \Drafts } mailbox "Gelöschte Elemente" { auto = no special_use = \Trash } mailbox "Gelöschte Objekte" { auto = no special_use = \Trash } mailbox Gesendet { auto = no special_use = \Sent } mailbox "Gesendete Elemente" { auto = no special_use = \Sent } mailbox "Gesendete Objekte" { auto = no special_use = \Sent } mailbox Important { auto = no } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Mistkübel { auto = no special_use = \Trash } mailbox Papierkorb { auto = no special_use = \Trash } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Synoptic/Alle { auto = no comment = All my messages special_use = \All } mailbox Trash { auto = no special_use = \Trash } mailbox Wichtig { auto = create } prefix = INBOX/ separator = / subscriptions = no type = private } namespace subscriptions { hidden = yes list = no location = prefix = subscriptions = yes } passdb { args = scheme=CRYPT username_format=%u /usr/local/etc/dovecot/users driver = passwd-file } plugin { acl = vfile:/etc/dovecot/dovecot-acl:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db mail_home = /var/mail/%u setting_name = sieve, managedsieve sieve = file:/var/mail/%u/sieve/;active=/var/mail/%u/sieve/%u.sieve } postmaster_address = postmaster@localhost protocols = imap pop3 lmtp imap lmtp sieve pop3 sieve service anvil { unix_listener anvil-auth-penalty { mode = 00 } } service auth { unix_listener auth-client { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 service_count = 1 } service imap { executable = imap postlogin process_limit = 1024 vsz_limit = 400 M } service lmtp { executable = lmtp -L user = vmail vsz_limit = 400 M } service postlogin { executable = script-login -d rawlog } ssl = required ssl_cert = </usr/local/etc/dovecot/dovecot.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /usr/local/etc/dovecot/users default_fields = home=/var/mail/%u driver = passwd-file } verbose_proctitle = yes verbose_ssl = yes protocol lmtp { auth_username_format = %n mail_plugins = zlib quota acl listescape mail_log notify virtual quota sieve acl } protocol lda { mail_plugins = zlib quota acl listescape mail_log notify virtual quota sieve acl } protocol imap { mail_max_userip_connections = 10 mail_plugins = zlib quota acl listescape mail_log notify virtual imap_quota imap_acl } Any ideas jakob

2 3

sieve problem config antispam
by Günther J. Niederwimmer 12 Dec '17

12 Dec '17

Hello, I like to configure the antispam with sieve from this site https:// wiki2.dovecot.org/HowTo/AntispamWithSieve#For_rspamd But when I compile the scripts I have this Errors sievec /usr/lib64/dovecot/sieve/report-ham.sieve report-ham: line 1: error: require command: unknown Sieve capability `vnd.dovecot.pipe'. report-ham: line 1: error: require command: unknown Sieve capability `imapsieve'. report-ham: line 15: error: unknown command 'pipe' (only reported once at first occurrence). report-ham: error: validation failed. sievec(root): Fatal: failed to compile sieve script '/usr/lib64/dovecot/sieve/ report-ham.sieve' My system is a centos 7 dovecot 2.2.33.1 dovecot-pigeonhole 2.2.33.1 -- mit freundlichen Grüssen / best regards, Günther J. Niederwimmer

2 1

Recommended tool for migrating IMAP servers
by Davide Marchi 12 Dec '17

12 Dec '17

Hi Friends, I would like to ask you a suggestion: I need to migrate a imap server to a new one and then dismiss the old one. Reading from relative Dovecot documentation page (https://wiki.dovecot.org/Migration) more tools are shown: UW-IMAP's mailutil, imapsync, YippieMove and Larch. The each mail servers are Linux based, one of this (mine) is Dovecot. Based on your experience which of these tools would be preferable to use? Thank you very much Davide

6 12

Re: hosting emails at home
by André Rodier 11 Dec '17

11 Dec '17

Hello Mike, Yes, I am using a static IP address, but in theory, you could use a dynamic one. Nothing technically would prevent email exchanges between two boxes, as long as the SPF records are up to date and the DKIM is properly setup. Unfortunately, some ISPs are simply blacklisting full range of private IP addresses just because they are not officials / commercials. Kind regards, André On 10/12/17 19:24, Mike wrote: > > Nice. > > Are you using a static IP in this setup? > > It doesn't seem like it, but wanted to be sure. > > Mike. > > Quoting André Rodier <andre(a)rodier.me>: > >> Hello everyone, >> >> I have been using Postfix and Dovecot for my personal emails for years. >> After being tired of reinstalling my personal mail server many times, I >> am currently writing some Ansible scripts to do it automatically. >> >> I obviously checked the other projects, and did not found anything close >> to what I am looking for, so I am implementing it now. >> >> The final goal is to have a box that once online, would setup itself, by >> creating the certificates, the DKIM keys and update the appropriate DNS >> records. >> >> This is so far what I have achieved: >> - Automatic generation of certificates using LetsEncrypt >> - Automatic update of the domain entries: imap, smtp, webmail, etc. >> - Automatic generation of a DKIM keys >> - Automatic update of specific records (MX, SPF, DKIM, etc.) >> - LDAP server for user accounts, with or without system login. >> - Installation of Postfix, Dovecot and Roundcube >> >> Sending DKIM signed emails is working, and the IMAP server is configured >> as well, although basic. >> >> The postfix and dovecot configuration are not yet entirely finished. I >> am planing to add an anti spam system, and sieve, amongst other things. >> >> Although in development during my spare time, the system is normally >> robust and you should be able to run it multiple times without errors. >> >> If anyone is interested to use it, to have a look, or to take part, it >> is here: https://github.com/progmaticltd/homebox >> >> Kind regards, >> André Rodier. > >

5 10

hosting emails at home
by André Rodier 11 Dec '17

11 Dec '17

Hello everyone, I have been using Postfix and Dovecot for my personal emails for years. After being tired of reinstalling my personal mail server many times, I am currently writing some Ansible scripts to do it automatically. I obviously checked the other projects, and did not found anything close to what I am looking for, so I am implementing it now. The final goal is to have a box that once online, would setup itself, by creating the certificates, the DKIM keys and update the appropriate DNS records. This is so far what I have achieved: - Automatic generation of certificates using LetsEncrypt - Automatic update of the domain entries: imap, smtp, webmail, etc. - Automatic generation of a DKIM keys - Automatic update of specific records (MX, SPF, DKIM, etc.) - LDAP server for user accounts, with or without system login. - Installation of Postfix, Dovecot and Roundcube Sending DKIM signed emails is working, and the IMAP server is configured as well, although basic. The postfix and dovecot configuration are not yet entirely finished. I am planing to add an anti spam system, and sieve, amongst other things. Although in development during my spare time, the system is normally robust and you should be able to run it multiple times without errors. If anyone is interested to use it, to have a look, or to take part, it is here: https://github.com/progmaticltd/homebox Kind regards, André Rodier.

5 7

recover missing messages - files still present in storage
by Webert de Souza Lima 11 Dec '17

11 Dec '17

Hi, I have a user account that had almost 20GB of emails and now they're missing. Only a few are available trough IMAP or doveadm. I can see in /path/to/mailbox/storage that thousands of "m." files are still there, summing up 19GB of files. doveconf -n http://termbin.com/7lgc I have tried: accessing via IMAP accessing via doveadm search/fetch/mailbox status doveadm index doveadm force-resync doveadm dump: -- INDEX: /srv/dovecot2/index/DOMAIN_SUPRESSED/ACCOUNT_SUPRESSED/storage/dovecot.map.index version .................. = 7.3 base header size ......... = 120 header size .............. = 176 record size .............. = 20 compat flags ............. = 1 index id ................. = 1500105889 (2017-07-15 05:04:49) flags .................... = 0 uid validity ............. = 1500105889 (2017-07-15 05:04:49) next uid ................. = 26514 messages count ........... = 26513 seen messages count ...... = 0 deleted messages count ... = 0 first recent uid ......... = 1 first unseen uid lowwater = 1 first deleted uid lowwater = 26446 log file seq ............. = 47 log file tail offset ..... = 15656 log file head offset ..... = 15656 log2 rotate time ......... = 1512558922 (2017-12-06 09:15:22) last temp file scan ...... = 0 (1969-12-31 21:00:00) day stamp ................ = 1512604800 (2017-12-06 22:00:00) day first uid[0] ......... = 26450 day first uid[1] ......... = 26395 day first uid[2] ......... = 26328 day first uid[3] ......... = 26252 day first uid[4] ......... = 26234 day first uid[5] ......... = 26216 day first uid[6] ......... = 26135 day first uid[7] ......... = 26055 -- Extension 0 -- name ........ = map hdr_size .... = 8 reset_id .... = 0 record_offset = 8 record_size . = 12 record_align = 4 header ........ = 6111000001000000 -- Extension 1 -- name ........ = ref hdr_size .... = 0 reset_id .... = 0 record_offset = 6 record_size . = 2 record_align = 2 -- Keywords -- -- CACHE: /srv/dovecot2/index/DOMAIN_SUPRESSED/ACCOUNT_SUPRESSED/storage/dovecot.map.index.cache cache is unusable Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil*

2 3

Mailsploit problem in responce of BODYSTRUCTURE
by TACHIBANA Masashi 11 Dec '17

11 Dec '17

Hi, I tried to see a mail that have a strange From header in bellow URL: https://www.mailsploit.com/index Then, I got BODYSTRUCTURE response contain next: ((NIL NIL "service" "paypal.com")) Are this problem already founded by anyone? So already fixed? -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana@qualitia.co.jp

3 6

iPhone no longer authenticating
by Mark Foley 11 Dec '17

11 Dec '17

I've switched a user to being an active directory user. That user's email client authorizes just fine with dovecot using GSSAPI. However, now his iPhone won't authorize. In the dovecot log file I get: Dec 01 14:27:28 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=q4n3W0xfggBiZj9s lip=98.102.63.107 rip=98.102.63.108 lport=993 rport=49538 resp=AG1wcmVzcwBEaW5va3JvbndhbGw0NQ== (previous base64 data may contain sensitive data) Dec 01 14:27:32 auth-worker(5988): Debug: shadow(mpress,98.102.xx.yyy): lookup Dec 01 14:27:32 auth-worker(5988): Info: shadow(mpress,98.102.xx.yyy): unknown user (given password: *******) Dec 01 14:27:34 auth: Debug: client passdb out: FAIL 1 user=mpress Dec 01 14:27:34 imap-login: Info: Aborted login (auth failed, 1 attempts in 6 secs): user=<mpress>, method=PLAIN, rip=98.102.xx.yyy, lip=98.102.63.107, TLS, session=<q4n3W0xfggBiZj9s> Dec 01 14:27:34 imap-login: Debug: SSL alert: close notify [98.102.xx.yyy] This same user will authenticate OK from his local domain workstation: Dec 01 14:28:52 auth: Debug: master userdb out: USER 1948516353 mpress system_groups_user=HPRS\mpress uid=10005gid=10000 home=/home/HPRS/mpress auth_token=ce3050035718ed0996af698400c4de1be453ec06 auth_user=mpress(a)HPRS.LOCAL Dec 01 14:28:52 imap-login: Info: Login: user=<mpress>, method=GSSAPI, rip=192.168.0.54, lip=192.168.0.2, mpid=9755, TLS, session=<6MT1YExftwDAqAA2> I'm pretty sure the reason has to do with Active Directory authenication locally, but of course his iPhone is not a member of the domain, and he is no longer in /etc/passwd/shadow. So, what is the best way to get the iPhone to authenticate? Here's my current config: > doveconf -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 4.4.88 x86_64 Slackware 14.2 auth_debug = yes auth_debug_passwords = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain login gssapi auth_use_winbind = yes auth_username_format = %n auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2016-08-10/54e789087d419b6e.crt ssl_key = </etc/ssl/certs/OHPRS/GoDaddy/mail.ohprs.org.key userdb { driver = passwd } verbose_ssl = yes Thanks, --Mark

2 2

Doveadm backup error.
by Dovecot list 10 Dec '17

10 Dec '17

Hello. I try to migrate dovecot 1 to dovecot 2 with doveadm backup. But when i try to set doveadm backup i get : mx3:/root/dsync@[23:11] # doveadm -v -c ah.temp backup -R -u ah(a)test.pl <ahuryn(a)i-pi.pl> imapc: doveadm(ah(a)test.pl <ahuryn(a)i-pi.pl>): Error: Mail access for users with UID 145 not permitted (see first_valid_uid in config file, uid from userdb lookup). doveadm(ah(a)test.pl <ahuryn(a)i-pi.pl>): Error: User init failed mx3:/root/dsync@[22:13] # ls -la /home/mail/vhosts/test.pl/ah(a)test.pl/ <http://i-pi.pl/ahuryn@i-pi.pl/> total 1 drwxr-xr-x 2 vmail vmail 2 Nov 12 23:59 . mx3:/root/dsync@[22:14] # doveadm user ah(a)test.pl <ahuryn(a)i-pi.pl> field value uid 145 gid 145 home /home/mail/vhosts/test.pl/ah(a)test.pl <http://i-pi.pl/ahuryn@i-pi.pl> mail mdbox:~/mdbox quota_rule *:storage=50000M mx3:/root/dsync@[22:14] # id 145 uid=145(vmail) gid=145(vmail) groups=145(vmail) mx3:/root/dsync@[1:14] # doveconf -n | grep 145 first_valid_uid = 145 last_valid_uid = 145 I dont have any idea whats is the problem. Best regards.

2 3

Mail-crypt plugin clarification
by rje 10 Dec '17

10 Dec '17

I'm looking into ways to encrypt the stored email on my server. The idea is to make it impossible for my hosting provider (who has access to my VPS) to read the mail from the disk. So I'm looking into ways to do this, and I found the mail-crypt plugin for dovecot. Unfortunately I find the documentation very hard to understand. There is no clear description of what the goal and purpose of the plugin is, or how it works. Most of the documentation is very short and provides no explanation. So here are some questions - I will gladly help to update the documentation when some of these questions are answered :) If you cannot answer them all, please tell me what you know.. - It seems mail-cypt will transparently encrypt/decrypt mail - so it stores it on the server in encrypted form, but dovecot serves it unencrypted over IMAP. Is this correct? - It seems that mail-crypt needs both a private and a public key to work. Is this correct? - If mail-crypt has both private and public key in its configuration, does that not defeat the purpose of the whole thing? Anyone with access to the disk will be able to read everything? Regarding the settings: mail_crypt_global_private_key(_n) - Private key to decrypt files, you can specify many mail_crypt_global_public_key - Public key to use to encrypt files, you can specify one - How does this work? What does mail-crypt do when multiple private keys are specified? mail_crypt_private_key - Private key to decrypt user's master key, can be base64 encoded mail_crypt_private_password - Password to decrypt user's master key or environment private key - What is the relation between a users master key, and the private/public global keys above? What is an environment private key? TIA, and as I said above, I will help with updating the docs! -- Sent from: http://dovecot.2317879.n4.nabble.com/

1 0

Re: Use multiple mbox locations
by Joseph Tam 09 Dec '17

09 Dec '17

Steffen Kaiser > Hmm, this is a job for: > > https://wiki2.dovecot.org/Plugins/Snarf Cool! Can this be used with the imapc: driver to consolidate mail from separate IMAP accounts into one? (Sort of like how you can configure Gmail to slurp up mail into the Gmail account.) Joseph Tam <jtam.home(a)gmail.com>

1 0

Use multiple mbox locations
by bapt x 08 Dec '17

08 Dec '17

Hello, With GNU mailutils on Debian 9, we receive mails in /var/mail/<username> but when we read mails with the "mail" command, they are moved in a file ~/mbox: "Saved 1 message in /home/<username>/mbox". I use Roundcube webmail with Dovecot but if I also use use the "mail" command to read emails, Roundcube will not display old messages anymore since they were moved to ~/mbox. So is their a way to tell Dovecot that we want to lookup for emails both in /var/mail/<username> and ~/mbox? I saw https://wiki.dovecot.org/Namespaces#Mixed_mbox_and_Maildir but I it did not work if when I tried to add 2 times a mbox location. Thanks for your help.

2 1

Errors and dovecot crashing...
by SH Development 06 Dec '17

06 Dec '17

Our production dovecot/postfix server has been stable for a number of years. In the last month or so, we are seeing increasing errors such as these: Dec 6 15:51:20 mail dovecot: imap(redacted(a)lilythicket.com): Warning: Transaction log file /home/vmail/lilythicket.com/diana/Maildir/dovecot.index.log was locked for 322 seconds Dec 6 15:50:54 mail dovecot: imap(redacted(a)theormans.com): Warning: Maildir /home/vmail/theormans.com/connieorman/Maildir/.Junk: Synchronization took 66 seconds (1 new msgs, 0 flag change attempts, 0 expunge attempts) Dec 6 15:51:43 mail dovecot: master: Error: service(pop3-login): Initial status notification not received in 30 seconds, killing the process Dec 6 15:51:43 mail dovecot: master: Error: service(pop3-login): command startup failed, throttling Dec 6 15:51:43 mail dovecot: master: Error: service(imap-login): child 5868 killed with signal 9 Dec 6 15:51:43 mail dovecot: master: Error: service(imap-login): command startup failed, throttling Dec 6 15:55:31 mail dovecot: imap-login: Fatal: Corrupted SSL ssl-parameters.dat in state_dir: Truncated file Dec 6 15:55:32 mail dovecot: pop3-login: Fatal: Error reading configuration: Timeout reading config from /var/run/dovecot/config And so forth. Seems to be all over the place. The server slows down to a crawl. Restarting dovecot or postfix has no effect on the problem. Only a server reboot solves it, temporarily. Sometimes for weeks, sometimes for hours. The hard drive SMART status reads okay. During this time, of course, users cannot connect to check their email. Thoughts on where to go to troubleshoot this and why it’s happening? Ethon

1 0