https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6770
Bug #: 6770
Summary: initial dns test eventually creates incorrect
disabling of certain plugins
Product: Spamassassin
Version: 3.3.2
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P2
Component: spamassassin
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
the dns_available test disables plugins generally which are supposed to use dns
lookups
if the initial dns test fails for whatever reason a number of plugins are
disabled
at least it is definitely not ok for disabling SPF which uses existent
Received-SPF header, unless otherwise specified, so no need of DNS
other plugins as ASN, DKIM are also disabled without sufficient diag or
explanation, nor from their config docs neither from debugging (-D --lint), the
ladder even could lead to wrong conclusions because tells dns not available,
but if it is incorrectly assumed, or bad said, dns is available, spamassassin's
dns tests are disabled
IMO spamassassin should not care if user's DNS configuration is valid, working
or not, it should simply accept resolv.conf and not make assumptions by
eventual connection failures which may be temporary or not, either way, a user
with spamassassin in his hands should have enough knowledge of the need for an
working nameserver, if not it is another issue
it should instead diag that no dns could be reached or something but in no case
disable a plugin, the test could have failed for temporary reasons
in order to complete this PR for people who are with plugin issues:
who is used to see any SPF, ASN or DKIM report/scores and suddenly appears
always T_DKIM_INVALID no SPF and no ASN anymore, better checks if spamd was
started without being connected to the Internet or with erroneous dns_available
settings in local.cf
in any case no need of perl up/downgrading or other suspicious operations on
rules or code or following other suggestions as gmail dkim signatures always
wrong/invalid or similar things which you can find on search machines,
spamassassin works just fine, only this dns thing is at least insufficient
documented
Hans
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
