End User configuration of SpamAssassin

[rusty99]

I have a hosting company that uses cPanel SpamAssassin but I see the interface is rudimental. It would be great to have a more advanced interface to finely tune stuff, but I guess this is locked in.

I note that there is a SpamAssassin folder in my web server root area that has a user_prefs file. In general, can I configure this file without screwing up cPanel? I want to add about a dozen or more whitelist addresses. Is there a limit to how many to add?

Also, I'd like to set 'report_safe' to 0 as its interfering with an old email client. Can that be user configured any way? It seems my host uses kindergarten children for online customer support so asking them may be futile, but generally do service providers offer this level of config?

Thanks,

Rusty

 

[cPanelMichael]

Hello,

You should be able to modify the user_prefs file with your own custom rules. The following SpamAssassin document explains which values are available for configuration:

Mail::SpamAssassin::Conf - SpamAssassin configuration file
WritingRules - Spamassassin Wiki
BasicConfiguration - Spamassassin Wiki

Thank you.

 

[rusty99]

Thanks for this - I'll see how I go.

Hello,

You should be able to modify the user_prefs file with your own custom rules. The following SpamAssassin document explains which values are available for configuration:

Mail::SpamAssassin::Conf - SpamAssassin configuration file
WritingRules - Spamassassin Wiki
BasicConfiguration - Spamassassin Wiki

Thank you.

 

[rusty99]

I finally figured out that clear_report_template was the only directive that worked to remove the additional text ( Content preview: and scoring table - Content analysis details: ) from the body of older email clients. All I see now is X-Ham-Report: (no report template found) for non-spam emails. Real spam is still tagged via a SPAM preface if that's how you configured it. If I want to troubleshoot spam in the future I can just comment it out for a short period. Its a bit of a rough solution but there is a template SA accesses to write the body content (which is hidden in modern email clients) and that directive somehow interferes with accessing the template.

Thanks again for your assistance.