Comment on How do you solve email?
dihutenosa@piefed.social 4 days ago
I self-host it with https://gitlab.com/simple-nixos-mailserver/nixos-mailserver.
- I had to set it up with all these SPF and DKIM and DMARC stuff. Wasn’t too hard, just follow the guide. Test with GMail - the message details view says exactly what you have, what you haven’t, and what’s wrong.
- Every now and then I have to jump through some hoops to get my IP allowlisted in some weird provider or antispam system.
Email is a very old protocol, it originates from the time when computers were connected only occasionally. It is very much possible to come an agreement to power up the antennas at something o’clock every day to exchange emails, and the rest of the time they just sit in the queue.
Practically speaking, if your home lab is down for something like 12h, it should not impact email delivery much at all - the sending servers would just keep retrying. Usually for 48h. From https://www.rfc-editor.org/rfc/rfc5321#section-4.5.4.1
mail that cannot be transmitted immediately MUST be queued and periodically retried by the sender.
The sender MUST delay retrying a particular destination after one attempt has failed.
Retries continue until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days.
Microsoft documents this: https://learn.microsoft.com/en-us/defender-office-365/mail-flow-about#mail-flow-delivery-faq
Deferred messages remain in our queues for one day.
I guess technically they’re RFC-compliant, but 1 day is not as much as I’d like…
northertech@fedia.io 4 days ago
Were you actually able to get good domain reputation with your sever on a residential ip?
dihutenosa@piefed.social 4 days ago
No idea. I keep hearing the term, “IP reputation”, but I don’t know any official registry where I could look up mine.
"google-site-verification=<base64-or-what>"All told, I can deliver email, AFAICT. If it lands in spam, well, tough luck - email from large providers also does.