Warren Michelsen at 2002-11-10 01:11 from [EMAIL PROTECTED] wrote: >There's obviously nothing I can put on the secondary server to stop this.
Oh, okay - sorry for misunderstanding. >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? The only way would be to have an entry for ALL accounts, then route non-existing ones to a particular mailbox; something like: <[EMAIL PROTECTED]> = dom1-ac1 <[EMAIL PROTECTED]> = dom1-ac2 ... <[EMAIL PROTECTED]> = dom1-acN <*@domain1.com> = dom1-NoCigar this would be manageable if you don't have too many accounts in domain1; and, if you remember to add an entry above the last one, every time you add another account. ############################################################# 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]>
