Re: [exim-dev] [PATCH] Rudimentary XFORWARD-support in smtpt…

Top Page
Delete this message
Reply to this message
Author: David Woodhouse
Date:  
To: Kai Risku
CC: exim-dev
Subject: Re: [exim-dev] [PATCH] Rudimentary XFORWARD-support in smtptransport
On Thu, 2006-05-18 at 12:39 +0300, Kai Risku wrote:
> While trying to the p0f passive OS fingerprinting integration to work
> in amavisd-new 2.4.1, I realized it depended on the Postfix XFORWARD
> feature (see http://www.postfix.org/XFORWARD_README.html).


    XFORWARD NAME=spike.porcupine.org ADDR=168.100.189.2
    PROTO=ESMTP 
    250 Ok
    XFORWARD HELO=spike.porcupine.org
    250 Ok


How strange. Normally this information would just be put into a
Received: header.

Reading the HOWTO, where it speaks about "Internet->MTA1->filter->MTA2
style content filter applications", it sounds like this is just a hack
to work around the kind of problem we had with older versions of Exim --
that a message would need to pass through Exim _twice_, because the
first would pass it to an external filter, which then passed it back
into Exim for actual delivery.

That problem is fixed in Exim -- I don't really see much need for
anything like XFORWARD.

What exactly does amavisd use this for? It sounds like there should be a
better answer.

--
dwmw2