• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved attempts after reaching the limit

Hey Igor,

I'm not spotting in that document where it specifies what happens to all messages being sent out *after* the limit is reached. What is in the document is:

- That you can specify limits per subscription, domain and per mailbox
- The heirarchy of setting such limits
- How the counting of outgoing messages works
- How well scripts can be tracked

But it does not specify what happens in scenarios like:

1. A mailbox is limited to 10 messages per hour
2. The user of that mailbox sends 50 messages in an hour
3. The 11th through 50th message attempts to be sent
4. The user receive an email notification about their messages not being sent

At this point what happens? Does Plesk then send the 11th-20th message in the second hour, followed by the 21st-30th message in the third hour, etc? Or do they just never get sent at all and it's up to the user to resend them?
 
@manos, this should not be done, because it enables spammers to spam despite a limit. Their spam mails will simply wait in the queue for the next window to open. This is not the intention of such a security function. We have no plans to change the way the limit works to allow queue processing of held mails.
 
@manos, this should not be done, because it enables spammers to spam despite a limit. Their spam mails will simply wait in the queue for the next window to open. This is not the intention of such a security function. We have no plans to change the way the limit works to allow queue processing of held mails.
Thanks for reply Peter

I meant if want to keep safe ip not due to hacked account or something but for legit emails in order to not reach incoming from same ip/email limits at gmail, yahoo etc.

So after reaching limits whole queue will be discarded?

You could just put another 2 checkboxes with what to do in case of reach limits
1) Discard
2) Keep in queue
 
Such an option makes no sense, because it undermines the security algorithm. Why should mails be blocked in the first place if they are just delayed and sent out later?

But if you believe it is something that Plesk should add, we still have an option for you: Please add the idea as a feature request to Feature Suggestions: Top (1867 ideas) – Your Ideas for Plesk. If other users think the same and vote for this, the idea has a fair chance of becoming a reality in future Plesk versions.
 
Such an option makes no sense, because it undermines the security algorithm. Why should mails be blocked in the first place if they are just delayed and sent out later?

But if you believe it is something that Plesk should add, we still have an option for you: Please add the idea as a feature request to Feature Suggestions: Top (1867 ideas) – Your Ideas for Plesk. If other users think the same and vote for this, the idea has a fair chance of becoming a reality in future Plesk versions.
Hi Peter

Because gmail defers messages from same ip from custom domain after a number so it would be a protection measure
 
I would also prefer the messages to be delayed instead of discarded.

Admins will be notified when the limit has been reached, they can inspect the mail que and determine if the send out mails are spam. If not, mail is still being send out (delayed). If it is spam, they can clear the que and block the sending account.
 
Back
Top