> This is not actionable information. I think I misinterpreted your original request. Mail that needs to go to the external provider originates from any number of hosts/servers on a number of different networks. Email sent from these servers originates from cron, other daemons and our application. So, to the central relay the sending hosts and the email they receive looks no different, but the To:, From: and Received: info in each email does.
(application/cron/daemon) -> server's local postfix -> central relay's postfix -> external provider -> mail.google -> end user In the case of a UAT environment, to get the most consistent view of any changes made, server configuration, application configuration and data must be 1:1 with production. So, having a different configuration of each server's local postfix breaks this, which is why we would prefer to redirect application email from the UAT env before it leaves our network. > You need to provide more detail, such > as e.g. someone would need to attempt to route each type of traffic to the > right place. > I'm sorry, I don't follow. > > Also, though you might prefer to take care of everything on the mailhub, > if the trasition from the hosts to the mailhub loses critical differences > as to the type of mail being handled We don't care, all email is unclassified, we are tolerant of failures and completely control the private network. We would simply like to control the routing and redirection of email based on the source network and destination email address
