Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #211678 > unrolled thread

Threading; was Re: HTTP shimmed to HTTPS

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Threading; was Re: HTTP shimmed to HTTPS peter@easthope.ca - 2019-07-23 18:20 +0200
    Re: Threading; was Re: HTTP shimmed to HTTPS Reco <recoverym4n@enotuniq.net> - 2019-07-23 18:30 +0200
      Email client; was: Re: Threading. peter@easthope.ca - 2019-07-29 15:40 +0200
        Re: Email client; was: Re: Threading. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 17:30 +0200
    Re: Threading; was Re: HTTP shimmed to HTTPS David Wright <deblis@lionunicorn.co.uk> - 2019-07-23 21:40 +0200
    Re: Threading; was Re: HTTP shimmed to HTTPS Linux-Fan <Ma_Sys.ma@web.de> - 2019-07-24 02:20 +0200

#211678 — Threading; was Re: HTTP shimmed to HTTPS

*	From: Reco recoverym4n@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.  

The links are from the debian mailing list software.  128270(9) = 
1F50E(E) or 128270(decimal) = 1F50E(hexadecimal).  U+1F50E is beyond 
the list in 
https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references.
A clever Unicode supplemental character?  Does it comply to an RFC or 
standard?  Is it a good notation for the mailing list? I'd tend to 
look for someting slimpler.

In future I'll make more effort with the references.  Beyond 3 or 4 it 
can be tedious.  

Thanks,                             ... P.






-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [next] | [standalone]

#211680

	Hi.

On Tue, Jul 23, 2019 at 08:56:36AM -0700, peter@easthope.ca wrote:
> *	From: Reco ?recoverym4n@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-6g@enotuniq.net E1hpYQe-0000tm-Lx@dalton.invalid E1hpZan-0001lu-Df@enotuniq.net

What sane MUA does to be RFC2822-compliant is:

References: <E1hp6Yw-0002Kn-6g@enotuniq.net> <E1hpYQe-0000tm-Lx@dalton.invalid> <E1hpZan-0001lu-Df@enotuniq.net>


> 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

[toc] | [prev] | [next] | [standalone]

#211859 — Email client; was: Re: Threading.

From: Reco 
Date: Tue, 23 Jul 2019 19:26:13 +0300
> In short, please consider using another e-mail client.

I compose the reply from the debian-user Web page.  I don't know of a 
MUA capable of reading a page and composing a reply to it.

The boilerplate for a reply to a debian page is composed with a few 
mouse clicks. The interface allowing this is described in 
https://en.wikibooks.org/wiki/Oberon#Getting_Started and references 
there.

Regards,                   ... Peter E.

-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#211873 — Re: Email client; was: Re: Threading.

On Mon 29 Jul 2019 at 06:15:42 (-0700), peter@easthope.ca wrote:
> From: Reco 
> Date: Tue, 23 Jul 2019 19:26:13 +0300
> > In short, please consider using another e-mail client.
> 
> I compose the reply from the debian-user Web page.  I don't know of a 
> MUA capable of reading a page and composing a reply to it.

Bingo. Then it looks as if all my guesses in
https://lists.debian.org/debian-user/2019/07/msg01343.html
were basically correct.

> The boilerplate for a reply to a debian page is composed with a few 
> mouse clicks. The interface allowing this is described in 
> https://en.wikibooks.org/wiki/Oberon#Getting_Started and references 
> there.

I looked at that page some while back. Without seeing it in action,
I think I'd have difficulty in recommending any software suitable
for it because it's so different. Keep on trucking.

But the steps you've taken with In-Reply-To and References have worked fine.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#211690

On Tue 23 Jul 2019 at 08:56:36 (-0700), peter@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: <bla bla bla>

Paste the line untouched, then edit *just* these characters:

  Message-ID:    change into    In-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 peter@easthope.ca
and certainly not &peter@easthope.ca& where & is some weird character
you happened upon.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#211696

[Multipart message — attachments visible in raw view] — view raw

peter@easthope.ca writes:

> *	From: Reco recoverym4n@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  recoverym4n@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       >.<!--X-Body-of-
AE0     4d 65 73 73 61 67 65 2d  2d 3e 0a 3c 70 72 65 3e       Message-->.<pre>

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 0a        17:35:27 +0300.
B40     26 67 74 3b 20 59 6f 75  27 72 65 20 62 72 65 61       &gt; 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

[...]

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web