nik600:
> Virus, botnet and user's bad policies about password allows many 3rd party
> entities to stole passwords, in the last month i've experienced a grows of
> hacked users, and in some case many spam messages are sent from my servers
> before i can block the user.
>
> I've tried many combination
>
> smtpd_client_message_rate_limit
> smtpd_client_recipient_rate_limit
> anvil_rate_time_unit
>
> config options but as the sender changes frequently the client, sending
> from different locations, so the limits above has no effect and i can't
> stop the spammer.
>
> Does exists any configuration to limit the # of sasl login from an user?
>
> It could be very useful, and cloud be also useful monitor many login of the
> same sasl user from different ip.
>
> What do you thing about that?
Who has time? Technically it's the same problem as client, message
and recipient rate limits. The few cycles that I have are committed
to eliminating LMDB built-in hard limits and keeping LMDB usable
after program or system crashes.
Wietse
