You should probably implement it on your SMTP gateway.
An SMTP reject is infinitely more preferable than accepting the mail then generating a bounce.
But to do it on Mercury:
A domain mailbox, by definition, accepts all mail to *@domain.
You could use a filter rule to check the recipients and perform the desired action.
Maybe checking against a mailing list member file (can't recall if this test can be used for recipients as well as senders...) or individually in the filter.
This WON'T catch bcc's though, as only the mail body is available to filters, not the SMTP envelope addresses (unless your spam appliance writes the actual delivery address into the message).
You are also opening yourself to being a backscatter source.
<p>You should probably implement it on your SMTP gateway.</p><p>An SMTP reject is infinitely more preferable than accepting the mail then generating a bounce.</p><p>&nbsp;</p><p>But to do it on Mercury:</p><p>A domain mailbox, by definition, accepts all mail to *@domain.</p><p>You could use a filter rule to check the recipients and perform the desired action.</p><p>Maybe checking against a mailing list member file (can't recall if this test can be used for recipients as well as senders...) or individually in the filter.</p><p>This WON'T catch&nbsp; bcc's though, as only the mail body is available to filters, not the SMTP envelope addresses (unless your spam appliance writes the actual delivery address into the message).</p><p>You are also opening yourself to being a backscatter source.
</p>