Michael Thomas wrote in
<16a2fff4-8ed1-4de5-b48b-291651d0c...@mtcc.com>:
|On 3/6/25 1:22 PM, John Levine wrote:
|>
|> It would be reasonable to design DKIM2 to make signing multiple messages \
|> fast,
|> e.g., if messages only have different headers, reuse the body hash. \
|> But that's
|
Michael Thomas wrote in
:
...
|> I mean, it is provably more efficient to avoid doing unnecessary
|> hashes, but I don't think in this context that the win is significant
|> even at a large operator. My own open source implementation provides
|> no provision at all for reusing a body hash
Pete Resnick wrote in
<88b6616e-7661-4966-9326-c8c71cbad...@episteme.net>:
|On 6 Mar 2025, at 14:35, Steffen Nurpmeso wrote:
|
|> ...a german one that is known to be no good to customers...
|
|OK, this is going to stop right now.
|
|In the IETF, we do not make comments on anyone's personal
On Thu, Mar 6, 2025, 5:56 p.m. Michael Thomas wrote:
>
> On 3/5/25 5:52 PM, Allen Robinson wrote:
>
>
>> 2. declaring (under protection of its own signature) where the
>>message is being sent to next.
>>
>>
>> Assuming this means copying the rcpt-to in the 822 message, that doesn't
>> re
On 3/6/2025 4:03 AM, Laura Atkins wrote:
I can certainly see a space where bulk mail moves to DKIM2 but regular
mailing list mail or non-bulk mail stays at DKIM as it is now. I’m not
sure there’s any downside to that.
This seems a significant point for the working group to keep in mind,
rat
On 3/6/2025 5:07 AM, Richard Clayton wrote:
Yesterday (Wednesday) at $DAYJOB the percentage of mail delivered to a
single recipient (rather than 2 or more) was 99.8566% (I feel justified
in providing the precision because the total count was many billions)
For that service, is that percentage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In message <799da3ac-0b80-4aa4-857d-25d1b1027...@mtcc.com>, Michael
Thomas writes
>1) A sender or intermediate can already send a new message per rcpt-to.
>This is an operational issue,
yes, your MTA will have a configuration setting for this
>an
> On 6 Mar 2025, at 06:59, Jim Fenton wrote:
>
> On 5 Mar 2025, at 21:19, Murray S. Kucherawy wrote:
>
>> On Wed, Mar 5, 2025 at 3:54 PM Steffen Nurpmeso wrote:
>>
>>> But that DKIM2 draft mutilates SMTP to *only* work in this one
>>> recipient mode: even if a mailing-list has hundreds of Gm
Hello.
Murray S. Kucherawy wrote in
:
|On Wed, Mar 5, 2025 at 3:54 PM Steffen Nurpmeso wrote:
|
|> But that DKIM2 draft mutilates SMTP to *only* work in this one
|> recipient mode: even if a mailing-list has hundreds of Gmail
|> subscribers, where ACDC would (could) send one message to all
On 3/6/25 9:22 PM, John Levine wrote:
multiple recipients in mailing list mail
is an artifact of the fact that the software dates from the last millenuium when
networks were slow.
Looking forward, we might consider that the same conditions could apply
for interplanetary email.
--
Cheers,
Jere
On Thu, Mar 6, 2025 at 1:36 PM Michael Thomas wrote:
> On 3/6/25 1:22 PM, John Levine wrote:
> > It would be reasonable to design DKIM2 to make signing multiple messages
> fast,
> > e.g., if messages only have different headers, reuse the body hash. But
> that's
> > just an optimization.
>
> I t
On 3/6/25 2:27 PM, Murray S. Kucherawy wrote:
On Thu, Mar 6, 2025 at 1:36 PM Michael Thomas wrote:
On 3/6/25 1:22 PM, John Levine wrote:
> It would be reasonable to design DKIM2 to make signing multiple
messages fast,
> e.g., if messages only have different headers, reuse the b
On 3/5/25 5:52 PM, Allen Robinson wrote:
2. declaring (under protection of its own signature) where the
message is being sent to next.
Assuming this means copying the rcpt-to in the 822 message, that
doesn't require any modification to DKIM itself. There is no
Ha!
Steffen Nurpmeso wrote in
<20250306203525.oaFQ9udg@steffen%sdaoden.eu>:
|Murray S. Kucherawy wrote in
| :
...
||> One thing is plain: until ACDC or DKIM2 have penetrated the
||> infrastructure, the current mess of DMARC and ARC will have to be
||> dealt with! This IETF has forced all t
Richard Clayton wrote in
<0MG+VuB$taynf...@highwayman.com>:
|-BEGIN PGP SIGNED MESSAGE-
...
|it was solely for incoming mail (but will include email sent from one
|user of the platform to another)
But, please. One thing.
For one, do you have numbers from say ten years ago?
Google alr
15 matches
Mail list logo
