On Mon, 9 Sep 2002 19:50:10 -0400, Neil Herber <[EMAIL PROTECTED]> is alleged to have written: > > (snip)
>In much the same way with SIMS you need to do domain level routing to >point an account in a particular domain to a uniquely named local >account. The best way to do this is to establish a prefix or suffix >"rule" for the account names. > >Example email addresses: >[EMAIL PROTECTED] >[EMAIL PROTECTED] > >Example SIMS accounts: >fred-1 >fred-2 > >Example router entries (foreign aliasing): ><*@firstdom.com> = *-1 ><*@seconddom.com> = *-2 > >This will accomplish what you want to do. Your clients need to POP >from the account fred-1 or fred-2, but they can set their Reply-To >addresses to [EMAIL PROTECTED] and [EMAIL PROTECTED] respectively. > >Using a suffix or prefix rule makes account maintenance easy. You >could assign any arbitrary but unique string to each account - but >then you would need a routing entry for every one. You could also use >a longer, more meaningful string for the suffix. You could also present this as a security feature to your users. If your account name is different from your email address, it is less likely that somebody could get into your account, because in addition to guessing your password they would also have to guess your username. I like to use prefixes instead of suffixes, because with prefixes, all the users from a given domain are all grouped together in the list of users in SIMS. --Lyle ############################################################# 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]>
