|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Separate filtering for incoming (mx) and outgoing mail
From: Magnus Bäck (magnus
dsek.lth.se)
Date: Wed Mar 02 2005 - 06:32:26 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, March 2, 2005 10:24 am, Birger Brunswiek said:
> Magnus Bäck wrote:
>
> > Example (obviously substitute mumble and the exact filter
> > configuration):
> >
> > smtpd_recipient_restrictions > permit_mynetworks,
> > permit_sasl_authenticated,
> > check_mumble_access static:FILTER:[localhost]:10025,
> > reject_unauth_destination,
> > ...
>
> Replace numble with what?
client, helo, sender, recipient, ... Whatever you want. That's the point
of using the static: type.
> All the check_XXX_access options I have found
> take a access(5) table as parameter but yours definitely is a transport(5)
> one.
No, FILTER as a valid access table action. See access(5). The static: map
type is a special case that always matches.
--
Magnus Bäck
magnusdsek.lth.se
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]