https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6124
Summary: Too many companies using domain.lan for MS AD
Product: Spamassassin
Version: 3.2.5
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Plugins
AssignedTo: [email protected]
ReportedBy: [email protected]
Way too many people are using .lan (local area network) as their internal,
local lan.
I agree if FIRST untrusted does a 'helo *.lan' you should score it high, but if
they have an internal server that does a helo *.lan to their external (bastian
or smart host) and it uses a valid FQDN, you should not score it so high.
header HELO_LH_HOME X-Spam-Relays-Untrusted =~ /^[^\]]+ helo=\S+\.(?:home|lan)
/i
3.714 points is pretty high.
score HELO_LH_HOME 2.602 3.169 2.689 3.714
in this case client used the 'default' FQDN on their exchange server (yes,
stupid, not RFC compliant) they have a real FQDN that matches their ip, but
for some reason, microsoft does not make it abundantly clear how important the
FQDN setting in exchange is.
Score a little lower, or maybe score *.lan and *.home a little different
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
