Mark Brennand wrote:
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??"
Hi Mark,
we finally reproduced it. And yes, this is a real problem.
We'll fix this for 2.3.0b4.
Thank you for the reports!
You can track the progress here:
http://issues.apache.org/jira/browse/JAMES-570
Stefano
-----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??
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
