From: Steinar Bang <sb@metis.no>
Subject: Re: text/html parse failure
Date: 22 Jan 2000 14:04:29 +0100 [thread overview]
Message-ID: <whiu0mp89u.fsf@viffer.metis.no> (raw)
In-Reply-To: Karl Kleinpaste's message of "21 Jan 2000 14:52:01 -0500"
>>>>> Karl Kleinpaste <karl@justresearch.com>:
> Below are two messages, which I stole out of a mailing list and then
> hacked on manually in a different personal group until I got to a
> point where one difference between them determines whether they parse
> correctly as HTML or not.
When I did a C-d and visited the HTML parts, they both looked OK to me
in Gnus 5.8.3 (a friday checkout from CVS). The first one had the
extra text "steve_tassio@csgsystems.com" which was a mailto: URL to
the same address.
next prev parent reply other threads:[~2000-01-22 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 19:52 Karl Kleinpaste
2000-01-22 2:58 ` David Maslen
2000-01-22 13:04 ` Steinar Bang [this message]
2000-01-22 15:43 ` Karl Kleinpaste
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=whiu0mp89u.fsf@viffer.metis.no \
--to=sb@metis.no \
/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).