• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Forwarded to devs Custom outgoing mail limits are overwritten on service plan synchronization

Monty

Silver Pleskian
Plesk Guru
TITLE:
Custom outgoing mail limits are overwritten on service plan synchronization
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx
Version 17.8.11 Update #60,
CentOS Linux 7.6.1810
PROBLEM DESCRIPTION:
Custom outgoing mail limits for a subscription, mailbox or domain are overwritten with those from the service plan when updating and synchronizing the service plan​
STEPS TO REPRODUCE:
  1. Create a service plan, example "Plan 1" with outgoing mail limits for mailbox, subscription and domain set to 100 each
  2. Create a subscription "example.com" with that service plan
  3. Open the subscription and customize the outgoing mail limits for mailbox, subscription and domain and set a different value, example 500 for each
  4. Edit the service plan "Plan 1" and click "Update & Sync" (no changes to the plan are required, it's sufficient to just click the Update button).
ACTUAL RESULT:
The previously customized outgoing mail limits of the subscription are back at their original values (100), taken from the service plan.​
EXPECTED RESULT:
Customized outgoing mail limits should not be overwritten when you update and sync a service plan.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Is there any update on this? The issue still exists on Plesk Obsidian 18.0.38.
 
@Monty As I understand it, the developers did not find the problem.
I think it is worth creating a new request with detailed steps to reproduce the problem on the latest version of Plesk.
 
Back
Top