> Hi Anders,
>
> > > Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
> > > or ucspi-ssl sets TCPREMOTEIP?
> >
> > How about something like (untested):
> > "(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
> > in your startup script instead of just "
Hi Anders,
> > Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
> > or ucspi-ssl sets TCPREMOTEIP?
>
> How about something like (untested):
> "(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
> in your startup script instead of just "/home/vpopmail/bin/vchkpw" ?
I t
On 3 Mar 2003, Jonas Pasche wrote:
> The drawback is that tcpserver sets (besides others) the environment
> variable TCPREMOTEIP, which vchkpw uses for logging and for opening
> dynamic relays. sslserver from the ucspi-ssl package set SSLREMOTEIP
> instead, which causes vchkpw to stop logging IP a
Hi,
On Monday 03 March 2003 00:44, Jonas Pasche wrote:
> Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
> or ucspi-ssl sets TCPREMOTEIP?
How about something like (untested):
"(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
in your startup script instead of just "/
Hi out there,
I have a small feature request for vpopmail. Currently, I'm checking out
if I could successfully use ucspi-ssl instead of ucspi-tcp for accepting
network connections. Things are a lot easier with this tool, because you
can simple set up your SSL certificates and replace "tcpserver" w