• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Issue Upgrade to Plesk Onyx resets greylisting whitelist

danami

Silver Pleskian
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Upgrade from Plesk 12.5 to Plesk Onyx
Product version: Plesk Onyx 17.0.17 Update #12
Update date: 2017/01/01 06:53
Build date: 2016/11/17 16:00
OS version: CentOS 6.8
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2

PROBLEM DESCRIPTION
After upgrading from Plesk 12.5 to Onyx white domains patterns list was reset

STEPS TO REPRODUCE
On all our servers I normally whitelist services that don't play well with greylisting:

eg.
/usr/local/psa/bin/grey_listing --update-server -domains-whitelist "add:*pool.messaging.microsoft.com"
/usr/local/psa/bin/grey_listing --update-server -domains-whitelist "add:*.outbound.protection.outlook.com"

ACTUAL RESULT
After upgrading to Onyx customers were complaining about very long delivery times from office 365. I could see in the maillog that they were being greylisted again for some reason.

When I ran the command /usr/local/psa/bin/grey_listing --info-server it showed that all my "White domains patterns list" were gone and reset to Plesk defaults.

EXPECTED RESULT
Greylist whitelist should be retained though out the upgrade process.
 
Thank you for detailed report. I have submitted it to developers as PPPM-5541
 
Back
Top