I tried to maintain my self hosted email server for some years now. Altough I know what I'm doing, technical-wise, and there are a lot of nice tutorials and solutions, like dockerized all-in-one packages: you still have to take care of updates, upgrades and stuff described here. It happend more than once that my setup did not work and I was missing important messages. You could argue that I don't know what I am doing. Or hosting your own email service just does not make much sense if it's for your own private stuff only.
That's why I finally switched to Outlook to manage emails from my own domain.
As for “asking AWS for rdns/removing email restrictions”, I’ve always found that explaining what you have done to secure the server and what you have put in place to prevent the IPs from sending spam helps (as in my requests have always been fulfilled first try and never had them reply asking for more info / do you know what you are doing.)
The author complains that the Google employee is arrogant and links to some support posts to prove his point. I find nothing arrogant about the information or the way it is presented by the Google employee. I do find the author's posts to be extremely arrogant and rude.
It’s also a complaint of with as much detail as ‘it doesn’t work’ and even ‘don’t tell me what to do, I already have done everything correctly’. What does he expect to happen if he just mails in a complaint without even mentioning the addresses he’s trying to use?
It isn't even a Google employee that the author is complaining about - it's a volunteer on the Google support forums. I agree, the author does not come across in a good light at all.
5 comments
[ 3.5 ms ] story [ 21.2 ms ] threadThat's why I finally switched to Outlook to manage emails from my own domain.
Why isn't there a simple solution?