From: Boyd Roberts <boyd@strakt.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Usenet Gateway and Mailing List Archive Woes.
Date: Tue, 19 Feb 2002 13:05:21 +0100 [thread overview]
Message-ID: <3C723F81.11FFA801@strakt.com> (raw)
In-Reply-To: <25d6bf57d316372196b0f186f321c1d3@plan9.bell-labs.com>
rob pike wrote:
> This is acme/mail's fault. it's got a terrible heuristic for deciding the
> type of the attachment.
The real problem is the MINEfield (sic) that is the 4 MIME RFCs.
next prev parent reply other threads:[~2002-02-19 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 2:00 rob pike
2002-02-19 12:05 ` Boyd Roberts [this message]
2002-02-19 12:26 ` Lucio De Re
2002-02-19 12:35 ` Boyd Roberts
2002-02-19 12:59 ` Lucio De Re
2002-02-19 13:02 ` Boyd Roberts
2002-02-19 12:27 ` Matt H
[not found] <ralph@inputplus.demon.co.uk>
2002-02-18 14:43 ` Ralph Corderoy
2002-02-19 1:52 ` Scott Schwartz
2002-02-22 9:58 ` Ralph Corderoy
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=3C723F81.11FFA801@strakt.com \
--to=boyd@strakt.com \
--cc=9fans@cse.psu.edu \
/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).