Return-Path header value set to null using JAMES 2.3.0b3

[Mark Brennand <ma...@ten62.com>]

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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

Re: Return-Path header value set to null using JAMES 2.3.0b3

[Stefano Bagnara <ap...@bago.org>]

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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org