Hi Jack,
Here is a copy of the relevant headers:
X-Spam-Status: No, score=2.392 tagged_above=-999 required=3
tests=[HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377,
MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, TO_NO_BRKTS_HTML_ONLY=2,
T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001]
As you can see, the total score is approaching 3, the tipping point. The TO_NO_BRKTS_HTML_ONLY rule is responsible for almost all of that.
I know almost nothing about SpamAssassin. This might be specific to the mail server setup of my provider. But a value of 2 for the TO_NO_BRKTS_HTML_ONLY rule seems high enough to warrant some investigation…
By using custom values for the From: field in BNFW I can prevent the BNFW notifications being marked as spam. Before I started doing that, they almost invariably were.
Thanks for looking into this!
Sander