On 09/19/17 11:28 -0400, Michael Sofka wrote:
On 09/19/2017 10:12 AM, Dan White wrote:
The botnet is still hammering away, checking those old accounts.
But the bottleneck appears to have been saslauthd threads.
Doubling the thread count from 5 to 10 has resolved the problem
for now. (And,
On 09/19/2017 10:12 AM, Dan White wrote:
The botnet is still hammering away, checking those old accounts. But
the bottleneck appears to have been saslauthd threads. Doubling the
thread count from 5 to 10 has resolved the problem for now. (And,
If you're comfortable with caching, increase
On 09/19/17 09:52 -0400, Michael Sofka wrote:
The botnet is still hammering away, checking those old accounts. But
the bottleneck appears to have been saslauthd threads. Doubling the
thread count from 5 to 10 has resolved the problem for now. (And,
If you're comfortable with caching,
Follow up
The botnet is still hammering away, checking those old accounts. But
the bottleneck appears to have been saslauthd threads. Doubling the
thread count from 5 to 10 has resolved the problem for now. (And, might
even explain the occasional slow response from IMAP I've observed.)
I'm seeking help from the collective wisdom of the Cyrus world.
In the past two days we have seen first a doubling, and then a
quadrupling+ of badlogins to Cyrus. These appear to be coming from a
botnet, in that the IPs are spread around in a way that evades fail2ban.
It got so bad Friday
