Mark,
On Thu, 17 Jan 2008 21:22:46 +0100, Mark Martinec
<[EMAIL PROTECTED]> wrote:
> Does the message when it reaches amavisd already contain a Received
> header field inserted by your Exim? If so, it can be used in place
> of your X-My-ClientAddr, and provides a standards-based solution.
Yes
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 PROTECTE
Richard,
> ...but I've modified the amavisd binary to find a
> client ip address in a header added by the MTA. I'm sure I'm not the only
> person with a requirement for this feature so I'll document what I did:
> < 'UPDATE msgs SET content=?, quar_type=?, quar_loc=?, dsn_sent=?,'.
> >
All,
I've had another chance to look into this after a few months. I'm not a
Perl whizz by any means but I've modified the amavisd binary to find a
client ip address in a header added by the MTA. I'm sure I'm not the only
person with a requirement for this feature so I'll document what I did:
Richard,
> I noticed today that there is a client_addr field in the r/w database that
> stores the source server's IP address. On my setup (Exim4 -> Amavisd-new -
> -> Exim4) this is always populated with NULL.
Besides what Noel said, the answer may depend on what is
the purpose for which you n
At 10:48 AM 8/20/2007, Richard Bishop wrote:
>Hello all,
>
>I noticed today that there is a client_addr field in the r/w
>database that stores the source server's IP address. On my setup
>(Exim4 -> Amavisd-new -> Exim4) this is always populated with NULL.
>
>Having checked the mailing list I se
Hello all,
I noticed today that there is a client_addr field in the r/w database that
stores the source server's IP address. On my setup (Exim4 -> Amavisd-new ->
Exim4) this is always populated with NULL.
Having checked the mailing list I see that this is reliant upon the XFORWARD
feature of
