At 10:49 AM -0500 11/09/2002, The Count of CipherSpace wrote: >Warren Michelsen at 2002-11-07 15:05 from [EMAIL PROTECTED] wrote: > >>A spammer is hitting my backup mail server with lots of junk for >>non-existent addresses. When the primary tells the secondary that there is >>no such account, the original mail ends up in the queue -- along with the >>bounced bounce message. >> >>My current router entries are of the type" > ><*@domain1,com> = dom1-* >> >>What can I add to the router to catch the [EMAIL PROTECTED] type email and >>route it to null? > >On the backup mail server, exactly nothing - it has no way of knowing >what are valid addresses and which aren't -
There's obviously nothing I can put on the secondary server to stop this. The router entry above is on the main mail server. I was hoping for a router entry on the PRIMARY server, following the rule that catches the real addresses and routes them to local accounts: <*@domain1,com> = dom1-* Without using the "unknown" account, is there any way to catch all the bogus addressees on the primary server and not bounce them back to the backup mail server? ############################################################# 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]>
