From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: format=flowed flawed?
Date: Wed, 02 Jul 2003 18:11:42 +0200 [thread overview]
Message-ID: <m3llvgkiwx.fsf@merlin.emma.line.org> (raw)
Hi,
I am using a somewhat recent CVS Gnus, and I am wondering if Gnus'
format=flowed support is correct.
Please consider Message-ID: <bds3ii$10eu4j$2@ID-131796.news.dfncis.de>,
in de.comm.software.mailserver (01 Jul 2003 15:47:30 +0200, from Roland
Wolters).
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
This is what a body section looks like in Tin:
>>meldet er sich dort in eienr normalen Session zuerst mit dem 'Helo' an,
>>es folgt die Antowrt des Servers ('250-...'), danach kommt ein 'Mail
>>From: rolandwolters@web.de' und ein 'Rcpt To: soundos@xyz.de'.
>
> Wenn das so kommt, sind Mailclient und Mailservern kaputt.
>
> 1. die spitzen Klammern in MAIL FROM und RCPT TO fehlen; und:
>
> 2. HELO darf keine mehrzeiligen Antworten der Art 250- nach sich ziehen
And this is what it looks like in Gnus (yes the indentation is a
verbatim copy & paste):
>>meldet er sich dort in eienr normalen Session zuerst mit dem 'Helo' an,
>>es folgt die Antowrt des Servers ('250-...'), danach kommt ein 'Mail
>>From: rolandwolters@web.de' und ein 'Rcpt To: soundos@xyz.de'.
> Wenn das so kommt, sind Mailclient und Mailservern kaputt.
> 1. die spitzen Klammern in MAIL FROM und RCPT TO fehlen; und: 2. HELO
> darf keine mehrzeiligen Antworten der Art 250- nach sich ziehen
Apparently, Gnus chose to reformat this quoted part; this doesn't look
right to me.
Besides that, it seems (for a while now) that ^, AR and AT are totally
hosed, and C-u 50 M-g also behaves in a different way from q C-u 50 RET.
I suffered from .newsrc.eld corruption a while back, but can this be the
root of this AR/AT problem? I get all sorts of errors "This is a
pseudo-article" or when pressing AT, I see the root of the thread I'm
looking at, but all leaves in the thread that were visible before disappear.
--
Matthias Andree
next reply other threads:[~2003-07-02 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 16:11 Matthias Andree [this message]
2003-07-02 20:33 ` Simon Josefsson
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=m3llvgkiwx.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.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).