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.
Bill
on 11/5/00 7:19 PM, Dale Miracle at [EMAIL PROTECTED] wrote:
> Bill Shupp wrote:
>>
>> Sounds like you're expecting the pop client to send the equivalent of a
>> "host header" like in HTTP. That doesn't happen. What happens is vchkpw
>> does a reverse lookup for the ip that the request came in on, and that's the
>> domain that it looks up the user in. The most common cause for ip-based
>> vpopail errors is DNS problems.
>>
>> NOTE: reverse the ip to the domain name, not the MX (ie: test.com, not
>> mail.test.com). I believe I had problems with that before, but maybe
>> someone will correct me if I'm mistaken.
>
> If what your saying is correct then only pc's of a specific domain can
> use ip-based login's.
> Wouldn't that break the roaming user option? The idea behind roaming
> users is if a member of a domain goes out side of that domain 'roaming'
> and they want to check their mail they are going to have an ip that
> reverse lookup is going to go to the ISP they are currently using and
> not their own domain. That is what is making absolutely no sense right
> now.
> All of my virtual domains have users that connect using various domains
> (i don't have dialup access to my network).
> Here is an example to explain my point:
>
> A user is on anyisp (msn, aol, prodigy, local isp's, etc ,etc). They
> have a domain that has an ip address of 206.30.147.41 . They are
> dialing up using anyisp and they get an ip address of 209.153.300.1 that
> reverses to anyisp.com 's network. When they go and load their mail
> client to check their mail vpopmail is not going to let them in because
> their pc is going to be coming from 209.153.300.1 which reverses to
> anyisp and 'not' their domain ip of 206.30.147.41 .
> The way I think it should work is the IP address of the machine needing
> to be contacted so be reversed and that domain should be used. I can't
> imagine it work the other way around because it would technically never
> work unless that person was actually in is network ip range.
>
