Bill Shupp wrote:
>
> Uh, we're talking about 2 different things.. When I said it does a reverse
> lookup on the ip that the request came IN on, that'w what I mean. NOT the
> ip of the end user who's checking their mail.
>
> The ONLY reason for ip-based mail domains is so that users do not have to
> login with <user@domain>, just <user>.
>
> Example:
> test.com resolves to ip 192.168.1.1
> test1.com resolves to ip 192.168.1.2
> test3.com resolves toip 192.168.1.3
>
> and likewise:
> 1.1.168.192.in-addr.arpa resolves to test.com
> 2.1.168.192.in-addr.arpa resolves to test1.com
> 3.1.168.192.in-addr.arpa resolves to test2.com
>
> When [EMAIL PROTECTED] checks his mail simply with user "billybob", vchkpw
> knows the request came in on 192.168.1.1, so it does a reverse lookup on
> 192.168.1.1 and sees that the domain is test.com. It then checks the
> password for [EMAIL PROTECTED] If the request came in on 192.168.1.2, it
> would have looked up [EMAIL PROTECTED]
>
> This way, you can have a [EMAIL PROTECTED], [EMAIL PROTECTED], etc, and the
> users don't have to put their whole email address as their login.
>
> Roaming users is a completely different concept.
>
> Hope this helps.
Yes it does, thanks. The error message it kept putting in my log file
was confusing. That is how I thought it would work. It was the only
logical way I could think of. I will have to put reverses in that say
the domain instead of the fqdn. Right now my mail server will reverse
to atlas.teoi.net . I will try that and see if vpopmail works then.
Thanks,
--
Dale Miracle
System Administrator
Teoi Virtual Web Hosting
