February 2020 - dovecot

My sieve is failing
by ＠lbutlr 21 Feb '20

21 Feb '20

I have an active sieve file for my list account that alters the headers for this list (sets the reply-to address to the list instead of the poster) which is suddenly failing. require [ "regex", "variables", "fileinto", "envelope", "mailbox", "imap4flags", "editheader" ]; /* other stuff */ elsif header :contains "List-id" "dovecot.dovecot.org" { if header :matches "Reply-to" "*" { deleteheader "From"; addheader "From" "${1}"; deleteheader "Reply-To"; addheader "Reply-To" "dovecot(a)dovecot.org"; addheader "X-Covisp-Reply-To" "True"; } fileinto :create "dovecot"; stop;} And the trace file: 55: header test 55: starting `:contains' match with `i;ascii-casemap' comparator: 55: extracting `List-id' headers from message 55: matching value `Dovecot Mailing List <dovecot.dovecot.org>' 55: with key `dovecot.dovecot.org' => 1 55: finishing match with result: matched 55: jump if result is false 55: not jumping 56: header test 56: starting `:matches' match with `i;ascii-casemap' comparator: 56: extracting `Reply-to' headers from message 56: finishing match with result: not matched 56: jump if result is false 56: jumping to line 63 63: fileinto action 63: store message in mailbox `dovecot' 64: stop command; end all script execution ## Finished executing script '.active_sieve’ Neither the reply-to header nor the x- header are actually getting added, but the block is getting executed and the mail is filed in the right folder. In dovecot.conf I (still) have: managesieve_sieve_capability = editheader fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave

1 1

Test failure on ARM: backtrace_append
by Julien Lepiller 21 Feb '20

21 Feb '20

Hi, I am a packager in Guix and user of dovecot on an ARM server (armhf). The Guix package fails to build because of a test error (see the last lines of the full build log: https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3). As the name suggests, this is dovecot 2.3.9.3, the latest version. Previous versions built fine, as well as the same version on x86 and x86_64. Note that the build on guix's build farm was done in a qemu vm, but I got the same test failure on real hardware. I'm not sure what the best course of action is. Did I find a legitimate bug, or should I simply ignore that test for that architecture? Dovecot itself seems to be running fine when I ignore the tests. Thanks for any guidance you could provide!

2 8

How does dovecot determine users from /etc/passwd?
by Philip Colmer 20 Feb '20

20 Feb '20

We're using dovecot on a help desk ticketing system. The system doesn't perform any cleanup of IMAP mailboxes so we have a regular cronjob doing this: /usr/bin/doveadm flags add -A '\Deleted' SEEN SENTBEFORE 12w && /usr/bin/doveadm expunge -A DELETED MAILBOX '*' Recently, doveadm has been reporting this: doveadm(nobody): Error: User initialization failed: Namespace '': mkdir(/nonexistent/mail) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup)) doveadm(nobody): Error: User init failed doveadm(DEFAULT-CW-USER): Info: User no longer exists, skipping Indeed, using doveadm user "*" does include "nobody" in the list but I can't understand why. The mail group in /etc/group does not include "nobody" and there are users in /etc/passwd with similar attributes to "nobody" that do not appear in the list of users from doveadm. What can I do to tell doveadm to forget about "nobody"? Thanks. Philip

4 4

BUG: dsync and folder names with "@"
by spamvoll＠googlemail.com 20 Feb '20

20 Feb '20

Hello, dovecot version: 2.3.9.2 When I use dsync: /usr/bin/dsync -v -D -o plugin/quota= -f -u my(a)email.dom backup maildir:/tmp/mailbackup/Maildir it always stops when it comes to a folder with an "@" in its name. Error Message: Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID (maybe it was just deleted?) I dont know if it makes a difference, but my dovecot uses mdbox and the backup export is maildir. Hans

2 2

RE: Unknown setting error with dovecot-sql.conf.ext
by Andy Woolley 20 Feb '20

20 Feb '20

OMG, that was it, so sorry to have wasted your time. The text editor I am using (Ultraedit) is adding a BOM (Byte Order Marker) to the beginning of the file. I have disabled this in settings but it keeps doing it. Thank you so much for pointing me in the right direction. After removing the 3 invisible characters from the dovecot-sql.conf.ext file it magically worked. Andy -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi@open-xchange.com] Sent: 20 February 2020 11:26 To: Andy Woolley <andy(a)milonic.com> Subject: Re: Unknown setting error with dovecot-sql.conf.ext I am unable to reproduce the issue here, can you send me the file itself? Maybe it has some strange thing in it? On 20.2.2020 12.23, Andy Woolley wrote: > > doveconf -n > > # 2.3.9.2 (cf2918cac): /etc/dovecot/dovecot.conf > > # OS: Linux 5.4.19-200.fc31.x86_64 x86_64 Fedora release 31 (Thirty > One) > > # Hostname: data.tia3.com > > auth_mechanisms = plain login > > mail_location = /home/vmail/%d/%n > > mail_privileged_group = mail > > 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 > > } > > passdb { > > args = /etc/dovecot/dovecot-sql.conf.ext > > driver = sql > > } > > service auth-worker { > > user = vmail > > } > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0660 > > user = postfix > > } > > unix_listener auth-userdb { > > mode = 0600 > > user = vmail > > } > > user = dovecot > > } > > service imap-login { > > inet_listener imap { > > port = 143 > > } > > inet_listener imaps { > > port = 993 > > ssl = yes > > } > > } > > service lmtp { > > unix_listener lmtp { > > group = postfix > > mode = 0600 > > user = postfix > > } > > } > > service pop3-login { > > inet_listener pop3 { > > port = 110 > > } > > inet_listener pop3s { > > port = 995 > > ssl = yes > > } > > } > > ssl = required > > ssl_cert = </etc/letsencrypt/live/intelliset.co.uk/fullchain.pem > > ssl_cipher_list = PROFILE=SYSTEM > > ssl_key = # hidden, use -P to show it > > userdb { > > driver = passwd > > } > > userdb { > > args = /etc/dovecot/dovecot-sql.conf.ext > > driver = sql > > } > > > > > > > > > > dovecot-sql.conf.ext: > > driver = mysql > > connect = host=127.0.0.1 dbname=mail user=foo password=bar > > default_pass_scheme = SHA512-CRYPT > > password_query = SELECT email as user, password FROM users WHERE > email='%u'; > > > > > > > > > > Many thanks, > > Andy > > > > > > *From:*dovecot [mailto:dovecot-bounces@dovecot.org] *On Behalf Of *Aki > Tuomi > *Sent:* 20 February 2020 10:11 > *To:* Andy Woolley <andy(a)milonic.com <mailto:andy@milonic.com>>; > dovecot(a)dovecot.org <mailto:dovecot@dovecot.org> > *Subject:* Re: Unknown setting error with dovecot-sql.conf.ext > > > > > > On 20.2.2020 12.06, Andy Woolley wrote: > > Hi All, > > > > I am trying to install Dovecot connecting to MySQL and all seems to be > working until I try to send/receive. > > > > Im getting a Unknown setting error for anything that is inside > dovecot-sql.conf.ext > > > > dovecot-sql.conf.ext is inside /etc/dovecot and is referenced from > /etc/dovecot/conf.d/auth-sql.conf.ext > > > > The error I get is: > > > > auth: Fatal: sql /etc/dovecot/dovecot-sql.conf.ext: Error in > configuration file /etc/dovecot/dovecot-sql.conf.ext line 1: Unknown > setting: driver > > > > Can anybody help me? > > > > Andy > > > > Post 'doveconf -n' please and the contents of the sql.conf.ext file. > Mind passwords. > > Aki > > > > *From:*dovecot [mailto:dovecot-bounces@dovecot.org] *On Behalf Of *Aki > Tuomi > *Sent:* 20 February 2020 10:11 > *To:* Andy Woolley <andy(a)milonic.com>; dovecot(a)dovecot.org > *Subject:* Re: Unknown setting error with dovecot-sql.conf.ext > > > > > > On 20.2.2020 12.06, Andy Woolley wrote: > > Hi All, > > > > I am trying to install Dovecot connecting to MySQL and all seems > to be working until I try to send/receive. > > > > Im getting a Unknown setting error for anything that is inside > dovecot-sql.conf.ext > > > > dovecot-sql.conf.ext is inside /etc/dovecot and is referenced from > /etc/dovecot/conf.d/auth-sql.conf.ext > > > > The error I get is: > > > > auth: Fatal: sql /etc/dovecot/dovecot-sql.conf.ext: Error in > configuration file /etc/dovecot/dovecot-sql.conf.ext line 1: > Unknown setting: driver > > > > Can anybody help me? > > > > Andy > > > > Post 'doveconf -n' please and the contents of the sql.conf.ext file. > Mind passwords. > > Aki >

1 0

Unknown setting error with dovecot-sql.conf.ext
by Andy Woolley 20 Feb '20

20 Feb '20

Hi All, I am trying to install Dovecot connecting to MySQL and all seems to be working until I try to send/receive. I'm getting a "Unknown setting" error for anything that is inside dovecot-sql.conf.ext dovecot-sql.conf.ext is inside /etc/dovecot and is referenced from /etc/dovecot/conf.d/auth-sql.conf.ext The error I get is: auth: Fatal: sql /etc/dovecot/dovecot-sql.conf.ext: Error in configuration file /etc/dovecot/dovecot-sql.conf.ext line 1: Unknown setting: driver Can anybody help me? Andy

2 2

Flush userdb cache entry
by Tom Sommer 19 Feb '20

19 Feb '20

Hi all I have a problem when users change quota in SQL, the change is not reflected in Dovecot immediately so quota_warning is still triggered on some occasions. I think it's because the quota is stored in userdb, and there is no way to flush userdb cache? Is there a way to flush userdb entries? What controls userdb cache TTL/size? auth_cache entries? I can't seem to find any documentation on this, sadly :( Thanks -- Tom

1 1

Message-id parsing by sieve
by Russell King 19 Feb '20

19 Feb '20

Hi, I'm using Dovecot for my mail with pigeonhole's sieve extension, from debian stable (2.3.4.1 (f79e8e7e4)). One of the sieve stanzas that I use is for duplicate elimination: if duplicate { discard; stop; } This mostly works fine, but I seem to have trouble with some messages that come from certain domains where duplicates are not eliminated. >From /var/log/mail.log, I see: Feb 18 12:48:50 mail dovecot: lmtp(24320:linux@xxx.armlinux.org.uk): sieve: msgid=? <VI1PR04MB513558BF77192255CBE12102B0110(a)VI1PR04MB5135.eurprd04.prod.outlook.com>: stored mail into mailbox 'INBOX' Feb 18 12:49:42 mail dovecot: lmtp(24320:linux@xxx.armlinux.org.uk): sieve: msgid=<VI1PR04MB513558BF77192255CBE12102B0110(a)VI1PR04MB5135.eurprd04.prod.outlook.com>: stored mail into mailbox 'INBOX' The first was received direct from the recipient with a message-id line formatted thusly: Message-ID: <VI1PR04MB513558BF77192255CBE12102B0110(a)VI1PR04MB5135.eurprd04.prod.outlook.com> The second was received from the mailing list with a message-id line formatted thusly: Message-ID: <VI1PR04MB513558BF77192255CBE12102B0110(a)VI1PR04MB5135.eurprd04.prod.outlook.com> It would appear that the parsed message-id value that dovecot uses includes white-space (including newline characters). RFC5322 gives the message-id header format as: message-id = "Message-ID:" msg-id CRLF msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] It goes on to say: The message identifier (msg-id) itself MUST be a globally unique identifier for a message. and: Semantically, the angle bracket characters are not part of the msg-id; the msg-id is what is contained between the two angle bracket characters. However, it seems dovecot sieve is using the entire content of the msg-id, including CFWS, as the message id used for detecting duplicate messages. This seems wrong, and appears to lead to duplicates not being detected, and thus seems like a bug. Is there a workaround for this, and/or can it be changed? -- Russell King

2 1

Sieve junks mail script creating links
by ＠lbutlr 19 Feb '20

19 Feb '20

My Junk mailbox is still filling up with hard linked emails. There are some junk mails with over 3000 hard linked files and over half a million files in the .Junk/cur folder. I had a handy script to remove them all by doing a find for inodes and sorting the list by age and keeping the olds hard link and removing all the others, but I now can’t find it :/ so I have just taken to periodically nuking the entire folder, but I’d like to fix this. *everything is current on FreeBSD 12.1-RELEASE => dovecot.conf imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve => /usr/lib/dovecot/sieve/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}" ]; => /usr/lib/dovecot/sieve/sa-learn-spam.sh: #!/bin/sh exec /usr/local/bin/sa-learn -u ${1} —spam -- When the stars threw down their spears And watered heaven with their tears, Did He smile his work to see? Did He who made the Lamb make thee?

2 1

managesieve / sieve - append dot prefix on moving mails into folder
by Andre Hoepner - i.based: Systemhaus GmbH + Co. KG 18 Feb '20

18 Feb '20

Hello mailinglist-subscribers, i have an issue with the managesieve / sieve plugin in dovecot. We use roundcube as webmailer and if i define a new filter to move incoming mails directly into a subfolder i get the following sieve-code: require ["fileinto","imap4flags"]; # rule:[mail into folder] if allof (header :contains "from" "sender(a)domain.org") { fileinto "Foldername"; setflag "\\Seen"; } So anything seems to be right and there are no errors on creating the correct syntax. But if a mail comes from the named sender, sieve does not put the email in the folder "Foldername" but ".Foldername". It appends a dot (.) in front of the name and i have no idea, why this happens. There are no errors in logfile and all mails go into the .Folder. Maybe it is wrong separator for mailbox, at the moment there is no separator defined in "10-mail.conf" and we use "Maildir" as mail_location. I have also tried to change the target folder in sieve script an named him "INBOX/Monitoring" - as subfolder of INBOX but than i get an error in .dovecot.sieve.log with message: Invalid mailbox name: Name must not have '/' characters. I edited the new rule with roundcube / managesieve-plugin and maybe this needs separate configuration because of separator in foldernames? Please let me know if i should provide any extra information or dovecot configuration etc. best regards Andre Hoepner

3 3