Re: Threading; was Re: HTTP shimmed to HTTPS
pe...@easthope.ca writes: * From: Reco recovery...@enotuniq.net * Date: Mon, 22 Jul 2019 17:35:27 +0300 > You're breaking threading. Just a friendly note. I've been adding References manually. By "breaking" do you refer to omission of older references (For example, http://lists.debian.org/debian-user/2019/07/msg01131.html has only two references whereas it was about 8 from the original.) or to the presence of links labelled [ & # 128270; ]? ( <== Spaces inserted to suppress character reference.) The omission is only that I failed to put all of them. Others have already mentioned the issues with the missing In-Reply-To header etc. The most problematic thing seems to be the inclusion of NUL-characters in the lines of form: * From: Reco recovery...@enotuniq.net | ^^ The indicated columns (with `^`) seem to appear as tabs, NUL bytes or pad bytes in other mail user agents. It is problematic that these occur in your e-mails because they cause the mails to be displayed wrongly for some users (some clients see only the begin of line until the first NUL, others only the begin of message until the first NUL). Check the source code of https://lists.debian.org/debian-user/2019/07/msg01178.html to find out that there are unexpected NUL-bytes: $ wget -Otest.html https://lists.debian.org/debian-user/2019/07/msg01178.html From a hex editor ($ dhex test.html): AD0 3e 0a 3c 21 2d 2d 58 2d 42 6f 64 79 2d 6f 66 2d >.. PROBLEM vv--v AF0 2a 09 46 72 6f 6d 3a 20 52 65 63 6f 20 00 72 65 *.From: Reco .re B00 63 6f 76 65 72 79 6d 34 6e 40 65 6e 6f 74 75 6e coverym4n@enotun B10 69 71 2e 6e 65 74 00 0a 2a 09 44 61 74 65 3a 20 iq.net..*.Date: PROBLEM --^^-^ B20 4d 6f 6e 2c 20 32 32 20 4a 75 6c 20 32 30 31 39 Mon, 22 Jul 2019 B30 20 31 37 3a 33 35 3a 32 37 20 2b 30 33 30 30 0a17:35:27 +0300. B40 26 67 74 3b 20 59 6f 75 27 72 65 20 62 72 65 61 > You're brea I am using a niché e-mail client as well, so I wish you the best of luck in fixing that issue... HTH Linux-Fan [...] pgpHhoUykeepv.pgp Description: PGP signature
Re: Threading; was Re: HTTP shimmed to HTTPS
On Tue 23 Jul 2019 at 08:56:36 (-0700), pe...@easthope.ca wrote: > In future I'll make more effort with the references. Beyond 3 or 4 it > can be tedious. If you're typing (or pasting) the references, I would just add the In-Reply-To instead. That way, you can Cut/Copy the original's Message-ID: Paste the line untouched, then edit *just* these characters: Message-ID:change intoIn-Reply-To: which will make your message thread correctly. As for the From/Date lines you're adding into the *body* of the message, just use their names. (Yours would be peter, not pe...@easthope.ca and certainly not &pe...@easthope.ca& where & is some weird character you happened upon.) Cheers, David.
Re: Threading; was Re: HTTP shimmed to HTTPS
On Tue, 23 Jul 2019 12:28:50 -0400 Greg Wooledge wrote: Hello Greg, >We may be seeing different symptoms as a result of *whatever* Peter is >doing, depending on how each individual mail transport agent and each >mail user agent deals with the incoming mess. Indeed. I looked up his MUA (Oberon, based on the X-Mailer header). There seems to be exactly one web site mentioning it. Definitely minority MUA. Given what you and others are saying regarding non-RFC compliant headers, added manually, no less, it seems like this MUA should be avoided until improvements are made. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I can't do a thing 'cause I can't relax Independence Day - Comsat Angels pgpR1XFXOh2Es.pgp Description: OpenPGP digital signature
Re: Threading; was Re: HTTP shimmed to HTTPS
On Tue, Jul 23, 2019 at 05:22:44PM +0100, Brad Rogers wrote: > On Tue, 23 Jul 2019 12:16:31 -0400 > Greg Wooledge wrote: > > Hello Greg, > > >You need to add "In-Reply-To:" as well. And stop doing whatever it is > >you're doing that puts NUL bytes in your "* From:" lines. Or simply > >drop those lines altogethe > > I /think/ they're tab characters. At least, that seems to be the case > from a quick glance at the message source: A 5 character (or so) space > was 'jumped' when my cursor encountered those chars. We may be seeing different symptoms as a result of *whatever* Peter is doing, depending on how each individual mail transport agent and each mail user agent deals with the incoming mess. The file I had in my ~/Maildir/new/ directory definitely had NUL bytes in it (it's gone now -- I don't save these mails). I suppose it's conceivable that someone else's MTA may translate the NULs to TABs, or that someone's MUA may display the NULs as TABs. Or that *my* MTA is translating something else into NUL bytes. Who knows? All I can say for sure is: Peter, whatever you're doing, please fix it.
Re: Threading; was Re: HTTP shimmed to HTTPS
Hi. On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote: > * From: Reco ?recovery...@enotuniq.net? > * Date: Mon, 22 Jul 2019 17:35:27 +0300 > > You're breaking threading. Just a friendly note. > > I've been adding References manually. By "breaking" do you refer to > omission of older references (For example, > http://lists.debian.org/debian-user/2019/07/msg01131.html has only two > references whereas it was about 8 from the original.) This. And, I have to add, you're adding them wrong. What you do is a violation of RFC2822: References: e1hp6yw-0002kn...@enotuniq.net E1hpYQe-tm-Lx@dalton.invalid e1hpzan-0001lu...@enotuniq.net What sane MUA does to be RFC2822-compliant is: References: > or to the presence of links labelled [ & # 128270; ]? ( <== Spaces > inserted to suppress character reference.) Does not bother me. You e-mails look somewhat unusual, but it's a part of my job to deal with malformed e-mails. I've seen stranger e-mails. It is a problem for other participants of this maillist though. > The omission is only that I failed to put all of them. Also, quoting RFC2822, The "References:" field will contain the contents of the parent's "References:" field (if any) followed by the contents of the parent's "Message-ID:" field (if any). So, the omission of certain values from parent's "References" also violates RFC2822. On a side note, your e-mails lack "In-Reply-To" header, and that can break threading for some MUAs. Again, RFC2822. In short, please consider using another e-mail client. Implementing RFC2822 by hand in every e-mail you write is something that should not require a human intervention. ktnxbye, Reco
Re: Threading; was Re: HTTP shimmed to HTTPS
On Tue, 23 Jul 2019 12:16:31 -0400 Greg Wooledge wrote: Hello Greg, >You need to add "In-Reply-To:" as well. And stop doing whatever it is >you're doing that puts NUL bytes in your "* From:" lines. Or simply >drop those lines altogethe I /think/ they're tab characters. At least, that seems to be the case from a quick glance at the message source: A 5 character (or so) space was 'jumped' when my cursor encountered those chars. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I ain't got no time for intellectual music, e.g. Hergest Ridge Heads Down No Nonsense Mindless Boogie - Alberto y Lost Trios Paranoias pgpMR1NW7LKSH.pgp Description: OpenPGP digital signature
Re: Threading; was Re: HTTP shimmed to HTTPS
On Tue, Jul 23, 2019 at 08:56:36AM -0700, pe...@easthope.ca wrote: > * From: Reco > > You're breaking threading. Just a friendly note. > > I've been adding References manually. You need to add "In-Reply-To:" as well. And stop doing whatever it is you're doing that puts NUL bytes in your "* From:" lines. Or simply drop those lines altogether.
Threading; was Re: HTTP shimmed to HTTPS
* From: Reco
