At 10:05 AM -0600 11/09/2002, Michael wrote: >Put this line in the router table of your secondary server. > ><[EMAIL PROTECTED]> = spamtrap ><[EMAIL PROTECTED]> = spamtrap ><[EMAIL PROTECTED]> = spamtrap > >This will stop the secondary from accepting mail for that account but it >will still accept all the other mail for domain1.com
It's a dictionary attack. The names they might try are unknown. The place to catch it is at the primary server where the account mailbox files are. Would something like <*%Domain.com@unknown> = null work? I've seen others use "@blacklisted". Is "@unknown" valid? ############################################################# 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]>
