Remix.run Logo
▲ BLKNSLVR 3 hours ago

> 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.

▲cowlevel 8 minutes ago | parent | next [-]

The majority of the internet has been blocking or silently discarding mail from your server then. This has been a de facto requirement for a long time.

▲rafram 3 hours ago | parent | prev | next [-]

I’m surprised your emails have ever gotten through if they’re coming from a residential IP. That’s definitely not considered good practice.

▲BLKNSLVR 2 hours ago | parent | next [-]

Residential IPs seem to be the most trusted these days, other than those, ironically, owned by the handful of big tech companies.

Email should be able to be run from anywhere.

▲traceroute66 an hour ago | parent [-]

> Residential IPs seem to be the most trusted these days

Oh, I see we've got a stand-up comedian in our ranks. ;)

Most trusted ? You mean aside from all those residential IPs we see in our logs on a daily basis with the inevitably infected machines behind them taking part in DDoS attacks and other shenanigans.

At best residential IPs are in the same category of IPs of the so-called "bulletproof hosts" and similar.

Spamhaus and others maintain databases of residential IPs and whilst it doesn't get used for auto-blocking, most sensible organisations will reduce the trust score by a large chunk if its a residential IP.

▲BLKNSLVR an hour ago | parent | next [-]

;)

My comment is based on the various recent discussions of "residential proxies", which are used for scraping because almost all of the VPS hosted IP ranges have got bad enough reputations that they're either blocked or rate limited or captcha-barricaded, etc.

I personally keep a log of IP addresses that I block, but I'm entirely blind to their source, and often get negative feedback about "but if it's residential then the IP address will be re-assigned to someone else" - which doesn't sound like a good "trust that traffic" argument to me.

I'm of the opinion that 99.9% of residential proxies are malware / involuntary, and that even the companies that attempt to 'herd' residential proxies legitimately are either criminal front companies or grew from criminal activity (not that that's always a bad thing).

Getting well off-topic here though.

P.S.

> Oh, I see we've got a stand-up comedian in our ranks. ;)

Says traceroute66. Love it.

▲cowlevel 7 minutes ago | parent | prev [-]

Why do you think they're ending up in your logs and not being blocked at an earlier layer?

▲sneak 2 hours ago | parent | prev | next [-]

Not being able to send mail at all from a residential IP is bullshit, though. Increase its spam score, but let it through.

▲cowlevel 7 minutes ago | parent [-]

Spamhaus doesn't run anyone's mail server so that is what it is doing. If someone has configured their server to block mail over a certain Spamhaus score then that was their decision.

▲mzajc 2 hours ago | parent | prev [-]

I'm guessing good practice is renting a VPS and hoping it's not on blacklists already, or (more commonly) letting third parties read your mail by using a relay service. Or should we be applying for an ASN and buying IP blocks just to send mail?

▲cowlevel 5 minutes ago | parent | next [-]

You should just host your mail server on a VPS and not overthink it. If someone is blocking your VPS and you urgently need to reach them, just use your old address on a big provider as a fallback.

▲dspillett an hour ago | parent | prev | next [-]

There are SMTP relay services that are cheaper than a reliable VPS, that will manage monitoring the sending addresses for appearance in blocklists and do the work to fix that so you don't have to. I still send direct (my home account is in an almost-commercial plan with an ISP that takes things seriously including IP reputation), but if that starts to fail I'll move over to one of those services rather than using a cheap VPS for sending. Maybe more than one for resilience.

▲wahern 2 hours ago | parent | prev [-]

A reputable and conscientious VPS provider will rigorously block outbound port 25. Some of those allow you to request outbound port 25 on a discretionary basis. If they're quick to respond to complaints then their address blocks should be pretty clean. You can always lookup your assigned address in various blacklists and roll the dice again on a new instance if you get a bad one. Ditto if you find Google or Microsoft doesn't like it, either.

▲wahern 2 hours ago | parent | prev | next [-]

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.

▲BLKNSLVR 2 hours ago | parent [-]

My ISP does block outbound port 25 by default, I specifically asked for it to be unblocked for me, and they obliged.

▲wahern 43 minutes ago | parent [-]

Have you asked, yet, about a PTR record? Not every ISP has a DNS system tied into a web portal for automated edits. Even some large ISPs still manange their zones through traditional zone files. But that doesn't mean they don't support modifying PTR records for customers. It may be just a matter of you putting in a request and some greybeard sysadmin resolving the ticket by firing up vi or emacs to edit one of their zone files. This might even be preferable because it's more likely they'd be open to delegating d.c.b.a.in-addr.arpa to your own DNS server. That would allow you to add and modify PTR records without having to go through them each time, whether manually or through some bespoke web service.

▲basilikum 26 minutes ago | parent | prev | next [-]

Are you able to actually get emails delivered?

▲trollbridge 2 hours ago | parent | prev | next [-]

My residential connection has working reverse DNS, although I fail to see how this has anything to do with spam.

▲Saris an hour ago | parent | prev | next [-]

Worth calling and asking, some ISPs will update your static IPs rDNS on request.

▲sneak 2 hours ago | parent | prev | next [-]

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.

▲edelbitter 2 hours ago | parent | next [-]

If the ISP is not permitting you to configure the PTR of "your" addresses, then are they really your addresses? Spamhaus specifically recommends a "branded" name. Deferring to the (recognizable as such) ISPs defaults, and thus raising the suspicion of attempting to wash all customers together is not terribly useful with other antispam systems either.

▲BLKNSLVR 2 hours ago | parent | next [-]

On residential, they're never "your" IP address. The one assigned to me is 'mostly static', but they did notify me that the IP address they'd assigned to my connection was going to change, which it now has.

Given my ISP has been kind enough to allow 'bridge mode' for my router, and outgoing traffic on port 25, then maybe I could ask them to change the reverse DNS lookup as well - feels like it may be a bridge too far, all I can do is ask though.

Separate, but related, I host email for multiple domains on this connection, so the reverse lookup would only be relevant for one of those domains. I'm not sure if there are additional ways around that, but haven't thought in too much detail about it yet.

▲dspillett an hour ago | parent [-]

> I host email for multiple domains on this connection, so the reverse lookup would only be relevant for one of those domains.

For that you'll need to pick a domain that you don't mind the others being associated with, and having all MX entries be pointing to the sending hostnames for that. Or you'll need multiple addresses and some way to route outgoing mail through the right one.

▲sneak 2 hours ago | parent | prev [-]

No, your ISP’s IPs are not “really your addresses”, and precisely no one claimed they were. This is a workaround so that someone can send emails out. Most people don’t have their own PI IP space, especially these days.

▲BLKNSLVR 2 hours ago | parent | prev [-]

Yeah, it does have a reverse DNS that resolves to the ISP, and whilst looking at the article I had the same thought. Might see if I can implement that sooner rather than later.

▲UqWBcuFx6NV4r 2 hours ago | parent | prev [-]

Yeah, well, you can’t always get what you want.