Are you talking about residential or about dynamic? Because there kinda is a reason for this for dynamic addresses (PC malware sending spam, and the impossibility to list the particular affected PC because it's constantly changing addreses, so you only can block all the addresses those PCs could be using).
If you do have static addresses, whether residential or not, those should not be listed in dialup block lists.
If your home internet connection has dynamic addresses, you still can run your mail server at home by renting some tiny VPS and tunneling its addresses to your home server ...
Practical DIY SMTP is a lost battle. Unless you're in it for the experience of the hosting itself.
Any one of the thousands of VPS hosters that are not one of the half dozen huge "cloud server" companies?
> Practical DIY SMTP is a lost battle. Unless you're in it for the experience of the hosting itself.
No, it's very much not, it works perfectly fine. Or at least well enough--arguably, you should be able to send directly from dialup hosts with a well-established domain and SPF, so things aren't as good as they could be, but far from what some people claim.
Indeed my residential internet connection has a static address but it still gets flagged for spam because it’s inside a residential subnet.
As in? I mean, what makes it a "residential subnet"? Have you tried talking to your ISP about this?
But many people rely on spamlists, ie lists of ips known to relay spam. The proble with this is twofold:
1. Some people just took the authority to decide who sends spam and who does not. If you get on one of those lists, usually you have to get in touch and pay to get out.
2. Such people usually include residential ip subnets by default, for no technical reason whatsoever.
So in the end my mailserver at home has been in a spamlist for years, even though i never relayed spam and was very careful to configure outbound relay authentication/authorisation, spf, dkim etc.