From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: recent message.el quote changes.
Date: Tue, 07 Aug 2001 23:10:39 +0200 [thread overview]
Message-ID: <87y9ovshio.fsf@deneb.enyo.de> (raw)
In-Reply-To: <iluwv4faiaw.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Tue, 07 Aug 2001 18:31:03 +0100")
Simon Josefsson <jas@extundo.com> writes:
> The recent changes aren't perfect, I've seen a few versions of the
> following in just 2-3 days. Original text:
>
> ,----
> | >I think some servers MIME parse messages and store them in another
> | >equivalent format somehow, and when clients requests RFC822-messages
> | >it reconstructs MIME delimiters and MIME headers. All the
> | information
> | >is there, but since the signature was calculated over the first MIME
> | >delimiters/headers the reconstruction often breaks the signature.
> `----
I think I'm going to write a comb quoting detector and restorer.
BTW, does Outlook always use '>' and never '> '?
next prev parent reply other threads:[~2001-08-07 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 17:31 Simon Josefsson
2001-08-07 19:20 ` Kai Großjohann
2001-08-07 21:10 ` Florian Weimer [this message]
2001-08-08 11:59 ` Simon Josefsson
2001-08-08 20:35 ` Raymond Scholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y9ovshio.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).