- dovecot - dovecot.org

Is FTS needed for Subject/Recipient/Sender server-side searches?
by Sebastian Arcus 16 Apr '18

16 Apr '18

I've had a number of Dovecot installs happily running for quite a few years now, but I've just stumbled over a new issue. I am trying to get some iPhones to do server-side email searches through ActiveSync/Exchange protocol -> Horde -> Dovecot. The bit I can't figure out is if I need to enable and configure FTS in Dovecot for that to work? I've tested server-side email searches against the same Dovecot server on Thunderbird - through IMAP (there is an option to force the search on the server in Thunderbird) - and it is working really well and fast. I am only really interested in Sender/Recipient/Subject searches. Server-side searching is not working at the moment on the iPhones side - although I can see the ActiveSync commands being sent to Horde. Anyway, to begin with, does anybody know if server-side IMAP searches need FTS in Dovecot (Horde is talking to Dovecot through IMAP). The fact that they work fine in Thunderbird would suggest the answer is 'no' - but could someone confirm that is correct please? Anticipated thanks for any hints. I am on Dovecot 2.2.33 if in case it matters.

1 0

Migration from Maildir to mdbox on another server preserving POP3 UIDLS
by DurgaPrasad - DatasoftComnet 15 Apr '18

15 Apr '18

Hi all, Does anyone have a good migration document for Migration from Maildir (old server 2.1.x) to mdbox onto another new server with SIS preserving POP3 UIDLS. Preserving UIDLs is of paramount importance so that clients don't download mails again into outlook. Regards/DP --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

52.184.164.73 in my logs
by daniel_1983＠protonmail.com 15 Apr '18

15 Apr '18

Dear list, One of my users is reading e-mail from his phone. When he logs in, this is what I see in my logs : Apr 10 16:17:58 auth-worker(17101): Debug: sql(xxx(a)mydomain.tld,52.184.164.73): query: SELECT email as user, password FROM users WHERE email = LOWER('xxx(a)mydomain.tld') [...] Apr 10 16:17:58 imap-login: Info: Login: user=<xxx(a)mydomain.tld>, method=LOGIN, rip=52.184.164.73, lip=10.10.10.19, mpid=19286, TLS, session=<E6cEB4BprgA0uKRJ> Both lines show a remote IP of 52.184.164.73, which is strange since all my users are, and connect from, Algeria. According to the ispinfo website (http://www.ispinfo.net/isp/52.184.164.73.html) this IP belongs to Microsoft. Could it be that the outlook app uses microsoft's servers to fetch the mail before handing them to the user ? Daniel.

2 2

imapsieve fail to pipe to sa-learn-spam.sh
by David Mehler 14 Apr '18

14 Apr '18

Hello, I'm trying to get Dovecot 2.31, pidgeonhole 0.51 going with imapsieve and rspamd. I'm getting the below in my errorlog: cat dovecot.log 2018-04-13 17:35:34 imap-login: Info: Login: user=<testuser(a)domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=57977, secured, session=<o4T2psFpje5/AAAB> 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Error: sieve: pipe action: failed to pipe message to program: program `sa-learn-spam.sh' not found 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Info: sieve: left message in mailbox 'Spam' 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Error: sieve: Execution of script /usr/home/vmail/sieve/global/report-spam.sieve failed 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Info: copy from INBOX: box=Spam, uid=1, msgid=, size=1638 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Info: delete: box=INBOX, uid=2, msgid=, size=1638 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Info: expunge: box=INBOX, uid=2, msgid=, size=1638 2018-04-13 17:35:34 indexer-worker(testuser(a)domain.com)<59488><o4T2psFpje5/AAAB:5O+4G6Yi0Vpg6AAA0J78UA>: Info: Indexed 0 messages in Spam 2018-04-13 17:35:34 imap(testuser(a)domain.com)<57977><o4T2psFpje5/AAAB>: Info: Logged out in=144 out=1227 deleted=1 expunged=1 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 90-plugin.conf excerpt: plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_before = /home/vmail/sieve/global/admin.sieve sieve = file:/home/vmail/sieve/%d/%n/scripts;active=/home/vmail/sieve/%d/%n/active-script.sieve # Spam learning # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/home/vmail/sieve/global/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/home/vmail/sieve/global/report-ham.sieve sieve_pipe_bin_dir = /home/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment Here are my sieve scripts, they have been compiled, and the shell scripts, all are owned and group of vmail:vmail and the scripts are 775. home/vmail/sieve/global#cat report-spam.sieve require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; if environment :matches "imap.user" "*" { set "username" "${1}"; } pipe :copy "sa-learn-spam.sh" [ "${username}" ]; /home/vmail/sieve/global#cat report-ham.sieve require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; if environment :matches "imap.mailbox" "*" { set "mailbox" "${1}"; } if string "${mailbox}" "Trash" { stop; } if environment :matches "imap.user" "*" { set "username" "${1}"; } pipe :copy "sa-learn-ham.sh" [ "${username}" ]; /home/vmail/sieve/global#cat sa-learn-spam.sh #!/bin/sh exec /usr/local/bin/rspamc -h /var/run/rspamd/rspamd.sock -P "Password" learn_spam /home/vmail/sieve/global#cat sa-learn-ham.sh #!/bin/sh exec /usr/local/bin/rspamc -h /var/run/rspamd/rspamd.sock -P "password" learn_ham I'd appreciate any suggestions. Thanks. Dave.

2 1

ACL for system users?
by Rubén Fernández Asensio 13 Apr '18

13 Apr '18

Hello all, I'm setting up an IMAP server with dovecot. I've set up system users with PAM authentication and Maildir maiboxes. I'd like to share mailboxes among them, but regardless of what I try, I bump into filesystem permissions. I want to have Maildirs created for new users with the right permissions. I even changed "UMASK" in file /etc/login.defs from 022 to 002, but the Maildirs are still created with 700 permissions: ls -l /home/ximplet2/ total 4 drwx------ 9 ximplet2 users 4096 Apr 12 19:10 Maildir Really there's no better way than running "chmod -R g=u /home/ximplet2/Maildir" and "chmod g+s /home/ximplet2/Maildir" for every user? Really?? I read that, before v.2, Dovecot had a "umask" option to do precisely want I need, but it was removed. How are we supposed to use ACL with system users nowadays? Rubeno P.S: my doveconf -n: # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.4.0-119-generic x86_64 Ubuntu 16.04.4 LTS auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain mail_access_groups = kundividantoj mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = acl managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace { list = yes location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/Komunujo/%%n prefix = Komunujo/%%n/ subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Malnetujo { auto = subscribe comment = Mesaĝoj ne finitaj nek senditaj special_use = \Drafts } mailbox Rubujo { auto = subscribe autoexpunge = 120 days comment = Ĉi tien iras la forviŝitaj mesaĝoj special_use = \Trash } mailbox Senditujo { auto = subscribe special_use = \Sent } mailbox Spamujo { auto = create autoexpunge = 30 days comment = Mesaĝoj markitaj kiel ne deziritaj special_use = \Junk } prefix = subscriptions = yes type = private } passdb { driver = pam } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/kundividitaj/shared-mailboxes imapsieve_mailbox1_before = file:/etc/dovecot/sieve/imapsieve/report-spam.sieve imapsieve_mailbox1_causes = COPY FLAG imapsieve_mailbox1_name = Spamujo imapsieve_mailbox2_before = file:/etc/dovecot/sieve/imapsieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spamujo imapsieve_mailbox2_name = * sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve/final sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.debug sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.debug sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = mode = 0777 user = } } ssl = required ssl_cert = </etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lda { mail_plugins = acl sieve } protocol imap { mail_plugins = acl imap_acl imap_sieve }

2 2

Re: two unrelated issues, lastlogin, and an out of memory fatal error
by David Mehler 13 Apr '18

13 Apr '18

Hello Aki and everyone, "Increase memory, your cache takes more memory than you have anticipated." What setting do I need to update in dovecot? I hope your not talking about the vps it has 4GB of ram. Thanks. Dave. On 4/12/18, Reio Remma <reio(a)mrstuudio.ee> wrote: > Hey, > > maybe it's like Aki said, you need more memory. :) Other than that I > can't think of anything. :/ > > Good luck, > Reio > > On 12.04.18 2:42, David Mehler wrote: >> Hello, >> >> Thanks a lot. That did it. >> >> Do you have any idea as to my other issue, the fatal out of memory one? >> >> Thanks. >> Dave. >> >> >> On 4/11/18, Reio Remma <reio(a)mrstuudio.ee> wrote: >>> Hello, try: >>> >>> SELECT userid, FROM_UNIXTIME(last_login) FROM users; >>> >>> Reio >>> >>> On 11.04.2018 21:39, David Mehler wrote: >>>> Hi, >>>> >>>> Can I get the database display to display those timestamps in a >>>> particular format? >>>> >>>> Thanks. >>>> Dave. >>>> >>>> >>>> On 4/11/18, Reio Remma <reio(a)mrstuudio.ee> wrote: >>>>> On 11.04.18 18:23, David Mehler wrote: >>>>>> Hello Aki, >>>>>> >>>>>> Thanks for your suggestion. I followed it and the wiki at: >>>>>> >>>>>> https://wiki.dovecot.org/Plugins/LastLogin >>>>>> >>>>>> Good news, I get a record in the users table, with the username that >>>>>> just logged in. This is good. Bad news is I got unexpected output >>>>>> from >>>>>> the last_login time stamp. Here's the table and the user: >>>>>> >>>>>> mysql> describe users; >>>>>> +------------+--------------+------+-----+---------+-------+ >>>>>> | Field | Type | Null | Key | Default | Extra | >>>>>> +------------+--------------+------+-----+---------+-------+ >>>>>> | userid | varchar(255) | NO | PRI | NULL | | >>>>>> | last_login | int(11) | YES | | NULL | | >>>>>> +------------+--------------+------+-----+---------+-------+ >>>>>> 2 rows in set (0.00 sec) >>>>>> >>>>>> mysql> select * from users; >>>>>> +------------------------+------------+ >>>>>> | userid | last_login | >>>>>> +------------------------+------------+ >>>>>> | user(a)domain.com | 1523459718 | >>>>>> +------------------------+------------+ >>>>>> 1 row in set (0.01 sec) >>>>>> >>>>>> >>>>>> The issue is the 1523459718 I was expecting something like a time >>>>>> stamp. Is this fixable? Also, can I use last_login to see on which IP >>>>>> the user last logged in from? >>>>> SELECT FROM_UNIXTIME(1523459718) >>>>> >>>>> Maybe that will help? >>>>> >>>>> Good luck, >>>>> Reio >>>>> >>> > > > -- > Tervitades > Reio Remma > > > MR Stuudio 25 aastat > > *MR Stuudio OÜ* > Tondi 17b, 11316, Tallinn > Tel +372 650 4808 > Mob +372 56 22 00 33 > reio(a)mrstuudio.ee > www.mrstuudio.ee > > > >

1 0

Re: lda fails in parse_angle_addr if sieve is enabled
by Stephan Bosch 12 Apr '18

12 Apr '18

Op 12-4-2018 om 15:52 schreef Leo Gaspard: > Here are the first two headers of the mail you just sent, delivered with > the rolled-back-into dovecot 2.3.0.1: > > Return-Path: stephan(a)rename-it.nl > Delivered-To: dovecot(a)leo.gaspard.io > > Does that clear the facts? The Return-Path appears to not have <>, which > appears to be opposed to RFC5322. So I guess dovecot could as before > accept it, and a bug should be reported upstream (I guess to opensmtpd, > as rspamd should not touch the Return-Path) so that it puts the expected > <> around the address. What do you think about this? Yes, I will make Dovecot more lenient in this regard. Regards, Stephan. > > On 04/12/2018 12:24 PM, Stephan Bosch wrote: >> Hi, >> >> This code path is only executed when there is a return-path header. >> Given the fact that this fails consistently, can you provide an example >> of a message successfully delivered using an older version of Dovecot; >> i.e., as it is stored in the mailbox? There should be a return-path >> header there. >> >> Alternatively, you could temporarily wrap dovecot-lda in a shell script >> that copies the message to some file you can read after. >> >> I just need one example to confirm my suspicions. >> >> Regards, >> >> >> Stephan. >> >> >> Op 12-4-2018 om 11:54 schreef Leo Gaspard: >>> (sorry for the absence of In-Reply-To, I could neither find it on the ML >>> interface nor figure out a way to customize it in Thunderbird, and am >>> not subscribed) >>> >>> Just wanted to chime in to say I've hit the same issue with the upgrade >>> from 2.3.0.1 to 2.3.1. My setup is an opensmtpd sending mail to rspamd, >>> that then delivers to dovecot LDA. >>> >>> In the logs, I see (slightly reformated and censored): >>> >>> Panic: file message-address.c: line 147 (parse_angle_addr): assertion >>> failed: (*ctx->parser.data == '<') >>> Error: Raw backtrace: >>> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] >>> -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] >>> -> >>> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(i_fatal+0) […] >>> -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] >>> -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] >>> -> >>> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(message_address_parse_path+[…]) >>> >>> […] >>> -> >>> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot-lda.so.0(mail_deliver_get_return_address+[…]) >>> >>> […] >>> -> /etc/dovecot/modules/lib90_sieve_plugin.so(+[…]) […] >>> -> >>> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot-lda.so.0(mail_deliver+[…]) >>> >>> [0x7f04e2d08e20] >>> -> /nix/store/[…]-dovecot-2.3.1/libexec/dovecot/deliver(main+[…]) […] >>> -> >>> /nix/store/[…]-glibc-2.26-131/lib/libc.so.6(__libc_start_main+[…]) […] >>> -> /nix/store/[…]-dovecot-2.3.1/libexec/dovecot/deliver(_start+[…]) […] >>> >>> For some reason there are not many symbols, but hope that helps!

1 0

Re: lda fails in parse_angle_addr if sieve is enabled
by Stephan Bosch 12 Apr '18

12 Apr '18

Hi, This code path is only executed when there is a return-path header. Given the fact that this fails consistently, can you provide an example of a message successfully delivered using an older version of Dovecot; i.e., as it is stored in the mailbox? There should be a return-path header there. Alternatively, you could temporarily wrap dovecot-lda in a shell script that copies the message to some file you can read after. I just need one example to confirm my suspicions. Regards, Stephan. Op 12-4-2018 om 11:54 schreef Leo Gaspard: > (sorry for the absence of In-Reply-To, I could neither find it on the ML > interface nor figure out a way to customize it in Thunderbird, and am > not subscribed) > > Just wanted to chime in to say I've hit the same issue with the upgrade > from 2.3.0.1 to 2.3.1. My setup is an opensmtpd sending mail to rspamd, > that then delivers to dovecot LDA. > > In the logs, I see (slightly reformated and censored): > > Panic: file message-address.c: line 147 (parse_angle_addr): assertion > failed: (*ctx->parser.data == '<') > Error: Raw backtrace: > /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] > -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] > -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(i_fatal+0) […] > -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] > -> /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(+[…]) […] > -> > /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot.so.0(message_address_parse_path+[…]) > […] > -> > /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot-lda.so.0(mail_deliver_get_return_address+[…]) > […] > -> /etc/dovecot/modules/lib90_sieve_plugin.so(+[…]) […] > -> > /nix/store/[…]-dovecot-2.3.1/lib/dovecot/libdovecot-lda.so.0(mail_deliver+[…]) > [0x7f04e2d08e20] > -> /nix/store/[…]-dovecot-2.3.1/libexec/dovecot/deliver(main+[…]) […] > -> /nix/store/[…]-glibc-2.26-131/lib/libc.so.6(__libc_start_main+[…]) […] > -> /nix/store/[…]-dovecot-2.3.1/libexec/dovecot/deliver(_start+[…]) […] > > For some reason there are not many symbols, but hope that helps!

1 0

lda fails in parse_angle_addr if sieve is enabled
by Bernard Spil 12 Apr '18

12 Apr '18

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e \"/usr/local/libexec/dovecot/deliver -d %{user.username}\"" %{user.username} is the local user after virtusers, aliases etc. verified using a shell wrapper and capturing the username. conf.d/15-lda.conf protocol lda { mail_plugins = $mail_plugins sieve } maillog: Apr 8 19:36:54 email smtpd[6390]: smtp-in: Accepted message 9db769b1 on session 81939f0d30337a47: from=<user1(a)example.org>, to=<user2(a)example.net>, size=2871, ndest=1, proto=ESMTP Apr 8 19:36:54 email smtpd[6390]: smtp-in: Closing session 81939f0d30337a47 Apr 8 19:36:55 email dovecot: lda(user2)<21091><Ljv6JzdTylpjUgAAWr0fMA>: Panic: file message-address.c: line 147 (parse_angle_addr): assertion failed: (*ctx->parser.data == '<') Apr 8 19:36:55 email smtpd[6390]: delivery: TempFail for 9db769b13edef5a7: from=<user1(a)example.org>, to=<user2(a)example.net>, user=bernard, method=mda, delay=1s, stat=Error ("") Apr 8 19:36:57 email smtpd[6390]: smtp-out: Closing session 81939f0c09f5140b: 1 message sent. Apr 8 19:37:04 email dovecot: lda(user2)<21102><vAChMkBTylpuUgAAWr0fMA>: Panic: file message-address.c: line 147 (parse_angle_addr): assertion failed: (*ctx->parser.data == '<') Apr 8 19:37:04 email smtpd[6390]: delivery: TempFail for 9db769b13edef5a7: from=<user1(a)example.org>, to=<user2(a)example.net>, user=bernard, method=mda, delay=10s, stat=Error ("") Removing sieve from mail_plugins configuration and restarting Apr 8 19:37:32 email dovecot: master: Warning: Killed with signal 15 (by pid=21106 uid=0 code=kill) Apr 8 19:37:32 email dovecot: imap(user2)<21085><WGCXullpKzasEQIC>: Server shutting down. in=774 out=5373 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Apr 8 19:37:32 email dovecot: master: Dovecot v2.3.1 (8e2f634) starting up for imap, lmtp, sieve Apr 8 19:37:35 email dovecot: lda(user2)<21134><tNPZHl9TylqOUgAAWr0fMA>: msgid=<32984450d041e5c2f887bed5f6512c92(a)example.org>: saved mail to INBOX Apr 8 19:37:35 email smtpd[6390]: delivery: Ok for 9db769b13edef5a7: from=<user1(a)example.org>, to=<user2(a)example.net>, user=user2, method=mda, delay=41s, stat=Delivered Mail gets delivered. Don't understand why it is looking for a <>-address if sieve is enabled. Cheers, Bernard Spil.

2 6

two unrelated issues, lastlogin, and an out of memory fatal error
by David Mehler 11 Apr '18

11 Apr '18

Hello, I've got a few misc issues that I'm trying to get a handle on. I'm having what is probably a simple error with last logins. It's not working, unable to write values to the database. Here's the log lines: 2018-04-10 10:43:34 imap-login: Info: Login: user=<user(a)domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=75934, TLS, session=<db0EjH9pOix/AAAB> 2018-04-10 10:43:34 imap(user(a)domain.com)<75934><db0EjH9pOix/AAAB>: Error: last_login_dict: Failed to write value for user user(a)domain.com: dict-server returned failure: sql dict: commit failed: Field 'name' doesn't have a default value (reply took 0.013 secs (0.000 in dict wait, 0.012 in other ioloops, 0.000 in locks, async-id reply 0.002 secs ago, started on dict-server 0.005 secs ago, took 0.005 secs)) Here's an excerpt from my dovecot-dict-sql.conf.ext file: map { pattern = shared/last-login/$user table = accounts value_field = last_login value_type = uint fields { username = $user } } and the relevant database table: describe accounts; +------------+------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+------------------+------+-----+---------+----------------+ | id | int(10) unsigned | NO | PRI | NULL | auto_increment | | name | varchar(255) | NO | | NULL | | | username | varchar(64) | NO | MUL | NULL | | | domain | varchar(255) | NO | MUL | NULL | | | password | varchar(255) | NO | | NULL | | | quota | int(10) unsigned | YES | | 0 | | | enabled | tinyint(1) | YES | | 0 | | | sendonly | tinyint(1) | YES | | 0 | | | last_login | int(11) | YES | | NULL | | Second issue, I've used imapsync to download my gmail messages to dovecot. I am atempting to access these messages and getting: 2018-04-08 11:11:58 indexer-worker(user(a)domain.com)<44193><4GzoqFdpisJ/AAAB:StoZDD4xylqhrAAA0J78UA>: Info: Indexed 0 messages in INBOX 2018-04-08 11:11:58 indexer-worker(user(a)domain.com)<44193><4GzoqFdpisJ/AAAB:0AaXFD4xylqhrAAA0J78UA>: Info: Indexed 0 messages in INBOX 2018-04-08 11:11:58 indexer-worker(user(a)domain.com)<44193><4GzoqFdpisJ/AAAB:CP3TIT4xylqhrAAA0J78UA>: Info: Indexed 0 messages in INBOX 2018-04-08 11:11:58 indexer-worker(user(a)domain.com)<44193><4GzoqFdpisJ/AAAB:eNEWMT4xylqhrAAA0J78UA>: Info: Indexed 0 messages in INBOX 2018-04-08 11:15:28 imap(user(a)domain.com)<21374><4GzoqFdpisJ/AAAB>: Fatal: block_alloc(8388608): Out of memory 2018-04-08 11:15:28 imap(user(a)domain.com)<21374><4GzoqFdpisJ/AAAB>: Fatal: master: service(imap): child 21374 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) when I atempt to do so. For completeness the imapsync command I used was: imapsync --host1 imap.gmail.com --user1 Username --password1 Password --host2 localhost --user2 username --password2 Password --ssl1 --useheader 'Message-Id' --regextrans2 's/\[Gmail\]/user\@domain/' Any help appreciated on either issue. Thanks. Dave. doveconf -n # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p4 amd64 # Hostname: localhost auth_cache_size = 24 M auth_cache_ttl = 18 hours auth_default_realm = domain.com auth_mechanisms = plain login dict { acl = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext lastlogin = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_gid = 999 first_valid_uid = 999 hostname = xxxx.xxxx.xxxx imap_idle_notify_interval = 10 mins last_valid_gid = 999 last_valid_uid = 999 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = 127.0.0.1 xxx.xxx.xxx.xxx log_path = /var/log/dovecot/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = vmail mail_gid = vmail mail_home = /home/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs mail_plugins = acl mail_log notify quota trash virtual welcome zlib mail_privileged_group = vmail mail_server_admin = mailto:postmaster@davemehler.com mail_uid = vmail mailbox_idle_check_interval = 59 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 spamtest spamtestplus virustest editheader imapflags notify imapsieve vnd.dovecot.imapsieve namespace { location = maildir:/home/vmail/public/:LAYOUT=fs:CONTROL=~/mail/public:INDEX=~/mail/public mailbox office { auto = subscribe comment = Public Folder for message sharing } prefix = public/ separator = / subscriptions = yes type = public } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } mailbox virtual/All { comment = All my messages special_use = \All } prefix = separator = / type = private } namespace virtual { location = virtual:/usr/local/etc/dovecot/virtual:INDEX=~/virtual:CONTROL=~/virtual prefix = virtual/ separator = / } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300 acl_globals_only = yes acl_shared_dict = proxy::acl fts = lucene fts_autoindex = yes fts_autoindex_max_recent_msgs = 80 fts_index_timeout = 90 fts_lucene = whitespace_chars=@. normalize no_snowball imapsieve_mailbox1_before = file:/home/vmail/sieve/global/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/home/vmail/sieve/global/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = proxy::lastlogin last_login_key = last-login/%n mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = dict:User quota::proxy::quota quota_exceeded_message = Storage quota for this account has been exceeded, please try again later. quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = true quota_warning = storage=100%% quota-exceeded 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u quota_warning5 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_before = /home/vmail/sieve/before.d sieve_default = /home/vmail/sieve/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +spamtest +spamtestplus +virustest +editheader sieve_global_dir = /home/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.environment sieve_max_redirects = 30 sieve_max_script_size = 1M sieve_pipe_bin_dir = /home/vmail/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_user_log = /home/vmail/sieve/sieve_error.log sieve_virustest_status_header = X-Virus-Scan: Found to be (.+)\. sieve_virustest_status_type = text sieve_virustest_text_value1 = clean sieve_virustest_text_value5 = infected trash = /usr/local/etc/dovecot/trash.conf welcome_script = welcome %u postmaster@%d welcome_wait = yes } postmaster_address = postmaster@xxx protocols = imap lmtp sieve sendmail_path = /usr/local/sbin/sendmail service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } user = root } service imap-login { inet_listener imap { address = 127.0.0.1 } inet_listener imaps { address = xxx.xxx.xxx.xxx port = 993 ssl = yes } } service imap-postlogin { executable = script-login /usr/local/etc/dovecot/trackauth.sh user = vmail } service imap { executable = imap imap-postlogin } service lmtp { executable = lmtp unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } service welcome { executable = script /usr/local/etc/dovecot/welcome.sh unix_listener welcome { user = vmail } user = vmail } ssl = required ssl_cert = </usr/local/etc/ssl/acme/davemehler.com/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 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 userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { info_log_path = /var/log/dovecot/dovecot-lmtp.log log_path = /var/log/dovecot/dovecot-lmtp-errors.log mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol lda { mail_plugins = acl mail_log notify quota trash virtual welcome zlib sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl mail_log notify quota trash virtual welcome zlib imap_acl imap_quota imap_sieve imap_zlib last_login fts fts_lucene } protocol sieve { info_log_path = /var/log/dovecot/dovecot-sieve.log log_path = /var/log/dovecot/dovecot-sieve-errors.log }

4 4

dovecot, imap sieve, roundcube markasjunk2 plugin
by David Mehler 10 Apr '18

10 Apr '18

Hello, Does anyone have the above combination going? Per the wiki: https://wiki.dovecot.org/HowTo/AntispamWithSieve I have configured Dovecot for imap sieve and rspamd setting up the learn sieve and shell scripts. This is working. Now i'd like to integrate roundcube's markasjunk2 plugin. Looking at it's config file I am uncertain as to which options to enable. If anyone has a working markasjunk2 roundcube config that works with dovecot and imap sieve i'd appreciate seeing it. Thanks. Dave.

1 0

IMAP_ID_LOG
by j.emerlik 10 Apr '18

10 Apr '18

Hi, there in configuration is possibile to set imap_id_log for logging Client ID e.g.: ID sent: name=Thunderbird, version=52.7.0. Is possible to set same but for POP3 or SMTP Auth ? Ideally, it would be possible to log in to the database e.g. using postlogin script. Regards, MattX

3 3

Filesystem level backups?
by Steve Atkins 09 Apr '18

09 Apr '18

Up until now I've been backing up my IMAP server by taking an atomic snapshot of the entire VM, so I've not really had to worry about it. I'm moving to hosting where I have neither VM snapshots nor a filesystem that can take snapshots, so I need to think about consistent backups a bit more. Will a simple backup of all the files of an multi-dbox give me a consistent state when I recover, or do I need to do something (e.g. lock writes to the mailbox) while I run a backup? (I could use doveadm backup if I were backing up to local storage I controlled, but I'm pushing it to offsite buckets so I'd prefer to avoid backing up the entire thing locally, then copying that offsite). Cheers, Steve

4 5

Raw Backtrace Error when backing up specific user
by Marius Fassbender 09 Apr '18

09 Apr '18

Hi, probably since the update to 2.3.1 I can't backup a specific users mailbox. For backup I use the command 'dsync -o plugin/quota= -f -u user@domain backup dbox:/backup/dir' When I execute this command with the -D option, I get to see (above only Debug messages) dsync(user@domain): Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(user@domain): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xcc724) [0x7f0f15364724] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0f1536476a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0f152d524b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x566ac) [0x7f0f156686ac] -> doveadm(dsync_mailbox_import_attribute+0x4d) [0x5581a663bf4d] -> doveadm(dsync_brain_sync_mails+0x2ef) [0x5581a66377ff] -> doveadm(dsync_brain_run+0x2b0) [0x5581a6632e90] -> doveadm(+0x2960c) [0x5581a661a60c] -> doveadm(+0x2b4f7) [0x5581a661c4f7] -> doveadm(+0x2c0dc) [0x5581a661d0dc] -> doveadm(doveadm_mail_try_run+0x205) [0x5581a661da75] -> doveadm(main+0x475) [0x5581a660cce5] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0f14ca3c05] -> doveadm(+0x1be65) [0x5581a660ce65] cancelled my dovecot -n output: # 2.3.1 (0580a21bf): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) xfs doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem auth_cache_negative_ttl = 0 auth_cache_size = 100 M auth_master_user_separator = * auth_mechanisms = login plain auth_verbose = yes auth_verbose_passwords = sha1:16 deliver_log_format = msgid=%m from=%f subject=%s psize=%p status=%$ first_valid_gid = 5000 first_valid_uid = 5000 hostname = imap_capability = +XLIST imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 5000 last_valid_uid = 5000 lmtp_rcpt_check_quota = yes lmtp_save_to_detail_mailbox = yes mail_attachment_dir = /storage/mail/attachments mail_attachment_hash = %{sha512} mail_gid = 5000 mail_home = /storage/mail/settings/%Ld/%Ln mail_location = sdbox:/storage/mail/mails/%Ld/%Ln mail_plugins = zlib quota acl listescape fts fts_lucene mail_server_admin = mailto:postmaster@domain mail_uid = 5000 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 imapsieve vnd.dovecot.imapsieve namespace { list = children location = sdbox:/storage/mail/mails/%%d/%%n prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Archive { special_use = \Archive } mailbox Archives { special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/storage/mail/settings/global-acls:cache_secs=300 acl_shared_dict = file:/storage/mail/settings/shared-mailboxes fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. imapsieve_mailbox1_before = file:/usr/lib64/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/usr/lib64/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_log_fields = uid box msgid size subject quota = dict:User quota::file:%h/dovecot-quota quota_grace = 5%% quota_rule = Trash:storage=+5%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:%h/sieve;active=%h/.dovecot.sieve sieve_execute_bin_dir = /usr/lib64/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute sieve_pipe_bin_dir = /usr/lib64/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster@domain protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { group = dovemail mode = 0600 user = dovemail } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = dovemail } user = dovecot } ssl = required ssl_cert = </etc/pki/tls/certs/cert.cer ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = master_user=%u driver = ldap } protocol lmtp { mail_plugins = zlib quota acl listescape fts fts_lucene sieve postmaster_address = postmaster@domain } protocol imap { mail_plugins = zlib quota acl listescape fts fts_lucene imap_acl imap_quota imap_sieve imap_zlib } I tried to rebuild the settings files of this mailbox by deleting them and restart the service but this didnt help. A reboot did neither. I dont know where to start fixing this problem, does anyone has an advice? Thanks in advance

1 0

Re: 2.3.1 Replication is throwing scary errors
by Reuben Farrelly 08 Apr '18

08 Apr '18

Hi, [Formatting is a bit rough, replying from a trimmed digest email] > Message: 1 > Date: Fri, 6 Apr 2018 15:04:35 +0200 > From: Michael Grimm <trashcan(a)ellael.org> > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: 2.3.1 Replication is throwing scary errors > Message-ID: <E7E7A927-68F8-443F-BA59-E66CED8FE878(a)ellael.org> > Content-Type: text/plain; charset=utf-8 > > Reuben Farrelly wrote: >> From: Michael Grimm <trashcan(a)ellael.org> > >>> [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.] >>> I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows: >>> | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ >>> no activity for 600 seconds (last sent=mail_change, last recv=mail_change (EOL)) >>> | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ >>> (send=changes recv=mail_requests) >>> [?] >>> | Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ >>> no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) >>> | Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ >>> (send=mails recv=recv_last_common) >>> I cannot see in my personal account any missing replications, *but* I haven't tested this thoroughly enough. I do have customers being serviced at these productive servers, *thus* I'm back to 2.2.35 until I do understand or have learned what is going on. > > In my reply to this statement of mine I mentioned that I have seen those timeouts quite some times during the past year. Thus, I upgraded to 2.3.1 again, and boom: after some hours I ended up in hanging processes [1] like (see Remko's mail in addition) ... > > doveadm-server: [IP4/6 <USER1> SOME/MAILBOX import:0/0] (doveadm-server) > > ? at server2 paired with a file like ? > > -rw------- 1 vmail dovecot uarch 0 Apr 3 16:52 /home/to/USER1/.dovecot-sync.lock > > Corresponding logfile entries at server2 are like ? > > Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't lock /home/to/USER1/.dovecot-sync.lock: \ > fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds \ > (WRITE lock held by pid 51110) > > [1] Even stopping dovecot will not end those processes. One has to manually kill those before restarting dovecot. > > After one day of testing 2.3.1 with a couple of those episodes of locking/timeout, and now missing mails depending with server your MUA will connect to, I went back to 2.2.35. After two days at that version I never had such an episode again. > >> It's not just you. This issue hit me recently, and it was impacting >> replication noticeably. I am following git master-2.3 . > [...] >> There is also a second issue of a long standing race with replication >> occurring somewhere whereby if a mail comes in, is written to disk, is >> replicated and then deleted in short succession, it will reappear >> again to the MUA. I suspect the mail is being replicated back from >> the remote. A few people have reported it over the years but it's not >> reliable or consistent, so it has never been fixed. >> And lastly there has been an ongoing but seemingly minor issue >> relating to locking timing out after 30s particularly on the remote >> host that is being replicated to. I rarely see the problem on my >> local disk where almost all of the mail comes in, it's almost always >> occurring on the replicate/remote system. > > It might be time to describe our setups in order to possibly find common grounds that might trigger this issue you describe and Rimko and myself ran into as well. > > Servers: Cloud Instances (both identical), around 25ms latency apart. > Intel Core Processor (Haswell, no TSX) (3092.91-MHz K8-class CPU) > Both servers are connected via IPsec/racoon tunnels > OS: FreeBSD 11.1-STABLE (both servers) > Filesystem: ZFS > MTA: postfix 3.4-20180401 (postfix delivers via dovecot's LMTP) > IMAP: dovecot running in FreeBSD jails (issues with 2.3.1, fine with 2.2.35) > Replication: unsecured tcp / master-master > MUA: mainly iOS or macOS mail.app, rarely roundcube For me: Servers: Main: VM on a VMWare ESXi local system (light load), local SSD disks (no NFS) Redundant: Linode VM in Singapore, around 250ms away Also no NFS. Linode use SSDs for IO. There is native IPv6 connectivity between both VMs. As I am using TCPs I don't have a VPN between them - just raw IPv6 end to end. OS: Gentoo Linux x86_64 kept well up to date Filesystem: EXT4 for both MTA: Postfix 3.4-x (same as you) IMAP: Dovecot running natively on the machine (no jail/chroot) Replication: Secured TCP / master-master (but only one master is actively used for SMTP and MUA access) MUA: Thunderbird, Maildroid, MS Mail, Gmail client, Roundcube, LG Mail client on handset etc > I believe it is worthwhile to mention here that I run a poor man's fail-over approach (round-robin DNS) as follows: > > DNS: mail.server.tld resolves to one IP4 and one IP6 address of each server, thus 4 IP addresses in total For me I have a simple pair of servers that replicate mail to each other. Clients connect to the main server only, which is where mail comes in. The second one that experiences the problem with locking is only a redundant server which is a secondary MX, that only gets occasional SMTP deliveries from time to time. So the amount of replication back from the "secondary" is very minimal; the vast bulk of the replication is the primary replicating changes out. Reuben

1 0

changed behavior for dovecot-lda in 2.3.x
by Martin Waschbüsch 08 Apr '18

08 Apr '18

Hi all, Hey all, I upgraded to dovecot 2.3.1 (from 2.2.34) and noticed that the behavior for dovecot-lda changed. Apparently it no longer accepts -f "" or -f "<>? With 2.2.34, both were accepted now I get: root@mail:~# /usr/local/libexec/dovecot/dovecot-lda -f "<>" lda(root): Fatal: Invalid -f parameter: Null path not allowed or root@mail:~# /usr/local/libexec/dovecot/dovecot-lda -f "" lda(root): Fatal: Invalid -f parameter: Path is empty string I guess this must be a bug? I mean, envelope sender *must* be empty for bounces. Thanks, Martin

2 2

Can’t authenticate any users after upgrade.
by Kevin Cummings 08 Apr '18

08 Apr '18

I’m in the process of upgrading an old server from Fedora 21 to something more modern. Now, Dovecot won’t let any client login to get their email. PAM audit_log_acct_message() failed: Operation not permitted imap-login: Disconnected (AUTH failed, 2 attempts in 10 secs): user=<username>, method=PLAIN, rip=192.168.1.94 lip=192.168.1.94, TLS, session=<sessionid> # 2.3.1 (8e2f634): /etc/dovecot/dovecot.conf # OS: Linux 4.4.14-200.fc22.x86_64 x86_64 Fedora release 22 (Twenty Two) # Hostname: kjchome.homeip.net mbox_write_locks = fcntl 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 } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = PROFILE=SYSTEM ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } -- Kevin J. Cummings cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us kjchome(a)icloud.com Registered Linux User #1232 (http://www.linuxcounter.net/)

4 8

sharing a folder with all users in a domain
by David Mehler 08 Apr '18

08 Apr '18

Hello, I'm wanting to make a shared folder that anyone in a domain can get to, but not anyone in any other domain. Here's my dovecot shared namespace: namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h:INDEX=~/shared/%%u subscriptions = no list = yes } The dovecot-dict-sql.conf.ext file has: map { pattern = shared/shared-boxes/user/$to/$from table = user_shares value_field = dummy fields { from_user = $from to_user = $to } } map { pattern = shared/shared-boxes/anyone/$from table = anyone_shares value_field = dummy fields { from_user = $from } } and in my global acl file I have: shared/office@ user(a)domain.com lrwstipekxa shared/office@ user2(a)domain.com lrwstipekxa Thanks. Dave.

1 0

Warning message about quota.conf
by forums＠mehl-family.fr 06 Apr '18

06 Apr '18

Hi, In my maillog I see this warning message at every reception of e-mail: _STATUS=SENT (DELIVERED VIA DOVECOT SERVICE (DOVECONF: WARNING: /ETC/DOVECOT/CONF.D/90-QUOTA.CONF LINE 39: GLOBAL SETTING MAIL_PLUGINS WON'T CHAN....._ It is just a warning, the e-mail was delivered. I don't find where is the problem. Thank's.

1 0

Dsync from multiple IMAPs -- personal/local dovecot setup
by Kim ALLAMANDOLA 06 Apr '18

06 Apr '18

Hello list, new aspiring user here, if I'm not in the wright place sorry, I do not fund any other option for now... As from subject I'm looking for a *personal* *standalone* dovecot setup, especially I'm looking for a DSync from multiple IMAP accounts to a local maildir (to being compatible with notmuch). My actual mail setup is: OfflineIMAP that sync different mailboxes in a personal taxonomy ~/mail/$mailboxName/... and notmuch-emacs + various scripts as MUA. Local postfix just to avoid emacs freeze during send, muchsync to support It does work but is slow, buggy and sometime complicated to kept up to date (I have many homegrow spaghetti-code scripts and snippets in zsh, elisp, python etc stratified in years). My dream is switch to a local Dovecot that DSync from multiple IMAPs instead of OfflineIMAP, with sieve filters instead of homegrow scripts that wrap notmuch search --output=files | xargs ... For the MUA part I'd like to stick with notmuch. So my questions are: is possible to dsync from multiple IMAPS to a maildir? if yes does dovecot accept physical messages moves if I refile (archive etc) them via notmuch? Thanks! -- Kim ALLAMANDOLA

1 0

Re: 2.3.1 Replication is throwing scary errors
by Reuben Farrelly 06 Apr '18

06 Apr '18

Hi, > ------------------------------ > > Message: 2 > Date: Mon, 2 Apr 2018 22:06:07 +0200 > From: Michael Grimm <trashcan(a)ellael.org> > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: 2.3.1 Replication is throwing scary errors > Message-ID: <29998016-D62F-4348-93D1-613B13DA90DB(a)ellael.org> > Content-Type: text/plain; charset=utf-8 > > Hi > > [This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.] > > I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows: > > | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ > no activity for 600 seconds (last sent=mail_change, last recv=mail_change (EOL)) > | Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ > (send=changes recv=mail_requests) > [?] > | Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \ > no activity for 600 seconds (last sent=mail, last recv=mail (EOL)) > | Apr 2 18:59:03 <mail.err> server1.lan dovecot: doveadm: Error: Timeout during state=sync_mails \ > (send=mails recv=recv_last_common) > > I cannot see in my personal account any missing replications, *but* I haven't tested this thoroughly enough. I do have customers being serviced at these productive servers, *thus* I'm back to 2.2.35 until I do understand or have learned what is going on. > > Any ideas/feedback? > > FYI: I haven't seen such errors before. Replication has been working for years now, without any glitches at all. > > Regards, > Michael It's not just you. This issue hit me recently, and it was impacting replication noticeably. I am following git master-2.3 . Here's a last known reasonably good point in the tree where things worked quite well: EGIT_REPO_URI="https://github.com/dovecot/core.git" EGIT_BRANCH="master-2.3" EGIT_COMMIT="d9a1a7cbec19f4c6a47add47688351f8c3a0e372" So something after that (which could have gone into 2.3.1) has caused this. There is also a second issue of a long standing race with replication occurring somewhere whereby if a mail comes in, is written to disk, is replicated and then deleted in short succession, it will reappear again to the MUA. I suspect the mail is being replicated back from the remote. A few people have reported it over the years but it's not reliable or consistent, so it has never been fixed. And lastly there has been an ongoing but seemingly minor issue relating to locking timing out after 30s particularly on the remote host that is being replicated to. I rarely see the problem on my local disk where almost all of the mail comes in, it's almost always occurring on the replicate/remote system. For me it seems very unlikely that on an unloaded/idle VPS there are legitimate problems obtaining a lock in under 30s. This is with the default locking configuration. This problem started happening a lot more after the breakage in (1) above. These replication issues are similar, and could possibly be related. My system is Gentoo Linux keeping up with the latest kernels, and on an EXT4 FS. I am using TCPS based replication. My remote replicate is also on Gentoo Linux with EXT4 but on a Linode VPS (around 250ms latency away). I know in a later post you've said that you don't think it has anything to do with dovecot-2.3.1, so I'd be interested to know what really is the cause in that case. Reuben

4 3

Compatibility of Submission in 2.3.1
by Paul Hecker 06 Apr '18

06 Apr '18

Hi, Dovecot 2.3.1 (8e2f634). When using submission one client of mine can not send messages. Directly sending through exim works. Seems that dovecot is too picky or follow the RFC too precise here to be compatible. Here is the debug log (note the space between “From:" and "<user2(a)host.com>”): Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: Received new command: MAIL From: <user(a)host.com> Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: command MAIL; 501 reply: Submitted Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: command MAIL: Ready to reply Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: Trigger output Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: Timeout stop Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: Sending replies Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: command MAIL; 501 reply: Sent: 501 5.5.4 Invalid FROM: Missing '<' at beginning of path Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: command MAIL: Destroy Apr 6 12:02:08 mail dovecot: submission(user(a)host.com)<14972><ko4tJitpt9JYSSSC>: Debug: smtp-server: conn 22.73.xx.144:53943 [0]: command MAIL; 501 reply: Destroy Is there a chance that you will incorporate a fix (be more compatible but less stringent)? Thanks, Paul

3 3

dovecot welcome scripts for multiple domains
by David Mehler 06 Apr '18

06 Apr '18

Hello, I've got dovecot 2.3 going, and it uses welcome scripts successfully. My question is does anyone have a script that is multi-domain capable? Currently mine sends it's welcome message from say postmaster(a)domain1.com, well I've got five domains, can I set this script up so that it's smart about them? If user(a)domain3.com logs in it would send a message from postmaster(a)domain3.com? If anyone has any welcome scripts i'm curious to take a look. Thanks. Dave.

2 1

issue with sieve forwarding after upgrade to 0.5.1
by Christos Chatzaras 05 Apr '18

05 Apr '18

Finally I found a workaround to not depend on sendmail to forward messages using sieve: In postfix main.cf I have: authorized_submit_users = root, filter (I want only root and filter to use sendmail and block other users to send e-mails from system accounts. Only allow users to send e-mails from virtual accounts and after smtp authentication. Username filter is used for bogofilter and needs access to sendmail) And in dovecot.conf: submission_host = 138.201.248.xxx The same workaround maybe works for NoNewPrivileges too as the authorized_submit_users setting in postfix has similar result.

1 0

GFS2 writes extremely slow
by DurgaPrasad - DatasoftComnet 05 Apr '18

05 Apr '18

Hello all, We are facing extremely slow GFS2 issues in Redhat 7 64 bit. Backend is 16 Gbps FC SAN so no issues there. I have scoured the entire (anyways most of the) Internet and arrived at the following settings. mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes mmap_disable = yes lock_method = fcntl Did a systemctl restart dovecot and did not find any major improvement. Can you please help. Regards Durga Prasad --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1