Re: Simplistic (but solid??) smtpd_recipient_restrictions

From: p dont think (no email)
Date: Wed May 01 2002 - 03:55:55 EDT


OK, I misunderstood the meaning of "permit_mynetworks" -- reading
sample-smtpd.cf cleared that up -- it's somewhat misleading, if I
understand correctly, in that "permit_mynetworks" here is placing
a limitation on the address of the connecting client and NOT on
the actual contents of RCPT TO, even though we are listing it in
"smtpd_recipient_restrictions".

On a related note, is it correct to structure the listing as
follows in order to enable UCE controls EXCEPT for those users
listed in a client access map (with "OK")? --

smtpd_recipient_restrictions =
        permit_mynetworks
        permit_sasl_authenticated
        check_recipient_access maptype:mapname (list users in the
               map with "OK" who don't want UCE controlled delivery)
<--
    insert appropriate UCE controls here, such as
    reject_maps_rbl, reject_invalid_hostname,
    reject_unauth_pipelining, reject_non_fqdn_hostname, reject_non_fqdn_sender
-->
        reject_unauth_destination
        permit

> > smtpd_sender_restrictions =
> > smtpd_client_restrictions =
> > smtpd_recipient_restrictions = permit_mynetworks,
> > permit_sasl_authenticated,
> > reject
>
> And how can you receive mail?
> smtpd_recipient_restrictions =
> permit_mynetworks
> permit_sasl_authenticated
> reject_unauth_destination
> permit

__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD