On Mon, 15 Jan 2024, Cabel Sasser wrote:
There are 1,239 gTLDs. The SpamAssassin source* blocks just *22* of them.
If you believe every new gTLD is garbage (and I get that!), why isn’t
SpamAssassin automatically dinging, say, 1,200+ of them?
Or put another way, why _these_ 22, and _only_ these 22, and not the rest?
That’s the “science” I’m trying to understand! :)
Primarily it's the real-world email traffic that scoring contributors use
to evaluate the effectiveness of the rules and automatically assign their
scores (called "masscheck"). We basically see a lot of spam from those 22
TLDs, and little or no ham, so rules that penalize those TLDs perform well
with few "false positives" in that corpora.
(And I’m still curious if there is any path of redemption for these 22. )
Most likely, SA specifically whitelisting legit domains in those poisonous
TLDs which are brought to our attention by, for instance, reports like
yours. Less likely but possible: seeing enough ham claiming to be from
those TLDs in the masscheck contributors' corpora that the scores for
those rules are automatically reduced.
A possible alternative that is under your control and will likely get
faster positive results than SA rules changes: register the domain
playdatesupport.com for your support department's use. They can still
*receive* email at supp...@play.date, but for outbound email that wouldn't
be the From: domain and thus wouldn't suffer the TLD reputational hit. (If
you do that, avoid setting "ReplyTo: supp...@play.date", as that would
also take a reputation hit.)
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
People that keep dreaming about the wasteland, labyrinths and
quick cash, die in amusing ways. -- Root the Dragon
-----------------------------------------------------------------------
2 days until Benjamin Franklin's 318th Birthday
