OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Ben Rosengart (brpanix.com)
Date: Wed Dec 19 2001 - 14:12:05 CST

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

    On Wed, Dec 19, 2001 at 10:06:24PM +0200, David Behr wrote:
    > Hi
    >
    > Yes, it does make sense thanks! However, I already have
    > check_recipient_access towards the end of my restrictions - I use it to
    > bypass RBL checks. In this case I will have to move it above
    > reject_unknown_recipient_domain - which is ok, I just have to watch the RHS
    > to ensure I don't become an open relay for domains in that file that have OK
    > in the RHS.

    You can have more than one check_recipient_access restriction in a
    restriction list. Just point them at different maps.

    Oh, I see you already thought of that. Yes, the scenario you
    outline below works.
     
    > One more thing - do you know if you can have multiple check_recipient_access
    > lines for a single restriction (rather than multiple files). Something like:
    >
    > restrict1
    > check_recipient_access maptype:/etc/postfix/foomap
    > reject_unknown_recipient_domain
    > restrict3
    > check_recipient_access maptype:/etc/postfix/RBL_exceptions
    > restrict4
    >
    > If that was possible then foomap could handle the reject case for foo.com
    > that disappeared and RBL_exceptions could handle the rest.
    >
    > Regards
    >
    > David
    >
    > > -----Original Message-----
    > > From: owner-postfix-userspostfix.org
    > > [mailto:owner-postfix-userspostfix.org]On Behalf Of Ben Rosengart
    > > Sent: Wednesday, December 19, 2001 9:59 PM
    > > To: David Behr
    > > Cc: postfix-userspostfix.org
    > > Subject: Re: relocated_maps before smtpd_recipient_restrictions
    > >
    > >
    > > Let's say your restrictions are
    > >
    > > restrict1
    > > reject_unknown_recipient_domain
    > > restrict3
    > > restrict4
    > >
    > > You can make a map, call it foomap, which looks like this:
    > >
    > > foo.com restrict3,restrict4
    > >
    > > Then add
    > >
    > > check_recipient_access maptype:/etc/postfix/foomap
    > >
    > > between restrict1 and reject_unknown_recipient_domain. The effect
    > > of this is to short-circuit the reject_unknown_recipient_domain
    > > restriction, only in the case of mails addressed to foo.com. Does
    > > that make sense to you?
    > >
    > > On Wed, Dec 19, 2001 at 09:49:02PM +0200, David Behr wrote:
    > > > Hi
    > > >
    > > > I have a domain foo.com that has disappeared from the Internet.
    > > I want to
    > > > tell my users that they have gone. So I have put a message in
    > > relocated and
    > > > added this in main.cf:
    > > >
    > > > relocated_maps = hash:/etc/postfix/relocated
    > > >
    > > > relocated is:
    > > > foo.com This domain has disappeared!
    > > >
    > > > Problem is that in smtpd_recipient_restrictions I have
    > > > reject_unknown_recipient_domain and this seems to kick in before
    > > > relocated_maps.
    > > >
    > > > Anyway to change this or am I doing this wrong?
    > > >
    > > > Regards
    > > >
    > > > David
    > > >
    > > >
    > > >
    > > > -
    > > > To unsubscribe, send mail to majordomopostfix.org with content
    > > > (not subject): unsubscribe postfix-users
    > >
    > > --
    > > Ben Rosengart (212) 741-4400 x215
    > >
    > > EOF
    > > -
    > > To unsubscribe, send mail to majordomopostfix.org with content
    > > (not subject): unsubscribe postfix-users
    > >
    >

    -- 
    Ben Rosengart     (212) 741-4400 x215
    

    EOF - To unsubscribe, send mail to majordomopostfix.org with content (not subject): unsubscribe postfix-users