Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

How to check that SpamAssassin is protecting a Plesk server from spam

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Linux kb: how-to ABT: Group B

Applicable to:

  • Plesk for Linux

Question

How to check that SpamAssassin is protecting a Plesk server from spam?

Answer

  1. Make sure that the SpamAssassin service is running at Tools & Settings > Services Management.


    Screenshot_2019-09-06_Services_-_Plesk_Onyx_17_8_11.png

  2. Make sure that the Switch on spam filtering for this email address option is enabled at Domains > example.com > Email Addresses > john_doe@example.com > Spam Filter tab.


    Screenshot_2019-09-06_jdoe_example_com_-_Plesk_Onyx_17_8_11.png

  3. Test SpamAssassin using the steps from this KB article. When SpamAssasin detects spam, the following messages appears in /usr/local/psa/var/log/maillog (can be checked via an SSH connection only):

    CONFIG_TEXT: spamd[1107]: spamd: identified spam (1000.0/7.0) for test@domain.tld:110 in 6.1 seconds, 3926 bytes.

     

    If all the above steps are successful - SpamAssassin is working fine.

Comments

2 comments

Sort by Date Votes

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles