DKIM, DMARC, SPF, rDNS/PTR, EHLO… all correct and verified in the email “original source,” BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.
DKIM, DMARC, SPF, rDNS/PTR, EHLO… all correct and verified in the email “original source,” BY GOOGLE. Still goes to SPAM folder because **** you, apparently. I hate Google.
Probably bad place to ask but.
Self hosting email is complicated only for sending mails or for receiving mail it’s also hard?
Depending on what you want to do you might not need to actually send any mail.
Also, the anti-spam rules do also apply if you are answering a mail, I suppose it does as a response envelopement doesn’t have any evidence that it’s an actual response. But I have no experience self hosting email.
@daniskarma @laurenceOfSuburbia yeah the complication is not technical so much as bureaucratic. Email itself is simple, but then you have to jump through hoops of tuning various other technical settings for Big Email to allow you in
I think it’s usually to do with sending, so if you’re only interested in receiving I think you’ll be fine (unless your server uptime’s really bad or something)
Self hosting receiving mail is honestly, pretty straightforward, all things considered. Setup your MX record to point at a server you control, configure software to save messages however you want. Perhaps the most complicated step is wiring up certbot or similar software to get your SSL certificate for your mailserver. A Debian Linux system,
apt-get install postfix; apt-get install dovecotwill get you nearly 90% of the way there.Depending on your preference. there are docker containers that can do 100% of the process too, with all sorts of nice bells and whistles. If you don’t care about sending email, you can skip DKIM/SPF/DMARC. (though, if you are never sending from your domain, check here: https://www.cloudflare.com/learning/dns/dns-records/protect-domains-without-email/ – there are some entries you can add to DNS to make sure everyone else knows)