That whole #dovecot breaking update (and from what I've seen the unreasonable pro version, at least for small setups) makes me question self-hosting my mail server…
I'm fine with investing time to setup something the first time - but updates (especially not minor) should never be breaking… - neither should they require quiet some time investment imho…
#SelfHosting #mailserver

So I guess I either try courier-imap server or cyrus-imapd. Not sure of the differences between the two or whether one is better than the other.

Since Dovecot 2.4 is dropping replication, I'll definitely need to rework my mail servers and those for BSDMail. I think I'll be going back to Cyrus, which I last used over 20 years ago. The problem is my memories have long faded, so it'll be like studying it again from scratch. And that makes me happy, because it'll be like learning something totally new!

Special thanks to @h3artbl33d for the heads up!

damn, #dovecot changed most configuration syntax.. looks like someone will be working hard tonight.

Hey #BSD friends!

Is there a way to set up oauth2 on Dovecot for authentication? (All local Auth, no Google or Microsoft involved). Do I have to run some big chunky java blob like keycloak or is there a much lighter weight implementation C somewhere?

#eMail #selfHosting gurus: I am looking for the simplest possible way to host myself a mailbox I can add to my email clients (Thunderbird, phone, etc.) as usual, so I can move mails there to free up space on the 3rd party "real" emails, then back them up separately on my server.

I do not want receiving or sending emails to work. Just an IMAP or whatever box I can shove emails in the face by dragging them in Thunderbird or with a script.

Ideally available in #NixOS

#dovecot?

I've Got Mail https://bonesmoses.org/2025/ive-got-mail/

I seem to have a #DNS problem (unheard of, right?).
I've got #nginx working with #HTTPS, using #certbot, and there's an A record that points at the IP address of the server. So I can go to https://mydomain.com and it's all dandy (thank you @eff).
Now I want a TLS certificate for the #Dovecot mail server. I've set up a virtual server for mail.mydomain.com like this:
```
server {
listen 80;
listen [::]:80;
server_name mail.mydomain.com;

root /usr/share/nginx/html/;

location ~ /.well-known/acme-challenge {
allow all;
}
}
```
But when I run certbot I get this:
```
NoRecords
Fatal
No valid A or AAAA records could be ultimately resolved for mail.mydomain.com. This means that Let's Encrypt would not be able to connect to your domain to perform HTTP validation, since it would not know where to connect to.
No A or AAAA records found.
```
On my domain registrar's dashboard it says that I don't need to set up a MX record if I have only one mail server and it is on the same IP address as my Domain Record. But I'm thinking the certbot error doesn't sound like it's looking for an MX record.
Should I temporarily make a subdomain record for mail.mydomain.com?
#ImSoConfused #AskFedi #FediTechSupport

#fedihelp , please: I'm #selfhosting #dovecot and #postfix and running out of disk space with my mails reaching back into last century. I'd like to remove the oldest ones and keep an archive of any kind on a different host. What would be the easiest way to achieve that?
Maybe just imap-sync to some special maildir?

Edit:typo

found #k9 #Android or #thunderbird #Windows11 email client had expired #certificate error and would not download emails so I restarted dovecot on Linux server and error stopped #dovecot #postfix #certificate #error #linux certificate had been updated but Dovecot had not synced @thunderbird

A few months ago, I wrote an article about how to use a Dovecot plugin to give yourself push email on iOS devices: https://colincogle.name/blog/dovecot-with-apple-push/

Well, thanks to @gctnwl@newsie.social and countless GitHub users — i.e., https://github.com/freswa/dovecot-xaps-daemon/issues/43 — I regret to inform you all that the XAPPLEPUSHSERVICE concept might be dead.

This project relied on using macOS Server’s API’s to request a certificate for the Apple Push Notification Service, so that one could send yourself notifications. Well, macOS Server died a long time ago, configurations evolved into MDM profiles (which, honestly, are easier), and the certificate API was deprecated and then disabled last autumn to little fanfare.

Is there any hope for push IMAP on iOS in the future? Only time will tell. If you have a valid certificate, XAPSd will keep working until it expires, but after that, who knows? I might have to go back to fetching my email!

(Oh, and if it works for you, don’t upgrade to Dovecot 2.4. I wasted an evening migrating and unmigrating my config files.)

If anyone knows anyone at Apple, please let me know how to complain to something that’s not a feedback form.

well, #Dovecot 2.4 came out and it brought more changes than expected.

Not just the dropping of checkpassword-based authentication, but also many changes in configuration syntax and in some architecture.

After a couple of days trying to adjust from the previous configuration, it now appears to be working as expected. Time will tell.

*Info from dad: Mail-Server down
*checks docker ps: Dovecot "Restarting"
*checks docker logs: Permission denied
*corrects permissions, to what log expects
*Still restarting
*docker log: "unknown setting"
*checks docker tag
*searches release notes
*

Dovecot 2.4 secure IMAP server has been released with a new signing key, experimental ARM64 Docker support, and major config changes.
https://linuxiac.com/dovecot-2-4-secure-imap-server-released/

Test run successfully completed!

I moved from a classic multi-component mail server setup (based on #postfix, #dovecot,…) to #Stalwart mailserver - entirely written in Rust and it runs and performs great so far after half an year :)