Do you run your own Secondary Mail Server? You can have it use the same RBL that you use on your Primary Mail Server. How many accounts do you have on Domain1? You could just act as Secondary for the known accounts.
on 11/10/02 12:18 AM, Warren Michelsen at [EMAIL PROTECTED] wrote: > 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? No I don't think so. The Secondary does not know what is valid and known. > I've seen others use "@blacklisted". Is "@unknown" valid? > No I don't think so. The Secondary does not know what is valid and known. Michael ############################################################# 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]>
