On 03/03/2025 01:08, Andrea Pappacoda wrote:
Hi Blair,On Sun Mar 2, 2025 at 2:00 PM CET, Blair Noctis wrote:FWIW, I've enabled format=flowed after learning it in this thread, hopefully also giving those who would rather wrap some freedom (as to let it reflow, which effectively means to wrap, or not).Yeah, this email has been sent with the Format=Flowed Content-Type parameter, but the message actually still has long, non-wrapped, lines and you aren't using "soft breaks", (i.e., line breaks preceded by a space, called "flowed lines" in the RFC). So... Setting format=flowed doesn't bring any benefit in this case :/In other words, your paragraph as sent below:FWIW, I've enabled format=flowed after learning it in this thread, hopefully also giving those who would rather wrap some freedom (as to let it reflow, which effectively means to wrap, or not).should've been sent as:FWIW, I've enabled format=flowed after learning it in this thread, hopefully also giving those who would rather wrap some freedom (as to let it reflow, which effectively means to wrap, or not).without "> ", of course :)Note how lines are break at ~72 cols, but all end with a space apart from the last one.
Thanks Andrea, for not only pointing it out but also analyzing the cause. I guess it's a problem in Thunderbird which I currently use. The comparison didn't work in it either; only in the source view did I see the difference: In your Content-Transfer-Encoding: quoted-printable reply message, the original paragraph I sent has = at the end of each line, while your correctly flowed message has =20. I'm not sure how this happened, but it's another reason I need to get off Thunderbird. -- Sdrager, Blair Noctis
OpenPGP_signature.asc
Description: OpenPGP digital signature
