- dovecot - dovecot.org

Abort IMAP COPY command from imapsieve?
by Tom Hendrikx 10 Mar '24

10 Mar '24

Hi, I'm finding myself regularly moving messages to the wrong folder in my MUA. Most of the time this is easily corrected, but sometimes this is a bit harder. Imagine selecting all messages in the 'Trash' or 'Junk' folder, and moving them in the 'Archive' folder (by clicking on the MUA's 'Archive' button in stead of the 'Delete' button). I'm looking into blocking this server-side using an IMAPSieve script. So far I've been able to log relevant details of such a message move, but I don't how I can abort the message move altogether. I'm now using the following config, which result in log messages like: dovecot: imap(tom(a)example.org)<540588><TmDbwVATNOoqEDeBFZcAASOvWpPsXcmR>: sieve: DEBUG: move-to-archive: Message archived: mailbox-from=INBOX mailbox-to=Archives.2023 message-id=<648ab0b4-8439-4b2d-8e53-b97e700ff9d0(a)mail.example.org> subject='Testing IMAPSieve' File: dovecot.conf ----- protocol imap { mail_plugins = $mail_plugins imap_sieve } plugin { sieve_plugins = sieve_imapsieve sieve_implicit_extensions = +vnd.dovecot.debug # Find out how to block messages from being from 'Trash' to 'Archive' folder imapsieve_mailbox1_name = Archives.* #imapsieve_mailbox1_from = INBOX imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/move-to-archive.sieve } ----- File: move-to-archive.sieve ----- require "environment"; require "variables"; require "vnd.dovecot.debug"; require "vnd.dovecot.imapsieve"; if header :matches "Message-ID" "*" { set "message_id" "${1}"; } else { set "message_id" "UNKNOWN"; } if header :matches "Subject" "*" { set "subject" "${1}"; } else { set "subject" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-from" "*" { set "mailbox_from" "${1}"; } else { set "mailbox_from" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-to" "*" { set "mailbox_to" "${1}"; } else { set "mailbox_to" "UNKNOWN"; } debug_log "move-to-archive: Message archived: mailbox-from=${mailbox_from} mailbox-to=${mailbox_to} message-id=${message_id} subject='${subject}'"; ----- I tried the "reject" sieve command but that only works in the context of delivery. Is there a way to abort the actual move, and return an error to the MUA? Or am I on the wrong track altogether, and is there a better approach? NB: While doing research I found that not all environment variables in RFC 6785 (https://www.rfc-editor.org/rfc/rfc6785.html#section-4) are implemented in Pigeonhole? I tried to access the 'imap.cause' and 'imap.mailbox' variables but they were empty, only the variables from RFC 5183 seem to be available. This is inline with the docs at https://github.com/dovecot/pigeonhole/blob/main/README, but not with https://github.com/dovecot/pigeonhole/blob/main/doc/plugins/imapsieve.txt and https://doc.dovecot.org/configuration_manual/sieve/plugins/imapsieve/, which both seems to imply that RFC 6785 is implemented? Kind regards, Tom

1 0

Fw: User-configurable time-based mail deletion in specific folders
by Rupert Gallagher 10 Mar '24

10 Mar '24

> Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven -- https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org > Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven - - https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list - - dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

6 8

JMAP status?
by Brad Koehn 08 Mar '24

08 Mar '24

Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world. Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world.

3 2

High number of folders, Low sink speed
by aria mazloom 07 Mar '24

07 Mar '24

I just moved my server. Dovecot version 2.3.19.1 (9b53102964) After the transfer, I deleted the indexes and caches and rebuilt them. One of my users is experiencing slowness when send/recevie all his folders. The user has about 250 folders with a maximum depth of 3. The volume of emails is about 13 GB. Outlook wants to receive all email folders in every send/recevie all folders. Outlook 2019 and Windows 10. We connected to other users with his Outlook and we don't have this problem. We also tested with another device and same user and we have this problem. Another user with 100 folders also reported slower sync speeds after transfer server. Outlook 2019 and Windows 10. I just moved my server. Dovecot version 2.3.19.1 (9b53102964) After the transfer, I deleted the indexes and caches and rebuilt them. One of my users is experiencing slowness when send/recevie all his folders. The user has about 250 folders with a maximum depth of 3. The volume of emails is about 13 GB. Outlook wants to receive all email folders in every send/recevie all folders. Outlook 2019 and Windows 10. We connected to other users with his Outlook and we don't have this problem. We also tested with another device and same user and we have this problem. Another user with 100 folders also reported slower sync speeds after transfer server. Outlook 2019 and Windows 10.

1 0

Bug/Warning not sure which
by Richard Shetron 04 Mar '24

04 Mar '24

Hello, My sysadmin and I spent a couple hours trying to figure out a POP3 problem that has worked for about 20 or so years. We run our own dns for sgeinc.com. I've always used mail.sgeinc.com as my incoming and outgoing server. At various times mail has been an alias for another machine. It's currently on the same address as sge.sgeinc.com. On the update forced on us on 2/22/24 or 2/23/24 it stopped working. It still works as an outgoing server but incoming POP3 it stopped working. It started working when I changed my incoming server to sge.sgeinc.com. You might want to look into it or not. We chased the initial problem to, we think, ssh-keygen in /usr/local/bin/ which was Not found but is there. Thanks root@sge:/usr/local/bin# dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-172-generic x86_64 Ubuntu 20.04.6 LTS # Hostname: sge.sgeinc.com auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } } ssl = required ssl_cert = </etc/letsencrypt/live/sgeinc.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd }

5 6

Re: Bug/Warning not sure which
by Joseph Tam 03 Mar '24

03 Mar '24

> From: Richard Shetron <guest2(a)sgeinc.com> > We run our own dns for sgeinc.com. > I've always used mail.sgeinc.com as my incoming and outgoing server. At > various times mail has been an alias for another machine. It's > currently on the same address as sge.sgeinc.com. On the update forced > on us on 2/22/24 or 2/23/24 it stopped working. It still works as an > outgoing server but incoming POP3 it stopped working. It started > working when I changed my incoming server to sge.sgeinc.com. Maybe your SSL cert? $ openssl s_client -connect mail.sgeinc.com:995 < /dev/null |& openssl x509 -noout -text | grep DNS: DNS:sge.sgeinc.com, DNS:sgeinc.com, DNS:www.sgeinc.com "mail.sgeinc.com" is not in your list of alternate names, hence your mail clients started rejecting the SSL certificate as invalid. Joseph Tam <jtam.home(a)gmail.com>

1 0

LMTP: user does not exist
by dienes_devout_0d＠icloud.com 03 Mar '24

03 Mar '24

Hello all, I have been using Postfix/Dovecot for some time, but now need to setup Sieve. As I understand this requires Dovecot to do the local mailbox delivery. In my case LMTP would be the best. Here is the current setup. The users on the system all have local accounts and authenticate with Kerberos via pam_krb5 against kerberos realm domain.tld. They authenticate to the mail server as user(a)domain.tld. The server name is mail.domain.tld and mailbox names on the mail server are user(a)mail.domain.tld. User mailboxes are located in /home/user/Maildir. I went through the configuration described in the documentation (https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/#ho…) but hit a weird problem. When LMTP is enabled in Postfix, the delivery fails with an error: 550 5.1.1 <user(a)mail.domain.tld> User doesn't exist: user(a)mail.domain.tld (in reply to RCPT TO command)) If LMTP is not enabled in Postfix, it successfully delivers the messages to ~/Maildir as expected. Can anyone advise me why is this failure with LMTP occurring and how do I fix it? Thank you, Alex

1 0

better delivery mechanism to maildir?
by dovecot.org＠schildbach.de 03 Mar '24

03 Mar '24

As many of you probably are, I'm using Postfix together with Dovecot. Postfix delivers mail for my users by writing them directly to the filesystem (maildir). I wonder is there a better alternative? I'd like to separate the two services on different physical machines, so a shared filesystem isn't trivial any more. (I'd also like to stay with maildir storage and rather not do SQL or similar.) Can mail be delivered via IMAP for example? Or is there some other delivery protocol I don't know about that both Dovecot and Postfix support? Thanks!

4 7

Dbox-storage error when compiling: no member named 'st_atim' in 'struct stat'
by James L. Brown 03 Mar '24

03 Mar '24

Hi all. I’m getting errors when trying to compile 2.3.21 on macOS 14.3.1 Sonoma. It ends with: 3.2.1/include -MT dbox-storage.lo -MD -MP -MF .deps/dbox-storage.Tpo -c dbox-storage.c -fno-common -DPIC -o .libs/dbox-storage.o dbox-storage.c:296:32: error: no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24: error: no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; ~~~~~ ^ 2 errors generated. make[5]: *** [dbox-storage.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 Before ‘make’ I ran: sudo CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/homebrew/opt/openssl@3/lib LDFLAGS=-L/opt/homebrew/lib ./configure --with-ssl=openssl --with-mysql --with-sodium I had to run ’sudo’ before ‘make’ as I was getting this error: error: error opening '.deps/fuzzer.Tpo': /Users/jlbrown/Downloads/dovecot-2.3.21/src/lib-test/.deps/fuzzer.Tpo: Permission denied Would someone be able to help we with the dbox-storage error? Thanks, James. Hi all. I’m getting errors when trying to compile 2.3.21 on macOS 14.3.1 Sonoma. It ends with: 3.2.1/include -MT dbox-storage.lo -MD -MP -MF .deps/dbox-storage.Tpo -c dbox- storage.c -fno-common -DPIC -o .libs/dbox-storage.o dbox-storage.c:296:32:error:no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24:error:no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; ~~~~~ ^ 2 errors generated. make[5]: *** [dbox-storage.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 Before ‘make’ I ran: sudo CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/ homebrew/opt/openssl@3/lib LDFLAGS=-L/opt/homebrew/lib ./configure --with- ssl=openssl --with-mysql --with-sodium I had to run ’sudo’ before ‘make’ as I was getting this error: error:error opening '.deps/fuzzer.Tpo': /Users/jlbrown/Downloads/dovecot- 2.3.21/src/lib-test/.deps/fuzzer.Tpo: Permission denied Would someone be able to help we with the dbox-storage error? Thanks, James.

1 0

IMAPSieve plugin and special-use attribute
by Kirill Kirilenko 02 Mar '24

02 Mar '24

Hello. Since version 0.5.9 Pigeonhole has RFC 8579 support, so Dovecot admins can easily setup redirection of spam messages into a personal mailbox identified by a particular special-use attribute rather than the mailbox's name. That's great! But, if we need to setup, for example, spam/not-spam reporting using IMAPSieve plugin, we still forced to specify mailbox's name in rules: # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/report-ham.sieve I think, it would be great to allow one to specify a special-use attribute in imapsieve_mailboxXXX_name and imapsieve_mailboxXXX_from settings. Best regards, Kirill Kirilenko.

1 0