On 10/17/2012 10:36 AM, /dev/rob0 wrote:
On Wed, Oct 17, 2012 at 09:35:33AM +0200, Tom Kinghorn wrote:
I was wondering id there is any way to specify a
destination_concurrency_limit for clients which have used
SMTP_AUTH and whose source is not on the $mynetworks.
We currently have a problem where the accounts of clients
(who have used weak passwords), are being used to spam.
This issue last came up on this list way back in 2012, on the 16th of
October,
Like, yesterday ?
"Alert of unusually large queue". As per that thread, the
solution is a combination of rate limiting by means of a policy
service and content filtering of submission.
I am looking for a way to reduce the impact of this while
we contact all these users.
I'd revoke their credentials ASAP, as soon as the compromised account
is identified.
--
J.
