As a sidenote, it seems that "Microsoft SMTPSCV" is not rfc compliant
either, because it have to override the Return-Path using the address
used in "MAIL FROM" in the protocol.
I was not able to reproduce this issue because most email servers (at
least sendmail and postfix) correctly replace the "wrong" header added
by james with the correct one (as the rfc specify).
Stefano
Mark Brennand wrote:
Here is a header to one of my external mail accounts (work) from one of my
JAMES accounts where the null value is showing up:
--8<--
Microsoft Mail Internet Headers Version 2.0
Received: from mail.ten62.com ([65.99.215.49]) by {omitted} with Microsoft
SMTPSVC(6.0.3790.211);
Tue, 18 Jul 2006 06:35:30 +1000
Return-Path: null
Received: from {omitted} ([{omitted}])
by mail.ten62.com (JAMES SMTP Server 2.3.0b3) with SMTP ID 996
for <[EMAIL PROTECTED]>;
Tue, 18 Jul 2006 06:35:23 +1000 (EST)
Reply-To: <[EMAIL PROTECTED]>
From: "Mark Brennand" <[EMAIL PROTECTED]>
To: "Mark Brennand" <[EMAIL PROTECTED]>
Subject: Meeting on Wednesday
Date: Tue, 18 Jul 2006 06:35:18 +1000
Organization: TEN62
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0026_01C6AA34.581EC270"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcapVIGkr4v/thNuT56QqfM2BVg8rQ==
X-MessageIsInfected: false
X-OriginalArrivalTime: 17 Jul 2006 20:35:30.0444 (UTC)
FILETIME=[8B7A14C0:01C6A9E0] {boundary stuff omitted}
--8<--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
