Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Dave Crocker via mailop
On 6/21/2022 8:25 PM, Rob Nagler via mailop wrote: Dave Crocker continues: > The existing repertoire of relevant email tech specs are for > authentication, except for SPF, which includes authorization of SMTP > client engines, and DMARC, which include rfc5321.From field domain name >

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Rob Nagler via mailop
On Tue, Jun 21, 2022 at 5:34 PM John Levine wrote: > I think you underestimate the persistence and bad faith of spammers. I certainly don't. > That also doesn't scale. There are at least 100,000 mail systems on > the Internet. How many complaints per second are you prepared to > investigate

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Dave Crocker via mailop
On 6/20/2022 8:59 AM, Rob Nagler via mailop wrote: IMHO, the problem is a lack of a public trust model. ARC, SPF, and DKIM do not solve the trust problem. There should be some FOSS that implements the model (just like certbot implements ACME). We still need virus/spam detection algorithms.

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread John Levine via mailop
According to Rob Nagler via mailop : >We could still have a public trust system that didn't require everybody to >agree on this concept. What needs to be known is to define publicly how to >fix your (authenticated) reputation at any given ADMD. If you have a >content (or otherwise) problem with a

Re: [mailop] Best practice for mailing list servers

2022-06-21 Thread Mark Fletcher via mailop
On Mon, Jun 20, 2022 at 11:47 AM Grant Taylor via mailop wrote: > On 6/15/22 6:19 PM, Ángel via mailop wrote: > > There is a fallback of connecting to the A record on port 25 if there > > is no MX. > > When was the last time that anyone has seen the fall back to A record work? > > Just did a

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Rob Nagler via mailop
On Tue, Jun 21, 2022 at 7:02 AM Bill Cole wrote: > Rewriting header and envelope addresses is as old as Sendmail. > > > I'm mystified by your distinction between rewriting the envelope sender > and "managing bounce addresses." Since this has been a discussion of history, one used to be able to

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Dave Crocker via mailop
On 6/21/2022 9:20 AM, Alessandro Vesely via mailop wrote: Mail forwarded by gmail, for example, has an X-Google-DKIM-Signature but is not otherwise DKIM-signed.  It is ARC-sealed.  (Brandon Long explained why a couple of years ago[*]). Hmmm. Sorry I missed his message when it originally

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Alessandro Vesely via mailop
On Tue 21/Jun/2022 15:40:51 +0200 John Levine via mailop wrote: According to Alessandro Vesely via mailop : "Some responsibility" is quite a long way from "ownership".  It was phrased to refer to any sort of handling or even analysis involvement. Yet, ARC sounds like a way to permit an

Re: [mailop] Timeouts to Microsoft?

2022-06-21 Thread Ken O'Driscoll via mailop
They have two open incidents in their alert centre relating to access to Exchange Online and Microsoft 365. As an EU based user, I can't say I've experienced anything, nor have any clients reported problems to me but most of them are only waking up now so... Ken. > -Original Message-

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Alessandro Vesely via mailop
On Tue 21/Jun/2022 12:06:16 +0200 Slavko via mailop wrote: Dňa 21. 6. o 9:07 Alessandro Vesely via mailop napísal(a): Section 3.9 is perhaps the worst one in that document.  By that wording, the addition of /any/ header field is forbidden, including List-*. IMO it describes headers change,

[mailop] Timeouts to Microsoft?

2022-06-21 Thread Stefano Bagnara via mailop
Hi, Since 4 hours we are experiencing slowness (e.g. connections timing out, very slow responses), to Microsoft both sending to their SMTP and reading via IMAP, from europe (checked from 4 different datacenters in europe). Do you see the same? -- Stefano Bagnara Apache James/jDKIM/jSPF

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread John Levine via mailop
According to Alessandro Vesely via mailop : >> "Some responsibility" is quite a long way from "ownership".  It was phrased >> to >> refer to any sort of handling or even analysis involvement. > >Yet, ARC sounds like a way to permit an organization to claim /somewhat less/ >responsibility for a

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Dave Crocker via mailop
On 6/21/2022 12:07 AM, Alessandro Vesely via mailop wrote: RFC 5321, sect. 3.9 Mailing Lists and Aliases ... When a message is delivered or forwarded to each address of an expanded list form, the return address in the envelope ("MAIL FROM:") MUST be changed to be the

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Bill Cole via mailop
On 2022-06-20 at 23:25:49 UTC-0400 (Mon, 20 Jun 2022 21:25:49 -0600) Rob Nagler via mailop is rumored to have said: On Mon, Jun 20, 2022 at 12:17 PM Bill Cole wrote: Which part? "That form of mailing list was already dying out 20 years ago" I don't think people were rewriting From: or

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Slavko via mailop
Dňa 21. 6. o 9:07 Alessandro Vesely via mailop napísal(a): Section 3.9 is perhaps the worst one in that document.  By that wording, the addition of /any/ header field is forbidden, including List-*. IMO it describes headers change, not headers addition. But worst one from that RFC? Why?

Re: [mailop] OVH contact required - 54.38.34.203 - vps-28239cc9.vps.ovh.net

2022-06-21 Thread Atro Tossavainen via mailop
Cher M CARON > Sorry but I represent OVH email team (not abuse), I have no power and > visibility on stuff out our email offer perimeter. This is understood. > As I say in private, the abuse form https://www.ovh.com/abuse/#!/ permit to > report spam problems. It ensure to abuse team enough

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Alessandro Vesely via mailop
On Sun 19/Jun/2022 14:15:51 +0200 Dave Crocker via mailop wrote: On 6/17/2022 9:35 PM, Brandon Long via mailop wrote: DKIM implies ownership that one doesn't want to use for relaying. FWIW, that interpretation of DKIM semantics goes beyond the DKIM specification, which, instead says:   

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Alessandro Vesely via mailop
On Mon 20/Jun/2022 20:18:04 +0200 Jaroslaw Rafa wrote: Dnia 20.06.2022 o godz. 20:05:37 Jaroslaw Rafa via mailop pisze: Mailing lists can operate minimal changes, like this list does, for example. I received your message with "From: Jaroslaw Rafa " after my filter verified that your DKIM

Re: [mailop] OVH contact required - 54.38.34.203 - vps-28239cc9.vps.ovh.net

2022-06-21 Thread Pierre-Edouard Caron via mailop
Hello Hans-Martin, Sorry but I represent OVH email team (not abuse), I have no power and visibility on stuff out our email offer perimeter. As I say in private, the abuse form https://www.ovh.com/abuse/#!/ permit to report spam problems. It ensure to abuse team enough information to check and

Re: [mailop] Microsoft Announces Tenant Trusted ARC Seal

2022-06-21 Thread Alessandro Vesely via mailop
On Mon 20/Jun/2022 19:48:50 +0200 Slavko via mailop wrote: Dňa 20. júna 2022 16:53:41 UTC používateľ Alessandro Vesely via mailop napísal: Plus, use of SPF with DMARC - even with rewriting - causes the same problem as with mailing lists. Yes, you have to rewrite From: as well, if you alter

Re: [mailop] No MX? use A/AAAA

2022-06-21 Thread Stuart Henderson via mailop
On 2022/06/20 15:39, Jarland Donnell via mailop wrote: > I've seen it work but frankly, I don't bother with it anymore. No MX for > sender or recipient, I don't send it. This rspamd module right here: > https://rspamd.com/doc/modules/mx_check.html That is not what mx_check does at all. It looks

Re: [mailop] OVH contact required - 54.38.34.203 - vps-28239cc9.vps.ovh.net

2022-06-21 Thread Hans-Martin Mosner via mailop
Am 20.06.22 um 20:25 schrieb Hans-Martin Mosner via mailop: Am 20.06.22 um 07:35 schrieb Hans-Martin Mosner via mailop: I've reported a list of a few dozen IPs at OVH that are clearly used by one snowshoe spammer to Pierre-Edouard and to abuse@OVH, but to no effect. Today I see an effect,