On Fri, 4 Sep 2020 15:00:59 +0100, Laura Atkins via mailop <[email protected]>
wrote:
>Oh.
>
>Youre trying to send mail from an Amazon compute server sitting in the middle
>of a range of IPs that have the generic aws rDNS.Youre being blocked because
>youre sending from a place many, many people dont want mail from.
>
>You need to get your mailserver hosted somewhere that is not a cloud provider.
>Get a VPS or better.
A hazard of multiple AWS IPs: they tend to be spread out over multiple
netblocks, making one appear to some observers to be a snowshoe operation (not
to minimize the poor reputation some of those netblocks, or the entire AS may
have).
For the third time this week, I have a client who also was not diligent in
getting rDNS set up properly; they would EHLO as smtp1-3.example.com but the
IP would reverse to something-or-other.compute-1.amazonaws.com. Instant
death.
One of the clients had failed to deal with IP reassignments, so even the
forward DNS didn't match the EHLO. Complicated by the fact that the server
had RFC 1918 addresses for the bound IPs, but nobody on the client's staff had
access to the NAT configuration to even tell us what the entries should have
been.
Thus the 0.5% open rates on otherwise decent mail...
mdr
--
"There are no laws here, only agreements."
-- Masahiko
_______________________________________________
mailop mailing list
[email protected]
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
