- dovecot - dovecot.org

Replication going away?
by Vladimir Mishonov 26 Jan '24

26 Jan '24

Hello everyone. Just saw this commit in the official Github repo: https://github.com/dovecot/core/commit/4c04e4c30fd4817a8b0e11d04d9681173f69… Looking at the commit details, it appears that it completely removes the replication feature. I'm a bit perplexed by this change and am not sure what might be the justification for it. Personally, I find replication to be very useful, as it allows me to maintain a synchronized mirror of all of my mailboxes on my home server, for use as backup in case the primary server goes down for some reason. Perhaps there's some sort of replacement being planned for this feature? Or maybe the relevant code is simply going to be refactored to a plugin or external program, and there's nothing to worry about at all? In any case, I'd greatly appreciate if one of the developers could comment on this change. -- Kind regards, a concerned user of Dovecot (Vladimir)

34 66

Error activating filter set
by joe a 25 Jan '24

25 Jan '24

Some success creating and using filters, created via roundcube, but, when testing activate and deactivating filter sets, received an error. However, I can edit and add filters without apparent error, even "importing" from an existing filter set. var/log/dovecot-info.log shows, in part: ([%user] refers to the active dovecot user, whose account seems to operate perfectly, aside from filters). Obfuscated out of habit. Form is user(a)domain.com. "Jan 24 15:44:49 managesieve([%user])<23204><Pk9VIrcPfKx/AAAB>: Info: Failed to activate script `dovecot.orig': Internal error occurred. Refer to server log for more information. [2024-01-24 15:44:49]" It is unclear, among other things, what and where this "server log" is. tail -f /var/log/messages shows nothing during the various traipsing about in filters Not just foggy outdoors lately.

1 1

IMAP Sieve fileinto :create intermediate folders
by dovecot-4tg＠freakin.rocks 25 Jan '24

25 Jan '24

I apologize if this isn't the appropriate place for this question. Consider a Sieve script with this instruction: fileinto :create "folder 1.folder 2.folder 3"; That faithfully creates in Maildir the folder named '.folder 1.folder 2.folder 3'/ An IMAP Client shows this in tree format as: - folder 1 - - folder 2 - - - folder 3 But there isn't really a "folder 2". That is, there is no Maildir '.folder 1.folder 2' so what happens in the MUA is really subject to its coding. In Thunderbird, for example, 'folder 2' is grayed out. You can't subscribe to it or drop a file into that folder because it is disabled. With no mail actually targeted to that folder, that's generally not a problem, but Thunderbird does raise errors as it attempts to scan folders, correctly claiming that it can't access the folder because it doesn't exist. That's irritating to the user. So to the questions: 1) Is there anything in Dovecot or Pidgeonhole Sieve that might allow us to auto-create the missing intermediate folders? Maybe using a vnd.dovecot.* extension or some sieve capability? 2) Aside from being inelegant, is there anything wrong with a cron script that creates missing Maildir folders? While I am developer, I haven't yet looked into the proper way to create and configure folders user folders. 3) Would it be more appropriate to create a new extension, implementation of some RFC, Lua script, or some other type of plugin that might get triggered on a fileinto operation? Again, I haven't looked deeply in this direction and could use a few RTM references. 4) Might there already exist an external script or custom extension that does this? 5) Might this be a worthy enhancement request for Dovecot or Pidgeonhole Sieve? Thanks! Dovecot 2.3.7.2 / Pidgeonhole 0.5.7.2 / Ubuntu v20

1 0

lda or lmtp for sieve?
by Joe Acquisto 25 Jan '24

25 Jan '24

I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does it matter to sieve implementation if one uses only lmtp?

7 13

Can Dovecot use an MH data store?
by Steve Litt 25 Jan '24

25 Jan '24

Hi all, I know Dovecot can use a Maildir mail store and a Mailbox mail store. Can it also use an MH mail store? If so, is there a way of getting procmail to dump messages into the correct MH folder? Thanks, SteveT Steve Litt Autumn 2023 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21

1 0

Re: "Connection reset by peer" errors with Outlook
by Joseph Tam 24 Jan '24

24 Jan '24

From: Steve Dondley <s(a)dondley.com> > I have no idea what is triggering it for so many different users from legit > email addresses. Still investigating. But this appears to be a fail2ban > problem, not a dovecot problem. My logs are filled with failed authentication from Outlook clients. The clients seem to be trying different usernames (with/without domains), and maybe SSL/TLS flavours. My guess is Outlook is doing some autodiscovery/autoconfiguration thing, and occasionally hits the right combo and successfully authenticates. I'm not sure I would characterise this as a fail2ban problem. Fail2ban is doing what it says on the side of the tin: looking for repeated authentication failures, and blocking those that fail too many times. The real problem is Outlook fumble around for the correct settings, and mimicking a brute force attack. I've had great difficulty getting some Outlook clients to configure exactly the settings it should have (like excluding domain names from usernames). Try running his command line using Windows-R (not from cmd.exe). outlook.exe /PIM NoEmail This will avoid the auto-setup process that railroads you into frustration. MacOSX Mail app tries the same stuff, but at least you can turn that behaviour off and stop it from second guessing your settings. Joseph Tam <jtam.home(a)gmail.com>

2 1

Managesieve "config" unable to complete?
by joe a 24 Jan '24

24 Jan '24

What say we try this again, on a "blank slate"? Dovecot installed on OpenSuse Leap 15.5, from their supplied "dovecot23" package. That package claims to be Dovecot 2.3.21 and Pigeonhole 0.5.21 Unable to get managesieve to bind to port 4190. Output of dovecot -n attached. Various tools, including lsof, sockets, do not show 4190 in use. While grasping for/at straws, noticed this: ~: # lsof | grep manage config 19097 root mem REG 0,47 6896 257261 /usr/lib64/dovecot/modules/settings/libmanagesieve_settings.so config 19097 root mem REG 0,47 14696 257260 /usr/lib64/dovecot/modules/settings/libmanagesieve_login_settings.so Does that suggest an attempt to configure managesieve is unable to do so? What does it infer? Bad configuration? File ownership? File rights? Bug? Thanks for patience and forbearance

3 6

Strangeness in defining "protocols"
by joe a 24 Jan '24

24 Jan '24

Well, a strangeness to my view. Since this is an opensuse package and not the "lastest and greatest", not sure if I should post this here or "over there". It is a given that I may have, through some noobiness have bungled something early on that is causing this. I am prepared to accept the semi-public ritual shaming that may follow. All references to results mean per "dovecot -n". One can be assured that dovecot.conf was edited followed by "dovecot -n", then 20-managesieve.conf edited followed by "dovecot -n", for each "set". What happens is, it appears, that if one specifies or alters the "default" protocols in /etc/dovecot/dovecot.conf, any protocols subsequently defined, at least in /etc/dovecot/conf.d/20-managesieve.conf, are not honored. It does not seem to matter if it is specified as "protocols = sieve" or "protocols = $protocols sieve". Further, in /etc/dovecot/dovecot.conf, if one comments out "protocols", one finds protocols is not listed at all, unless there is a protocol defined later such as "sieve" in 20-managesieve.conf. if one lists "protocols = " then "protocols = " is listed even if a protocol is defined later such as "sieve" in 20-managesieve.conf of one lists "protocols = $protocols", nothing is listed, unless if: "protocols = sieve" is defined in 20-managesieve.conf, "protocols = sieve" is listed "protocols = $protocols sieve" is defined in 20-managesieve.conf - then "protocols = imap pop3 lmtp sieve" is listed. Again, all as shown by "dovecot -n" after editing each file(s). I hope this is useful in determining if there is a problem, and helps lead to a solution if one is warranted. I'll send this also to the openSuse list as a distinct email.

1 0

managesieve server not answering?
by Joe Acquisto 23 Jan '24

23 Jan '24

Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . .

6 32

Replication between three or more servers
by tomas.simonaitis＠gmail.com 23 Jan '24

23 Jan '24

Hi list members, documentation says "Replication works only between server pairs. If you have a large cluster, you need multiple independently functioning Dovecot backend pairs". Do I understant correctly, that in order to have replication between 3 servers, one would need to run 2 instances of dovecot on each server with (a bit) different configuration. e.g. Serv1: -- dovecot-1.conf .. plugin { mail_replica = tcps:Serv2:1234 } .. -- dovecot-2.conf .. plugin { mail_replica = tcps:Serv3:1234 } .. Serv2: -- dovecot-1.conf .. plugin { mail_replica = tcps:Serv1:1234 } .. -- dovecot-2.conf .. plugin { mail_replica = tcps:Serv3:1234 } .. etc. Won't two processes of dovecot in one machine (assuming local storage) conflict accessing same Maildirs? Thanks for any insights

1 0