http://bugzilla.spamassassin.org/show_bug.cgi?id=3549
------- Additional Comments From [EMAIL PROTECTED] 2005-05-27 01:38 -------
Subject: Re: Inconsistent coverage of private registries in
RegistrarBoundaries.pm
> Can you clarify:
>
> If spammer.domain.com is a bad guy and hammer.domain.com is a good guy,
> wouldn't *.domain.com catch both of them and therefore FP if
hammer.domain.com
> appeared in a message body URI?
Jeff, I think it is the other way around from what he is saying and you said
earlier.
To paraphrase your ealier comment (as best I remember it) "If foo.bar.com is
spamming and bar.com is legit, we don't list bar.com. If blabbel.blob.com
is spamming and blob.com is owned by spammers we do list blob.com."
Assuming that paraphrase is more or less correct, and taking it with his
statements, he's merely saying to list:
blob.com
*.blob.com
Clearly line #1 is what you are doing, and it catches blobbel.blob.com only
if someone strips off the first level of the name before doing the check.
Adding line #2 merely catches blobble.blob.com, and anything.blob.com, even
if someone doesn't strip off the spammer frontend names from the main
domain. I don't see that this in any way endangers the bar.com case that
you would not have listed in the first place. (But note that you actually
*could* list *.foo.bar.com and foo.bar.com and catch the spamming domain on
a non-spamming host if you wanted to in the future, again without
endangering the non-spamming host itself.)
I see the advantage here that this means the questions about exception files
for mini-registrars and the like go away, since the requestor doesn't have
to strip the frontend fake domains down to the real domain. If you have
listed the right blackhat host with an asterisk in the right place, things
will magically work.
Loren
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
