Re: content_filter .vs. transport_maps

2010-02-16 Thread Victor Duchovni 
On Sun, Feb 14, 2010 at 09:25:12PM +0100, Stefan Palme wrote:

 On Sun, 2010-02-14 at 14:21 -0500, Wietse Venema wrote:
  content_filter and FILTER have precedence over all routing mechanisms
  in Postfix including transport_maps, relayhost, address classes, etc.
 
 Ok, but if I have a very simple setup without any per-whatever
 transport_maps, relayhost, etc. it does not really make any
 difference if I use a simple transport_map or the content_filter
 declaration?

Setting:

default_transport = ...
relay_transport = ...

Is cleaner than using * in transport_maps. If you also have local
delivery or virtual mailbox domains:

local_transport = ...
virtual_transport = ...

On filter-and-forward relays, I always have:

local_transport = error:5.1.2 Mailbox unavailable

and no virtual mailbox domains, so just the first two settings are
sufficient, and enable me to use transport_maps for filter exceptions.

-- 
Viktor.

P.S. Morgan Stanley is looking for a New York City based, Senior Unix
system/email administrator to architect and sustain our perimeter email
environment.  If you are interested, please drop me a note.

content_filter .vs. transport_maps

2010-02-14 Thread Stefan Palme 
Hi,

Is the effect of 

  content_filter = smtp:[127.0.0.1]:10025

the same as

  transport_maps = hash:/etc/postfix/transports

/etc/postfix/transports:
  *smtp:[127.0.0.1]:10025

?

Thanks and regards
-stefan-

Re: content_filter .vs. transport_maps

2010-02-14 Thread Wietse Venema 
Stefan Palme:
 On Sun, 2010-02-14 at 14:21 -0500, Wietse Venema wrote:
  content_filter and FILTER have precedence over all routing mechanisms
  in Postfix including transport_maps, relayhost, address classes, etc.
 
 Ok, but if I have a very simple setup without any per-whatever
 transport_maps, relayhost, etc. it does not really make any
 difference if I use a simple transport_map or the content_filter
 declaration?

These mechanisms not only have different names, but they also have
different behaviors.

- The meaning of empty transport or nexthop fields is different,
  and this difference depends on Postfix versions.

- Running postsuper -r will remove the content filter override.

There may be other differences. I suggest that you study the
documentation and determine if those differences matter to you.

Wietse