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

Groups > linux.debian.user > #212769

Re: Shimming HTTP to HTTPS.

Show all headers | View raw

Sorry for the late reply.

From: David Wright
Date: Sun, 28 Jul 2019 19:40:04 -0500
> You read postings on the web with a browser. When you want to reply,
> you open a composition window and paste in the To/Cc/Subject headers
> from the web page.

Correct.

> But the point is that Message-ID:s, In-Reply-To:s and References:
> in *emails* are not URLs, but <strings>, even though their text
> is used to mark links on the web page.

OK, thanks.  For the In-Reply-To above I omitted the link string.
Hopefully I got the right message.

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

Yes.  My worst error, which spoiled the References, was to omit < and >. 

> > 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 ...

It's self contained.  The entire MUA in one module.
Nothing to add; just install and use.

> If you're typing (or pasting) the references, ...

One mouse action does copy and paste.

> 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.

OK.  Will see the result with In-Reply-To only for this message.

Thanks,              ... Peter E.



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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy. peter@easthope.ca - 2019-07-18 00:20 +0200
  Re: HTTP shimmed to HTTPS; was Re: stunnel as transparent proxy. Reco <recoverym4n@enotuniq.net> - 2019-07-18 09:20 +0200
    Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-07-28 18:40 +0200
      Re: Shimming HTTP to HTTPS. Reco <recoverym4n@enotuniq.net> - 2019-07-28 19:00 +0200
        Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 02:50 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-22 18:10 +0200
          Re: Shimming HTTP to HTTPS. Reco <recoverym4n@enotuniq.net> - 2019-08-22 19:40 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-23 19:30 +0200
      Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 02:50 +0200
        Re: Shimming HTTP to HTTPS. Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-29 08:30 +0200
          Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 18:50 +0200
        Re: Shimming HTTP to HTTPS. peter@easthope.ca - 2019-08-14 05:10 +0200
          Re: Shimming HTTP to HTTPS. David Wright <deblis@lionunicorn.co.uk> - 2019-08-15 00:10 +0200

csiph-web