actually 'letting MTA figure out how to get it to the internet' is not a great approach for high volume senders. there are lots of parameters you want to control 'logically' that no MTA out there supports. If you compare the config options of powerMTA and postfix you will see how they differ as a delivery agent. i wish i had time to implement all those features and more on postfix, but after investigating a little bit seemed like a lot of work to me... because of that i usually use a software 'email sending engine' as an independent middleware to those MTAs..
anyways, thanks for the advice.. best, erbiL.. On Mon, Oct 20, 2008 at 3:13 PM, Barney Desmond <[EMAIL PROTECTED]> wrote: > mouss wrote: >> use multiple instances: run postfix 8 times, each with its own config >> dir, queue dir, data dir, ... etc, and configure each for its own >> domain(s). > > > This is something we've run into at work. One customer already uses > PowerMTA, and there's another we'd like to discourage. We figured this > is probably the way to do it, but I'd like to be sure: Would you leave > the "main" instance mostly as-is, and use > sender_dependent_relayhost_maps to pass mail through to the additional > instances? If you have naive/simplistic mailing software, chances are > it's easiest to just pass everything to localhost:25 and let the MTA > figure out how to get it to the internet. > >
