On Fri, 2001-09-28 at 08:03, David Brady wrote:
> I have been running vpopmail for quites some time now, without problems. I
> am running purely virtual, with several domains, including our own. Upon
> upgrading to 4.9.10, Virtual Domains cease to work. here is what I am
> getting with 4.9.10:
> 
> Sep 27 10:52:53 ns1 vpopmail[5283]: vchkpw: setgid() failed
> Sep 27 10:52:57 ns1 vpopmail[5285]: vchkpw: setgid() failed
> Sep 27 10:52:57 ns1 vpopmail[5287]: vchkpw: setgid() failed
> Sep 27 10:52:57 ns1 vpopmail[5289]: vchkpw: setgid() failed
> Sep 27 10:52:58 ns1 vpopmail[5291]: vchkpw: setgid() failed
> Sep 27 10:52:58 ns1 vpopmail[5293]: vchkpw: setgid() failed
> Sep 27 10:52:58 ns1 vpopmail[5295]: vchkpw: setgid() failed
> Sep 27 10:52:58 ns1 vpopmail[5297]: vchkpw: setgid() failed
> Sep 27 10:52:59 ns1 vpopmail[5299]: vchkpw: setgid() failed
> Sep 27 10:52:59 ns1 vpopmail[5301]: vchkpw: setgid() failed
> Sep 27 10:53:06 ns1 qmail: 1001605986.047129 delivery 29: success:
> 192.89.172.133_accepted_message./Remote_host_said:_250_Ok:_queued_as_4468492
> B68/
> Sep 27 10:53:06 ns1 qmail: 1001605986.047269 status: local 0/10 remote 0/20
> Sep 27 10:53:06 ns1 qmail: 1001605986.047323 end msg 574
> Sep 27 10:53:06 ns1 vpopmail[5312]: vchkpw: No user found
> lindad@:63.82.233.62
> Sep 27 10:53:39 ns1 vpopmail[5580]: vchkpw: No user found
> rodmiller@:63.82.233.54
> Sep 27 10:53:42 ns1 vpopmail[5583]: vchkpw: setgid() failed
> Sep 27 10:54:06 ns1 vpopmail[5585]: vchkpw: setgid() failed
> Sep 27 10:54:16 ns1 vpopmail[5589]: vchkpw: setgid() failed
> 
> Upon installing 5.0pre5, the setgid() errors go away, but virtual domains
> still do not work, as noted by the persistant "No user found" errors.
> 
> Changing compilation options makes no difference here. Forward and reverse
> DNS are both in working order for each domain, and --enable-ip-alias-domains
> is compiled in.
> 
> Any suggestions?

If you are running IP aliased domains look into the vipmap
command line program. Stans for Virtual IP MAPping. vpopmail
is no longer dependent on DNS resolution to associate IP's
with virtual email domains. Instead you set up those mappings
with the vipmap command. This creates a file in ~vpopmail/etc
with a IP <--> Domain mapping.

Ken Jones

Reply via email to