On 30 Sep 2026, at 14:05, Bron Gondwana wrote:
On Wed, Sep 30, 2026, at 11:58, Steffen Nurpmeso wrote:
Today an OpenSSL announcement, which has a 77198 bytes HTML part.
If that is reposted through a mailing-list which cuts HTML parts,
only leaving text,
Those mailing lists should stop doing that. As part of upgrading to
DKIM2 they can also upgrade to not arbitrarily dropping parts of the
original message, whether that's HTML parts or attachments. It's not
1995 any more, and they don't need to "save bandwidth" by excessively
tampering the incoming message.
I think Mauro's request was more general than the mailing list case:
What we don't want is software (mailing list or otherwise) taking "the
message that came in" and blindly comparing it to "the message that is
going out after modification" and forming an instance header from that.
Putting a cap on header size is one way to make it clear to such
middleware that it is about to do a bad thing. Whether that's the way we
want to put it in the BCP is up to the WG.
pr
--
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
