3 ms·

It's not that difficult. I host my email server on an AWS machine (so the IP that gests out is clean), and all I had to do is to setup DKIM signature and create

It's not that difficult. I host my email server on an AWS machine (so the IP that gests out is clean), and all I had to do is to setup DKIM signature and create the SPF, DMARC and DKIM DNS records for the domains. Setting all up is complex, but there are project that give all the tools in a Docker container. Since I wanted to learn it I did all manually, and did set up postifx, dovecot, opendkim, postfixadmin and even squirrelmail as a "retro" web interface, with a postgresql database to keep the mailboxes and the accounts. It was an interesting experience, plus now I have full control of the mail system, e.g. I can decide to route the mail in whatever directory just by changing the SQL query that decides in which mailbox a message should be delivered.

baobabKoodaa 3y ago
> It's not that difficult. I host my email server on an AWS machine (so the IP that gests out is clean), and all I had to do is to setup DKIM signature and create the SPF, DMARC and DKIM DNS records for the domains. I personally did do all of that, and my emails didn't get delivered. I wrote about my experience in detail here: https://www.attejuvonen.fi/dont-send-email-from-your-own-server/ https://www.attejuvonen.fi/dont-send-email-from-your-own-ser...
- alerighi 3y ago
  The most important thing is to setup DKIM, SPF and DMARC correctly. I mean sign the emails with the correct key, but also setup the correct records, e.g. SPF record must be TXT, if you create a (deprecated) SPF type record GMail won't recognize it, even if you also have the TXT one! Of course they don't mention it in the documentation, and I've spent 1 month of trial and error to figure it out. And the DKIM record needs to be formatted exactly correctly (antother thing that took me time to figure it out) With DMARC you can specify that the recipient sends you a periodc report of the delivery status, this is useful to debug eventual problems. For example GMail and Outlook send this out, and gives you information about the fact that your DMARC is working correctly and SPF and DKIM checks are passed. Anyway when you manage to get it working, it did work for around 4 years without any issues. I've even reinstalled the mailserver to another machine (keeping the same IP) and I did not have any issue in the migration.

baobabKoodaa 3y ago

> It's not that difficult. I host my email server on an AWS machine (so the IP that gests out is clean), and all I had to do is to setup DKIM signature and create the SPF, DMARC and DKIM DNS records for the domains. I personally did do all of that, and my emails didn't get delivered. I wrote about my experience in detail here: https://www.attejuvonen.fi/dont-send-email-from-your-own-server/ https://www.attejuvonen.fi/dont-send-email-from-your-own-ser...

alerighi 3y ago
The most important thing is to setup DKIM, SPF and DMARC correctly. I mean sign the emails with the correct key, but also setup the correct records, e.g. SPF record must be TXT, if you create a (deprecated) SPF type record GMail won't recognize it, even if you also have the TXT one! Of course they don't mention it in the documentation, and I've spent 1 month of trial and error to figure it out. And the DKIM record needs to be formatted exactly correctly (antother thing that took me time to figure it out) With DMARC you can specify that the recipient sends you a periodc report of the delivery status, this is useful to debug eventual problems. For example GMail and Outlook send this out, and gives you information about the fact that your DMARC is working correctly and SPF and DKIM checks are passed. Anyway when you manage to get it working, it did work for around 4 years without any issues. I've even reinstalled the mailserver to another machine (keeping the same IP) and I did not have any issue in the migration.