Disabled Greylisting for several domains on a server still being applied globally

Created:

2016-12-12 03:45:04 UTC

Modified:

2017-08-19 03:09:11 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Disabled Greylisting for several domains on a server still being applied globally

Applicable to:

  • Plesk 12.5 for Linux

Note: This article has the reference to the issue with the fix available:

  • #PPPM-5109 "Running the plesk sbin mchk utility removed all records from the local_domains table of the SpamAssassin’s greylisting database."
    Fixed in:
Please consider updating your server:

Symptoms

Disabled Greylisting for several domains on a server still being applied globally.

The content of local_domains table in settings.db database where domains with disabled greylisting are stored is empty:

# sqlite3 /var/lib/plesk/mail/greylist/settings.db 'select * from local_domains;'

If greylisting for a domain is enabled and then disabled again, domain name will be written to local_domains table in settings.db database but will be erased after some time.

Cause

This is an internal issue with ID #PPPM-5109 , which is planned to be fixed in future product updates.

Workaround

Apply a custom fix file so that local_domains table in settings.db database is not erased:

  1. Download the custom fix attached for Plesk 12.5 for CentOS 6 , Plesk 12.5 for CentOS 7 or for Plesk 12.5 for Ubuntu 14.04 and extract it.

  2. Create a backup of /usr/lib64/plesk-9.0/mail_grey_restore file:

    # cp /usr/lib64/plesk-9.0/mail_grey_restore /usr/lib64/plesk-9.0/mail_grey_restore_backup
  3. Move extracted mail_grey_restore file to /usr/lib64/plesk-9.0/ directory so that it has the same permissions as /usr/lib64/plesk-9.0/mail_grey_restore_backup

  4. Enable and then disable back the greylisting for affected domain (where Greylisting should be disabled): Domains > example.com > Mail Settings

Attachments:

Have more questions? Submit a request
Please sign in to leave a comment.