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


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

Re: Threading; was Re: HTTP shimmed to HTTPS

Started byGreg Wooledge <wooledg@eeg.ccf.org>
First post2019-07-23 18:20 +0200
Last post2019-07-23 18:30 +0200
Articles 4 — 2 participants

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

  Re: Threading; was Re: HTTP shimmed to HTTPS Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-23 18:20 +0200
    Re: Threading; was Re: HTTP shimmed to HTTPS Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-23 18:30 +0200
      Re: Threading; was Re: HTTP shimmed to HTTPS Brad Rogers <brad@fineby.me.uk> - 2019-07-23 19:10 +0200
    Re: Threading; was Re: HTTP shimmed to HTTPS Brad Rogers <brad@fineby.me.uk> - 2019-07-23 18:30 +0200

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

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-23 18:20 +0200
SubjectRe: Threading; was Re: HTTP shimmed to HTTPS
Message-ID<yn5G9-6Y4-5@gated-at.bofh.it>
On Tue, Jul 23, 2019 at 08:56:36AM -0700, peter@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.

[toc] | [next] | [standalone]


#211679

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-23 18:30 +0200
Message-ID<yn5PQ-71w-3@gated-at.bofh.it>
In reply to#211677
On Tue, Jul 23, 2019 at 05:22:44PM +0100, Brad Rogers wrote:
> On Tue, 23 Jul 2019 12:16:31 -0400
> Greg Wooledge <wooledg@eeg.ccf.org> 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.

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


#211684

FromBrad Rogers <brad@fineby.me.uk>
Date2019-07-23 19:10 +0200
Message-ID<yn6sy-7v5-5@gated-at.bofh.it>
In reply to#211679

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

On Tue, 23 Jul 2019 12:28:50 -0400
Greg Wooledge <wooledg@eeg.ccf.org> 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
        / _)rad        never immediately apparent"
I can't do a thing 'cause I can't relax
Independence Day - Comsat Angels

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


#211681

FromBrad Rogers <brad@fineby.me.uk>
Date2019-07-23 18:30 +0200
Message-ID<yn5PQ-71w-5@gated-at.bofh.it>
In reply to#211677

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

On Tue, 23 Jul 2019 12:16:31 -0400
Greg Wooledge <wooledg@eeg.ccf.org> 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
        / _)rad        never 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

[toc] | [prev] | [standalone]


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


csiph-web