October 2022 - dovecot

grabbing multiple patterns from allof
by Marc 10 Oct '22

10 Oct '22

Anyone an idea how you should grab multiple matches from allof? if allof ( true, header :regex "Subject" "(test).*(test2)", envelope :matches "from" "*" )

2 1

Static build problems
by Jacob Welsh 09 Oct '22

09 Oct '22

I'm attempting to build the latest Dovecot, version 2.3.19.1, on Gales Linux, a distribution based on musl libc with all static linking. After working around some expected troubles to generate configure, such as the libtool and iconv.m4 dependencies, the build appeared to complete successfully. But on closer inspection, the plugins were installed as a bunch of .a and .la files rather than getting linked into any of the binaries, as would be necessary to actually use them. I determined that the probe for dynamic module support (DOVECOT_MODULES defined in 'm4/modules.m4') had returned a false positive: in the static configuration musl includes a stub dlopen() that always returns failure at runtime, so a compile-and-link-only test is not predictive. Libtool itself is affected in the same way, but it comes with the --disable-shared option which usually makes things works fine. Short of a proper solution (perhaps removing modules.m4 and going instead by what libtool already determined, since you've decided to depend on it anyway), I stubbed out modules.m4 to simply return the correct result for this platform, thus: AC_DEFUN([DOVECOT_MODULES], [ have_modules=no AC_SUBST(MODULE_LIBS) AC_SUBST(DLLIB) ]) Now the build is failing due to the absence of a function that's defined only when HAVE_MODULES is true: libtool: link: gcc -I../../src/lib -I../../src/lib-test -I../../src/lib-ssl-iostream -DDCRYPT_MODULE_DIR=\"/gales/pkg/dovecot-0.0-2.3.19.1/lib/dovecot\" -DDCRYPT_SRC_DIR=\"../../src/lib-dcrypt\" -std=gnu99 -g -O1 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -Wl,--whole-archive -Wl,../lib-ssl-iostream/.libs/libssl_iostream.a -Wl,--no-whole-archive -o test-stream test_stream-dcrypt.o test_stream-istream-decrypt.o test_stream-ostream-encrypt.o test_stream-test-stream.o ../lib-ssl-iostream/.libs/libssl_iostream.a ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a test_crypto-dcrypt.o: In function `dcrypt_initialize': /home/user/gales-linux/gports/dovecot/build/dovecot-2.3.19.1/src/lib-dcrypt/dcrypt.c:34: undefined reference to `module_dir_try_load_missing' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:664: test-crypto] Error 1 I noticed commit d21897832a443d139d56b1fb1c86d8f76e5f77f3 from 2009, "Fixed compiling without module support", and clearly it's supposed to work since the #ifdefs are there, but I begin to suspect that nobody's actually tested this branch of the configuration tree recently. Further, looking through the automakefiles I'm not finding how the plugin libraries are supposed to work at all in this case and I begin to fear that they simply... aren't. Say it ain't so? Jacob

2 3

rspamd results
by Benny Pedersen 09 Oct '22

09 Oct '22

Results for file: 2 (0.0633 seconds) [Metric: default] Action: add header Spam: true Score: 3.99 / 30.00 Symbol: ARC_REJECT (1.00)[signature check failed: fail, {[1] = sig:dovecot.org:reject}] Symbol: DKIM_TRACE (0.00)[junc.eu:-] Symbol: DMARC_POLICY_SOFTFAIL (0.10)[junc.eu : No valid SPF, none] Symbol: FROM_HAS_DN (0.00) Symbol: FROM_NEQ_ENVFROM (0.00)[me(a)junc.eu, dovecot-bounces(a)dovecot.org] Symbol: HAS_LIST_UNSUB (-0.01) Symbol: HAS_ORG_HEADER (0.00) Symbol: HFILTER_HOSTNAME_UNKNOWN (2.50) Symbol: MAILLIST (-0.20)[mailman] Symbol: MID_RHS_MATCH_FROM (0.00) Symbol: MIME_GOOD (-0.10)[text/plain] Symbol: MIME_TRACE (0.00)[0:+] Symbol: RCPT_COUNT_ONE (0.00)[1] Symbol: RCVD_COUNT_SEVEN (0.00)[7] Symbol: RCVD_IN_DNSWL_MED (-0.40)[172.104.150.56:received, 94.237.105.223:received] Symbol: RCVD_NO_TLS_LAST (0.10) Symbol: RCVD_VIA_SMTP_AUTH (0.00) Symbol: R_DKIM_REJECT (1.00)[junc.eu:s=default] Symbol: TO_DN_NONE (0.00) Message-ID: 38f38a585892368901bd47944ca617ab(a)junc.eu just to be sure its not a fail in spamassassin with dkim_invalid ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=junc.eu header.s=default header.b=rodgOLEw; spf=pass (talvi.dovecot.org: domain of me(a)junc.eu designates 172.104.150.56 as permitted sender) smtp.mailfrom=me(a)junc.eu; dmarc=pass (policy=none) header.from=junc.eu where is the problem ? i will report fuglu dkim signing non existing headers in a moment if that my fault cc: is non existing here but are still signed, why did ARC verify not find this problem ?

1 0

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 30 Sep '22

30 Sep '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