Re: [mailop] Compromised email account trends

2023-02-23 Thread Steve Freegard via mailop
Gah - sorry, my work email address changed recently and I forgot to update it here, so my post to the mailing list bounced and I only just noticed as I'm at M3AAWG. This was the blog post that I posted to Jarland that didn't make it to the list:

Re: [mailop] Compromised email account trends

2023-02-23 Thread Giovanni Bechis via mailop
On 2/22/23 15:44, Andrew C Aitchison via mailop wrote: On Wed, 22 Feb 2023, Giovanni Bechis via mailop wrote: this would not work for me, on my servers ~6% of imap logins are from bots. *Successful* IMAP logins ? not for bots but, at least my[.]com address space does successful imap logins.

Re: [mailop] Compromised email account trends

2023-02-23 Thread Taavi Eomäe via mailop
> Really? RFC6749: Maybe I was a bit too eager with the quote earlier as I was really pointing at the "register as a developer part." Your qualm was that *you* have to register as a developer. How that process looks like, how tedious it is and how many MUAs already have added support is

Re: [mailop] SPF and DMARC Passed Phishing Spam from Oracle.com

2023-02-23 Thread Alessandro Vesely via mailop
On Thu 23/Feb/2023 05:30:28 +0100 Peter Beckman wrote: It seems that if you are able to get a server in oraclecloud.com, you can send SPF- and DMARC-passing spam to be sent by Oracle.com, which includes a phishing URL attempt. Is this for real??? Yup, that's how DMARC works: [...]

Re: [mailop] Compromised email account trends

2023-02-23 Thread Julian Bradfield via mailop
On 2023-02-22, Taavi Eomäe via mailop wrote: >> Why should I need to use a program registered to the service provider >> in order to read my email? (Or in my case, register myself as a >> developer with Microsoft in order to allow me and my colleagues to >> read our own mail.) > > > You are