Richard,
> You therefore end up with an initial header being added by Exim which looks
> a bit like this:
> Received: from [190.67.164.205] (helo=estacion03) by
> my-amavis-server.local with smtp (Exim 4.63) (envelope-from
> <[EMAIL PROTECTED]>) id 1JH0Cw-0007yR-1j for
> [EMAIL PROTECTED]; Mon, 21 Jan 2008 17:13:14 +0000
That is acceptable, the IP address is parseable by amavisd
from the above header field.
I wonder why must Exim violate the standard syntax of a trace field,
as clearly prescribed by RFC 2821, section 4.4:
Extended-Domain = Domain /
( Domain FWS "(" TCP-info ")" ) /
( Address-literal FWS "(" TCP-info ")" )
TCP-info = Address-literal / ( Domain FWS Address-literal )
; Information derived by server from TCP connection
; not client EHLO.
Namely, the "[190.67.164.205]" above is a HELO name, not TCP information
(which should follow in parenthesis).
> Excellent! This is even better than my solution. Is this going to be
> included into the 2.6.0 release? If so then I'll wait for the stable
> release and upgrade then.
Yes, it will be in 2.6.0.
You may try it when 2.6.0-rc1 comes out.
Mark
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
