January 2018 - dovecot

PDFs getting mangled
by Adam Weinberger 24 Jan '18

24 Jan '18

Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. It seems to be happening when I use vnd.dovecot.filter. When I comment out the block, things come through fine. My filter block looks like this: require "vnd.dovecot.filter"; filter "bogofilter_filter"; if header :contains "X-Bogosity" [ "Spam, tests=bogofilter, spamicity=1.00", "Spam, tests=bogofilter, spamicity=0.99" ] { fileinto "spam/totally"; stop; } elsif header :contains "X-Bogosity" "Spam," { fileinto "spam/probably"; stop; } elsif header :contains "X-Bogosity" "Unsure," { fileinto "spam/maybe"; stop; } filter/bogofilter_filter looks like this: #!/bin/sh cat /dev/stdin | /usr/local/bin/bogofilter -p -e -c /path/to/bogofilter.cf Images seem to come through fine. I didn't have this problem before the upgrade. It could easily be a problem with bogofilter, but I figured that I'd check here first to see if anybody else has an attachment-mangling issue with vnd.dovecot.filter. # Adam -- Adam Weinberger adamw(a)adamw.org http://www.adamw.org

3 7

Auth cache prevents login when non-password fields change
by Tom Sommer 23 Jan '18

23 Jan '18

The auth cache contains all fields returned by "password_query" (in itself a little odd), including the fields "nologin" and "reason". If a user is cached with "nologin=Y" and the database-source is changed so nologin condition is no longer true, then the cache prevents login for as long as the TTL remain? is there any way around this? Thanks -- Tom

1 0

rewrite copy to trash->delete->expunge mail with move??
by Chi Min Wang 23 Jan '18

23 Jan '18

Hello Everyone: When user got quota exceed and trying to delete mail. Most MUA's default "move to trash folder" will proceed by copy mail to trash folder,then by delete/expunge it(copy before expunge). Unfortunately this will not success due to quota exceed. Is there any way to let dovecot proceed it by IMAP MOVE instead of "copy to trash folder"->delete/expunge,Thanks!! *********************************************** CONFIDENTIALITY NOTICE:This e-mail and any attachments are confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, and (ii) please notify immediately the sender by reply mail, and (iii) please delete all copies of the email from your system. Failure to follow this process may be unlawful. We greatly appreciate your cooperation.

3 2

How to set autoexpunge rule for single user mailbox in dovecot conf?
by Alexey Murz Korepov 23 Jan '18

23 Jan '18

I need to set autoexpunge rule only for one single user and one mailbox (mail folder), so apply it only for user alice(a)example.com mailbox INBOX. How can I set namespace in dovecot config, that will apply only to single user? -- Best regards, Alexey Murz Korepov. Email, Jabber: murznn(a)gmail.com

3 2

LAYOUT=fs
by Jungersen, Danjel - Jungersen Grafisk ApS 23 Jan '18

23 Jan '18

2 5

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?
by Aki Tuomi 23 Jan '18

23 Jan '18

You can do passdb { driver = passwd-file args = /path/to/some/file skip = unauthenticated } and put in this file alice@example.com::::::noauthenticate userdb_namespace/inbox/mailbox/INBOX/autoexpunge=31d or nopassword instead of noauthenticate. Please keep replies in-list. Aki On 23.01.2018 12:31, Alexey Murz Korepov wrote: > So, with using `passwd` driver as userdb - there are no ways to set > some dovecot single per-user setting? Change passwd to real user > database is too hard on working system. > Maybe exists some other ways to do auto expunge function for separate > mailbox folder on single user? > > As workaround, can I use command like `doveadm expunge` in cron job > for do this task? > --- > doveadm expunge -u alice(a)example.com <mailto:alice@example.com> > mailbox INBOX savedbefore 31d > --- > > On 23 January 2018 at 13:20, Aki Tuomi <aki.tuomi(a)dovecot.fi > <mailto:aki.tuomi@dovecot.fi>> wrote: > > Well, to have per-user settings, you need a userdb, that can > provide per-user settings. > > Aki > > > On 23.01.2018 12:19, Alexey Murz Korepov wrote: >> I can't understand what you mean in `return from userdb` - in >> which place of dovecot config files I can set this rule? I don't >> use separate userdb for dovecot users. >> Or maybe this must be set somewhere in user home folder? >> >> On 23 January 2018 at 13:17, Aki Tuomi <aki.tuomi(a)dovecot.fi >> <mailto:aki.tuomi@dovecot.fi>> wrote: >> >> No. >> >> The namespace name is irrelevant, it just has to be there. >> Assuming you have no other namespace config around, >> >> namespace inbox { >> inbox = yes >> mailbox INBOX { >> } >> } >> >> Then return from userdb, >> namespace/inbox/mailbox/INBOX/autoexpunge=31d >> >> The namespace config will be global (affects all users), but >> autoexpunge setting will be for alice only. >> >> Aki >> >> On 23.01.2018 12:08, Alexey Murz Korepov wrote: >>> Thanks, Aki, for quick answer! But can you give me please a >>> real example with user alice(a)example.com >>> <mailto:alice@example.com> and mailbox INBOX? In my setup I >>> have no user database, I use real linux users, managed via >>> Webmin/Virtualmin. >>> So I must set in `/etc/dovecot/conf.d/15-mailboxes.conf` >>> file something this? >>> ------ >>> namespace alice(a)example.com <mailto:alice@example.com> { >>> mailbox INBOX { >>> } >>> } >>> >>> namespace/alice(a)example.com/mailbox/INBOX/autoexpunge=31d >>> <http://alice@example.com/mailbox/INBOX/autoexpunge=31d> >>> >>> ------ >>> Or I must fill last string not in `mailboxes.conf` file, but >>> in some other place? >>> >>> On 23 January 2018 at 12:58, Aki Tuomi <aki.tuomi(a)dovecot.fi >>> <mailto:aki.tuomi@dovecot.fi>> wrote: >>> >>> Configure >>> >>> namespace <name> { >>> mailbox <name> { >>> } >>> } >>> >>> and return from userdb >>> >>> namespace/<name>/mailbox/<name>/autoexpunge=value >>> >>> Ak >>> >>> >>> On 23.01.2018 11:57, Alexey Murz Korepov wrote: >>>> I need to set autoexpunge rule only for one single user >>>> and one mailbox (mail folder), so apply it only for >>>> user alice(a)example.com <mailto:alice@example.com> >>>> mailbox INBOX. How can I set namespace in dovecot >>>> config, that will apply only to single user? >>>> >>>> -- >>>> Best regards, >>>> Alexey Murz Korepov. >>>> Email, Jabber: murznn(a)gmail.com <mailto:murznn@gmail.com> >>> >>> >>> >>> >>> -- >>> Best regards, >>> Alexey Murz Korepov. >>> Email, Jabber: murznn(a)gmail.com <mailto:murznn@gmail.com> >> >> >> >> >> -- >> Best regards, >> Alexey Murz Korepov. >> Email, Jabber: murznn(a)gmail.com <mailto:murznn@gmail.com> > > > > > -- > Best regards, > Alexey Murz Korepov. > Email, Jabber: murznn(a)gmail.com <mailto:murznn@gmail.com>

1 0

v2.3.0 release candidate released
by Timo Sirainen 23 Jan '18

23 Jan '18

https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig It's finally time for v2.3 release branch! There are several new and exciting features in it. 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. Please test these before v2.3.0 to make sure we don't have any bad bugs left! BTW. The v2.3.0 will most likely be signed with a new PGP key ED409DA1. 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. - Many other smaller fixes

13 26

logging download speed for services
by Arkadiusz Miśkiewicz 23 Jan '18

23 Jan '18

Jan 23 07:14:13 srv dovecot[7702]: imap(something): session=<xgmrdGtj/u3B7y+g>, Logged out bytes=189/2669 Jan 23 07:14:57 srv dovecot[7702]: pop3(abc): session=<X7tLd2tjeeSy7wrl>, Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, bytes=12/43 Could dovecot be logging download speed for these and log it? (ignoring idle times for imap and only counting fetches etc) The goal is to be able to compare users speed, notice degradation and other such problems. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Strange thing on log rotation front
by Luciano Mannucci 22 Jan '18

22 Jan '18

Hi all! I've decided to rotate the dovecot logs automatically on my freebsd 10.4 server using the system's newsyslog feature. I started with logfile.info putting the line /var/log/dovecot/logfile.info 600 31 * @T16 ZCU /var/run/dovecot/master.pid 30 which should send a SIGUSER to the master process, which it seems to do for I see in the log file: master: Warning: Sent SIGKILL to 1 log processes master: Warning: Killed with signal 15 (by pid=69871 uid=0 code=kill) though the log process doesn't die. What did I do wrong? my doveconf -n says: root@baobab:/var/log/dovecot # doveconf -n # 2.2.28 (bed8434): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: FreeBSD 10.4-RELEASE-p3 amd64 ufs auth_cache_size = 3 k auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 1228 default_vsz_limit = 712 M disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 100 info_log_path = /var/log/dovecot/logfile.info listen = * log_path = /var/log/dovecot/logfile login_greeting = Dovecot at Baobab ready. login_trusted_networks = 127.0.0.0/8 212.45.144.0/24 192.168.134.0/24 mail_location = mbox:/var/spool/mailboxes/%u:INBOX=/var/spool/mail/%u:DIRNAME=mbox:INDEX=/var/dovecot_indexes/%u maildir_copy_with_hardlinks = no 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 mbox_lock_timeout = 443 secs namespace { inbox = yes location = prefix = separator = . type = private } passdb { driver = pam } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } protocols = pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imaps { address = * } process_limit = 512 } service pop3-login { chroot = executable = pop3-login -D inet_listener pop3s { address = * } process_limit = 512 } ssl_ca = </usr/local/etc/ssl/ca.crt ssl_cert = </usr/local/etc/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes } protocol lda { info_log_path = /var/log/dovecot/lda.log log_path = /var/log/dovecot/lda-errors.log postmaster_address = postmaxxxster(a)mcs.it } Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

2 2

Re: Questions about SPECIAL-USE IMAP extension
by Joseph Tam 19 Jan '18

19 Jan '18

Aki Tuomi writes: >>>>> https://wiki2.dovecot.org/Plugins/MailboxAlias > > There is also gotcha that MailboxAlias is not compatible with > mailbox_list_index=yes setting. Thanks. How does this manifests itself: the client gets an inconsistent view of the outgoing mailbox that depends on which mailbox the client is using, or the optimization is broken and dovecot keeps having to (re)read the mailbox to acquire the IMAP STATUS? Joseph Tam <jtam.home(a)gmail.com>

2 1