Hi Nami,
incoming rate limiting works fine, if your users send through a mailsever, that can deal with the 400-errors, your MTA generates, throttle and try again later. However if you have mail clients that send, a 400-error is a real error to the user and they probably do not even understand, whats going on and will try on and on. Also outgoing rate limiting should be in place to not annoy other mailservers. Additonally i always like to learn from users behavior. So i would not only limit amount of mail, i would also scan for spam/virus etc and monitor all of it. Spammers do not only send many mails at once, they send also at very low rate but ongoing. Rate limiting would not take care of this. Stefan Bauer. -----Ursprüngliche Nachricht----- Von: missytake via mailop <mailop@mailop.org> Gesendet: Dienstag 27 April 2021 18:31 An: mailop@mailop.org Betreff: [mailop] Best practices for outbound rate limiting? Hi, we have a small semi-open-registration mail server (not systemli.org, in case you are wondering) and we would like to learn more about best practices for rate limiting outgoing mail. We are using postfix. We don't want to restrict our users too much, but obviously we also care about not burdening the mail ecosystem with spam, and it's possible, though not very likely that spammers find out how to automatically use our registration mechanism. The smtpd_client_message_rate_limit option seems to do the trick, and we are thinking about setting it to 20 - is this enough to make it unprofitable for spammers, but not annoy our users? What are your experiences? Thanks, Nami _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
