• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Reset spam policy

JogoVogo

Basic Pleskian
Server operating system version
os_CentOS 7
Plesk version and microupdate number
Plesk Obsidian v18.0.48_build1800221104.03
Hi all, when I try to reset the spam setting I get the following message:

1671455036106.png
 
Try to repair mail and database settings first with

# plesk repair mail
# plesk repair db
 
Yes I have already done that, but it did not remedy the situation.

One strange thing under summary (Plesk Email Security) I see thousands of email addresses that are not assigned to any user in the system.

For example:

srs0=p2+h=4d=askolsers.hz.cz=[email protected] 0 0 0 0 1 0
srs0=p2dt=4m=eu-west-1.amazonses.com=0102018511576b04-93d351e9-bb5f-4d59-941f-5283a3048405-000000@placeholder.de 0 0 0 1 0 0
srs0=p7og=4e=gmx.de=[email protected] 0 0 0 1 0 0
srs0=pagp=4a=freelance-market.de=[email protected] 0 0 0 1 0 0
srs0=pe2t=4h=placeholder.de=[email protected] 0 0 0 4 0 0
srs0=pavo=4r=berg-dach-schiefer.de=[email protected] 0 0 0 1 0 0
srs0=pb9c=4i=koeln.de=[email protected] 0 0 0 1 0 0
srs0=pbfr=4m=eu-west-1.amazonses.com=01020185110af64f-523453ac-b9ac-49cf-a708-2d158dc27bd5-000000@placeholder.de 0 0 0 1 0 0
srs0=pbhv=4s=icloud.com=[email protected] 0 0 0 1 0 0
srs0=pcbd=4o=web.de=[email protected] 0 0 0 1 0 0
srs0=pchn=4r=ml-cgn01.ispgateway.de=fortbildung_kita-fortbildung.com-bounces+kita-elisabeth=[email protected] 0 0 0 1 0 0
srs0=pdgt=4h=ml.vn.va=[email protected] 0 0 0 1 0 0
srs0=pdlw=4e=elektro-oppenau.de=[email protected] 0 0 0 1 0 0
srs0=oom6=4o=rp.mailing4.dhl.de=[email protected] 0 0 0 1 0 0
[email protected] 1 0 0 0 0 0
srs0=onmx=33=nokopolsky.radio.am=[email protected] 0 0 0 0 1 0
srs0=nz6c=34=hhlkoj.ru=[email protected] 0 0 0 0 1 0
srs0=o5ia=4g=smtp.shop-apotheke.com=bounces-51415126-now=[email protected] 0 0 0 1 0 0
 
Where do these entries come from that are displayed here and in which database are they stored?

90% are from one domain, and there are more every day...

Help!
 
One email address gets extremely much spam.

No matter how strong (1) the filter is set the spam goes through.
How can I make the antispam settings for individual emailboxes?
 
You can set a custom threshold for each mailbox via:

Subscription -> Websites & Domains -> Mail Accounts

Click on the mailbox's "Settings" link to change the spam settings.
 
Hi,

this is not possible because Plesk Email Security is installed.

Somehow this is not so happily solved
 
I've checked this on a server that has PES installed.

You should see the Settings links on the overview of the email accounts:

Screenshot 2022-12-21 at 12.16.54.png
 
It's not your fault; it's the weird place of the Spam settings. They should have used a tab for these settings, like in the Plesk UI without PES.
 
Can I mark this thread as resolved, or do you still have issues resetting the spam settings, as you asked in the first post?
 
Hi delaosa, do you have a solution for this error message?
Hi oliverweidel

I contacted plesk support at https://support.plesk.com/ and they reinstalled the extension to apply a hotfix.

"After reinstalling the extension and applying the hotfix on the file /usr/local/psa/admin/plib/modules/email-security/library/Policies.php, the Reset SPAM policy button doesn't fail anymore.
Please note that all the stats were reset during the reinstallation."
 
@oliverweidel Please contact Plesk support staff. This issue does not have a standard solution, it can only be fixed on a case-by-case basis at this time. The solution applied for @delaosa might not necessarily be the same that is required for you.
 
Back
Top