https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6259
Summary: Evaluate ReturnPath's RNBL
Product: Spamassassin
Version: 3.3.0
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Rules
AssignedTo: [email protected]
ReportedBy: [email protected]
This bug is splitting off the DNSBL from Bug #6247.
# Return Path Reputation Network Blacklist (RNBL):
# https://senderscore.org/blacklistlookup/
header RCVD_IN_RP_RNBL
eval:check_rbl('rnbl-lastexternal','bl.score.senderscore.com.')
describe RCVD_IN_RP_RNBL Relay in RNBL,
https://senderscore.org/blacklistlookup/
We have no formal written requirements for accepting a new blacklist in
spamassassin yet. But if we did have requirements they might contain things
like:
1) Sufficient capacity to handle global lookups and DoS attacks on your
infrastructure.
2) What volume do you allow for free?
3) Clearly written listing and delisting policy.
4) Clearly superior performance demonstrated in weekly masschecks.
#1 I'm guessing ReturnPath has no problem.
#3 Might already be clear enough, not sure.
#2 Requires further discussion about acceptability to the spamassassin project.
#4 http://ruleqa.spamassassin.org/20091212-r889898-n/T_RCVD_IN_RP_RNBL/detail
We have had only one weekend of data on the performance of RNBL. Very few FP's
but small spam detection rate as well. This might be considered too small to
be worthwhile to be added as a spamassassin default rule, especially given your
stated intention to have volume limits and payment requirements in the future.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
