Hi experts,
I want to limit volume email sending via proxmox in a hours, pls tell me what's to do?
Thanks in Advance

Hello, I also have this need.
Did you get a solution?

As written, provide a use case, open a feature request bug in the bug tracker and maybe it will be added in future. However, PMG isn't meant (currently, I would also prefer something different to improve the product, e.g. adding archive functionality, adding mail server functionality, adding mail security functionality) to be either incoming final destination nor outgoing first destination but being a relay in between filtering for spam and viruses. So if you're using e.g. Plesk as Mail Server (or would relay from Zimbra through Plesk) there is such a feature implemented. However, this feature is primarily (so about the use case) implemented there because Plesk is for hosting customers (mail but more primary also websites) and if this ones got hacked and misused as spam source (because of insecure code or applications) the Plesk provider can prevent their IPs from being blacklisted by limiting possible outgoing spam (and be able to get notified, look after and react on possible injections, e.g. suspending a hosting package until the problem has been solved). I really don't see this use case with "just a mail server" like Zimbra unless you're providing service to customers which use their e.g. IMAP/SMTP/... access to send mass mails via newsletter or infected computers.

Thanks so much! I'll try this way

As written, provide a use case, open a feature request bug in the bug tracker and maybe it will be added in future. However, PMG isn't meant (currently, I would also prefer something different to improve the product, e.g. adding archive functionality, adding mail server functionality, adding mail security functionality) to be either incoming final destination nor outgoing first destination but being a relay in between filtering for spam and viruses. So if you're using e.g. Plesk as Mail Server (or would relay from Zimbra through Plesk) there is such a feature implemented. However, this feature is primarily (so about the use case) implemented there because Plesk is for hosting customers (mail but more primary also websites) and if this ones got hacked and misused as spam source (because of insecure code or applications) the Plesk provider can prevent their IPs from being blacklisted by limiting possible outgoing spam (and be able to get notified, look after and react on possible injections, e.g. suspending a hosting package until the problem has been solved). I really don't see this use case with "just a mail server" like Zimbra unless you're providing service to customers which use their e.g. IMAP/SMTP/... access to send mass mails via newsletter or infected computers.

Thank you for replying

As written, provide a use case, open a feature request bug in the bug tracker and maybe it will be added in future. However, PMG isn't meant (currently, I would also prefer something different to improve the product, e.g. adding archive functionality, adding mail server functionality, adding mail security functionality) to be either incoming final destination nor outgoing first destination but being a relay in between filtering for spam and viruses. So if you're using e.g. Plesk as Mail Server (or would relay from Zimbra through Plesk) there is such a feature implemented. However, this feature is primarily (so about the use case) implemented there because Plesk is for hosting customers (mail but more primary also websites) and if this ones got hacked and misused as spam source (because of insecure code or applications) the Plesk provider can prevent their IPs from being blacklisted by limiting possible outgoing spam (and be able to get notified, look after and react on possible injections, e.g. suspending a hosting package until the problem has been solved). I really don't see this use case with "just a mail server" like Zimbra unless you're providing service to customers which use their e.g. IMAP/SMTP/... access to send mass mails via newsletter or infected computers.

Zimbra email customers accounts can also be hacked...
and PMG can deliver mail too fast for some mail servers, it's be great to have an option to control that.

Is there any update on this issue?

When our users trigger spam reports, we are being blacklisted on Gmail and Hotmail, and as a result we are unable to send emails. We need a solution where the user is either restricted with a certain sending limit or we receive an informational alert email when such activity occurs.