> While hosting mail for several domains, a local user > with an account name of say "biz" has a domain of say "domain.com" > would receive mail from other domains hosted at the same site > such as "[EMAIL PROTECTED]". > > What I am looking for is a general setup criteria that would eliminate this > behavior so that [EMAIL PROTECTED] would be rejected even though > otherdomain.com is hosted on the same server but has no username of biz.
I use the virtusertable (sendmail) for this. There are several things that I have done. You can use the *strange* method, which works very well, and allows for greater expandibility and management when dealing with thousands of users, or use the straight up approach and ensure that there is a catchall for the domain after it's last valid user, so [EMAIL PROTECTED] will not be sent to the improper user: [EMAIL PROTECTED] companya01 [EMAIL PROTECTED] companya02 [EMAIL PROTECTED] companya03 @companya.com company04 [EMAIL PROTECTED] companyb01 [EMAIL PROTECTED] companyb02 @companyb.com /dev/null or [EMAIL PROTECTED] tammy [EMAIL PROTECTED] david @this.com /dev/null [EMAIL PROTECTED] biz [EMAIL PROTECTED] help @that.com biz Both of these situations force the username to be inside of it's own domain to accept mail. With both setups above, you can be assured that biz will only receive email if it is sent to the domain his virtuser entry resides in. Note that the second approach is the exact same, but using the actual named account. This will quickly become a nightmare (and a large mess) if you get up around the thousand user mark. Steve > > One thing I thought of would be to use strange local usernames and > then create virtual users that point to them. > > can anyone give me a suggestion on standard practice with this? > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message