> On May 4, 2018, at 1:04 AM, Phil Ingram wrote:
>
> 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
> 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.
> On May 3, 2018, at 11:13 PM, Phil Ingram wrote:
>
> 1. Cron email from things we don't care about and while these are mostly set
> as &>/dev/null anyway, but we need to ensure that we have a catch all for the
> 'just in case' scenario where someone makes a furfy (i.e. >&/dev/null).
> 2. Cro
There are a few different types of mail we deal with:
1. Cron email from things we don't care about and while these are mostly
set as &>/dev/null anyway, but we need to ensure that we have a catch all
for the 'just in case' scenario where someone makes a furfy (i.e.
>&/dev/null).
2. Cron email fro
> On May 3, 2018, at 8:37 PM, Phil Ingram wrote:
>
> We are using postfix as a central email relay that forwards to an external
> provider for trusted sending to our customers. Centralising this relay is a
> must to limit the distribution of sasl creds required for sending to our
> external
Hello,
We are using postfix as a central email relay that forwards to an external
provider for trusted sending to our customers. Centralising this relay is a
must to limit the distribution of sasl creds required for sending to our
external provider. We have several products, each with dev, staging
