OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Selecting a nexthop based on the current nexthop

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Tue Jan 02 2007 - 14:56:02 CST


On Tue, Jan 02, 2007 at 03:51:41PM -0500, Wietse Venema wrote:

> Perhaps a combination of check_recipient_mx_access, with an access
> map of
>
> yahoo.com filter [graveyard]:25
>
> would hack it.

More precisely:

        yahoo.com filter smtp:[graveyard]:25
        # If parent_domain_matches_subdomains omits smtpd_access_maps
        .yahoo.com filter smtp:[graveyard]:25

as what follows "filter" is a transport not a nexthop. This works provided
the mail in question arrives via SMTP rather than local list expansion.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.