Also, if all your users are all on a local network (or known ip addresses) you can set up a mercS transaction filter to reject (& blacklist) MAIL FROM local users.
e.g.
M, "*@your.domain*", BS, "554 Fraudulent MAIL FROM"
Just make sure to exempt your local ip's from the transfilter in the SMTP - Connection Control tab
I have a couple of users outside on dynamic ip's so have put exceptions for them BEFORE the reject rule
M, "*dyn.user@your.domain*", X, "MAIL FROM accepted"
This leaves a hole in this method but these particular users don't get hit much and Spamhalter has cleaned up any that did get through like this.
<p>Also, if all your users are all on a local network (or known ip addresses) you can set up a mercS transaction filter to reject (&amp; blacklist) MAIL FROM local users.</p><p>e.g.</p><p>&nbsp;M, "*@your.domain*", BS, "554 Fraudulent MAIL FROM"</p><p>&nbsp;</p><p>Just make sure to exempt your local ip's from the transfilter in the SMTP - Connection Control tab</p><p>I have a couple of users outside on dynamic ip's so have put exceptions for them BEFORE the reject rule</p><p>&nbsp;M, "*dyn.user@your.domain*", X, "MAIL FROM accepted"</p><p>This leaves a hole in this method but these particular users don't get hit much and Spamhalter has cleaned up any that did get through like this.&nbsp;</p><p>
</p>