📅 Original date posted:2015-06-19
📝 Original message:>
> The new list currently has footers removed during testing. I am not
> pleased with the need to remove the subject tag and footer to be more
> compatible with DKIM users.
>
Lists can do what are effectively MITM attacks on people's messages in any
way they like, if they resign for the messages themselves. That seems fair
to me! :)
> I'm guessing DKIM enforcement is not very common because of issues like
> this?
>
DKIM is used by most mail on the internet. DMARC rules that publish in DNS
statements like "All mail from bitpay.com is signed correctly so trash any
that isn't" are used on some of the worlds most heavily phished domains
like google.com, PayPal, eBay, and indeed BitPay.
These rules are understood and enforced by all major webmail providers
including Gmail. It's actually only rusty geek infrastructure that has
problems with this, I've never heard of DKIM/DMARC users having issues
outside of dealing with mailman. The vast majority of email users who never
post to technical mailing lists benefit from it significantly.
Really everyone should use them. Adding cryptographic integrity to email is
hardly a crazy idea :)
> It seems that Sourceforge silently drops DKIM enforced mail like jgarzik's.
>
It's not SourceForge, it's your spam filter. His mail gets through to me
but it's all in the spam folder.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/3aababa5/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:38:52
in reply to nevent1q…urvs
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:38:52Event JSON
{
"id": "e167c7cec670744897aa4d2283629f92768d9ca93066f12e847873e3140a4e52",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686152332,
"kind": 1,
"tags": [
[
"e",
"68431f1625fd57e06833873953eb80e2e3b94c7e8396ada58852db791460fa68",
"",
"root"
],
[
"e",
"727f9621a897df5975dab56f4b98e370c826bbc6f26c52494eb666e9fb1ac1bb",
"",
"reply"
],
[
"p",
"8502a34ff455a038f6a04f4e3cd053dcbb5d711b89a3d211e65615b00e0ed65d"
]
],
"content": "📅 Original date posted:2015-06-19\n📝 Original message:\u003e\n\u003e The new list currently has footers removed during testing. I am not\n\u003e pleased with the need to remove the subject tag and footer to be more\n\u003e compatible with DKIM users.\n\u003e\n\nLists can do what are effectively MITM attacks on people's messages in any\nway they like, if they resign for the messages themselves. That seems fair\nto me! :)\n\n\n\u003e I'm guessing DKIM enforcement is not very common because of issues like\n\u003e this?\n\u003e\n\nDKIM is used by most mail on the internet. DMARC rules that publish in DNS\nstatements like \"All mail from bitpay.com is signed correctly so trash any\nthat isn't\" are used on some of the worlds most heavily phished domains\nlike google.com, PayPal, eBay, and indeed BitPay.\n\nThese rules are understood and enforced by all major webmail providers\nincluding Gmail. It's actually only rusty geek infrastructure that has\nproblems with this, I've never heard of DKIM/DMARC users having issues\noutside of dealing with mailman. The vast majority of email users who never\npost to technical mailing lists benefit from it significantly.\n\nReally everyone should use them. Adding cryptographic integrity to email is\nhardly a crazy idea :)\n\n\n\u003e It seems that Sourceforge silently drops DKIM enforced mail like jgarzik's.\n\u003e\n\nIt's not SourceForge, it's your spam filter. His mail gets through to me\nbut it's all in the spam folder.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/3aababa5/attachment.html\u003e",
"sig": "3bb9efcd760b7c98d11f6b7ffe05339a70b9f76083f26836e0a71bdbf4336b9c764d8a33a4fc5e27220d73d44967b284ace8bc0d2526b304bed18e45c0571067"
}