On Wed, Apr 20, 2005 at 12:15:32PM -0700, Phil Kemp wrote:
> It was definitley not a QUIT..
>
> I'm beginning to believe that it was a client disconnect. It's very hard to
> tell why.... on the client machine ALL POP3 clients fail. Eudora, Outlook
> 2003, and a Telnet to port 110..
This sounds to me like you might still be running into the AV
software issue.
It is possible that Symantec (you did say it was Symantec NAV,
right?) may have changed their MO for clientside POP filtering from
changing the mail client settings in Eudora/etc. as they used to do, to
silently performing TCP redirection to the NAV local proxy and
rewriting the session commands on the fly so that they can do their
spam and AV filtering.
To debug this, or at least to verify if it's happening, you'll need
to run tcpdump on the server POP session, while connecting to POP via
telnet from the suspect box.
If you're typing one thing, but you're seeing something quite
different come across the wire and hit the POP server, then you can be
fairly sure that something like that is going on inside the client
machine.
-- Clifton
--
Clifton Royston -- [EMAIL PROTECTED]
Tiki Technologies Lead Programmer/Software Architect
"I'm gonna tell my son to grow up pretty as the grass is green
And whip-smart as the English Channel's wide..."
-- 'Whip-Smart', Liz Phair
