On Thu, Aug 01, 2002 at 03:59:19PM +1000, Matt Hyne wrote:

> So I did some testing and I did a 'telnet xxxx 110'.  The tcp connection is 
> set up immediately, however it can take up to 30 seconds for POPD to give 
> the 'POP3 .... server ready' message.  It looks like it is taking this long 
> for xinetd to start /usr/bin/ipop3d.
> 
> However, connecting to it from the local LAN or localhost gives it instantly.
> 
> Doing an SSH, www or any other protocol also works instantly.
> 
> Anyone got any ideas ?

xinetd or pop3d is sending an ident request which is being blocked by a
firewall - the packet being silently dropped so the originator has to
wait for a timeout.

I tested it here.  Dropping packets to port 113 on my workstation then
trying to connect to our internal pop3 server caused a long delay
before the `POP3 ... ready' message appeared.  Changing `DENY' to
`REJECT' caused the `POP3 ... ready' message to appear immediately.



Cheers,

John
-- 
whois [EMAIL PROTECTED]
GPG key id: 0xD59C360F
http://kirriwa.net/john/
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to