Re: Testing From-Munging
dkg <[email protected]> Wed, 30 Mar 2022 16:36:15 +0000
| Newsgroups | gmane.ietf.smtp |
|---|---|
| Message-ID | <BM7YT092MMqf5RO5rnoXeFHzAPT3LxvRlwaIiVI9v06Wq0tc23ha8s43n3gqkBmVQPsLat91gqwJKD6QkqMfgM38xtXf4LbnTwibL1l6RRc=@protonmail.com> |
heh -- there are multiple forms of From-munging, i guess. This test wasn't about the "From:" header field (which i think is what you're talking about). This test was about the "From " in the body of the message getting prefixed with a ">" character, which it did. It's a relic of the old mbox format, where each message started with a line with "From ", so the message bodies that had that got a > prepended to them so that they wouldn't start a new message. This shouldn't really be happening on modern systems for new messages, though, since there are much better formats than mbox available today. (and, if you are for some reason obliged to use mbox, there are known reversible ways to from-munge, so that when messages transit through an mbox they don't come out modified.) If you're interested in helping diagnose or fix this on IETF infrastructure, it's probably best to follow up on https://github.com/ietf-tools/mailarch/issues/3487 --dkg Sent with [ProtonMail](https://protonmail.com/) secure email. ------- Original Message ------- On Wednesday, March 30th, 2022 at 11:18 AM, Todd Herr <[email protected]> wrote: > On Wed, Mar 30, 2022 at 1:04 AM dkg <[email protected]> wrote: > >> Sorry for the noise. I'm just confirming that From-munging still happens on IETF mailing lists (see https://github.com/ietf-tools/mailarch/issues/3487) >> >>>From protonmail, this is an unsigned message. > > My understanding has always been that the munging happens if the original Author Domain has published a DMARC policy that isn't p=none, like protonmail.com has done: > >> $ dig +short _dmarc.protonmail.com txt >> >> "v=DMARC1; p=quarantine; fo=1; aspf=s; adkim=s;" > > -- > > Todd Herr | Technical Director, Standards and Ecosysteme: [email protected]: 703.220.4153 > > This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system. _______________________________________________ ietf-smtp mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-smtp