Facebook
Twitter- Server operating system version
- Ubuntu 24.04
- Plesk version and microupdate number
- 18.0.80_build1800260901.22
Hi all,
I think I ran into a bug with service plan syncing for the outgoing mail limits. Posting here in case someone else has seen this or a dev can confirm.
Background:
One of our customer's mailboxes started hitting the outgoing mail rate limit ("The limit on the number of allowed outgoing messages was exceeded") in the maillog, even for legitimate mail. I went into the panel and raised the limit for that mailbox/domain/subscription directly to 50, then later to 200 — but mails kept getting rejected with the same error, unchanged.
At that point I started digging to figure out why the new limits weren't taking effect. Restarting the pc-remote milter (the process that actually enforces these limits) made no difference, so the limit clearly wasn't cached in that process.
That's when I noticed something odd: for this subscription, the limits I'd raised were the ones set directly in Outgoing Mail Control for that specific mailbox/domain/subscription — not the ones inherited from the service plan. So I checked whether the plan-level setting was the actual source of truth, since we manage limits centrally via the service plan "Kundenpaket X" for consistency across customers.
What I found:
I edited the service plan "Kundenpaket X" and raised the outgoing messages limits (mailbox/domain/subscription per hour) from the server default (20) to a custom value (50). Saved successfully.
I then checked a different subscription assigned to that same plan, which had never had a manual override:
plesk bin subscription --info <domain>
→ confirms it's not locked for syncing.
Triggered a manual sync just to be safe:
plesk bin subscription --sync-subscription <domain>
→ "Subscription <domain> was synchronized with the associated service plans."
But when I go to Websites & Domains → Outgoing Mail Control → Subscriptions → <domain>, it still shows "Server-wide default value (20 messages per hour)" — the new plan value never made it through, neither on save nor after the explicit sync.
Workaround: setting the limit directly per subscription in Outgoing Mail Control works fine (that's how I fixed the original mailbox), it just doesn't come from the plan. Not great if you manage several subscriptions on the same plan and expect the plan to be the single source of truth.
Anyone else seen this, or is there a known reason outgoing mail limits behave differently from the other plan limits (disk space, traffic, mailbox count etc., which do sync fine)?
Thanks!
I think I ran into a bug with service plan syncing for the outgoing mail limits. Posting here in case someone else has seen this or a dev can confirm.
Background:
One of our customer's mailboxes started hitting the outgoing mail rate limit ("The limit on the number of allowed outgoing messages was exceeded") in the maillog, even for legitimate mail. I went into the panel and raised the limit for that mailbox/domain/subscription directly to 50, then later to 200 — but mails kept getting rejected with the same error, unchanged.
At that point I started digging to figure out why the new limits weren't taking effect. Restarting the pc-remote milter (the process that actually enforces these limits) made no difference, so the limit clearly wasn't cached in that process.
That's when I noticed something odd: for this subscription, the limits I'd raised were the ones set directly in Outgoing Mail Control for that specific mailbox/domain/subscription — not the ones inherited from the service plan. So I checked whether the plan-level setting was the actual source of truth, since we manage limits centrally via the service plan "Kundenpaket X" for consistency across customers.
What I found:
I edited the service plan "Kundenpaket X" and raised the outgoing messages limits (mailbox/domain/subscription per hour) from the server default (20) to a custom value (50). Saved successfully.
I then checked a different subscription assigned to that same plan, which had never had a manual override:
plesk bin subscription --info <domain>
→ confirms it's not locked for syncing.
Triggered a manual sync just to be safe:
plesk bin subscription --sync-subscription <domain>
→ "Subscription <domain> was synchronized with the associated service plans."
But when I go to Websites & Domains → Outgoing Mail Control → Subscriptions → <domain>, it still shows "Server-wide default value (20 messages per hour)" — the new plan value never made it through, neither on save nor after the explicit sync.
Workaround: setting the limit directly per subscription in Outgoing Mail Control works fine (that's how I fixed the original mailbox), it just doesn't come from the plan. Not great if you manage several subscriptions on the same plan and expect the plan to be the single source of truth.
Anyone else seen this, or is there a known reason outgoing mail limits behave differently from the other plan limits (disk space, traffic, mailbox count etc., which do sync fine)?
Thanks!
