Re: Misunderstanding of transport map format VS master.cf

2 msg	postfix + gmail + multiusers
2 msg	strange question regarding lmtp
3 msg	Updated amavisd-new; can't send/receive mail
8 msg	RPM 'n stuff
7 msg	DSN setup
4 msg	Local Users on Virtual Domains?
5 msg	postfix + courier + active directory 2003
12 msg	Fail to test postfix
2 msg	Global groups
7 msg	About creating database

Misunderstanding of transport map format VS mas...
\ Jeremie Le Hen (14 Jun 2007)
. \ Ralf Hildebrandt (14 Jun 2007)
. \ mouss (14 Jun 2007)

2 msg	Problems Backscatter
5 msg	question about receive_override_options
4 msg	specific whitelisting
3 msg	Real unknown host ???
2 msg	Another question about logs...
4 msg	fallback_relay not getting used
3 msg	Maildir
6 msg	Outgoing Mail Copy
1 msg	Close to getting SASL and SMTP AUTH on OS X wor...

Subject:	Re: Misunderstanding of transport map format VS master.cf
Group:	Postfix-users
From:	mouss
Date:	14 Jun 2007

Jeremie Le Hen wrote:
> Hi,
>
> I'm reading the chapter 11 "How External Content Filters Work" of
> Ralf Hildebrandt and Patrick Koetter's Postfix book.
>
> In main.cf, the book tells to use ``content_filter'' like this:
> % content_filter = foo:[127.0.0.1]:54321
>
> Later on the "foo" transport is defined in master.cf:
> % foo unix - - n - 2 smtp
> ^^^^
> % -o smtp_data_done_timeout=1200s
> % -o disable_dns_lookups=yes
> % ...
>
> As far as I understand master(5) manual page, the service "foo" is
> defined to listen on a UNIX socket but main.cf gives an inet address.
>
> What am I missing here?
>

foo is the transport that will talk to the content filter. It is not the
content filter.