http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5682
Summary: FH_HOST_ALMOST_IP matches static addresses
Product: Spamassassin
Version: 3.2.3
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: Rules
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
we have many DSL customers with statically assigned IP addresses, but generic
DNS names, e.g. static-081-024-000.dsl.nextra.sk. When they are sending mail to
us, our SA gives them high score because they match FH_HOST_ALMOST_IP, which
often results to marking message as spam.
Most of them can be avoided by using SMTP authentication, but since they often
run mailserver on that IP (which is why they send mail from it), it's not always
possible.
Of course we can change their DNS names, but should FH_HOST_ALMOST_IP really
match this kind of users? It would be nice to combine FH_HOST_ALMOST_IP check
with __RDNS_STATIC the same way RDNS_DYNAMIC does.
(btw, aren't RDNS_DYNAMIC and FH_HOST_ALMOST_IP kind of redundant?)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
