On Thu, 26 Jan 2017, John Stimson wrote:
I am running SpamAssassin 3.4.1. It is running as a background daemon,
started with:
/usr/bin/spamd -d --allow-tell
Incoming mail is accepted by postfix 3.1 and submitted via the milter
interface to spamass-milter 0.40 for processing in SpamAssassin.
My Postfix installation is set up to use SASL authentication managed by
dovecot for any message that does not have a local sender or recipient. This
was done to allow users of my system to send mail from mobile devices which
may be on cellular connections or remote WiFi networks.
Sometime around January 19th, I suddenly started having messages from
authenticated users on remote networks rejected by SpamAssassin, with these
test flags in the X-Spam-Status header:
HELO_MISC_IP,HTML_MESSAGE,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC
I have been running this configuration since April 2016 without having this
issue before.
Just to be clear: nothing in the MTA stack got upgraded? Postfix, dovecot,
spamass-milter, etc.? No SA config changes?
Any ideas about what might be going on, or how to get SpamAssassin to pass
messages from authenticated senders?
Can you provide the full headers from such a message? It's possible that
the authentication information is (for some reason) being incorporated in
a manner that SA does not recognize.
Also post your trusted_networks and internal_networks settings.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
[email protected] FALaholic #11174 pgpk -a [email protected]
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Activist: Someone who gets involved.
Unregistered Lobbyist: Someone who gets involved
with something the MSM doesn't approve of. -- WizardPC
-----------------------------------------------------------------------
88 more days working to pay your (average) annual US tax bill
before you're finally working for yourself.
