- dovecot - dovecot.org

Quota plugin creates IMAP folder
by Thorsten Hater 25 Jan '18

25 Jan '18

Hi everyone, I have noticed recently that Dovecot creates lock directories under users' Maildirs which look like IMAP folders. This is bad since users will see IMAP folders that are not supposed to be there. In my logs I see dovecot: imap(...): Error: file_create_locked(/.../Maildir/.vsize.lock) failed: Is a directory The directory in question # ls /.../Maildir/.vsize.lock/ cur/ dovecot.index.log dovecot-uidlist maildirfolder new/ tmp/ so Dovecot seems to think this to be an IMAP folder. I am using Dovecot 2.2.27 under Debian, built from source, the lock_method is set to fnctl, and the quota plugin uses the maildir method. Can somebody advice me on how to fix this? Best regards, Thorsten

3 7

Single mailbox optimizations
by Alex Shishkin 25 Jan '18

25 Jan '18

Hello, I have unconventional load profile for my email server and I would like to ask if someone can suggest optimizations in my case. I have only one mailbox on the server for collecting emails from variety of external mail servers. I use Postfix for collecting emails and Dovecot to provide IMAP for downloading emails from this mailbox. Currently Postfix configured to use LMTP for transferring emails to Dovecot. Dovecot mail storage format is mdbox. Everything was in order (no incoming and active queues in Postfix) when daily incoming email count was up to 1 million emails. But now I have to process up to 2 million incoming emails and I faced bottleneck of 10 emails per second for saving emails from Postfix active queue to mdbox using LMTP. Currently Postfix receives about 20 emails per second, incoming and active queues in Postfix are growing and I have to find the way to speed up transferring process from Postfix to mdbox. This setup is running on the virtual machine with 8 CPU and 8 GB RAM. CPU loaded only by dovecot/lmtp process but not more than 20% per core. I/O wait is 2-3%. Disk load is about 200 wMB/sec and 300 rKB/sec (and this sounds quite a bit for our storage capacity) . Postfix has destination concurrency limit 20 for default and virtual transport (I’m using virtual transport due to virtual domains configuration). Strace showed up that dovecot/lmtp processes have some delays only on waiting for write lock on truncation log file dovecot.index.log. I have temporary moved all index files including truncation log to tmpfs, but this did not help. The only thing that helped me to increase speed up to 20 emails per second is removing almost all emails from the mailbox (with empty Inbox I got even 30 emails per second). But I have to keep all incoming emails in the mailbox at least for one week so this way is unacceptable. So I would like to ask for suggestions, because I can’t find the root cause of this bottleneck. Dovecot version 2.2.31 Postfix version 2.10.1 ------------------------------------------------Dovecot conf ------------------------------------------------ mail_location = mdbox:~/mdbox mdbox_rotate_interval = 1 days mdbox_rotate_size = 200MB mail_plugins = " zlib” plugin { zlib_save = gz zlib_save_level = 6 } userdb { args = /etc/dovecot/passwd default_fields = uid=vmail gid=vmail home=/opt/vmail/%u driver = passwd-file } passdb { args = /etc/dovecot/passwd driver = passwd-file } service lmtp { process_min_avail = 8 service_count = 0 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 0 } ------------------------------------------------------------------------------------------------ --------------------------------------Postfix conf------------------------------------------- virtual_alias_maps = hash:/etc/postfix/virtual virtual_mailbox_domains = test.com, example.com virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_transport = lmtp:unix:private/dovecot-lmtp default_destination_concurrency_limit = 20 virtual_destination_concurrency_limit = 20 ------------------------------------------------------------------------------------------------

1 0

Re: dovecot Digest, Vol 177, Issue 55
by Matthew Brown 25 Jan '18

25 Jan '18

No reason to tell me about security, I just need chmod for my tests. Where to change it ? On Thu, Jan 25, 2018 at 12:00 PM, <dovecot-request(a)dovecot.org> wrote: > Send dovecot mailing list submissions to > dovecot(a)dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request(a)dovecot.org > > You can reach the person managing the list at > dovecot-owner(a)dovecot.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dovecot digest..." > > > Today's Topics: > > 1. Re: Panic: data stack: Out of memory when allocating bytes > (Josef 'Jeff' Sipek) > 2. Re: 777 permissions on mailbox, subfolders subfiles new > emails (Nikolai Lusan) > 3. Re: problem with lda (Stephan Bosch) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 24 Jan 2018 17:39:36 -0500 > From: Josef 'Jeff' Sipek <jeff.sipek(a)dovecot.fi> > To: Thomas Robers <robers(a)tutech.de> > Cc: dovecot(a)dovecot.org > Subject: Re: Panic: data stack: Out of memory when allocating bytes > Message-ID: <20180124223936.GE14966@meili> > Content-Type: text/plain; charset=us-ascii > > On Wed, Jan 24, 2018 at 18:55:47 +0100, Thomas Robers wrote: > > Am 23.01.2018 um 20:07 schrieb Josef 'Jeff' Sipek: > > > On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > > > > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > ... > > > > 1. Do you have any idea what the imap process was doing at the time > of the > > > > allocation failure? > > > > Yes perhaps. We use shared mailboxes and at the time of failure the > > imap process is reading acl files in a shared mailbox (and subfolder). > > This shared mailbox has about 2800 subfolder and the acl files are read > > in about 10sec and and during this reading the imap process dies with > > the already mentioned error. It seems it has something to do with the > > shared mailbox, because since yesterday morning 5 core dumps have been > > created, 4 of them by one user accessing the shared mailbox and 1 > > by the user who is the owner of the shared mailbox. No other mailboxes > > are affected until now. > > Based on the stack trace, the client was creating a new mailbox, which > caused an acl list rebuild, which ended up triggering this oddly sized > allocation. > > > > > 2. You snipped all the important parts of the back trace. :) It > *starts* on > > > > the line: > > > > #0 0x00007f73f1386495 in raise () from /lib64/libc.so.6 > > > > > > In case you haven't used gdb before... after starting up gdb, run "bt > full" > > > at the gdb prompt. That'll print out a very detailed backtrace. (You > might > > > want to sanity check it to make sure there aren't any user passwords > in it > > > before posting it here...) > > > > Yes, sorry I'm not very familiar in using gdb, but here is the full > > backtrace: > > It looks like the binaries are stripped. There should be a "debug" package > you can install with symbol information. Then, the backtrace should be > much > more helpful. > > > > > Having the backtrace should help answer question number 1. > > > > 3. How big is this process when it dies? > > > > I don't know which imap process dies beforehand so how do i get this > > information? > > The size of the core file will give you an general idea. gdb can also > print > out lots of info via "maintenance info sections", but I don't think that'll > help figuring out why things blow up. > > Jeff. > > -- > Keyboard not found! > Press F1 to enter Setup > > > ------------------------------ > > Message: 2 > Date: Thu, 25 Jan 2018 13:09:40 +1000 > From: Nikolai Lusan <nikolai(a)lusan.id.au> > To: dovecot(a)dovecot.org > Subject: Re: 777 permissions on mailbox, subfolders subfiles new > emails > Message-ID: <1516849780.4714.5.camel(a)lusan.id.au> > Content-Type: text/plain; charset="UTF-8" > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > On Thu, 2018-01-25 at 00:35 +0200, Matthew Brown wrote: > > What I have to change, so dovecot on new email create, sets chmod 777 on > > Mailbox and all subfolders subfiles all new emails/sent emails etc. > > This is a really bad idea. It is possible to setup in dovecot if you're > using dovecot as your LDA. The only reason I can think of for anything > close to this is virtual mailboxes ... and even then I set things up with a > specific user to own the files and set them as 770 for the directories and > 660 for the files. With that setup dovecot limits users to their own mail > directories with values returned via the passdb/userdb. > > As a general rule anything on a *nix system that is chmod 777 is to be > avoided - it's a massive security risk. > > - -- > Nikolai Lusan <nikolai(a)lusan.id.au> > -----BEGIN PGP SIGNATURE----- > > iQIzBAEBCgAdFiEEVfd4GW6z4nsBxdLo4ZaDRV2VL6QFAlppSnQACgkQ4ZaDRV2V > L6To/BAAjKeTi6reaRrcSClKm6PEbgewtF1KvHgO1zr+hv9T2XOnVGFSajeFwSXR > rDSXGQ/H9s97KDGZB4VKxuSKZsDRFkF9u7ILttuXOgj8kG8XZl4sqg/w0FIrTC1K > GD8T0TZWSJGFIzrLXTpgzoO1LeQXIuXgnZIMbcaneCHKZc1do/GwQ4DEFVdUnxRJ > n+76nbs8RdQwZKGXYGGTU/BXPniTSW1pmTFxnlruxE7fuWBYeEyQGQRke/CT2rFF > ET+d7LlV4Nds6eGjalyf7m5tCNS87Zm78xegANuMNaMdzPI8NlbnFO82bAlC7kP/ > WkCFSfhJL3s9daEnMWT/dxY2lNKy3kTyOZssXM6ROkNhOFRipNwRr77tO6qzu8l9 > pvaVxr8a0pMVQwxGAyW84vS9GWmeMNMMiY0k7XdPSBS/6CVlQm8eUhnDo6GFZoH9 > Tbn4XNkEKysbZEjImjXb6eQpRwQLniIULjeyoX8aqmN2sh4kDndLJwjxpz7Jd6v2 > j2tuS7+79G9qU8dqpCSwzvWYTteOLJeqJLy6s5F+zf8FHGLcHdNasoo+/Sdzg4+E > tZm31wp7iQdzKMwbOnRk9FceYXbb9WjxI1QY+7U11Rx25y44UDPzUYYOL+ZoWOXJ > zAr/F9fhUP/u8AubOgOn6BLaguiWcFK0g6HhCqDkVAUibEMzC+0= > =YUek > -----END PGP SIGNATURE----- > > > > ------------------------------ > > Message: 3 > Date: Thu, 25 Jan 2018 09:35:57 +0100 > From: Stephan Bosch <stephan(a)rename-it.nl> > To: Infoomatic <infoomatic(a)gmx.at>, dovecot(a)dovecot.org > Subject: Re: problem with lda > Message-ID: <2544728b-5441-c163-34fd-bd155e28f591(a)rename-it.nl> > Content-Type: text/plain; charset=utf-8 > > Op 1/24/2018 om 5:30 PM schreef Infoomatic: > > Hello, > > > > I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I > have a strange problem with lda. > > We use bounce mails for internal users if they try to send > virus/spammails. The exact same config works with 2.2.23, but not with > 2.3.0. > > > > The relevant postfix/master.cf part: > > dovecot unix - n n - - pipe > > flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver > -d ${recipient} -f ${sender} > > > > On the same machine, with 2.2.23 I get a bounce mail when trying to send > a virus, with the subject "VIRUS in message apparently from you > (Eicar-Test-Signature)", to both the users inbox as well as to the mailbox > of virusalert(a)ourdomain.internal > > > > With 2.3.0, in the logs I get an error: > > > > relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced > (command line usage error. Command output: lda: Fatal: Invalid -f > parameter: Missing domain > > > > and the alert message is only sent to virusalert(a)ourdomain.internal, > but not to the user who tried to send the mail. > > > > The relevant part of our dovecot.conf: > > protocol lda { > > mail_plugins = " quota zlib sieve acl mail_log notify" > > postmaster_address = postmaster(a)ourdomain.internal > > } > > > > Does anyone know how to solve this problem? Or is there a workaround via > postfix/amavis/spamassassin? Any hints are highly appreciated, thanks! > > Apparently, the ${sender} has no @domain part. Why? > > Regards, > > Stephan. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > dovecot mailing list > dovecot(a)dovecot.org > https://dovecot.org/mailman/listinfo/dovecot > > ------------------------------ > > End of dovecot Digest, Vol 177, Issue 55 > **************************************** > -- zxzzzzzzzzzzzzz

1 1

777 permissions on mailbox, subfolders subfiles new emails
by Matthew Brown 25 Jan '18

25 Jan '18

What I have to change, so dovecot on new email create, sets chmod 777 on Mailbox and all subfolders subfiles all new emails/sent emails etc.

2 1

Questions about SPECIAL-USE IMAP extension
by Joseph Tam 25 Jan '18

25 Jan '18

I'd like to configure my dovecot service to use the IMAP SPECIAL-USE extension, but have a few questions for those who have used them, or are knowledgable about its use. Using this configuration as an example, namespace { ... mailbox xxx { special_use = \Sent } } Q1) Am I correct that mail client that don't understand SPECIAL-USE extentions will behave the same way with repect to outgoing mailbox storage? Q2) Will SPECIAL-USE enabled mail clients switch the mailbox used for outgoing mail from whatever it was using (e.g. "Sent Mail") to the (new) special-use mailbox "xxx"? Q3) Will SPECIAL-USE enabled mail clients connecting for the first time use "xxx" for outgoing mail, auto-creating it if necessary? Or will "xxx" be used only if the user does not manually configure a mailbox for this purpose? Q4) If I have an additional configuration mailbox yyy { special_use = \Sent } how does it affect Q2, Q3? Thanks to any who can provide clarity on this. Joseph Tam <jtam.home(a)gmail.com>

4 5

"Timeout (180s) while waiting for lock for transaction log file" since 2.3 upgrade?
by Zube 24 Jan '18

24 Jan '18

dovecot 2.1.x and 2.2.x has "just worked" with a minimal configuration for just about anything I've ever thrown at it. Now, with 2.3.0, there is one user (and only one user) that continually sees horrible delays, which is not surprising given the logs: Error: imap(user)<70175><356C8oljxrCBUppP>: Timeout (180s) while waiting for lock for transaction log file /path/to/home/directory/.imap/dovecot.list.index.log (WRITE lock held by pid 69995) where 69995 is the pid of the first dovecot process and 70175 is the pid of, e.g., the first LIST command. What's unique about this user is that he's the only one using linux (thunderbird) and his home directory is NFS-mounted. I understand that something is incorrect with the locking, but there are a couple of issues that I do not understand: 1) Is there a default that changed between 2.2 and 2.3 that would cause this? Despite potential issues associated with NFS, I didn't see the problem with 2.2. There is nothing in my conf file related to locking, so if there was a change, it must be a default for 2.3 (from doveconf -a): dotlock_use_excl = yes lock_method = fcntl mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl 2) If the problem is related to NFS locks, why would the problem persist when the user runs thunderbird from the server where his home directory *is not* NFS-mounted? Thanks for any help. Cheers, Zube

1 0

Autoexpunge is not working with dotlock locking
by Jaakko Seppälä 24 Jan '18

24 Jan '18

Hello, Autoexpunge is not working when used with dotlock locking. It seems to been broken since version 2.2.28. When autoexpunge is enabled and mailbox locking is set to dotlock all imap, pop and lmtp connections crash with the same error "file file-lock.c: line 287: unreached". Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN] Dovecot ready. X LOGIN testuser password X OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE LITERAL+ NOTIFY] Logged in X LOGOUT * BYE Logging out X OK Logout completed (0.001 + 0.000 secs). Connection closed by foreign host. => Jan 22 09:25:55 dovecottest dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=::1, lip=::1, mpid=8274, secured, session=<EDVCNV5jvNsAAAAAAAAAAAAAAAAAAAAB> Jan 22 09:25:57 dovecottest dovecot: imap(testuser)<8274><EDVCNV5jvNsAAAAAAAAAAAAAAAAAAAAB>: Panic: file file-lock.c: line 287: unreached Jan 22 09:25:57 dovecottest dovecot: imap(testuser)<8274><EDVCNV5jvNsAAAAAAAAAAAAAAAAAAAAB>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc8d24) [0x7ff43bef5d24] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc8dde) [0x7ff43bef5dde] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff43be69190] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xcd8ff) [0x7ff43befa8ff] -> /usr/local/lib/dovecot/libdovecot.so.0(file_wait_lock_error+0x26) [0x7ff43befac46] -> /usr/local/lib/dovecot/libdovecot.so.0(file_try_lock_error+0x13) [0x7ff43befacc3] -> /usr/local/lib/dovecot/libdovecot.so.0(file_create_locked+0x253) [0x7ff43bef7df3] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_user_lock_file_create+0xc5) [0x7ff43c1f5f15] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mail_user_autoexpunge+0x1f8) [0x7ff43c1dfc68] -> dovecot/imap(+0x1ba7c) [0x7ff43c72fa7c] -> dovecot/imap(client_input+0xb5) [0x7ff43c7308c5] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7ff43bf0d315] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7ff43bf0ebbf] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7ff43bf0d412] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7ff43bf0d638] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff43be8bb73] -> dovecot/imap(main+0x333) [0x7ff43c7226c3] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff43ba8bc05] -> dovecot/imap(+0xe8a1) [0x7ff43c7228a1] Jan 22 09:25:57 dovecottest dovecot: imap(testuser)<8274><EDVCNV5jvNsAAAAAAAAAAAAAAAAAAAAB>: Fatal: master: service(imap): child 8274 killed with signal 6 (core dumps disabled) Configuration used for testing: [root@dovecottest dovecot]# /usr/local/sbin/dovecot -n # 2.3.0 (c8b89eb): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) lock_method = dotlock mail_location = maildir:~/Maildir namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX { autoexpunge = 30 days } 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 } service lmtp { inet_listener lmtp { port = 24 } } ssl = no userdb { driver = passwd } Regards, Jaakko

2 1

version conflict in freebsdports?
by ＠lbutlr 24 Jan '18

24 Jan '18

I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if dovecot2 already installed ===> Registering installation for dovecot2-2.2.31_1 as automatic Installing dovecot2-2.2.31_1... pkg-static: dovecot2-2.2.31_1 conflicts with dovecot-2.2.33.2_2 (installs files into the same place). Problematic file: /usr/local/bin/doveadm *** Error code 70 (FreeBSD 11.1) -- Take my hand and I'll show you what was and will be.

2 2

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

Re: Error: Corrupted dbox file
by Webert de Souza Lima 19 Jan '18

19 Jan '18

Hello Florent, How did you proceed with the upgrade? Did you follow the recommended steps guide to upgrade ceph? (mons first, then OSDs, then MDS) Did you interrupt dovecot before upgrading the MDS specially? Did you remount the filesystem? Did you upgrade the ceph client too? Give people the complete scene and someone might be able to help you. Ask on ceph-users list too. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Thu, Jan 18, 2018 at 8:41 AM, Florent B <florent(a)coppint.com> wrote: > Hi list, > > I'm sorry to come back with my problem. I'm pretty sure it's not > dovecot-related, but can someone help me to bring some debug information > to Ceph developers ? > > For example, how writes are handled in Dovecot, and what kind of > corruption it is according to error messages ? > > > On 13/12/2017 16:19, Florent B wrote: > > Hi, > > > > I use Dovecot (last released version), 2 backends and 1 director, each > > user account handled by a single assigned backend. > > > > I use CephFS filesystem for messages (FUSE client). > > > > Since Ceph upgrade from Kraken to Luminous, I have a lot of erreurs > > "Error: Corrupted dbox file" on a single (large) mail account. > > > > I know the problem seems to come from Ceph, but maybe someone here can > > help me diagnose the situation. > > > > The error is exactly : EOF reading msg header (got 0/30 bytes) > > > > Dovecot backends are configured like this : > > > > mmap_disable = yes > > mail_fsync = optimized > > mail_nfs_storage = no > > mail_nfs_index = no > > mdbox_rotate_size = 12M > > > > CephFS supports file locking, and 2 backends never write the same file > > because each user is assigned to a backend. > > > > Did you ever see this problem with others FS maybe ? > > > > It seems problem disappeared when I disable pagecache for the Fuse mount. > > > > Thank you for your help. > > > > > >

1 0

Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed:
by Thomas Robers 19 Jan '18

19 Jan '18

Hi, after updating Dovecot to version 2.3 I get a lot of core-dumps like: > Jan 18 10:08:20 mail dovecot: imap(bob(a)tutech.de)<18200><CIPhNwljJcdYS/hg>: Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || > zstream->ostream.ostream.stream_errno != 0) > Jan 18 10:08:20 mail dovecot: imap(bob(a)tutech.de)<18200><CIPhNwljJcdYS/hg>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc71da) [0x7f9b510c81da] -> /usr/lib64/dovecot > /libdovecot.so.0(+0xc7766) [0x7f9b510c8766] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3be11) [0x7f9b5103ce11] -> /usr/lib64/dovecot/lib20_zlib_plugin.so(+0x4ffb) [0x7f9b4fc21ffb] -> > /usr/lib64/dovecot/libdovecot.so.0(+0xed3a6) [0x7f9b510ee3a6] -> dovecot/imap(client_disconnect+0x4f) [0x7f9b518f3a1f] -> dovecot/imap(cmd_logout+0x5b) [0x7f9b518ede5b] -> > dovecot/imap(command_exec+0x65) [0x7f9b518f7585] -> dovecot/imap(+0x1a7b0) [0x7f9b518f47b0] -> dovecot/imap(+0x1a848) [0x7f9b518f4848] -> dovecot/imap(client_handle_input+0x1d5) > [0x7f9b518f4c35] -> dovecot/imap(client_input+0x6e) [0x7f9b518f517e] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f9b510deec5] -> /usr/lib64/dovecot > /libdovecot.so.0(io_loop_handler_run_internal+0xbf) [0x7f9b510e0dcf] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x55) [0x7f9b510defb5] -> /usr/lib64/dovecot > /libdovecot.so.0(io_loop_run+0x38) [0x7f9b510df1d8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f9b5105eab3] -> dovecot/imap(main+0x33e) [0x7f9b51903cee] -> > /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f9b50c8bd1d] -> dovecot/imap(+0xe339) [0x7f9b518e8339] > Jan 18 10:08:20 mail dovecot: imap(bob(a)tutech.de)<18200><CIPhNwljJcdYS/hg>: Fatal: master: service(imap): child 18200 killed with signal 6 (core dumped) The gdb backtrace is: > gdb /usr/libexec/dovecot/imap /var/core/18200 > GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6) > Copyright (C) 2010 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-redhat-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/libexec/dovecot/imap...done. > [New Thread 18200] > Reading symbols from /usr/lib64/dovecot/libdovecot-storage.so.0...done. > Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0 > Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...done. > Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0 > Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. > Loaded symbols for /lib64/libc.so.6 > Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done. > Loaded symbols for /lib64/librt.so.1 > Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. > Loaded symbols for /lib64/libdl.so.2 > Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. > Loaded symbols for /lib64/ld-linux-x86-64.so.2 > Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. > [Thread debugging using libthread_db enabled] > Loaded symbols for /lib64/libpthread.so.0 > Reading symbols from /usr/lib64/dovecot/lib01_acl_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib01_acl_plugin.so > Reading symbols from /usr/lib64/dovecot/lib02_imap_acl_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib02_imap_acl_plugin.so > Reading symbols from /usr/lib64/dovecot/lib15_notify_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib15_notify_plugin.so > Reading symbols from /usr/lib64/dovecot/lib20_mail_log_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib20_mail_log_plugin.so > Reading symbols from /usr/lib64/dovecot/lib20_zlib_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib20_zlib_plugin.so > Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. > Loaded symbols for /lib64/libz.so.1 > Reading symbols from /lib64/libbz2.so.1...(no debugging symbols found)...done. > Loaded symbols for /lib64/libbz2.so.1 > Reading symbols from /usr/lib64/dovecot/lib30_imap_zlib_plugin.so...done. > Loaded symbols for /usr/lib64/dovecot/lib30_imap_zlib_plugin.so > Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols found)...done. > Loaded symbols for /lib64/libgcc_s.so.1 > Core was generated by `dovecot/imap'. > Program terminated with signal 6, Aborted. > #0 0x00007f9b50c9f495 in raise () from /lib64/libc.so.6 > Missing separate debuginfos, use: debuginfo-install dovecot23-2.3.0-3.gf.el6.x86_64 My Dovecot configuration is: ---snip--- # 2.3.0 (c8b89eb): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.0.1 (d33dca20) # OS: Linux 2.6.32-696.3.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 12345 imap_max_line_length = 2 M mail_debug = yes mail_location = maildir:/export/home/imap/%Lu/Maildir mail_plugins = acl zlib mail_log notify mailbox_idle_check_interval = 10 secs 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 { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { hidden = no inbox = yes list = 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 = INBOX/ separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/export/home/shared-db/shared-mailboxes mail_log_events = append delete undelete expunge copy mailbox_delete mailbox_rename flag_change mail_log_fields = uid box msgid size from flags mail_replica = tcp:mail2.tutech.de sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ sieve_user_log = ~/.dovecot.sieve.log zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service config { unix_listener config { user = vmail } } service doveadm { inet_listener { port = 12345 } user = vmail } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_limit = 500 process_min_avail = 20 } service imap { executable = imap } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 } service replicator { unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/mail.tutech.de.crt_chain ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL:!EXPORT ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local6 userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = acl zlib mail_log notify sieve } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl zlib mail_log notify imap_zlib imap_acl rawlog_dir = /tmp/rawlog/%u } ---snip--- Is this a bug or a misconfiguration? Is it possible to disable the zlib Plugin? Can Dovecot read the previous compressed e-mails and will they stay compressed? Thanks for the help! Kind regards Thomas

2 1

Fatal: nfs flush requires mail_fsync=always
by Søren Skou 19 Jan '18

19 Jan '18

Hiya all, I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on my testbed. The issue is that from what I can see, mail_fsync is set to always : # doveconf -n | grep mail_fs mail_fsync = always The result is that the client does not connect at all, which is not really what I wanted to happen :) Any idea what is going wrong here? Best regards Søren P. Skou doveconf -n # 2.3.1.alpha0 (bdfa22623) [XI:2:2.3.1~alpha0-1~auto+14]: /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1.alpha0 (d5f710e0) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 nfs auth_worker_max_count = 200 dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lock_method = dotlock mail_fsync = always mail_location = maildir:/mnt/virtual_mail/%d/%n mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota mailbox_list_index = no metric imap_select_no { event_name = imap_command_finished filter { name = SELECT tagged_reply_state = NO } } mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_rule = *:storage=1000m:messages=300000 quota_rule2 = Trash:storage=+10%%:messages=+10%% quota_rule3 = Junk:storage=+20%%:messages=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=75%%:messages=75%% quota-warning 75 %u quota_warning2 = storage=95%%:messages=95%% quota-warning 95 %u quota_warning3 = -storage=100%%:messages=100%% quota-warning below %u sieve = /etc/dovecot/sieve/default.sieve sieve_global_dir = /etc/dovecot/sieve } protocols = " imap pop3" service dict { unix_listener dict { mode = 0600 user = vmail } } service imap { executable = imap } service quota-status { client_limit = 1000 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_ca = /etc/ssl/certs/ca-root.crt ssl_cert = </etc/ssl/certs/stjerne.danskkabeltv.dk-2019.crt ssl_cipher_list = TLSv1+HIGH !SSLv2 !RC4 !aNULL !eNULL !3DES-CBC !3DES @STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = uid=2000 gid=2000 home=/mnt/virtual_mail/%d/%n driver = static } protocol lmtp { mail_plugins = quota } protocol lda { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota rawlog_dir = /tmp/rawlog/%u }

2 1

[BUG] dovecot 2.3.0 - service(lmtp) killed with signal 11 when user is overquota
by Marco Giunta 17 Jan '18

17 Jan '18

Hi, I'm using dovecot 2.3.0 installed on a new CentOS 7.4 with rpm from Dovecot repo. When I use LMTP to deliver an email to an overquota user, lmtp service hangs with a segfault: Jan 17 13:39:45 server-02.example.com kernel: lmtp[5099]: segfault at 0 ip 0000563599e372c2 sp 00007ffeaa4fdc80 error 4 in lmtp[563599e31000+b000] Jan 17 13:39:45 server-02.example.com dovecot[5089]: lmtp(5099): Fatal: master: service(lmtp): child 5099 killed with signal 11 (core dumped) If I try to deliver a mail with 'dovecot-lda' on the same overquota user, email was rejected, as expected: Jan 17 13:38:26 server-02.example.com dovecot[6773]: lda(USERNAME)<6773><ZbQDO8FDX1p1GgAASpDaHg>: Debug: Mailbox stdin: Opened mail UID=1 because: copying Jan 17 13:38:26 server-02.example.com dovecot[6773]: lda(USERNAME)<6773><ZbQDO8FDX1p1GgAASpDaHg>: msgid=unspecified: save failed to INBOX: Quota exceeded (mailbox for user is full) Jan 17 13:38:26 server-02.example.com dovecot[6773]: lda(USERNAME)<6773><ZbQDO8FDX1p1GgAASpDaHg>: msgid=unspecified: rejected: Quota exceeded (mailbox for user is full) Jan 17 13:38:26 server-02.example.com dovecot[6773]: lda(USERNAME)<6773><ZbQDO8FDX1p1GgAASpDaHg>: msgid=: Return-Path missing, rejection reason: Quota exceeded (mailbox for user is full) If user is no more overquota, LTMP delivery works: Jan 17 14:13:16 server-02.example.com dovecot[8651]: lmtp(USERNAME(a)example.com)<8665><ZMKmEexLX1rZIQAASpDaHg>: Debug: Mailbox <lmtp DATA local>: Opened mail UID=1 because: copying Jan 17 14:13:16 server-02.example.com dovecot[8651]: lmtp(USERNAME(a)example.com)<8665><ZMKmEexLX1rZIQAASpDaHg>: Debug: INBOX: Mailbox opened because: quota count Jan 17 14:13:16 server-02.example.com dovecot[8651]: lmtp(USERNAME(a)example.com)<8665><ZMKmEexLX1rZIQAASpDaHg>: sieve: msgid=<151619479629.10128.16766154794856971096(a)client.example.com>: stored mail into mailbox 'INBOX' Attached my dovecot configuration and a backtrace from gdb. Thanks, Marco --

3 4

Replication configuration
by Mantas Gegužis 17 Jan '18

17 Jan '18

Hello, I am trying to configure replication between two servers, for only specified virtual users, without success of course :) I am using LDAP for accounting. I have tried to pass a file with list like this: replication_dsync_parameters = -d -N -l 30 -U -F /etc/dovecot/list I have even tried to specify users with LDAP filter: iterate_filter = (|(uid=user1)(uid=user2)) both without success... But replicator every 5 minutes tries to replicate all users. I want this mainly for testing (i am preparing to server migration) and for bigger control who and when will be replicated/transferred. Dovecot 2.2.27 (Debian 9.3) -- Pagarbiai Mantas Gegužis VU Informacinių technologijų taikymo centras

2 1

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

17 Jan '18

Tanstaafl <tanstaafl(a)libertytrek.org> writes: >> Is this what you are looking for? >> >> https://wiki2.dovecot.org/Plugins/MailboxAlias >> >> It seems already be implemented... > > A first step maybe, but no, not quite. So what are the gotchas of using this? How much does this free lunch cost? Joseph Tam <jtam.home(a)gmail.com>

3 2

nfs flush requires mail_fsync=always
by Søren Peter Skou 16 Jan '18

16 Jan '18

Hiya, I'm getting nfs flush requires mail_fsync=always rather consistently from my servers. As you can see below this has been enabled already - So what else am I missing? Best Regards Søren # 2.3.1.alpha0 (6f9ffa758) [XI:2:2.3.1~alpha0-1~auto+6]: /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1.alpha0 (c9f2afe0) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 nfs auth_worker_max_count = 200 dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lock_method = dotlock mail_fsync = always mail_location = maildir:/mnt/virtual_mail/%d/%n mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = quota mailbox_list_index = no metric imap_select_no { event_name = imap_command_finished filter { name = SELECT tagged_reply_state = NO } } mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_rule = *:storage=1000m:messages=300000 quota_rule2 = Trash:storage=+10%%:messages=+10%% quota_rule3 = Junk:storage=+20%%:messages=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=75%%:messages=75%% quota-warning 75 %u quota_warning2 = storage=95%%:messages=95%% quota-warning 95 %u quota_warning3 = -storage=100%%:messages=100%% quota-warning below %u sieve = /etc/dovecot/sieve/default.sieve sieve_global_dir = /etc/dovecot/sieve } protocols = " imap pop3" service dict { unix_listener dict { mode = 0600 user = vmail } } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog } service quota-status { client_limit = 1000 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_ca = /etc/ssl/certs/ca-root.crt ssl_cert = </etc/ssl/certs/stjerne.danskkabeltv.dk-2019.crt ssl_cipher_list = TLSv1+HIGH !SSLv2 !RC4 !aNULL !eNULL !3DES-CBC !3DES @STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = uid=2000 gid=2000 home=/mnt/virtual_mail/%d/%n driver = static } protocol lmtp { mail_plugins = quota } protocol lda { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota rawlog_dir = /tmp/rawlog/%u } root@dovecot-09:/etc/dovecot/conf.d# doveconf -n | less } plugin { quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_rule = *:storage=1000m:messages=300000 quota_rule2 = Trash:storage=+10%%:messages=+10%% quota_rule3 = Junk:storage=+20%%:messages=+20%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=75%%:messages=75%% quota-warning 75 %u quota_warning2 = storage=95%%:messages=95%% quota-warning 95 %u quota_warning3 = -storage=100%%:messages=100%% quota-warning below %u sieve = /etc/dovecot/sieve/default.sieve sieve_global_dir = /etc/dovecot/sieve } protocols = " imap pop3" service dict { unix_listener dict { mode = 0600 user = vmail } } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog } service quota-status { client_limit = 1000 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail } ssl_ca = /etc/ssl/certs/ca-root.crt ssl_cert = </etc/ssl/certs/stjerne.danskkabeltv.dk-2019.crt ssl_cipher_list = TLSv1+HIGH !SSLv2 !RC4 !aNULL !eNULL !3DES-CBC !3DES @STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = uid=2000 gid=2000 home=/mnt/virtual_mail/%d/%n driver = static } protocol lmtp { mail_plugins = quota } protocol lda { mail_plugins = quota } protocol imap { mail_plugins = quota imap_quota rawlog_dir = /tmp/rawlog/%u }

1 0