From: Christoph Groth <christoph@grothesque.org>
To: info-gnus-english@gnu.org
Subject: Re: Gnus capitalizes non-header "from"
Date: Tue, 14 Nov 2017 12:26:44 +0100 [thread overview]
Message-ID: <87lgj9hzij.fsf@grothesque.org> (raw)
In-Reply-To: <22bmk59t76.fsf@netnod.se> (Lars-Johan Liman's message of "Tue, 14 Nov 2017 09:10:21 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]
Lars-Johan Liman wrote:
> This can possibly boil down to the old e-mail standard for the
> "mailbox" format - the old local storage format for incoming mail to a
> user (typically in /var/(spool/)mail/liman (in my case). In those
> files, messages are separated by a "From ...." line (no colon! not
> header!), and in order to not mistake a text line starting with "From
> " for a message separator, all "From " lines in a message had to be
> "quoted", typically with a ">" leading to text like this:
Yest that must be indeed the source of the problem, thanks for your
explaination.
> One way around this could be to see whether you can append your Python
> code as something else than "text/plain", and have it encoded in
> Quoted-Printable (or even BASE64), which ought to eliminate the
> problem. (Q-P encoding would lead to "From ..." --> "=70rom ...", if I
> remember the standard correctly, which I probably don't ;-).
The body of the mbox file I attached to my reply to Adam is encoded in
quoted-printable.
Christoph
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-11-14 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 15:44 Christoph Groth
2017-11-13 16:32 ` Adam Sjøgren
2017-11-14 0:57 ` Eric Abrahamsen
2017-11-14 7:38 ` Adam Sjøgren
2017-11-14 11:08 ` Christoph Groth
2017-11-14 16:00 ` Adam Sjøgren
2017-11-14 19:13 ` Christoph Groth
2017-11-14 19:19 ` Adam Sjøgren
2017-11-14 19:47 ` Eric Abrahamsen
2017-11-14 16:13 ` Eric Abrahamsen
2017-11-14 8:10 ` Lars-Johan Liman
2017-11-14 11:26 ` Christoph Groth [this message]
2017-11-15 19:56 ` Eric Abrahamsen
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=87lgj9hzij.fsf@grothesque.org \
--to=christoph@grothesque.org \
--cc=info-gnus-english@gnu.org \
/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).