146 points by computer23 4 days ago | 148 comments | View on ycombinator
BLKNSLVR 4 days ago |
albertgoeswoof 4 days ago |
But with AI, it’s easy to get DKIM, DMARC, HELO etc. set up perfectly for almost no effort (maybe fcrdns is a bit more complex as it’s a manual process at most ISPs)
I think we are in the end going to go back to it just being based on IP (v4) reputation, and this is all theatre.
cowlevel 3 days ago |
computer23 4 days ago |
Microsoft Office 365 relies on Spamhaus and was blocking my email because the HELO on the mail server was mydomain.com instead of mailserver.mydomain.com.
Once the problem was fixed, it took time for Spamhaus to re-scan the mail server and take the mail server off the block list. And it took more time for Microsoft to stop blocking mail.
johnea 3 days ago |
superkuh 4 days ago |
I've published a DMARC record that basically says to ignore DMARC and do nothing. I wonder if this will be enough.
v=DMARC1;p=none;adkim=r;aspf=r;pct=0
I have no plans to ever change from none.greatgib 3 days ago |
tete 3 days ago |
I am unsure how the first ones are financially viable, maybe also hacked into?
Improperly setup mail servers I think are a thing of the past, since all the big providers have been blocking them for ages. Sure every now and then some come through, but at this point I believe these are basically all just old spam systems that are extremely easy to detect.
sneak 4 days ago |
fschuett 3 days ago |
gertrunde 3 days ago |
It's pretty much the only thing I usually bother with reverse DNS for.
xmddmx 4 days ago |
Or does it also apply to people sending mail through their mail hosting company (when that company is not Google or Microsoft).
Specific example: I run servers "at home" that send mail through SMTP.
I have forward DNS properly set up, but my reverse DNS is syn-123-123-123-123.res.spectrum.com
My mail servers are, however, sending the mail through my mail host (DreamHost) and so I'm hoping that not having reverse DNS at home won't be a problem.
Am I reading the Spaumhaus rules correctly?
raggi 4 days ago |
can i get recruiter list spam punished?
azinman2 3 days ago |
nubinetwork 4 days ago |
How was this not the default? If you're going to send me mail, I already check all of those... and I also check to see if you hold a MX. If your DNS is _that_ bad, I probably don't want your spam anyways...
undefined 3 days ago |
jiveturkey 3 days ago |
nikolay 3 days ago |
jwr 4 days ago |
We've allowed them to grow this way by preferring convenience.
zurfer 3 days ago |
Currently it seems to cost 0.001ct.
DmarcDkim about 1 hour ago |
djgrillmaster 4 days ago |
logicallee 3 days ago |
> 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.