Wietse Venema пишет:
Mathieu Kretchner:
smtp ----> proxy.foo.com -----> default.foo.com
|
redirect_map ?
--------------> new.foo.com
I'm new to postfix routing mail and I'm a little bit lost ...
So I think it's not a big deal to do but I don't know HOW ?
Postfix routing is controlled by address classes.
http://www.postfix.org/ADDRESS_CLASS_README.html
Wietse
Hello,
Thanks for your reactivity but the recipient field are all addressed to
proxy.foo.com and I've to discriminate by user account to redirect mail.
I find transport table by the link you've given to me and add :
transport_maps = hash:/etc/postfix/transport
to main.cf
and
[EMAIL PROTECTED] :[default.foo.com]
[EMAIL PROTECTED] :[new.foo.com]
to
transport file
The goal is to do a migration of our imap server. We want to attache the
service ip to proxy.foo.com and redirect mail wherever they must go.
Am I wrong with this method ? Do I've to check elsewhere ?
You have half the solution. What you describe is a variant of
Postfix as primary MX for mail that is delivered elsewhere.
Wietse
/etc/postfix/main.cf:
# Do not list proxy.example.com in other address classes.
relay_domains = proxy.example.com
relay_recipient_maps = hash:/etc/postfix/relay_recipients
mydestination = localhost localhost.example.com
smtpd_recipient_restrictions =
permit_mynetworks reject_unauth_destination
I'm setting up a backup MX server. I end up with very similar
configuration, but I have additional questions about this topic:
1) If I leave transport_maps empty, where the mail will go? How to
specify a primary MX host?
2) The documentation has some pointers to the permit_mx_backup
restriction. It is wise to put it right after the
reject_unauth_destination in smtpd_recipient_restrictions?
