How to limit volume email sending via PMG

[daolt]

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

 

[tom]

There is no such function, please describe your use case, how should this work?

 

[daolt]

Tom,
I'm using zimbra, I want to control volume email of users sending, but i don't want to use PolicyD

 

[Web-BR01]

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

 

[Kenny Huynh]

Vote for this feature

 

[heutger]

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.

 

[hata_ph]

Another option is to use postfwd.

https://github.com/postfwd/postfwd
https://manpages.debian.org/unstable/postfwd/postfwd1.1.en.html

 

[hata_ph]

there is a global option to set message rate limit

https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_mail_proxy_configuration

 

[daolt]

there is a global option to set message rate limit

https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_mail_proxy_configuration

Thanks so much! I'll try this way

 

[daolt]

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

 

[daolt]

Another option is to use postfwd.

https://github.com/postfwd/postfwd
https://manpages.debian.org/unstable/postfwd/postfwd1.1.en.html

Thank you replying

 

[franhis]

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.