On 4/24/15 2:22 PM, David B Funk wrote:
On Fri, 24 Apr 2015, Forrest wrote:
Since last night, suddenly Spamassassin/Milter is rejecting my own
reports to Spamcop. Out of nowhere and with no other changes
other than downloading new rules. Why is this happening?
Everything has been working for literally years. spam.spamcop.net
is whitelisted in both the system and user_prefs. 127 is a trusted
network.
The original message was received at Fri, 24 Apr 2015 14:06:23 -0400
from account@localhost
----- The following addresses had permanent fatal errors -----
submit.[omitted]@spam.spamcop.net
(reason: 550 5.7.1 Blocked by SpamAssassin)
(expanded from: submit.[omitted]@spam.spamcop.net)
----- Transcript of session follows -----
... while talking to [127.0.0.1]:
DATA
<<< 550 5.7.1 Blocked by SpamAssassin
554 5.0.0 Service unavailable
Does this mean that you're SA filtering your -outgoing- mail?
Locate the corresponding entry in your spamd logs and post the rules
that hit.
Yes, outgoing, which is what I find troubling.
Here are the rules I see hit from the mail logs:
spamd: result: Y 8 -
ALL_TRUSTED,FILL_THIS_FORM,FILL_THIS_FORM_FRAUD_PHISH,HTML_MESSAGE,HTML_TAG_BALANCE_BODY,MIME_QP_LONG_LINE,RAZOR2_CF_RANGE_51_100,
RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,TVD_PH_BODY_ACCOUNTS_PRE,T_HTML_ATTACH,URIBL_BLACK,URIBL_SBL,URIBL_SBL_A
I have the mutt mail/CLI agent configured to forward tagged messages to
my spamcop submit address. This has been in place for many years and
I've never had any problems until today.
Thanks.
