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

Página Inicial
Delete this message
Reply to this message
Autor: Matthias Waffenschmidt
Data:  
Para: David Woodhouse
CC: exim-dev, Kai Risku
Assunto: Re: [exim-dev] [PATCH] Rudimentary XFORWARD-support in smtp transport
Hello,

On Thu, May 18, 2006 at 12:29:34PM +0100, David Woodhouse wrote:
> 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.


You could for example deny at recipient time (recipients selectively)
instead of having only one deny/accept option after data.

But the most important point IMO is if callouts would send this
information via XFORWARD, because there currently is no way of
transfer such kind of data to MTA2 (as there is no data transferred).

-- 
Gruss / Best regards   |  LF.net GmbH        |  fon +49 711 90074-411
Matthias Waffenschmidt |  Ruppmannstr. 27    |  fax +49 711 90074-33
mw@???              |  D-70565 Stuttgart  |  http://www.lf.net