- dovecot - dovecot.org

imapsieve removeflag ignored
by Slavko 08 Oct '22

08 Oct '22

Hi, i have working SPAM reporting implementend by imapsieve in debian's 2.3.13 dovecot. Recently i decide to add personal spam filter by bogofilter and use logic to learn/unlearn SPAM/HAM based on message flags. Here is example of moving message from Junk folder (the opossite logic is similar): if hasflag "$Junk" { execute :pipe "bogofilter" ["-Sn"]; removeflag "$Junk"; debug_log "Learned HAM (and unlearned)"; } else { execute :pipe "bogofilter" ["-n"]; debug_log "Learned HAM (only)"; } # mark as learned addflag "$NotJunk"; report ... When i move message, the debug lines in log shows, that logic works and flag is added as expected, but the other flag is not removed. Thus after moving mail from Junk, which has $Junk flag, it has both flags, the $Junk and $NotJunk. I tried to move removeflag action outside of condition and add it just before addflag, but the result is the same. For now i do not know if here is something wrong in my script, or i did some other mistake. On IRC cmouse tell, that removeflag was fixed in some early version (2.3.5 or so), but it doesn't work here. Please, how i can get it working? regards PS: please CC me, i am not subscribed -- Slavko https://www.slavino.sk/

2 2

oauth2 passdb user authentication with PLAIN
by Simon 05 Oct '22

05 Oct '22

2 2

Replacing antispam plugin with IMAPSieve not 100% correct?
by Marc 04 Oct '22

04 Oct '22

I think this page[1] is not correct If you configure this option: imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve the file report-spam.svbin cannot be created because users cannot write there. [1] https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve/#how…

3 2

Using sqlite as dict for last_auth plugin
by Oleg petol 04 Oct '22

04 Oct '22

Hi! It is required to collect statistics about the time of the last IMAP and POP3 login of the user and the delivery of letters to him via lmtp. The last-login plugin is perfect. But I don't want to use heavy databases as the mail system service is served by the Oracle DB. The most suitable option, as I see, is to store statistics in the sqlite DB, but after going through all the options in the configuration file, I could not use sqlite. When writing in configuration: plugin { driver=sqlite last_login_dict = sqlite:statsdb last_login_key = last-login/%s/%u/%r last_login_precision = ms } I am getting an error: Oct 4 17:01:41 nms4 dovecot: imap(new_ver_test(a)test2.aroma.ru)<154597><q0VJ5jXq9o4KAQDI>: Error: last_login_dict: dict_init(sqlite:statsdb) failed: Unknown dict module: sqlite I did the last-login plugin setup exactly according to the instructions: https://doc.dovecot.org/configuration_manual/mail_location/obox/last_login_… I am using standard debian packages. Desperate, I built latest dovecot version from source, but got exactly the same error. Tell me, please, is it possible to use a dictionary in sqlite format to collect last-login plugin statistics? And how should I describe it in the configuration file? Sincerely, Oleg Additional Information: # /sbin/dovecot --build-options Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) passwd prefetch passwd-file sql # /sbin/dovecot -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-18-amd64 x86_64 Debian 11.5 # Hostname: nms4.some.host auth_default_realm = some.host auth_verbose = yes dict { statsdb = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_uid = 89 mail_debug = yes mail_gid = vmail mail_location = maildir:~/Maildir mail_plugins = quota mail_privileged_group = mail 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 index ihave duplicate mime foreverypart extracttext 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 { args = username_format=%u /etc/postfix/vusers.conf driver = passwd-file } plugin { driver = sqlite last_login_dict = sqlite:statsdb last_login_key = # hidden, use -P to show it last_login_precision = ms quota = maildir quota_grace = 10%% sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail user = vmail } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 10.1.0.187 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/letsencrypt/live/some.host/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/postfix/vusers.conf driver = passwd-file override_fields = uid=vmail gid=vmail } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = quota sieve quota last_login } protocol imap { mail_plugins = quota imap_quota last_login } protocol sieve { managesieve_max_line_length = 64 k } protocol pop3 { mail_plugins = quota last_login } -- /petol http://kab.tv/rus

1 0

Re: Pigeonhole redirect is adding a message-id header when it already exists
by hi＠zakaria.website 02 Oct '22

02 Oct '22

On 2022-10-01 22:59, michael.zork(a)feierfighter.de wrote: > Hi Zakaria, > > I'm very happy about your email to the mailing list, I thought I'm > alone with my problem, and it's nice to see that the problem might be > a bug/problem in pigeonhole. I was not sure about it because I didn't > get a technical answer from that German provider, so I didn't know it > it's a bug in pigeonhole or not. I didn't have time to investigate, > thanks for your time to investigate and pinpoint to the line of code > where the problem might be! > > Back then, a few months ago, I disabled the "Message-Id duplicate > check" because of this problem. > > It's just a problem of <0.001% of the emails, most systems generate > valid Message-IDs. Maybe Alibaba/Aliexpress is the biggest one who > generates invalid Message-Ids... > > It would be awesome if you could also try to contact > Alibaba/Aliexpress, and tell them the problem. Maybe they fix it if > multiple people report it. But I doubt it. > > Let's see what the Dovecot guys say to this problem. Maybe the best > solution is to remove the invalid Message-Id before adding a new one. > > Michael > > Am 01-Oct-2022 18:24:05 +0200 schrieb hi(a)zakaria.website: > >> On 2022-10-01 12:49, michael.zork(a)feierfighter.de wrote: >>> Hi there, >>> >>> I can confirm this behavior. A few months ago I introduced a >> milter >>> which is checking for multiple headers when the RFC says that >> there >>> just should be one of them For example "Message-Id". >>> >>> I found the described problem in an email coming from Alibaba, >> which >>> had an invalid "Message-Id" header. It didn't contain an "@" sign >> or >>> similar. It was RFC-invalid. >>> >>> This email was sent from Alibaba to a German email provider. There >> was >>> a redirect at that email provider, pointing to my mailserver. >>> >>> My server rejected the email because there were 2 "Message-Id" >>> headers: The original invalid "Message-Id" header from Alibaba, >> and a >>> new "Message-Id" header from the German provider, which seems to >> have >>> been added during the redirect. There were "Dovecot-sieve" headers >> in >>> that mail, so my guess was that it happened because of >>> Dovecot-sieve/pigeonhole implementation. >>> >>> I contacted the email provider, asking for help. Asking if it >> really >>> is a bug in pigeonhole (or maybe some other system at that >> provider, >>> who knows). And I contacted Alibaba, so they fix the invalid >>> "Message-Id". I got responses from both, but until now, as far as >> I >>> can see, it has not been fixed. >>> >>> The best fix would be (if it really is a bug in pigeonhole), if >>> pigeonhole fixes the problem, then it's fixed for all users of >>> Dovecot. I guess Alibaba is not the only sender with an invalid >>> "Message-ID" header, but that's the only one I saw. >>> >>> Michael >>> >>> Am 01-Oct-2022 14:00:45 +0200 schrieb sriccio(a)swisscenter.com: >>> >>>>> You wrote in the original email the message was rejected. Sorry >> I >>>> don't have login access to my gmail test account anymore since >> the >>>> google @#$%@#$% wanted to have me add a phone number. >>>> >>>> In my original post I said that gmail was rejecting the forwards >>>> because >>>> of duplicate headers, and that the duplicate header seems to be a >>>> Message-ID added by pigeonhole when it's "not happy" with the >>>> original >>>> mail Message-ID. >>>> >>>> I probably failed to explain the issue clearly and sorry for >> that. >>>> >>>> Thank you anyway for trying to help :) >> >> Hi Michael, >> >> I just wanted to say sorry, that I sent this empty email by mistake >> intending nothing else. >> >> Anyhow, thanks so much for your valuable input, it's very much >> appreciated. >> >> Zakaria. Good Morning Michael, No problem. Although, to be clear I didnt point out anything, but its Sébastien and the credit shall go for him. Also, by the way in EXIM MTA, there is verify syntax condition in data acl, which checks all email headers and validate that they are standards compliant and reject sending any email beforehand to your issue which has non-compliant header and offers the ability to remove such headers with condition handling e.g. if contained any Sieve header, to request removing message id headers with headers_remove and add compliant one with add_header, and I guess this will mitigate any mail service provider rejection issue. If you are postfix user and considering switching, let me know, I might be able to help. Zakaria.

1 0

Matching Addresses in Sieve
by Doug Hardie 01 Oct '22

01 Oct '22

I have an email with the following header line: From: 'Thank you!Kohls' <Kohls-MNc(a)FeedbackKohlsOpinionRequestedlxecrftHO.com> I am trying to match that with: if address :contains "from" "Thank you!Kohls" { addflag "\\Seen"; fileinto "Junk"; stop; } However, the matching portion of the from address is only the section between < and >. Since there are changing sections that are different for each email, I can't use that. I wanted to match the stuff before <. I have tried numerous formats for the if statement but none of them have worked. What is the proper way to make that match work? Thanks, -- Doug

2 2

new feature: sieve forward plugin
by Marc 26 Sep '22

26 Sep '22

As this page[1] describes a more often occurring problem of forwarding messages from servers that are not included in the spf records. Maybe there should be a plugin that offers this forward functionality. Something like get the spf records of the sender check if there is a -all then apply the sender substitution. https://doc.dovecot.org/configuration_manual/sieve/configuring_auto_forward…

4 4

Vmail Home
by Silvio Siefke 26 Sep '22

26 Sep '22

Hello, I use Opensmtpd with Dovecot LMTP. All this run but one point I not understand. I use Virtual Users, with System User vmail, home is /var/vmail but dovecot stored message in path /home/vmail/<domain>/user. In configuration files is /var/vmail (dovecot users). Thx for help Silvio ---- cat /etc/passwd | grep vmail vmail:x:2000:2000:Vmail Directory and User:/var/vmail:/usr/sbin/nologin ---- dovecot -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-18-amd64 x86_64 Debian 11.5 # Hostname: asia.sisi-systems.ovh default_vsz_limit = 1 G doveadm_password = # hidden, use -P to show it doveadm_port = 20000 mail_gid = vmail mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_privileged_group = vmail 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 index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * mail_replica = tcp:192.168.1.112 quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = lmtp imap pop3 sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service doveadm { inet_listener { port = 20000 } } service imap-login { inet_listener imap { port = 143 } vsz_limit = 1 G } service lmtp { unix_listener lmtp { group = vmail user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 ssl = yes } } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/lego/certificates/imap.sisi-systems.ovh.crt ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file override_fields = uid=vmail gid=vmail home=/home/vmail/%d/%n } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 20 mail_plugins = " notify replication quota imap_quota imap_sieve" } protocol lmtp { mail_plugins = " notify replication sieve notify push_notification" postmaster_address = network(a)sisi-systems.ovh } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = " notify replication" }

2 1

Custom post login scripting variables via ID command
by hi＠zakaria.website 26 Sep '22

26 Sep '22

Hi there, I wonder if dovecot would consider this feature request. In post login scripting, given USER, IP, LOCAL_IP, and userdb lookup fields, are only available, I want to push additional variables from web mail to dovecot using ID commands yet I looked at the source in imap-login-cmd-id.c and script-login.c it seems to be possible while I'm not an expert in C and IMAP standards and not sure if its something would break the standards. I hope the dev team to consider this and if anyone have a workaround or an idea with I can start to patch a workaround myself, please let me know as it would be very much appreciated. With thanks. Zakaria.

3 4

what sieve variables / syntax is available to sieve scripts.
by Marc 25 Sep '22

25 Sep '22

1. where can I find all variables like "imap.user" like in mentioned on page[2] 2. I have the impression that variables like "${from}" are all being set from scanning the whole email again seeing these "if matches" statements. Is that not super inefficient? I would assume that such variables would be set and made available upon the receipt of a message. 3. What is the point of this: if environment :matches "imap.user" "*" { set "username" "${1}"; } pipe :copy "sa-learn-ham.sh" [ "${username}" ]; Why can't I just use: pipe :copy "sa-learn-ham.sh" [ "imap.user" ]; [1] require [ "vnd.dovecot.pipe", "copy", "variables" ]; if header :matches "subject" "*" { set "subject" "${1}"; } if header :matches "from" "*" { set "from" "${1}"; } pipe :args [ "USER(a)DOMAIN.TLD", "${from}", "${subject}" ] :copy :try "jabber_notify.sh" ; from page https://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe [2] if environment :matches "imap.user" "*" { set "username" "${1}"; } pipe :copy "sa-learn-spam.sh" [ "${username}" ]; https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve/#how…

1 0