On 12/12/24 16:44, Scott Q. wrote:
I understood that. You temp block the MS IP that shows high failure rate, which
may or may not be warranted.
No. I'm blocking the accounts, not the IPs. I won't block an IP that is clearly
authenticating on compromised accounts.
My fault for the misunderst
On 12/12/24 16:19, Scott Q. wrote:
How can you tell if they are compromised if legitimate user A connects from
France via 'New' Outlook and hacker B connects from Australia via 'New' Outlook ?
I'm afraid you misunderstood my previous answers. When an IP is behaving like :
IP 4.233.216.98 (8075
On 12/12/24 14:52, Scott Q. wrote:
So are you guys blocking the connections from the MS ASN ? Does that result in
'New' Outlook not being able to login at all or not ?
No, we disable accounts when the credentials seem to be compromised.
François
___
On 12/11/24 17:19, Scott Q. via mailop wrote:
It seems MS is pushing really hard for the 'NEW' Outlook
adoption. This software, along with Outlook Mobile and myMail
(mail.ru), etc, cache logon information on their own infrastructure
and then basically proxy the connection to the service provider.
On 11/10/23 16:54, Carsten Schiefner via mailop wrote:
sort of triggered by Benoit's recent and absolutely spot-hitting rant about
Microsoft's inability resp. unwillingness to appropriately deal with spam
complaints, I thought I should share this article:
Microsoft lays hands on login data: Bew
On 3/30/23 18:36, Hans-Martin Mosner via mailop wrote:
I try to tackle this by analyzing domains present in mail headers and rejecting
mails accordingly. As you've experienced, talking the Office365 customers into
leaving their crappy host isn't working, so I will have to accept that a
signific
On 11/17/21 9:12 PM, Jarland Donnell via mailop wrote:
> If you can get the passwords that are going around in these database dumps and
> compare them to email accounts in your system, test those passwords against
> their email accounts using automation, and then force a password change it if
> mat
On 11/17/21 9:10 AM, Hans-Martin Mosner via mailop wrote:
> Here I want to focus on hacked mail accounts. I can think of two major root
> causes but I have no idea about their relative significance:
> * Easily guessable passwords, with two subcauses for exploits:
> o Brute force authenticati
On 9/11/20 2:07 PM, Kieran Cooper via mailop wrote:
> Does anyone have any knowledge of how Gmail decides when to send an
> auto-reply?
RFC 3834 :
2. When (not) to send automatic responses
An automatic responder MUST NOT blindly send a response for every message
received. In practice
On 3/24/20 11:36 AM, Steve Freegard via mailop wrote:
> I also found that I wasn't discarding some drive-by stuff which is more akin
> to
> what you were talking about so I've also corrected that which will further
> reduce the noise, raise the quality and reduce the number of daily reports
> bei
On 2/22/20 7:47 PM, Alessandro Vesely via mailop wrote:
> Even without 2FA, a password different from "12345" is probably desperately
> hard to guess.
_No_
When users tend to re-use the same password on different web sites or a slightly
different password from site to site, guessing a password mi
On 10/24/19 2:19 PM, Stefan Bauer via mailop wrote:
> Sometimes, customers feel clever and have another local mailfilter on
> site, that rejects mails, after we already have accepted them at
> spamfilter level.
> So the reject generates bounces at our spamfilters. Howto handle this?
_If_ your clie
12 matches
Mail list logo
