> Publish forward-confirmed reverse DNS for every sending IP
> Every sending IP must have a reverse DNS entry pointing to a fully qualified domain name (FQDN). That hostname must, in turn, resolve back to the same sending IP address. This is known as forward-confirmed reverse DNS (FCrDNS). An IP with missing or mismatched reverse DNS is treated as suspicious and is one of the most common reasons for an IP to be considered for listing.
I self-host an email server behind my ISPs connection, and so I do not own the IP address that I send mail from, therefore I can't satisfy the reverse DNS requirement.
I’m surprised your emails have ever gotten through if they’re coming from a residential IP. That’s definitely not considered good practice.
If you have a static IP address and they're allowing outbound port 25 then my first thought is that you might have some sort of premium residential or business account that permits hosting in the ToS, in which case I would then infer they might allow you to specify a PTR record in their zone or maybe even support delegation to you.
Lots of inferences there, but presuming Spamhaus isn't already blacklisting your IP address then that's additional evidence you don't have a vanilla residential IP address.
My residential connection has working reverse DNS, although I fail to see how this has anything to do with spam.
Most ISPs have a PTR that also resolves to the IP; try using the one they chose for you (cust-462728.atl1.ispname.com) in your HELO.
Yeah, well, you can’t always get what you want.
Worth calling and asking, some ISPs will update your static IPs rDNS on request.