From: Magnus Bäck (magnusdsek.lth.se)
Date: Wed Aug 02 2006 - 05:31:38 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wednesday, August 02, 2006 at 12:20 CEST,
     Hement Gopal <Hement.Gopalwits.ac.za> wrote:

> I am using a transport list to route mail for containers that exist on
> downstream mail servers.
>
> Eg :-
>
> clm.pg smtp:nike:25
> clm.ug smtp:nike:25
> ebe.pg smtp:nike:25
> ebe.ug smtp:nike:25
> hse.pg smtp:nike:25
> hse.ug smtp:nike:25

Note that you should probably enclose the hostname in square brackets to
avoid MX lookups.

Also consider using the relay transport instead of smtp to decrease the
risk of having your outbound messages starve your inbound messages.

> where nike is the mail server and clm, etc are containers on the
> server.
>
> I also have other downstream mail servers whose mail domains are the
> same as the server name itself
>
> Eg. userDOMAIN-XYZ should be routed to smtp:DOMAIN-XYZ:25
>
> The number of servers that require these entries is high and I do not
> want to insert individual entries for each of them.

Generate the list. Let the computer do the work for you. I assume you
have the domains listed somewhere in your Postfix configuration anyway,
probably relay_domains.

> Is there a wildcard option in the transport list I can use that will
> satisfy this :-
>
> Eg
>
> *.my.domain smtp:*.my.domain:25
>
> Where the * matches on both sides?

You can use a regexp/pcre map.

/^(.*\.example\.com)$/ smtp:$1

> Postconf -d follows

Why are you posting the "postconf -d" output? That displays the default
parameter values and it's of course completely useless in this context.

--
Magnus Bäck
magnusdsek.lth.se

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]