On Mon 24/Mar/2025 20:49:32 +0100 Wei Chuang wrote:
To support that use case and other scenarios where the recipient is not
explicitly declared in the RFC5322 message e.g. some mailing lists, the sender
can populate a DKIM2-Signature "rt=" tag. Note that "rt=" here still only
supports a single
On Tue, Mar 25, 2025 at 3:06 AM Alessandro Vesely wrote:
> On Mon 24/Mar/2025 20:49:32 +0100 Wei Chuang wrote:
> > To support that use case and other scenarios where the recipient is not
> > explicitly declared in the RFC5322 message e.g. some mailing lists, the
> sender
> > can populate a DKIM2-
If Joe Schmoe, an email administrator, signs corporate mail with DKIM2
but have other mail streams that may not support it, or legacy systems
incapable of using it, would not DMARC still be needed to apply/report
to/for these other mailstreams in that scenario, or to protect from
external entit
Colleagues,
The ball is in my court to summarize the transcript/audio from IETF 122's
DKIM session into minutes and post them to the datatracker. Due to travel
and my schedule upon returning, I probably won't get to that until this
weekend. Apologies for the delay.
-MSK
On Tue, Mar 25, 2025, 7:21 a.m. Alessandro Vesely wrote:
> On Mon 24/Mar/2025 14:13:01 +0100 Richard Clayton wrote:
> > In message <04daef5f-46a1-4393-8f42-677d2d375...@tana.it>, Alessandro
> Vesely writes
> >
> >>Accommodating multiple recipients in the signature would have the added
> value
>
