Furthermore, the dovecot 2.4 branch no longer supports their replication feature, it was removed.
For users relying on the replication feature or who are unable to perform the 2.4 migration right now, we provide alternative packages available in [extra]:
This update hit me unprepared. I was not able to get the new dovecot working. At the end I deinstalled dovecot. It was a left over from the old days anyways. Good bye, dovecot. You served me well, but this was it.
I never knew there are people that run mailservers on Arch Linux. I ran into this issue when migrating my mailserver from CentOS to Debian and had to redo most of Dovecot configuration.
I was hit by that train last night …
Fortunately I was able to install dovecot23 and pigeonhole23 as mentioned in the Arch News and my dovecot is running fine again.
During the next days I will try to migrate to the new dovecot version. Unfortunately the documentation what really needs to be changed in the dovecot.conf is not that good.
Did someone find an example where an old configuration is compared to a new one?
Well, my dovecot IMAP-server is running almost 6 years on EndeavourOS …
Cool. I prefer to run my mailserver stuff on a distribution that’s not rolling but cool that are people out there that do. What kind of setup are using dovecot for on EndeavourOS?
Normally I would agree. As I know the limitations of running server services on an Arch based installation I am happy with doing so. One main thing is to perform updates only once a week or less often.
dovecot stores the mailboxes of the whole family and runs together with postfix, fetchmail an sieve / pigeonhole.
We just have different requirements for a server, neither are wrong and both can have their advantages and disadvantages. I just like a setup that mostly is a setup and forget setup, as with Arch it may occur more often that configurations may change.
Do you know of a good guide for sieve, as the official documention hasn’t helped me much yet. I was wanting to use it to automatically have spam mails sorted to my junk folder if I were to receive one that is marked as spam. If not I’ll just look into it again and see how far I get, cause I don’t think it should be as hard to configure as how the dovecot documentation makes it seem.
Sorry, I cannot help you sorting SPAM with sieve. My configuration simply does sort e-mail to several folders according to some entries in the header of the e-mail.
My problem is that I really don’ t know a good howto for sieve. I have configured my scripts many years ago when there was a working sieve addon for thunderbird which had a good explanation and help.
The only way I know by today is using the filter option in software like roundcube or snappymail. My roundcube installation looks at my dovecot IMAP server and stores the sieve filters there so pigeonhole can use them. roundcube needs a plugin called managesieve.
What kind of setup are using dovecot for on EndeavourOS?