Here's how I do it: <*@domain2.tld>=domain2-* <*@domain3.tld>=domain3-*
If an e-mail is incorrectly addressed, SIMS now properly reports "No such account" rather than a relay attempt. Having something "guess" which account was intended is probably not a real good idea unless an account is very commonly misspelled; in that case, set up another account with the common misspelling set to discard mail after forwarding it to the proper account. Don't try to use the router for this function. At 10:13 AM -0400 4/12/02, Paul Galati wrote: >Let's say I am serving 3 domains on one SIMS server: >Domain-1 >Domain-2 >Domain-3 > >Primary Domain in General tab is Domain-1 > >Local accounts >Domain2-UserName1 >Domain2-UserName2 >Domain3-UserName1 etc > >Router Entry ><UserName1@Domain2> = Domain2-UserName1 ><UserName2@Domain2> = Domain2-UserName2 ><UserName1@Domain3> = Domain3-UserName1 > >If someone sends an email incorrect addressed, UseName1@Domain2, my server >currently says that the incorrect email is actually an attempt to relay, which >is forbidden. Is this normal behavior? > >What can be done to have the correct response message, user unknown, be sent >or better yet, a wildcard to have the router make an educated guess to which >account the sender intended for. ############################################################# 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]>
