Thunderbird Timeout

I am running the latest NOD32 3.0.566 on XP.
I can connect to my mail server with TB.
However, TB times out and I can't send/receive email.
I have submitted this problem to ESET.
I removed Comodo v 3 firewall and still have the issue.
Any thoughts?
Thanks.

 

I have same setup as you with Comodo 3.0 enabled. No problems with Thunderbird at all. Make sure you do a clean install of NOD32 and make certain any and all prior Eset files are deleted before install. Remnants can cause problems.

 

Running 3.0.566 and XP SP2.

I can not get NOD32 to scan any of my e-mails received with Thunderbird.

I have Thunderbird marked as my POP3 email client and NOD32 set up to "tag" all scanned e-mails, but none of them get tagged. Also, E-mail Protection always shows Zero e-mails scanned.

Any ideas why NOD won't scan my e-mails?

TIA.

 

Dear Bunkhouse Bunk -

I ran the uninstall program and deleted any folders marked ESET or NOD32. Are there any DLLs in Windows I should look for?

Also -- how did you configure NOD32 to handle TB? Anything out of the ordinary? Did you have to change Comodo at all?

Thanks.

 

My experience is that you don't need to do a thing to either NOD32 or TB. I do not have the Defense+ module running in Comodo (mainly because I am not that paranoid to run it), but when I did have it activated, I did nothing special. My guess is that there is something else causing problems. You might want to run CCleaner to delete any registry entries that might be causing problems.

http://www.ccleaner.com/

 

I have the same set up as you and Thunderbird is sending and receiving mail ok. We'll have to compare set ups in each app!! Gotta stick my son in the bath first and get him off to bed.

 

I'm sure this is a TB problem, have a read of this http://kb.mozillazine.org/Cannot_send_mail
http://kb.mozillazine.org/Connection_errors_-_SMTP

 

Well it turned out not to be a TB. However, I didn't know those links existed regarding email and TB so I'll file them away for the inevitable problems -- thanks.
An earlier suggestion was made about cleaning out the old install of NOD32 - 2.7. I loaded up a backup and uninstalled, cleaned, and washed throughly and then re-installed NOD32 v 3 and everything worked.

Thanks to one and all.