wiskbroomhotmail.com
Date: Wed Oct 01 2008 - 10:31:32 CDT

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

Many thanks for the help mouss, and my apologies for my hiatus...

As per my email, I am using NIS and DBM aliases foor all of my users and aliases for them.

What I must do is forward *ALL* email for say example.net to a Microsoft Exchange server, this forward to happen blindly and I do not wish to manage alias tables for users on the PF relay. I do however wish to process the email for spam and AV in the same way that I would for my regular accounts.

Man thanks in advance,

.vp

> Date: Wed, 30 Jul 2008 00:44:00 +0200
> From: moussnetoyen.net
> CC: postfix-userspostfix.org
> Subject: Re: Aliases Lookups, not found? Then Smarthost
>
> wiskbroomhotmail.com wrote:
> > Hello All;
> >
> > I currently have the following setup in my main.cf:
> >
> > alias_maps = dbm:/etc/postfix/aliases, nis:mail.aliases
> >
> > I've also enabled myself to receive email for about 15 domains.
> >
> > Everything works just fine, but because of some new domains I am now charged with maintaining, I am now faced with how I am going to synchronize these new domains users into my aliases, preferably in a way that would require very little effort on my part.
> >
> > What I am looking for is a way to forward all email for say domain XXX.COM to host server-1, if a users account is not found locally in either my aliases dbm or my NIS maps, ditto for domain ZZZ.com to smtp host server-2. Some of the users for XXX.COM might be residing at my domain/environment, therefore I need to first lookup locally before forwarding. Finally, the next stop on this forwarding would be Microsoft AD/bridgehead servers, just in case that matters.
> >
>
>
> use a shared map that contains all users and for each user contains the
> host where email should go. you can either use virtual_alias_maps:
>
> fooexample.com foohost10.example.com
>
> if the final host doesn't like the rewritten address, you can use
> smtp_generic_maps to rewrite it back (this happens after transports, so
> doesn't break the virtual alias functionality).
>
> or you can use transports:
>
> fooexample.com relay:[host10]
>
> if you use transports, you need to pre-process the file to remove the
> transport on the host itself (where the transport is obviously local:
> and not relay:[host10]).
>

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