March 2018 - dovecot - dovecot.org

recipient delimiter and sieve filters
by André Rodier 24 Mar '18

24 Mar '18

Dear all, I have found a way to automatically copy sent emails in the "Sent" folder, but I am not sure it is the simplest and more reliable way on the long term. I am open to suggestions if I miss a feature in Dovecot - or Postfix, that allows me to do this. I vaguely remember an SMTP extension that do that, but my memory could be wrong. First, I use "~" as a recipient delimiter. Then, I set up a postfix senders_bcc_map that add the ~Sent part: andre(a)homebox.space → bcc: andre~Sent(a)homebox.space It worked, except that the emails was marked as new. I tried first to add a global sieve filter like this: ---------------------------------------------------------------------- # Sieve script executed before for user require ["fileinto","imap4flags"]; # Move automatically copied emails to the sent folder # And mark them as read if header :contains "Delivered-To" "~Sent" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- But it did not work, so maybe there is a trick I am not aware of. If I use the "Received" header and a regex, it works ---------------------------------------------------------------------- require ["fileinto","imap4flags","regex"]; if header :regex "Received" "for <[a-z]+~Sent(a)homebox.space>;" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- This is working perfectly, but there is limitations, IMHO. - If the recipient delimiter is not compatible with a regex (e.g. "+"), then the script will probably fail. - Parsing every new email using a regular expression might not be the best option in term of system load. So, I finally use this: ---------------------------------------------------------------------- # Move automatically copied emails to the sent folder # And mark them as read require ["fileinto","imap4flags"]; if header :contains "Received" "~Sent" { setflag "\\Seen"; fileinto "Sent"; } ---------------------------------------------------------------------- My question is why the first one does not work? Does the email has been moved to the Sent folder, and dovecot sieve plugin is not able to find the email any more? Kind regards, André -- https://github.com/progmaticltd/homebox

2 2

lmtp service timeouting even after receiving full message
by Arkadiusz Miśkiewicz 23 Mar '18

23 Mar '18

I have a problem with some messages passed from exim to dovecot lmtp service: From exim debug: using socket /var/run/dovecot/lmtp LMTP<< 220 mbox8 ready LMTP>> LHLO mbox8... LMTP<< 250-mbox8 LMTP<< 250-STARTTLS LMTP<< 250-8BITMIME LMTP<< 250-ENHANCEDSTATUSCODES LMTP<< 250 PIPELINING LMTP>> MAIL FROM:... LMTP<< 250 2.1.0 OK LMTP>> RCPT TO:... LMTP<< 250 2.1.5 OK LMTP>> DATA LMTP<< 354 OK LMTP>> writing message and terminating "." cannot use sendfile for body: terminating dot wanted writing data block fd=6 size=6585 timeout=300 LMTP>> QUIT LMTP<< 421 4.4.2 mbox8 Disconnected client for inactivity now above "writting message and terminating" according to exim strace looks like this: 13413 22:07:24 write(2, " LMTP>> writing message and terminating \".\"\n", 45) = 45 <0.000018> 13413 22:07:24 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2705, ...}) = 0 <0.000025> 13413 22:07:24 write(2, "cannot use sendfile for body: terminating dot wanted\n", 53) = 53 <0.000022> 13413 22:07:24 lseek(3, 19, SEEK_SET) = 19 <0.000015> [...] 13413 22:07:24 write(2, "writing data block fd=6 size=6585 timeout=300\n", 46) = 46 <0.000019> 13413 22:07:24 alarm(300) = 0 <0.000013> 13413 22:07:24 write(6, "Return-path: [...] \nwrap\"><br></span></div>.\n", 6585) = 6585 <0.000023> and then exim waits for dovecot lmtp to say it accepted message but lmtp never does that. Isn't .\n always enough for dovecot to signal end of message? Because exim wrote full message to dovecot lmtp unix socket. Now the interesting this - exim does only one write() with 6585 bytes to write that message to lmtp. If exim needs more than one write() to do that (message is larger by some buffer) then it succeeds, dovecot accepts it. Could dovecot lmtp handling for single write() case be broken? dovecot 2.2.35 -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 4

Dovecot replication does not replicate subscription in shared mailboxes
by Ralf Becker 23 Mar '18

23 Mar '18

We use a pair of replicating Dovecot servers. If a user subscribes to a folder, shared by an other user, in one replica, that does not get replicated to the other node. Subscription of regular folders below INBOX seem to replicate correctly. Is that a general bug, a known problem or do we need to enable that somehow. Here's our configuration for the concerned namespace: namespace users { location = mdbox:%%h/mdbox:INDEXPVT=~/shared/%%u prefix = user/%%n/ separator = / subscriptions = no type = shared } I attached the full doveconf -n. Thanks for any points :) Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 0

How to stop sieve processing to skip sieve_after scripts ?
by Mr Nicolas Belan 23 Mar '18

23 Mar '18

Hello the list, I am trying to achieve filter processing using sieve, but i am not sure I can do what I want. I want to let the user decide to use my filtering script (sieve_after) or not.According to the documentation, i am trying to stop processing in user sieve script, but processing continue. I am using dovecot 2.2 (CentOS). My sieve configuration is:plugin { sieve = /var/vmail/%d/%n/%n.sieve sieve_before = /etc/dovecot/sieve/global-before sieve_after = /etc/dovecot/sieve/global [...]} 'sieve' is the filter script created by users. When trying to stop processing, it is generated by roundcube like:# rule:[deliver to mailbox] if anyof (true) { stop; } 'sieve_after' is the filter which handles the spam processing (fileinto Junk). But the processing continue until all sieve filters are processed: Mar 22 14:50:23 lda(user(a)example.com): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt=Mar 22 14:50:23 lda(user(a)example.com): Debug: Destination address: user(a)example.com (source: -a parameter) Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: Pigeonhole version 0.4.2 initializing Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: executed before user's personal Sieve script(1): /etc/dovecot/sieve/global-before Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: using the following location for user's Sieve script: /var/vmail/example.com/user/user.sieve;name=main script Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: executed after user's Sieve script(3): /etc/dovecot/sieve/global Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: opening script 1 of 3 from /etc/dovecot/sieve/global-before Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: loading script /etc/dovecot/sieve/global-before Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: script binary /etc/dovecot/sieve/global-before.svbin successfully loaded Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: binary save: not saving binary /etc/dovecot/sieve/global-before.svbin, because it is already stored Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: executing script from /etc/dovecot/sieve/global-before.svbin Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: opening script 2 of 3 from /var/vmail/example.com/user/user.sieve;name=main script Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: loading script /var/vmail/example.com/user/user.sieve;name=main script Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: script binary /var/vmail/example.com/user/user.svbin successfully loaded Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: binary save: not saving binary /var/vmail/example.com/user/user.svbin, because it is already stored Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: executing script from /var/vmail/example.com/user/user.svbin Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: opening script 3 of 3 from /etc/dovecot/sieve/global Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: loading script /etc/dovecot/sieve/global Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: script binary /etc/dovecot/sieve/global.svbin successfully loaded Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: binary save: not saving binary /etc/dovecot/sieve/global.svbin, because it is already stored Mar 22 14:50:23 lda(user(a)example.com): Debug: sieve: executing script from /etc/dovecot/sieve/global.svbin Mar 22 14:50:23 lda(user(a)example.com): Debug: Namespace : Using permissions from /var/vmail/example.com/user/Maildir: mode=0700 gid=default Mar 22 14:50:23 lda(user(a)example.com): Info: sieve: msgid=<cm.0045046409888.jyshukd.kidudykyhi.r(a)cmail19.com>: stored mail into mailbox 'Courrier indésirable' I would like to stop processing afterMar 22 14:50:23 lda(user(a)example.com): Debug: sieve: using the following location for user's Sieve script: /var/vmail/example.com/user/user.sieve;name=main scriptAt the end, I do not want mail to be delivered into Junk, but into INBOX.. Is it possible ? Perhaps a sieve, sieve2 setting exists ? (like sieve_before, sieve_before2 ...) Thank you for your help, ideas :) Best regards, Nicolas

3 5

limit pop login per user and per minute
by Markus Eckerl 23 Mar '18

23 Mar '18

Hi, like I have written in the subject line I want to limit the pop login per user and per minute. Currently I am having several customers which are fetching their email with popcon (MS Exchange). This has never been a problem. But... They all have got the same "technician" which take care of their systems. The problem is, that he misconfigured the servers of these customers. In detail: their servers are trying to fetch email every 2 - 5 seconds. For every email address. In the past I contacted the technician and told him about his mistake. He was not very helpful and simply told me that he is doing the same configuration since several years at all of his customer servers. Without problems. It is up to me to fix my problem myself. Well, I googled a lot but all I found is to limit for a specific IP or for a secific account. Both is not what I am looking for. Maybe someone can give me a hint? Thanks and kind regards Markus -- stairweb GmbH Firmensitz: Gutenbergstr. 8, 94036 Passau Telefon: +49 (0)851 / 20426650 Telefax: +49 (0)851 / 20426655 e-Mail: info(a)stairweb.de Internet: www.stairweb.de Registergericht: Amtsgericht Passau, HRB 6044 Geschäftsführer: Markus Eckerl, Karl Preißler, Alexander Lengl

4 4

why is dovecot "Allowing any password"
by mj 22 Mar '18

22 Mar '18

Hi, I noticed the following in the logs of our debian wheezy server: > Mar 21 07:13:47 mail dovecot: auth: Debug: ldap(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): bind search: base=CN=Users, DC=samba, DC=company, DC=com filter=(&(objectclass=person)(sAMA > ccountName=username)(!(userAccountControl=514))) > Mar 21 07:13:47 mail dovecot: auth: Debug: ldap(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): result: uid=username; uid unused > Mar 21 07:13:47 mail dovecot: auth: Debug: ldap(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): result: uid=username > Mar 21 07:13:48 mail dovecot: auth: ldap(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): invalid credentials (given password: invalid_password) > Mar 21 07:13:48 mail dovecot: auth: Debug: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): lookup > Mar 21 07:13:48 mail dovecot: auth: Debug: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): allow_nets: Matching for network 127.0.0.1/32 > Mar 21 07:13:48 mail dovecot: auth: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): allow_nets check failed: IP not in allowed networks > Mar 21 07:13:48 mail dovecot: auth: Debug: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): Allowing any password > Mar 21 07:13:54 mail dovecot: auth: Debug: auth client connected (pid=6174) The line second last line "Allowing any password" comes as a surprise..? Why would dovecot Allow any password..? We had the following bit in our config, but I removed it now: > #passdb { > # driver = static > # args = nopassword=y allow_nets=127.0.0.1/32 > #} Could anyone expain the "Allowing any password"? And lastly our current doveconf -n: > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-5-amd64 x86_64 Debian 7.11 xfs > auth_debug = yes > auth_debug_passwords = yes > auth_failure_delay = 10 secs > auth_master_user_separator = * > auth_mechanisms = plain login > auth_username_format = %Ln > auth_verbose = yes > auth_verbose_passwords = plain > deliver_log_format = %f | %s | msgid=%m: %$ > disable_plaintext_auth = no > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > login_greeting = Dovecot ready. > mail_gid = vmail > mail_location = maildir:/var/vmail/%Ln/Maildir:LAYOUT=fs:DIRNAME=mAildir > mail_plugins = acl lazy_expunge zlib quota mail_log notify > mail_uid = vmail > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave > namespace { > list = children > location = maildir:/var/vmail/%%u/Maildir:LAYOUT=fs:DIRNAME=mAildir:INDEX=/var/vmail/%u/shared/%%u > prefix = shared/%%n/ > separator = / > subscriptions = no > type = shared > } > namespace inbox { > inbox = yes > location = > mailbox "Deleted items" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent items" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > mailbox inbox { > auto = subscribe > } > prefix = > 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 > acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append > mail_log_fields = uid box msgid from subject > quota = maildir > quota_rule = ?:storage=5G > quota_rule2 = Trash:storage=+100M > quota_warning = storage=97%% quota-warning 97 %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=80%% quota-warning 80 %u > quota_warning6 = -storage=100%% quota-warning below %u > sieve = ~/.dovecot.sieve > sieve_default = /var/lib/dovecot/default.sieve > sieve_dir = ~/sieve > } > protocols = imap lmtp sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = vmail > mode = 0666 > user = vmail > } > } > service imap-login { > process_limit = 500 > process_min_avail = 2 > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > unix_listener quota-warning { > user = vmail > } > user = dovecot > } > shutdown_clients = no > ssl_ca = </etc/ssl/letsencrypt/fullchain.pem > ssl_cert = </etc/ssl/letsencrypt/cert.pem > ssl_key = </etc/ssl/letsencrypt/key.pem > ssl_protocols = !SSLv2 !SSLv3 > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%n allow_all_users=yes > driver = static > } > verbose_proctitle = yes > protocol lda { > mail_plugins = acl lazy_expunge zlib quota mail_log notify sieve quota > } > protocol imap { > imap_max_line_length = 2 M > mail_max_userip_connections = 30 > mail_plugins = acl lazy_expunge zlib quota mail_log notify imap_quota imap_acl > } MJ

4 16

dovecot-uidlist is not up-to-date
by Dmitry Filonov 22 Mar '18

22 Mar '18

Hi, Am using dovecot-2.2.10-8 on Centos-7 and everything seemed to be totally fine for many years. Now am trying to migrate our on-premises mail server to the cloud and I had to get some statistics. I was doing that using the doveadm utility. Unfortunately I found that the numbers don't match if I check the real messages in my Maildirs. For some account doveadm was reporting number of messages but that account didn't have any messages stored at all. So I looked a bit further and found that doveadm utility reports data form indexes and indexes are built using dovecot-uidlist data. For quite some folders these files have way more data than actual mailbox has. For example, my personal Inbox has 569 messages but dovecot-uidlist has 716 entries. I don't know when and how that happened but this happens a lot on many different mailboxes on my server. I never touched dovecot-uidlist files outside of dovecot. I might have removed messages from Maildirs though, but not at this scale. Now the question is if there's any way to tell dovecot to rebuild dovecot-uidlist files using actual Maildir data. I don't want to remove dovecot-uidlist files as this triggers the whole mailbox being re-downloaded by the imap client. With some accounts having over 100Gb of mail this is too much of a hassle. I just need dovecot itself to fix it's data. Thanks, Fil -- Dmitry Filonov Network Analyst 300 Longwood Ave. Enders-1262.2 Boston, MA 02115 617-919-4702

3 4

"failed to map segment from shared object" in sieve pipe
by Dorian Taylor 22 Mar '18

22 Mar '18

Hello, I have encountered a problem attempting to run a program in a sieve pipe. The program is a Perl script that loads a number of binary (XS) modules at runtime. The program crashes, it appears, if it tries to load too many. The (non-Perl part of the) error message is "failed to map segment from shared object” — no additional information. Cryptic error messages like this have the odour of imposed resource restrictions, so I’m wondering if there are any on the pipe/filter/execute implementation (e.g. via program_client_run). Any configuration knobs I can twiddle? Any insights for debugging? PS this is the dovecot 2.2.22 (fe789d2), the one that ships with Ubuntu Xenial. Regards, -- Dorian Taylor Make things. Make sense. https://doriantaylor.com

3 4

Fwd: Fwd: Everything works except sending mail
by Armin Tangelder 21 Mar '18

21 Mar '18

(Sorry Aki I send it wrong the first time, I feel like a n00b) ---------- Forwarded message ---------- From: Armin Tangelder <a.tangelder(a)gmail.com> Date: Tue, Mar 20, 2018 at 3:25 PM Subject: Re: Fwd: Everything works except sending mail To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Hi Aki, Mij postfix is sending and receiving mail. it might be an issue between Postfix and Dovecot. That is why I'm asking if one of the more experienced guru's ever did see something like this. A mail doesn't even reach the Postfix queue. And in paralel, I'm with this on postfix forums to take a look as well. But as Postfix probably is not discussed here I kept it to Dovecot only. But based on the dovecot -n you see anything wrong? Thnx, Armin Tangelder -- Very funny scotty, now beam down my clothes. On Tue, Mar 20, 2018 at 12:13 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > This sounds more like postfix problem. > > Aki > > On 20.03.2018 13:04, Armin Tangelder wrote: > > Hi people, > > > > Version of my beloved Dovecot installation: > > 2.2.27 (c0f36b0) > > > > I moved from a OS X server to a Linux (Ubuntu) Headless server. > All fun and good to play around with. Love almost everything. > > In the combination with Postfix and Dovecot I’m stuck to despair into > oblivion. > > > > Everything works except I cannot send mail from my (OS X) Outlook client I > keep getting: > > > > Connection to the server failed or was dropped. Error Code -3253 > > > > Nothing More and nothing less. O do not get any other error in a logfile > or anything. > And I followed almost every installation manual I found. Postfix I can > send and receive through telnet. > But I just can’t get this to work… > > The mail doesn’t even reach Postfix queue as I cannot connect to send. > I do have a awesome connection receiving my mail though ☺ > > Anyway: > > dovecot -n gives this (and I probably don’t see it anymore as I’ve been at > this for several days now) > > # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.4.16 (fed8554) > > # OS: Linux 4.13.0-37-generic x86_64 Ubuntu 17.10 > > auth_mechanisms = plain login > > auth_realms = formule1.demon.nl > > login_greeting = Dovecot ready. > > mail_location = maildir:~/Maildir > > mail_max_userip_connections = 50 > > 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 > > } > > protocols = imap > > service auth { > > unix_listener /var/spool/postfix/private/auth { > > group = postfix > > mode = 0666 > > user = postfix > > } > > } > > ssl_cert = </etc/ssl/certs/server.crt > > ssl_key = # hidden, use -P to show it > > userdb { > > driver = passwd > > } > > > > Anything useful I would love to see. > Any information needed. > > > > THNKS… > > > > Armin > > -- > > Very funny Scotty, now beam down my clothes… > > >

1 1

v2.2.35 released
by Aki Tuomi 21 Mar '18

21 Mar '18

https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.35.tar.gz.sig - charset_alias: compile fails with Solaris Studio, reported by John Woods. - Fix local name handling in v2.2.34 SNI code, bug found by cPanel. - imapc: Don't try to add mails to index if they already exist there. - imapc: If email is modified in istream_opened hook, mail size isn't updated. - lib-dcrypt: When reading encrypted data, more data would not be read if buffer was not consumed causing panic or hang. - notify: When notify plugin is used and transaction commit fails in dsync, crash occurs. - sdbox: When delivering to a mailbox that is over quota, temp files are not cleaned up when saving or copying fails.

3 4