The enclosed message causes problems for nmh-1.0.4 from the NetBSD
packages collection. It prints the headers, along with the message:
mhshow: bogus multipart content in message 1256
Alas, I don't know the mail RFCs well enough to pin the blame on the
IETF editor or NMH. Any ideas?
Thanks,
Kevin
[EMAIL PROTECTED]
------- Forwarded Message
Return-Path: <[EMAIL PROTECTED]>
Received: from nevertheless.selresearch.net (nevertheless.selresearch.net
[64.167.159.132])
by destroy.selresearch.net (8.12.0/8.12.0) with ESMTP id f9HJvFmZ004907
for <[EMAIL PROTECTED]>; Wed, 17 Oct 2001 12:57:15 -0700 (PDT)
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
by nevertheless.selresearch.net (8.12.0/8.12.0) with ESMTP id f9HJxMjK017410
for <[EMAIL PROTECTED]>; Wed, 17 Oct 2001 12:59:22 -0700 (PDT)
Received: (from adm@localhost)
by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA28546
for [EMAIL PROTECTED]; Wed, 17 Oct 2001 15:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA28064
for <[EMAIL PROTECTED]>; Wed, 17 Oct 2001 14:38:12 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03018;
Wed, 17 Oct 2001 14:38:12 -0400 (EDT)
Message-Id: <[EMAIL PROTECTED]>
To: IETF-Announce: ;
Subject: RFC 3143 on Known HTTP Proxy/Caching Problems
Cc: [EMAIL PROTECTED]
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: RFC Editor <[EMAIL PROTECTED]>
Date: Wed, 17 Oct 2001 14:38:12 -0400
Sender: [EMAIL PROTECTED]
X-UIDL: Dlo"!0SP!!1pl"!eRU!!
A new Request for Comments is now available in online RFC libraries.
RFC 3143
Title: Known HTTP Proxy/Caching Problems
Author(s): I. Cooper, J. Dilley
Status: Informational
Date: June 2001
Mailbox: [EMAIL PROTECTED], [EMAIL PROTECTED]
Pages: 32
Characters: 57117
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-cooper-wrec-known-prob-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3143.txt
This document catalogs a number of known problems with World Wide Web
(WWW) (caching) proxies and cache servers. The goal of the document
is to provide a discussion of the problems and proposed workarounds,
and ultimately to improve conditions by illustrating problems. The
construction of this document is a joint effort of the Web caching
community.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
- ----- End Included Message -----
- ----------
X-Sun-Data-Type: Multipart
X-Sun-Content-Length: 490
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 22
- --OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="[EMAIL PROTECTED]"
Content-Type: text/plain
Content-ID: <[EMAIL PROTECTED]>
RETRIEVE: rfc
DOC-ID: rfc3143
- --OtherAccess
Content-Type: Message/External-body;
name="rfc3143.txt";
site="ftp.isi.edu";
access-type="anon-ftp";
directory="in-notes"
Content-Type: text/plain
Content-ID: <[EMAIL PROTECTED]>
- --OtherAccess--
- --NextPart--
------- End of Forwarded Message
