October 2024 - dovecot

last_login plugin does not update IP
by Maciej Polewczyński 11 Oct '24

11 Oct '24

When using the last_login plugin I noticed that the IP address information is not updated. If there is no entry in the sql database for a given user, the first time the login date and time information and the IP address will be saved. Each subsequent login only updates the date and time. The IP address remains unchanged. Example configuration for pop3 service: map { pattern = shared/last-login/pop3/$user/$rip table = last_login value_field = last_pop3_access value_type = uint fields { userid = $user last_pop3_ip = $rip } } This is translated into the following sql command: INSERT INTO last_login (last_pop3_access,userid,last_pop3_ip) VALUES (1727691183673,'test','1.2.3.4') ON DUPLICATE KEY UPDATE last_pop3_access=1727691183673 You can see that after "ON DUPLICATE KEY" only the time is updated. Is there any way to influence the behavior of the plugin and the sql query so that the IP address is also updated? I'm using Dovecot v2.3.4 -- Best regards, Maciej Polewczyński Do or do not. There is no try.

3 3

Bug Report: Missing parent folders will cause some clients to not retrieve messages
by Brendon Meyer 09 Oct '24

09 Oct '24

Morning/Evening All, This is a general bug report but it applies to most versions of Dovecot that I have tested to date. I tried to find a previous case where something like this has been reported and for the life of me, I can't find one so if I am duplicating an existing bug report - please let me know. The server platform I am using is FreeBSD 14.1-STABLE (custom build) but that really doesn't have much of a bearing as I was able to recreate the problem on Linux as well as different FreeBSD versions and on different architectures going back as FreeBSD 12 under SPARC). Dovecot version is dovecot-2.3.21_6, but I have tried earlier versions as well and the behaviour is pretty consistent. Apple mail versions are multiple, but in the example I put forward below, I am specifically talking about v12.4 which came with OSX 10.14.6 (last release of Mojave). You get the same behaviour out of later versions of Apple mail that come with later relesaes of OSX/MacOS Thunderbird versions are multiple, but in the example I put forward I am using 115.15.0 (64-bit) under Linux. The behaviour is consistent with earlier versions as well as different platforms (such as Thunderbird on OSX, and Windows). Description of problem: When creating subfolders with tools such as imapfilter, if the parent of the subfolder does not exist, Dovecot will allow that folder to be created, and the tool will allow you to populate that folder with messages. The issue then rears it ugly head when you say use Thunderbird and the messages in this subfolder are not visible. This behaviour is not limited to Thunderbird (e.g. Outlook) but I am using Thunderbird as an example here. Oddly enough, the Apple mail client is *not* impacted in quite the same way (though it is impacted but the behaviour is very subtly different). Allow me to explain with a practical example as to what is happening, and I will parts of my *actual* config here to highlight the issue. I have a imapfilter task that routinely archives messages from the likes of "Sent". Easy enough. It takes each message and drops it in an Archives/sent-mail folder with the year as a parent and then inside that is the subfolders of YYYY-MM with the individual months. So looking at it, it looks something like this: Archives/sent-mail/YYYY/YYYY-MM The generated imapfilter rule that is used looks something like this: sent_202312_bgm = bgm['Sent']:sent_since('01-Dec-2023') * bgm['Sent']:sent_before('01-Jan-2024') sent_202312_bgm:move_messages(bgm['Archives/sent-mail/2023/2023-12']) This is all pretty simple - if the folder "Archives/sent-mail/2023/2023-12" does not exist it will create it and when done, it will then populate the folder with messages from "Sent". The issue is that if the "2023" parent folder does not exist, then some mail clients (as identified above - Thunderbird is an example) will never sync that mail. The workaround is to manually create the YYYY parent folders so that when imapfilter runs and creates the YYYY-MM subfolders then they are visible. I said that Apple mail is a weird edge case example. Its behaviour is not exactly simple or consistent either when missing parent folders, but you at least get some visual idea that something is wrong. Screenshots are probably doing going to come across very well in a forum group but allow me to describe what you see in Apple mail. In Apple mail, if the parent folder exists (for example say I use the year 2019), then see the subfolder in a "grey" colour with the name next to it and all is good. This folder *is* visible to Thunderbird and all the Apple mail functionality works. If the parent folder does *NOT* exist, this is where it gets a little weird. In my example, I have a year of 2023. That parent folder does *NOT* exist. That means that if you look at the Thunderbird view of the Archives/send-mail, you don't see a 2023 parent folder. Apple Mail *DOES* see the parent *BUT* two things are a bit off about it. #1. When you look at the folder in Apple mail, instead of being grey, it appears as a white colour. You can drill into the folder and see the YYYY-MM subfolders inside, but generally it doesn't appear to "work consistently". #2. Searches don't work correctly. Manually renaming the subfolders in Apple mail, then manually creating a parent folder and then moving everything back restores full functionality and also means that other mail clients such as Thunderbird for example will then see all the 2023 subfolders (e.g. 2023-01, 2023-02, etc). So ... is this a bug in Dovecot? If so ... has it been previously reported and if not, do I get a bug named after me? :P /BGM

4 4

aliases
by Сергей Сергей 09 Oct '24

09 Oct '24

Hello. Tell me how to set up mail aliases so that mail from one mailbox is forwarded to another mailbox. What configs need to be edited and what to enter. Thank you

3 3

LAYOUT=index requires mailbox_list _index=yes
by Marc 07 Oct '24

07 Oct '24

I am adding a namespace with LAYOUT=index to an existing configuration, and get this notification: LAYOUT=index requires mailbox_list_index=yes Maybe better to just not risk it and add LAYOUT=fs to my existing mail_location=mdbox: lines?

1 0

Namespace for seperate Storage of Archive
by Christian Großegger 05 Oct '24

05 Oct '24

Hi everyone, I found the Solution myself. The key was to simply create an unnamed mailbox directive so that the namespace prefix directly results into an mailbox that Thunderbirds shows as the Archive. Thanks everbody on the dovecot team for making such a brilliant Software! Greetings! Christian namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } namespace archivns { prefix = Archive/ <--- this is the Name which now appears at the same Level then Sent/Draft/... location = maildir:/mnt/mails2/%u separator = / mailbox { <--- here a name is omitted auto = subscribe special_use = \Archive } }

2 2

dovecot/Pigeonhole sieve sets seen flag
by Hadmut Danisch 05 Oct '24

05 Oct '24

Hi, I'm using dovecot, running Ubuntu 24.04 with dovecot 1:2.3.21+dfsg1-2ubuntu6 and postfix. Since Ubuntu dropped mailfilter for 24.04, I am replacing mailfilter with the sieve filter. Problem/Question: I am using something like if header :matches "Subject" "htest" { addflag "$label1"; fileinto :create "Test.${year}.${month}"; stop; } following https://doc.dovecot.org/2.3/configuration_manual/sieve/examples/ which works, but not as expected: When having the addflag, the mail is delivered as seen, i.e. put in the /cur directory of the Maildir folder. Without the addflag, it is put into /new , where it belongs to (as unseen). Why does addflag "$label1"; mark the Mail as seen? regards Hadmut (please respond directly, I am not on this list)

2 1

Helping doveadm sync detect moves between Maildir mailboxes? (reproducible example of bad behaviour)
by falsifian＠falsifian.org 02 Oct '24

02 Oct '24

Hi, Moving mail files between Maildir mailboxes often confuses doveadm sync: I end up with copies in both the original and new maildir. Exact details and script to reproduce follow. I can work around this by running doveadm move, but it does not fit well with my workflow, which is based on paths to mail files (using mblaze as my mail client). Two questions: 1. Is there anything I can do to help dovecot notice the moves, other than using doveadm move instead of just mv? I have tried liberal use of force-resync but the problem is still there. 2. Is this a bug? Details: OS: OpenBSD current $ dovecot --version 2.3.21.1 (d492236fa0) config: My repro script below uses a one-line config, only setting mail_location. (An OpenBSD 7.5 server running Dovecot 2.3.21 is involved in my real setup, but I was able to reproduce it locally without the server involved.) To reproduce: (shell script follows) - Make two maildirs "a" and "b", each with a subfolder ".Archive". - Manually write a mail file to a/cur. - doveadm sync - force-resync everything - manually move the file to a/.Archive/cur - force-resync everything again - doveadm sync - Now the mail file appears four times: in a, a/.Archive, b, and b/.Archive. Script to do the above follows my signature. -- James #!/bin/sh set -e # Run in a new directory with two maildirs named a and b and a simple config. mkdir bug; cd bug mkdir -p {a,b}/{,.Archive/}{cur,new,tmp} cat > dovecot.conf <<EOF mail_location=maildir:$PWD/a EOF # Deliver an email and sync. EXAMPLE_ID=12345.R67890.example.com cat > a/cur/$EXAMPLE_ID:2, <<EOF some email EOF doveadm -c dovecot.conf sync maildir:b # Move the email and sync again. Run force-resync between steps in case it helps. doveadm -c dovecot.conf force-resync INBOX doveadm -c dovecot.conf force-resync Archive doveadm -c dovecot.conf -o mail_location=maildir:$PWD/b force-resync INBOX doveadm -c dovecot.conf -o mail_location=maildir:$PWD/b force-resync Archive mv a/cur/$EXAMPLE_ID* a/.Archive/cur doveadm -c dovecot.conf force-resync INBOX doveadm -c dovecot.conf force-resync Archive doveadm -c dovecot.conf -o mail_location=maildir:$PWD/b force-resync INBOX doveadm -c dovecot.conf -o mail_location=maildir:$PWD/b force-resync Archive doveadm -c dovecot.conf sync maildir:b echo in a: doveadm -c dovecot.conf -fflow fetch 'mailbox guid' all echo echo in b: doveadm -c dovecot.conf -fflow -o mail_location=maildir:$PWD/b fetch 'mailbox guid' all

2 4