On 07.07.21 23:12, Jay Hennigan via mailop wrote:
>> Encourage transparent 2FA, and options like country auth restrictions,
>> blocking AUTH from cloud providers/hosting companies known for being a
>> haven for those types of attacks, (should make a blog post on best
>> practices for authenticati
On 7/7/21 13:08, Michael Peddemors via mailop wrote:
[snip]
You should consider adding some AUTH protections of course, to mitigate
compromised accounts, and better detection/rate limiters for when they do.
Encourage transparent 2FA, and options like country auth restrictions,
blocking AUTH
On 07.07.21 22:08, Michael Peddemors via mailop wrote:
> Start by including the IP(s) you are discussing ;)
mx-out-01.fh-muenster.de [185.149.214.63]
mx-out-02.fh-muenster.de [212.201.120.206]
> Compromised accounts are indeed the bane of the responsible
> administrator, and as you can see.. the
Start by including the IP(s) you are discussing ;)
Compromised accounts are indeed the bane of the responsible
administrator, and as you can see.. the rate limiting systems ARE
essential, you are unlikely to suffer a reputation issue, if only a few
escape (unless they have REALLY bad content,
Hey guys,
I have to take the walk of shame and report a spam outbreak on my
systems because of a phished user account and a loophole in the rate
limiting we do.
As soon as we got notifed, we stopped and cleaned the queues, blocked
the user, investigated the cause and fixed the rate limiting befor
