Thank you to J Daniel Smith for making me read the RFC 2046 at this time
in the morning :-)
I was missing a Mime-Version header.
Q. You'll notice that my message includes a preamble. Which from reading
hte SPEC is at the descretion of the MUA whether it's displayed or not?
I assume it's only displayed when using a non MIME MUA.
Is the following a correct interpreation of the message?
Date: Thu, 8 May 1997 06:07:01 -0400
From: Robert Nicholson <steffi2(_at_)dgsys(_dot_)com>
To: steffi(_at_)dgs(_dot_)dgsys(_dot_)com
Subject: Re: testing [rejected]
Parts/attachments:
1 Shown 15 lines Text
2 Shown 9 bytes Message
2.1 Shown 0 lines Text
Note the nine bytes for the Message yet when I try to display that
attatchment it shows nothing.
Here's the message which looks prefectly legal to me.
From steffi2 Thu May 8 06:07 EDT 1997
Return-Path: <steffi2>
Received: by dgs.dgsys.com (5.0/SMI-SVR4)
id AA15412; Thu, 8 May 1997 06:07:01 -0400
Date: Thu, 8 May 1997 06:07:01 -0400
From: steffi2 (Robert Nicholson)
Message-Id: <9705081007(_dot_)AA15412(_at_)dgs(_dot_)dgsys(_dot_)com>
To: steffi(_at_)dgs(_dot_)dgsys(_dot_)com
References:
<Pine(_dot_)SOL(_dot_)3(_dot_)94(_dot_)970508060644(_dot_)14533A-100000(_at_)dgs>
In-Reply-To:
<Pine(_dot_)SOL(_dot_)3(_dot_)94(_dot_)970508060644(_dot_)14533A-100000(_at_)dgs>
X-Loop: robert(_at_)elastica(_dot_)com
Subject: Re: testing [rejected]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="-- next item --"
Content-Length: 773
Status: RO
X-Status:
This is the preamble of an RFC-1521 encoded, mixed message.
---- next item --
Content-Type: text/plain
In an effort to combat unsolicited email I've adopted a scheme that allows
only email from approved originators. The sender of a message has to be
approved before I will see their email.
In this case you the originator of this message are not currently
approved.
If you are selling products and have obtained my email address from other
sources then I am not interested.
To be considered for approval please resend your message (attached below)
with
the string 4321 somewhere in the Subject header.
Thank you. I look forward to conversing with you shortly.
Original message follows
---- next item --
Content-Type: message/rfc822
testing
---- next item ----
I'm not doing the -I "From " hack yet.