|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: overriding transport_maps in master.cf
From: Nick Russo (nick
cs.uchicago.edu)
Date: Tue Jul 01 2003 - 17:28:43 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ok, I see now that transport_maps are no good if I only have one
Postfix instance. I've nothing against using access maps instead,
so let's see if I have the right idea now.
main.cf:
# This is for pop-before-smtp:
smtpd_recipient_restrictions = permit_mynetworks,
warn_if_reject reject_non_fqdn_recipient,
warn_if_reject check_client_access dbm:/etc/postfix/pop-before-smtp,
warn_if_reject check_relay_domains,
reject
# I should add this to the beginning of the list:
# check_recipient_access hash:/etc/postfix/access
access:
narusso
cs.uchicago.edu FILTER smtp-amavis:[128.135.11.66]:10024
master.cf:
10025 inet n - n - - smtpd
-o local_recipient_maps=
-o smtpd_helo_restrictions=
-o smtpd_client_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8,128.135.11.66
-o myhostname=private.cs.uchicago.edu
smtp-amavis unix - - n - 2 smtp
-o smtp_data_done_timeout=1200
-o disable_dns_lookups=yes
-o fallback_relay=localhost:10025
When the message comes back to port 10025, a different set of recipient
restrictions will be imposed (this is what I couldn't achieve with
transport_maps). Is 'permit_mynetworks,reject' a reasonable choice there?
Is anything else wrong in my configuration as listed above?
Thanks again,
Nick
****************************************************************
Nick Russo email: nick
cs.uchicago.edu phone: 773.702.3438
Computer Science Department The University of Chicago
Associate Director of Computing Systems, Systems Lead
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]