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.
--
Dale Miracle
System Administrator
Teoi Virtual Web Hosting
