> According to RFC822 :
> " message = fields *(CRLF *text) ;Everything after first null line is
message body "
RFC 822 (obsolete; see RFC 2822) governs message content, which is a client
issue. RFC 2821 governs message transport, and mandates James' behavior.
RFC 2821, section 2.4:
a relay SMTP SHOULD assume that the message content it has
received is valid and, assuming that the envelope permits
doing so, relay it without inspecting that content.
RFC 2821, section 3.7:
As discussed in section 2.4.1, a relay SMTP has no need to inspect or
act upon the headers or body of the message data and MUST NOT do so
except to add its own "Received:" header (section 4.4) and,
optionally, to attempt to detect looping in the mail system (see
section 6.2).
RFC 2821, section 4.5.3.1:
The general principle that relaying SMTP servers MUST NOT,
and delivery SMTP servers SHOULD NOT, perform validation
tests on message headers
The fact that you have provided an invalid message according to RFC 2822 is
not the concern of the mail transport governed by RFC 2821.
--- Noel
-----Original Message-----
From: Rumen Burrov [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2003 6:15
To: [EMAIL PROTECTED]
Subject: Bug report
Hi,
i like JAMES very much, so I decided to report you a bug:
SMTP command DATA doesnt work fine:
I have downloaded james-2.1.3 MailetSDK, started JAMES (on Java 2 Runtime
Environment , SE v1.4.1_02 ), made some mailboxes and sent the following
message:
220 rumen SMTP Server (JAMES SMTP Server 2.1.3) ready Mon, 4 Aug 2003
12:40:00 +
0300 (EEST)
mail from:<me>
250 Sender <[EMAIL PROTECTED]> OK
rcpt to:<t>
250 Recipient <[EMAIL PROTECTED]> OK
data
354 Ok Send data ending with <CRLF>.<CRLF>
msgbody.
250 Message received
these commands generate the following email (well, the date/time doesn't
match ;)
Return-Path: <[EMAIL PROTECTED]>
Received: from localhost ([127.0.0.1])
by rumen (JAMES SMTP Server 2.1.3) with SMTP ID 716
for <[EMAIL PROTECTED]>;
Mon, 4 Aug 2003 12:37:26 +0300 (EEST)
msgbody.
Date: Mon, 4 Aug 2003 12:37:26 +0300 (EEST)
From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
Message-ID: <[EMAIL PROTECTED]>
Which is not a valid message.
If you save this to a .txt file and rename it to .eml, then try to open it
and you'll see that message has no body.
This is (I think) because according to RFC822 before message body there must
be an empty line (I make no pretence to know RFC822, but I think that empty
line is the problem).
According to RFC822 :
" message = fields *(CRLF *text) ;Everything after first null line is
message body "
http://www.freesoft.org/CIE/RFC/index.htm
http://www.freesoft.org/CIE/RFC/822/index.htm
Hope I help
Rumen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
