Re: [dmarc-ietf] DMARC with multi-valued RFC5322.From

2024-01-17 Thread Steven M Jones
On 1/17/24 2:56 AM, Alessandro Vesely wrote: [ Discussion of  what to do with multi-valued From: in messages ] However, since DMARC bears the blame of banning multi-valued From:, it is appropriate for it to say something about the consequences and possible workarounds. DMARC doesn't ban mult

Re: [dmarc-ietf] DMARC with multi-valued RFC5322.From

2024-01-17 Thread Steven M Jones
On 1/11/24 10:46 AM, Murray S. Kucherawy wrote: What I recall from when we wrote that was that the first paragraph really means "Most MTAs reject this anyway so it shouldn't even get to your DMARC filter" and the second means "If it does get to you, here's how you should probably react." +

Re: [dmarc-ietf] DMARC with multi-valued RFC5322.From

2024-01-17 Thread Douglas Foster
As with the mailing list problem, when the recipient expects authentication but the sender cannot provide it, the sender is disadvantaged. Nor an I concerned about the limitations of a particular MSA product. However, we know that mailing list posts almost always start as authorized messages, so

Re: [dmarc-ietf] DMARC with multi-valued RFC5322.From

2024-01-17 Thread Murray S. Kucherawy
On Wed, Jan 17, 2024 at 2:56 AM Alessandro Vesely wrote: > Since email format allows multi-valued From:, its meaning is > straightforward. > Syntax, yes, but meaning? That seems debatable. Does the order of values matter, for example? As John says, it can also be the result of some kind of mi

Re: [dmarc-ietf] DMARC with multi-valued RFC5322.From

2024-01-17 Thread Alessandro Vesely
On Tue 16/Jan/2024 19:24:29 +0100 Murray S. Kucherawy wrote: On Tue, Jan 16, 2024 at 2:03 AM Alessandro Vesely wrote: On Mon 15/Jan/2024 20:49:35 +0100 John Levine wrote: It appears that Scott Kitterman said: I don't think that's sensible at all. It's not the place of a signing filter to