At 5:32 AM -0400 9/3/2003, Joe D'Andrea wrote:
>OK... for as long as I can remember we always configured our domains with primary and
>secondary MX servers. Then we got hit with spammers sending mail to our secondary and
>eventually our secondary became useless. The reason it became useless was because the
>primary, recognizing a large amount of non-deliverable mail (non-existant accounts
>that the secondary accepted) coming from the secondary would actually block the IP of
>the secondary for some period of time. If I could put the secondary in some whitelist
>somewhere that should eliminate its IP from being blocked. But do I really want all
>that mail being accepted by the secondary only to be discarded by the primary? What's
>the solution for this situation?
This solution may not be practical for domains with large numbers of accounts, but it
works very well, providing the backup server is also SIMS or can route accounts
individually. See below.
On the backup server, instead or routing:
domain1.com = domain1.com.smtp
use
[EMAIL PROTECTED] = [EMAIL PROTECTED]
[EMAIL PROTECTED] = [EMAIL PROTECTED]
[EMAIL PROTECTED] = [EMAIL PROTECTED]
[EMAIL PROTECTED] = [EMAIL PROTECTED]
etc.
Do this for each account on the primary server.
Repeat for each domain.
Also replicate each spamtrap address from the primary onto the secondary.
The secondary will not accept mail for any account that the primary won't accept. Your
queue will not fill up with unaccepted mail and bounces to bogus addresses.
It works very well.
--
Warren Michelsen <[EMAIL PROTECTED]>
Online Tools For Business -- <http://www.OTFB.com/>
Small Business & E-commerce web hosting
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
