tl;dr: some AWS IPs might be marked as spam senders due the previous users
first some sources:
check any Amaozn Elastic IP before you start using it here: http://www.mxtoolbox.com/SuperTool.aspx
and joke continue!
i’ve allocated new elastic IP, checked it on spamhaus lookup tool if its blocked, and picked the one what wasn’t.
so everything nice and clean, i’ve reset server settings than DNS settings and i did wait. it took some time for DNS to reset.
for now it was 2 days. sunday morning, when i’ve realized that DNS was finally refreshed, i’ve assigned this new ‘clean’ IP to my instance and deleted the old one
however, on my surprise i’ve realized that my IP is blocked again!!! WTF? HOW?
after re-reading forums (what is the only communication channel with AWS) again, i’ve filled form suggested by amazon for sending emails. (originally it was form for sending shits loats of emails to let amazon know what this is gonna happend, but now it looks like everyone who want to use EC2 as mail server have to use it)
nice to find out, after a week, that this has to be done!
of course, no response from amaozn what so ever, i haven’t even received confirmation email after filling that form!
they just dont care.
long story short, AWS for sending emails sucks hard! otherwise i still love it
- set linux command to run on start
- fontis ANZ extension – critical bug