![]() ![]() This option allows you to automatically delete emails that have not been. Thinking of how to reset the bayesian data if I ever wanted/needed, also wondering if option #1 cleans up after itself if another option was previously used. There you can also disable the SPAM filter. I guess with question #2 I am wondering if I used option 3 and have a user spam folder, would picking #1 remove that folder? ISPConfig uses amavis (which internally uses the spamassassin libraries) and not spamassassin, so disabling amavis as described in the FAQ disables the spamfilter and antivirus filter. However, as spamassassin fetches the user preferences from the database anyway, to have spamassassin directly decide whether it should scan or not. I would need to create an extra wrapper between postfix and spamassassin. Activate and Deactivate SPAM Filters in cPanel: To turn on SPAM Filters. Well, spamassassin is being invoked by postfix using the contentfilter option. Enable SpamAssassin Step 3: To disable SpamAssassin, click on Disable SpamAssassin. Spam Assassin Step 2: To enable SpamAssassin, click on the Enable SpamAssassin button. Do all options above enable SA or is the first one actually the state I'm in now, and would subsequently disable SA if I were to pick option 2-4? We recommend that you activate SPAM Filters immediately after you first access cPanel. Step 1: To access the SpamAssassin Menu, click on the SpamAssassin icon on the main screen of your cPanel interface. Send the spam to appropriate user's spam folder.Ģ.Redirect it to the catch-all ~/.spamassassin/spam folder.Click "Save" (below) to enable it." and the list of options In the SpamAssassin menu where I see "SpamAssassin is not currently enabled. I have not enabled SpamAssassin on any domains yet (I guess since I have never clicked the "SAVE" button) since I wanted to find out if what I do could be reversed first. ![]() I guess you could disable the channel by commenting out the CHANNELURL in the nf file. SpamAssassin is a free, open-source, flexible and powerful spam-fighting tool. See also SoughtRules - SPAMASSASSIN - Apache Software Foundation. Specifically, we will see how to check email header and body with Postfix and SpamAssassin (SA) to detect spam. If not then possibly a way to at least disable the SpamAssassin menu again. SpamAssassin documentation recommends not using the Sought rule set. I can back out the nf changes but am not sure if there is something I can do with spam.sh to reverse all that it did. How to reverse the 'Enable' steps from the KB article (link above) so spamd is once again unavailable/uninstalled? Mostly I am trying to experiment and learn more about this feature and those related/requiring SA in case I ever rent hosting space.Īnyhow, this leads me to a couple of questions:ġ. I personally use the Catch-All set to "Ignore: The email is dropped and completely ignored" so spam isn't that big of problem on my user email accounts, and I have mail client spam catching for those. ![]()
0 Comments
Leave a Reply. |