Here are the results of your suggested alwaysHit rule:
I sent the same test message from a list server several times through
our five mx servers.
Four of the five had these results:
DKIM_SIGNED,MISSING_HEADERS,RCVD_IN_BRBL_LASTEXT,RP_MATCHES_RCVD,T_DKIM_INVALID,alwaysHit
One had just the alwaysHit result.
So I now believe the problem is limited to one server but they all have
identical sendmail/mimedefang/spamassassin setups.
And the one server has normal hits, tests and scores for regular email
traffic processed before and after the test email.
On 5/21/2014 8:29 AM, David F. Skoll wrote:
On Wed, 21 May 2014 01:07:53 -0500
Cliff Hayes <[email protected]> wrote:
I don't know how long this has been going on but I just noticed that
about 1% of emails going through our system are being assigned zero
points/hits and blank tests/names.
Maybe those message actually don't hit any tests?
I don't know how to troubleshoot this? Where should I start?
Please post your filter or at least the relevant part that calls
SpamAssassin. Another thing to try is to make a test that *always* hits.
Maybe something like:
header ALWAYS_HIT Subject =~ /.?/
describe ALWAYS_HIT A rule that always hits
score ALWAYS_HIT 0.00001
Then make sure that you always see ALWAYS_HIT in the results.
Regards,
David.
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list [email protected]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang