You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2006/11/30 16:18:02 UTC
[Bug 5215] New: Safe TLD rulesets
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5215
Summary: Safe TLD rulesets
Product: Spamassassin
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: dev@spamassassin.apache.org
ReportedBy: Coracle_RSA@hotmail.com
Various gTLDs as well as various special 2TLDs are assigned to registrars or to
administrators that are generally beyond any doubt or whose users are subject
to very strict controls. As an example, it is difficult to imagine that, a spam
might be received from .aero, .coop, or .museum; like it or not, this would
also apply to .int, or .gov, and to 2nd Level Domains like .bund.de (the German
federal government), or .europa.eu (the European Union administrations) or
maybe even .ac.uk (U.K. Universities) and similar others. This fact provides
various possibilities for the improvement of Spamassassin:
(a) Current whitelist procedures in Spamassassin allow *@domain.tld but do not
allow *@*.tld - this should be changed;
(b) TLDs that have been declared safe could be entered into the software itself
as a "universal white list";
(c) The whitelist (b) can be used for better training of the bayesian filter
itself, giving added general positive probability to words used in mails from
these TLDs ("preselection");
(d) TLD Registrar groups or 2TLD registrars with large numbers of users might
apply to be "added" to the list if they can show and prove that they run a
strict and effective regime of anti-spam policy and procedures. This might
eventually create enough pressure to severly reduce or even eliminate spams
altogether.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5215] make whitelist specifications more generic
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5215
felicity@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Summary|Safe TLD rulesets |make whitelist
| |specifications more generic
Target Milestone|Undefined |Future
------- Additional Comments From felicity@apache.org 2006-11-30 19:15 -------
Just for the record, I'm kind of -0.5 on this idea. I don't think the TLD is
really a useful indication of spam versus non-spam.
If someone wants to come up with a more generic method for specifying whitelists
though, I can live with that. ie: "whitelist_from *@*.gov" or something (or
heck, just assume a username of * if there's no "@").
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5215] make whitelist specifications more generic
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5215
felicity@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From felicity@apache.org 2006-12-30 20:07 -------
(In reply to comment #2)
> Are you sure that *@*.tld doesn't work? We already have *@*.example.tld type
> patterns in 60_whitelist.cf and some of the others. The code in Conf::Parser.pm
> in 3.1 branch or in WLBLEval.pm in trunk acts on all the '*' characters in the
> pattern.
Good call, thanks Sidney. "whitelist_from *@*.tld" works fine.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5215] make whitelist specifications more generic
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5215
------- Additional Comments From sidney@sidney.com 2006-11-30 23:11 -------
Are you sure that *@*.tld doesn't work? We already have *@*.example.tld type
patterns in 60_whitelist.cf and some of the others. The code in Conf::Parser.pm
in 3.1 branch or in WLBLEval.pm in trunk acts on all the '*' characters in the
pattern.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.