Elaconta.com Webmaster wrote:
Benny Pedersen wrote:
Elaconta.com Webmaster skrev den 2013-03-14 11:48:
Specifically, if a user sends 100 emails and more than 25 of those
are send to non-existing users, disable email relaying for that user
for half an hour, for instance.
i say reject_unverified_recipient one more time
should i give links to pypolicyd-spf ?
sending 100000000 emails does change spf records ?
if you want another way of solving use rsyslog with sql query from
tempfails/hardfails on random recipient domains, and from that sql
logs block that sender local that spammed to it, impossible to use
reject_unverified_recipient or just ignoreing the problem ?
I'll look into reject_unverified_recipient, thanks for your insight.
Also for more clarification: We require authentication for all of our
email users, and have hourly email sending quotas in place.
But there's nothing stopping auth'ed users from sending emails to lots
of non-existent users, and that affects the email server's reputation
negatively.
Hence our trying to reduce to amount of emails send to non-existent emails.
