On Tuesday 11 December 2001 11:38, you wrote:
> Since xinetd tries to check ident for a pop connection, I would suspect
> that it the problem, and with the linksys blocking wan requests it would
> drop the packet for the ident request, and xinetd would wait for it to time
> out.
>
> So the other option is to change what xinetd tries to log for pop requests.
Thank you very much, George, disabling the Block Wan Request has solved the
problem for one user. I have yet to find out if the others are using a
Linksys DSL/Cable gateway.
> > I would recommend finding out what the problem really is rather than open
> > the local network to the world as a "fix"...
And I do agree with that. But right now, I'm more interested in a quick
fix that makes the problem go away and takes the pressure off. The client
was asking me to disable the Bastille firewall on the server, it was that
important to him. I'd *much* rather do that at the user end than at the
server end. Fortunately, I'd already done a test and found that Bastille
wasn't the cause of the problem.
I'll explain the issues to the individual users involved and let them make
the choice between security on their end with the concommittant delay in
collecting mail and the convenience of collecting mail quickly. I'm not
overly concerned about the security aspect as the Linksys is doing NAT/IP
masquerading afterall and that's a darn good firewall in and of itself.
In /etc/xinet.d/ipop3, it says:
service pop3
{
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/ipop3d
log_on_success += USERID
log_on_failure += USERID
}
I presume is that the log_on statements are causing the delay when Block WAN
Request is enabled and that if I remove them, the problem will be resolved at
the expense of logging connections.
--
Cheers,
Rob
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
