📅 Original date posted:2015-06-19
📝 Original message:On Thu, Jun 18, 2015 at 11:56 PM, Mike Hearn <mike at plan99.net> wrote:
> We already removed the footer because it was incompatible with DKIM
>> signing. Keeping the "[Bitcoin-dev] " prepend tag in subject is compatible
>> with DKIM header signing only if the poster manually prepends it in their
>> subject header.
>>
>
> I still see footers being added to this list by SourceForge?
>
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.
>
>
>> Opinions?
>>
>
> I've asked Jeff to not use his @bitpay.com account for now.
>
>
I'm guessing DKIM enforcement is not very common because of issues like
this?
It seems that Sourceforge silently drops DKIM enforced mail like
jgarzik's. LF seems to pass along their mail but mangles the header/body
and makes DKIM verification fail, which causes gmail to toss it into the
spam folder. I think this behavior is slightly worse than Sourceforge
because it makes the poster think their message was successfully sent (it
is in the archive), but many subscribers never see it due to the spam
binning.
I don't see any good solution to this except an auto-reject for DKIM
enforced domain postings. Yes this is rather terrible, but the instant
rejection is vastly better than Sourceforge silently dropping the post or
LF getting stuck in spam filters.
We should also auto-reject any other reason for mail getting stuck in the
moderation queue like including non-subscribers. I considered
auto-rejecting spam too, but that could go horribly wrong as a false From
address could make the Mailman server into a spammer itself. We may have
no choice but to silently drop spam for that reason.
Warren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/f9fad649/attachment.html>;
Warren Togami Jr. [ARCHIVE] /
npub1s5…zxem8
2023-06-07 15:38:51
in reply to nevent1q…a5l3
Author Public Key
npub1s5p2xnl52ksr3a4qfa8re5znmja46ugm3x3ayy0x2c2mqrsw6ewsmzxem8Published at
2023-06-07 15:38:51Event JSON
{
"id": "727f9621a897df5975dab56f4b98e370c826bbc6f26c52494eb666e9fb1ac1bb",
"pubkey": "8502a34ff455a038f6a04f4e3cd053dcbb5d711b89a3d211e65615b00e0ed65d",
"created_at": 1686152331,
"kind": 1,
"tags": [
[
"e",
"68431f1625fd57e06833873953eb80e2e3b94c7e8396ada58852db791460fa68",
"",
"root"
],
[
"e",
"d87ddda428347f0c2b46213c166ef731049a2311d41b7d87ce6536bf3ef29417",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-06-19\n📝 Original message:On Thu, Jun 18, 2015 at 11:56 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e We already removed the footer because it was incompatible with DKIM\n\u003e\u003e signing. Keeping the \"[Bitcoin-dev] \" prepend tag in subject is compatible\n\u003e\u003e with DKIM header signing only if the poster manually prepends it in their\n\u003e\u003e subject header.\n\u003e\u003e\n\u003e\n\u003e I still see footers being added to this list by SourceForge?\n\u003e\n\nThe new list currently has footers removed during testing. I am not\npleased with the need to remove the subject tag and footer to be more\ncompatible with DKIM users.\n\n\n\u003e\n\u003e\n\u003e\u003e Opinions?\n\u003e\u003e\n\u003e\n\u003e I've asked Jeff to not use his @bitpay.com account for now.\n\u003e\n\u003e\nI'm guessing DKIM enforcement is not very common because of issues like\nthis?\n\nIt seems that Sourceforge silently drops DKIM enforced mail like\njgarzik's. LF seems to pass along their mail but mangles the header/body\nand makes DKIM verification fail, which causes gmail to toss it into the\nspam folder. I think this behavior is slightly worse than Sourceforge\nbecause it makes the poster think their message was successfully sent (it\nis in the archive), but many subscribers never see it due to the spam\nbinning.\n\nI don't see any good solution to this except an auto-reject for DKIM\nenforced domain postings. Yes this is rather terrible, but the instant\nrejection is vastly better than Sourceforge silently dropping the post or\nLF getting stuck in spam filters.\n\nWe should also auto-reject any other reason for mail getting stuck in the\nmoderation queue like including non-subscribers. I considered\nauto-rejecting spam too, but that could go horribly wrong as a false From\naddress could make the Mailman server into a spammer itself. We may have\nno choice but to silently drop spam for that reason.\n\nWarren\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/f9fad649/attachment.html\u003e",
"sig": "2c9d041f900fe53fe1989629ee1263dadd69060a4fdb769b5fe19041fa39b1d6bff8972b2b2eed1f5b26b4c62e579658b977cf7df7b4a8d91ea867a26cfd6764"
}