System setup: Linux Redhat ES3 in a VPS, 160mb dedicated RAM
JAMES 2.3.0b3 was compiled from source directly on this box. I have
commented out my personal matchers and mailets in attempting to correct this
issue.
I use the ClamAV matcher/mailet for virus checking (which is working great
in all eicar test etc). Outbound from local accounts are checked before
sending as well as all inbound. I also check for prohibited extensions on
all inbound and outbound.
I use the SpamAssassin matcher/mailet (which is also not functioning
correctly but that is for another list mail!!) only on inbound, so messages
sent from local accounts at this point, if authenticated via
SMTPAuthSuccessful match, are sent directly to transport.
I am using virtual users via JDBCVirtualUserTable with default sql. Outbound
from local accounts never reach this mailet. Could this be a problem spot??
I noticed that when I use WhiteListManager mailet (working great!!) to
'display' current whitelisted users, the mail comes back from postmaster
with Return-Path: <[EMAIL PROTECTED]> as it supposed to.
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<--
Config.xml:
I have removed all NNTP stuff and in trying to correct this issue of null, I
have commented out most (I think!) of the the 'SetMimeHeader' calls after
reading a list post regarding the mangling of headers. A proverbial stab in
the dark that did not correct the issue. I can make a zipped copy of this
config file available if needed.
The mails I send with this null value in the Return-Path header still get
through to the intended destination (through spam and virus checks) which
begs the question "Is this a real problem??"
Regards MB
- Mark Brennand
- ACTiVEiNGREDiENT -
-----Original Message-----
From: Stefano Bagnara [mailto:[EMAIL PROTECTED]
Sent: Monday, 17 July 2006 11:14 PM
To: James Users List
Subject: Re: Return-Path header value set to null using JAMES 2.3.0b3
I cannot reproduce this.
I just tried sending a message and the header has a good return-path with my
own address. I also tried sending to an unknown address so that James
generate a bounce and the bounce has:
"Return-Path: <>".
This is correct by RFC.
Can you provide more informations about your issue? (Mail you send,
configuration, mail received)
Mark Brennand wrote:
> I am running a test install of JAMES 2.3.0b3, with my main server
> happily running JAMES 2.2.0 for the last 18 months or so. Amongst the
> changes I have noticed on this test install is that the 'Return-Path'
> header value is set to "null" in mail sent from the server. This is not
the case in JAMES 2.2.0.
> Is this considered normal??
>
> Regards MB
> - Mark Brennand
> - ACTiVEiNGREDiENT -
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
