Turn Off Postmaster Notifications

From MsgServerDocWiki

Is it possible to turn off postmaster notifications from failures of emails sent from specific domains?

The MTA's main controls for whether a postmaster is copied on the notifications it generates are the various *sendpost and *warnpost channel options. However, these controls operate on a channel basis; they do not provide the fine grained control necessary to control postmaster notifications on a per-domain basis.

Postmaster copies of returned messages are sent to the domain postmaster address if one is set for the domain. This address can be set to anything - it isn't limited to addresses within the domain. So the obvious way to do this is to set a domain postmaster to an address that sends the mail to the 'bitbucket.'

This trick only works for local domains, however. You cannot have domain entries for domains you don't have authority over. It isn't clear if you're talking about controlling this for local domains or not, but I suspect you're not, and if so there's not going to be a domain entry where you can set an appropriate 'bitbucket' address for the domain postmaster.

You have full control of the postmaster address associated with each domain and each channel, so one possiblity would be to use a bitbucketed postmaster address as the default and depend on domain postmaster addresses being used when they are needed. Trouble is, postmaster addresses are used for lots of things besides where copies of nondelivery notifications are sent and I'm pretty sure you won't be able to insure that domain-level postmasters are used in all the cases where they need to be for this to work.

Messaging Server 6.3 has a new feature whereby a FROM_ACCESS mapping can set the overriding postmaster address the same way the postmaster entry in a domain can set it, but of course the FROM_ACCESS mechanism will work with addresses in any domain. So this will solve your problem, but you'll have to be using Messaging Server 6.3

If you haven't installed/upgraded to Messaging Server 6.3, disable postmaster copies of these bounce messages completely. Do not switch all mail from a particular domain to its own channel and set the "nosendpost" on that. Unfortunately such a setup effectively requires that you build duplicates of all your destination channels and also have duplicates of all your rewrites (with lots of additional source channel checks). Such a setup is effectively unmaintainable.