Allow user-level filters to use Spam criteria even if SpamAssasin is disabled

Benjamin Chennells-Webb shared this idea 2 years ago
Open Discussion

We currently use a third-party product (Mailscanner) for our anti-spam. I've recently found that you cannot use user-level filters which rely on any of the three Spam criteria while SpamAssasin is disabled. Assuming the filtering process simply uses the email headers to check the Spam Score etc and act accordingly, allowing the filters to be used even with SpamAssasin disabled with give users better control of their email even if the provider is using a third-party anti-spam package.

Comments (5)

photo
1

Does the third party application create the same headers?

photo
1

Mailscanner uses the SpamAssasin engine so at the very least they would be similar. Sample below:

X-<<OrgName>>-MailScanner-Information: Please contact <<OrgName>> for more information

X-<<OrgName>>-MailScanner-ID: 1Z2Fvr-0005rB-8k

X-<<OrgName>>-MailScanner: Found to be clean

X-<<OrgName>>-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=-1.889,

required 3, autolearn=not spam, BAYES_00 -1.90, HTML_MESSAGE 0.00,

MIME_QP_LONG_LINE 0.00, SPF_PASS -0.00,

T_KAM_HTML_FONT_INVALID 0.01)

X-<<OrgName>>-MailScanner-From: <<From>>

X-Spam-Status: No

photo
1

Thank you for providing the additional information.

photo
photo
1

Any status on this.

Can we update the yaml file and make this work???

photo
1

No updates at this time, and I'm not sure on your second question. We don't offer support on the feature request site, but hop over to the cPanel forums to see if anyone in the community can provide you with some feedback.

photo