• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Migrated from Plesk 7.6 to 9.5 and more emails tagged as SPAM

D

domisupport

Guest
Hi,

We just migrated Plesk for Windows 7.6 to 9.5.2 and more real emails are marked as SPAM and whitelists doesn't seem to be working, I added a few domains and I still get the emails as SPAM.

I know that I'm running different version of spamassassin and it may happen that more real emails are tagged as SPAM, but I want to know why and why whitelists doesn't work.

Does someone already had this problem?

How can I do to debug "spamassassin"? So I can go to the logs and see what's going on.

Windows 2003 Server R2
Plesk for Windows 9.5.2
MailEnable Standard 4.23
Perl v5.8.8 built for MSWin32-x86-multi-thread
Plesk SpamAssassin 3.3.1


Thanks.

Carlos
www.domidot.net
 
Did you tried Train spamassassin feature?

Also seems that all rules in spam assassin are enabled. The rules are stored in the folder

C:\Parallels\Plesk\Additional\SpamAssassin\rules

By default there are no files with rules. The name of files with rules begins from a digit (like 10_default_prefs.cf)

As long as all rules are enabled then it is not wonder that some of them affect the score. In this case I see to ways to make it work:
1. Reset the rules to default ones.
2. Reset score of the rules which you counter not valid to zero.

To reset the score of a rule it needs to define it file

C:\Parallels\Plesk\Additional\Perl\site\etc\mail\spamassassin\local.cf

For example reset rule DOS_OE_TO_MX add this line

score DOS_OE_TO_MX 0

Then it needs to restart Plesk Management service.
 
Back
Top