Have you tried to delete the entry for Thunderbird in Firewall>Advanced>Network Security Policy>Application Rules and in Defense+>Advanced>Computer Security Policy to force CFP3 to find it again when you run it? Not sure if this will help just something else to try if you haven’t already.
Thanks for the response.
CFP3 found Thunderbird the first time, but I tried your suggestion. It finds Thunderbird again after I follow your suggestion, but I still have no Thunderbird email connectivity.
Are you using gmail or encrypted email through your ISP? Comodo left port 995 off the port list that supports their email client rules, so won’t work if you try to use that predefined policy. If you are using gmail and Thunderbird, also need to add port 587. FTP also usually won’t work if you use their predefined policy.
Melih, perhaps add the other email ports in the next upgrade? Not everyone spends their time playing with ports vs protocols for email. Need to add 995, used by most pop3 encrypted email; 587, used by gmail for smtp encrypted using TLS (Thunderbird; 465 is used for SSL/Outlook Express), 993 for encrypted IMAP. I use them all, so added them to the port list and all was well. The FTP client ruleset supplied is for active FTP;virtually all users and clients have gone to passive FTP. Adding rule to allow TCP out everywhere completes the policy. Great product. Now if I could export my settings and get the log to stop taking 0000Z to 0000PST as a holiday, and a few other minor things… (:CLP) 18.104.22.168, Vista Ultimate, Avast!
I checked the “Firewall Events” and found a bunch of entries for AshMailSv.exe being blocked.
Turned out I had apparently told Comodo to use some preset value for my virus checker (avast!) that it didn’t like relating to AshMailSv.exe. I deleted the value in the “Network Security Policy” and then told Comodo during mail checking to always allow the connection as a custom setting.
If you don’t encrypt your email or use gmail configured for pop3 access you will never see these changes-you just can’t do encrypted email until you update the ports. I use them exlusively, because I often use wifi to connect to public and private unsecured internet access points. If I didn’t do that, I would be happy with a NAT router and the Windows firewall. Nothing will change in your system, since you don’t try to access the added ports. As far at the FTP defaults, see http://www.slacksite.com/other/ftp.html for more than you ever wanted to know about ftp, and why mostly passive is used. And why the current defaults usually won’t work.
Okay, looks like some analysis has been done on this. Then by all means, enhance the default rules for passive FTP, encrypted e-mail etc… One needs to be very careful when making rule changes and my previous post was an appeal for using caution when making changes in this area. For example, a rule change in RC1 allowed a DIRECTX keylogger test to do its thing without having CFP block it.