- dovecot - dovecot.org

Dovecot /VMWare Boxer
by Djule Djukic 11 Jun '20

11 Jun '20

Hello all, My name is Djule Djukic and I am working for Hipotekarna Banka from Montenegro. We are using IMAP email server Dovecot version 2.1.17. As a email clients on our corporate workstations we are using Thunderbird or WebMail and everything is working fine. We decided to introduce MDM solution in our environment and we installed VMWare WorkspaceOne (former Airwatch) which use Boxer as a mail client in App per VPN scenario. When we syncronise email with Boxer we have found that the time and date displayed for some messages have been changed to the time at which the file was synchronized. This is not hapening with all messages. It is happening only with messages in subfolders, never with Inbox. It seems when messages is moved by some rule from WebMail or Thunderbird from Inbox to some subfolder, Boxer is not able to read dates correctly, By seraching on Internet we found couple of explanation what might be possibel cause of this behaviour. https://imapsync.lamiral.info/FAQ.d/FAQ.Dates.txt https://serverfault.com/questions/588618/maintain-email-timestamp-when-tran… https://dovecot.org/pipermail/dovecot/2008-July/032165.html Problem with some email clients is that they not look always for "Date:" from email message header. The "Date:" header is usually the date the message was written or sent the first time, at the writer side. This "Date:" header line is never changed by any transfer or copy. If an email client uses the "Date:" header for displaying the date of a message then no problem in synchronization with wrong date should arise. Obviously this is not a case with a Boxer email application. We tried GMail and everything is working fine. We are wondering if someone can explain what APPEND command could have done in our case? Is it relevant at all for our case? Is it used somehow by thunderbird or webmail clients? Also we would like to hear from someone if there are some improvemnents in further release of dovecot or some configuration that we can implement in order to fix this? Thank you in advanced for your suggestions and contribution, Đule Đukić Specijalista za informacionu bezbjednost / ISO ĐuleĐukić Specijalistaza informacionu bezbjednost / ISO http://www.hipotekarnabanka.com/hb-content/uploads/2014/06/slika1.jpg

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Yes tell that to the people that create rhel6, rhel7 and rhel8 and give lts support. Unless google pays you to train your software to mark their messages as spam, you might want to consider yourself not to smart as well ;) My solution would solve the problem others create (see the other mail). Your solution wastes your time and will always be carrying water to the sea. I think if 50% of providers in the world would do this, it would quickly be end of story for the spam originating from the networks like google and amazon. If there is a McDonalds build next to your home, and their clients throw waste into your garden. You hold McDonalds liable for cleaning this up not? Or are you also going to cleanup their mess indefinitely. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 11:09 To: Marc Roos; dominic; dovecot; lists; users Subject: Re: handling spam from gmail. Am 11.06.20 um 11:04 schrieb Marc Roos: > I have got lots of shit coming from *.google.com like these: > > X-Spam-Status: No, score=2.1 required=3.0 tests=BAYES_00 because you are too dumb to train your bayes give me one such message and i am pretty sure it will fire BAYES_80 or BAYES_99 which will burn it with fire and lead to a milter reject here SpamAssassin 3.3.1 is also not very smart in 2020 so instead ask for dumb solutions which making you part of a bigger problem better do your homework

2 1

Pigeonhole-sieve auto-reply
by ＠lbutlr 11 Jun '20

11 Jun '20

Is it possible to have a sieve script reply with a press message to certain emails (and only certain emails) based on sieve matches? I see a lot on vacation replies, but I want something more specific. Something along the lines of procmails formail command? Everything I’ve searched for is about vacation r filing replies into the same folder as the original message.

2 2

Special use folders in mailbox hierarchy
by Scott A. Wozny 11 Jun '20

11 Jun '20

Dear Dovecot Gurus, Setting up my first IMAP server and looking at the folder structure, I had a mailbox I built on a Dovecot server and a mailbox configured by a hosting provider next to each other in Thunderbird and I noticed that the special use folders (Drafts, Trash and Sent) in my default-ish (I did set them to auto = subscribe) Dovecot install make these folders appear parallel to my Inbox folder where my hosting provider’s default configuration has them under the Inbox hierarchically, along with all the folders I built for mail storage over the use of the account. I did some googling, but I cannot find any guidance on which of these is preferred, why, or how they could be controlled in Dovecot. The default Dovecot config is ambiguous (IMHO) in that the mailbox config elements are children to the inbox namespace (implying they go under Inbox in the hierarchy) but their special_use parameter names are \Name which (if you use a UNIX filesystem paradigm) implies they should be at the root of the hierarchy and, therefore, parallel with Inbox, which is how Thunderbird shows them, but I’m not sure if that’s a mail client decision and not anything to do with the server configuration. Since I can’t access the config of my hosting provider, I can’t make any comparisons, so I thought I’d ask on the list if there is any standard guidance on server side configuration of special use folders in Dovecot or if there’s no guidance available because I’m overthinking this. :) Thanks, Scott

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

>> Yes tell that to the people that create rhel6, rhel7 and rhel8 and give >> lts support. > >as said that has nothing to do with your wrong training and RHEL has >always the same problem: you can't package the latest and greatest shit >over 10 years because it requrires newer versions of dependencies > >so what you get with your lazyness by using a LTS distribution is a >"never change a running system, just fix the worst bugs and don't touch >anything else" > >upstream developers don't hold development for 10 years > >written from a Fedora workstation with kernel 5.6.18-200.fc31.x86_64 >from last night realyed over a datacenter firewall and a mailserver >using the same kernel > >> Unless google pays you to train your software to mark their messages as >> spam, you might want to consider yourself not to smart as well ;) > >unless i make good money from customers paying for a nearly 100% >hitrate of spam combine with a zero-false-positive policy i am likely >smarter than you I would argue it is quite difficult to identify intelligence. I am pretty sure I would not start with your reasoning. I have a favourite German saying I like to quote in matters like these "gegen Dummheit kämpfen Götter selbst vergebens" >> My solution would solve the problem others create (see the other mail). >> Your solution wastes your time and will always be carrying water to the >> sea. I think if 50% of providers in the world would do this, it would >> quickly be end of story for the spam originating from the networks like >> google and amazon. > >they won't give a shit and when i get such idiotic mails as you propose >i take the phone, call the sender and suggest to fire his mailadmin >better sooner than later > >> If there is a McDonalds build next to your home, and their clients throw >> waste into your garden. You hold McDonalds liable for cleaning this up >> not? Or are you also going to cleanup their mess indefinitely. > >what a nonsense

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Your logics sucks. There is a difference between how email works and how spamassassin works. You are assuming that everyone in the world is using spamassassin by including it in 'how email works'. Maybe you like to post a link to your bayes files???? Am 11.06.20 um 11:13 schrieb Marc Roos: > You do not understand how mail works. Google mail is only getting > through when spf checks and the likes are being passed. unless you don't manage to get rid of BAYES_00 in case of clear spam messages don't tell me you understand how email works

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

You do not understand how mail works. Google mail is only getting through when spf checks and the likes are being passed. I am not creating any problems with this, I am just bouncing them back. Google has enough billions to handle these issues. If everyone would apply this procedures, people with legitimate email accounts would move from a spam network to some other provider. People joining these providers are the problem, because it allows these networks to mix spam with legitimate email. When clients start moving out, spam networks are becoming easier to hard block and these providers start thinking about their infrastructure and their bussines model. If everyone would be doing this, it is solving the spam problem. My below procedure should be applicable for any network generating a lot of spam. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 10:25 To: Marc Roos; dovecot; users Subject: Re: handling spam from gmail. Am 11.06.20 um 10:19 schrieb Marc Roos: > I am sick of this gmail spam. Does anyone know a solution where I can > do something like this: > > 1. received email from adcpni444(a)gmail.com 2. system recognizes this > email address has been 'whitelisted', continue with 7. > 3. system recognizes as this email never been seen before 4. auto > reply with something like (maybe with a wait time of x hours): > Your message did not receive the final recipient. You are sending > from a known spam provider > network that is why we blocked your message. Please confirm that: > - you are not a spammer and > - you have permission to use the mail adress you send your message to > - you and your provider agree to uphold GDPR legislation > - you and your provider are liable for damages when breaching any > of the above. > > > Click link to confirm and you agree with the above > https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf > > 5. sender clicks confirm url > 6. email address is added to some white list. > 7. email is delivered to recipient. and i am sick of people not understanding how email works! you don't send unasked mail to a in the most cases forged sender unless you want to be part of the problem backscatters and brainless autoreplies have to be burnt with fire

1 0

Dovecot fs quota reports quota as byte
by Kazim Koybasi 11 Jun '20

11 Jun '20

Hello, My dovecot configuration is like below. My filesystem quota is reported as kb and dovecot quota reported as bytes so dovecot quota becomes wrongly greater than filesystem quota. How can I solve this issue? Any help apretiated. Quota name Type Value Limit % user STORAGE 10428416 3242880 321 # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 CentOS Linux release 8.1.1911 (Core) # Hostname: suretired auth_mechanisms = plain login auth_username_format = %Ln debug_log_path = /var/log/dovecot.log first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_debug = yes mail_location = maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u mail_plugins = quota 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 mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { quota = fs:user sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Score: (-?[[:digit:]]+\.[[:digit:]]).* sieve_spamtest_status_type = score } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = dovecot } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service quota-warning { executable = script /usr/bin/quota-warning.sh unix_listener quota-warning { group = dovecot mode = 0600 user = dovecot } user = dovecot } ssl_cert = </etc/pki/dovecot/certs/letsencrypt/fullchain1.pem ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !TLSv1 userdb { driver = passwd } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve quota } protocol imap { mail_plugins = quota quota imap_quota } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_max_line_length = 65536 } protocol pop3 { mail_plugins = quota pop3_quota quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

1 0

How to unset namespace configuration from dovecot.conf in conf.d/99-cutom.conf?
by Py Retta 09 Jun '20

09 Jun '20

Dear all, my /etc/dovecot/dovecot.conf [0] that is shipped with the Linux distro (Ubuntu 18.04, dovecot 2.3.10) has a namespace section: namespace inbox { ... mailbox Sent { ... } ... } I need to remove this whole section from the configuration, but I need to do this in a file such as /etc/dovecot/conf.d/99-custom.conf because I want this modification to be stable against automatic updates of dovecot.conf shipped by the distro. This raises the question, how do I "unset" an earlier namespace configuration at a later point in the stack of config files? Speaking in terms of `doveconf -n`, snippet [1] below lists the original configuration (including namespace setup) and [2] lists the desired configuration that results from deleting the namespace passage from dovecot.conf. However, I would like to achieve it without deleting it from dovecot.conf but by adding sth to conf.d/99-custom.conf. Thanks a lot, Py [0] original dovecot.conf (only relevant namespace section): # Default private namespace setup compatible with Courier-IMAP. namespace inbox { separator = . prefix = INBOX. inbox = yes mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox Drafts { auto = create special_use = \Drafts } mailbox Trash { auto = create special_use = \Trash } } [1] `doveconf -n` for the original configuration: # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 imapflags notify namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } [2] `doveconf -n` for the desired configuration (with the namespace section in dovecot.conf removed): # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 imapflags notify passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" }

1 0

doveadm protocol bug
by Felipe Gasper 08 Jun '20

08 Jun '20

Hi everyone, On 26th May I emailed this list a few times about an apparent protocol bug in Dovecot’s server-side doveadm implementation. Later that day I sent in a pull request to fix the issue. Thread reference: https://dovecot.org/pipermail/dovecot/2020-May/119066.html Pull request: https://github.com/dovecot/core/pull/129 Thus far neither the mailing list emails nor the PR have garnered any responses. Can someone please weigh in on these? It’s totally understandable if Dovecot’s behavior here is going to say as-is; I’d just like some confirmation so we can note it in our client implementation. (Switching our client to the HTTP API would be out-of-scope for our current project.) Thank you again! cheers, -Felipe Gasper

1 0