From: Dominique Blas (no email)
Date: Thu Jul 01 2004 - 10:41:10 EDT
Le jeudi 1 Juillet 2004 16:10, Magnus Bäck a écrit :
> On Thursday, July 01, 2004 at 16:04 CEST,
> Dominique Blas <> wrote:
>
> > On a relay I'm using relay_recipients_maps.
> >
> > It works but my problem is that this map is checked AFTER the
> > smtpd_recipients_restrictions.
> >
> > Is there a easy way (without going through policies) to force the
> > relay_recipients_maps to be checked somewhere in the
> > smtpd_recipients_restrictions ?
> > A kind ot check_recipient_access that would work the opposite way
> > (line not present => REJECT).
>
> Postfix 2.0: check_recipient_maps
> Postfix 2.1: reject_unlisted_recipient
>
> It's one of those restrictions that otherwise is evaluated at the end of
> smtpd_recipient_restrictions.
Oups, I forgot this one.
Sorry.
I'm using it with local_recipients_map but forgot that I could use it with relay_recipients_map.
BTW, it helps me to understand something for which I was going to ask about.
As it is written in the documentation
smtpd_reject_unlisted_recipient is, by default, true.
Howverer, yesterday, I was compelled to add reject_unlisted_recipient in the smtpd_reciîents_restricitions
to, effectively, see the unlisted ** local ** recipients to be rejected. But to be rejected AS SOON AS the RCPT TO arrives.
And now, through this exchange of mail I understand that, of course, smtpd_reject_unlisted_recipient is true by default but this means that
WITHOUT reject_unlisted_recipient flag the unlisted_recipient will be rejected AFTER the RCPT TO process.
OK, ok, it's logical.
Thank you very much,
db
>
|
|
|