OE 6 times out with NIS 2004

When Norton Internet Security 2004's Spam Filter is on, Outlook Express v6.x
will often time-out. This is the error from OE:

A time-out occurred while communicating with the server. Account: 'Karl
Thompson Pine Grove Software', Server: 'mail.pine-grove.com', Protocol:
POP3, Port: 110, Secure(SSL): No, Error Number: 0x800CCC19

When I turn the antispam feature off, then OE is able to retrieve the
messages.

Does anyone know of a fix for this? Or how to report this to Symantec (for
free)?

TIA

Actually, I did find one article in the Norton knowledgebase. This is there
comment:

Solution:
In most cases these errors occur because of problems unrelated to Norton
Internet Security.

Then they go on and say to turn off AntiVirus (of cource this is caused or
appears to be caused by Antispam).

Aren't Symantec products generally ho-hum? And doesn't their support just
generally suck? Or am I the only one that feels this way?



"Karl" wrote in message
...

When Norton Internet Security 2004's Spam Filter is on, Outlook Express
v6.x
will often time-out. This is the error from OE:

A time-out occurred while communicating with the server. Account: 'Karl
Thompson Pine Grove Software', Server: 'mail.pine-grove.com', Protocol:
POP3, Port: 110, Secure(SSL): No, Error Number: 0x800CCC19

When I turn the antispam feature off, then OE is able to retrieve the
messages.

Does anyone know of a fix for this? Or how to report this to Symantec
(for
free)?

TIA

Is the following option checked:

NIS2004 Options Norton AntiVirus Email Advanced Protect against
timeouts ?

"Karl" wrote in message


When Norton Internet Security 2004's Spam Filter is on, Outlook
Express v6.x will often time-out. This is the error from OE:

A time-out occurred while communicating with the server. Account:
'Karl Thompson Pine Grove Software', Server: 'mail.pine-grove.com',
Protocol: POP3, Port: 110, Secure(SSL): No, Error Number: 0x800CCC19

When I turn the antispam feature off, then OE is able to retrieve the
messages.

Does anyone know of a fix for this? Or how to report this to
Symantec (for free)?

TIA