Bruce, thanks for the reply. Unfortunately, that does not really help.
We have always required all of our hosted domains to alias their postmaster and abuse addresses directly to us (we set it up initially and require them to keep that configuration). This worked fine up until the 8/13 release (14.2.5703) when "Changed: Messages sent over SMTP to postmaster@[domain] will now deliver to the primary domain admin and the global postmaster address if a postmaster account has not been created for the target domain."
I discovered this last night when I added a new domain and tested the alias. Before, this worked great. Now, SM always delivers mail addressed to postmaster@domain to the primary domain admin. It never sends it to the server postmaster mailbox nor does it send to the alias postmaster address we created under the domain. I deleted the alias and sent another test and get the same results. I tried from an outside mail account to see if this was just an internal mail issue but got the same result. I tried another (existing) domain and got the same results. Finally, I created a postmaster mailbox under the account and it successfully intercepts the postmaster@domain mail. However, forwarding of that mail to the server postmaster mailbox failed.
The bottom line -- the server postmaster mailbox does not get a copy of the message and creating an alias also does not work. Creating a postmaster mailbox works but forwarding does not.
In the end, we do not necessarily want the domain admin getting ANY postmaster messages and would prefer this was a configuration option that could be overridden by a specific alias being created to distribute the postmaster email. I also do not like the idea of having to create either a primary domain admin or postmaster mailbox to intercept these messages.
At this moment, we are blind to any incoming postmaster email on all of our hosted domains.