Hi The Ox
I’m sorry to hear you had some thunderbird problems when you installed Comodo SecureEmail. Our deepest apologies for the problems you have encountered.
It seems also that for a reason we do not yet know, that you have had a failed uninstall also, possible due to a incorrect network registry configuration.
Btw - I am in the UK so differences in timezones do apply.
Neither of these issues appeared in our testing and beta testing or in our many other users. As you can imagine it is not theoretically possible to simulate the environment of each and every desktop PC no matter how hard we try to simulate the real world environment. Real world PCs can have any number of applications installed and uninstalled over a long period of time and even though we follow all the rules, unfortunately some problems can occur for a few users. This does not however mean we will not try to resolve your problems, quite the opposite, we’ll put 100% effort into finding and fixing the problem you encountered with the software (if you wish) and/or correcting your existing issue. I’ve ask a developer to contact you regarding this.
Comodo SecureEmail is a one size fits all solution for POP/SMTP/IMAP. To support as many e-mail clients as possible Comodo SecureEmail uses Microsoft’s Winsock 2 Layered Service Provider Interface (not a hook, but a standard network stack extension system used in the windows network stack for a long time now) and encrypt/signs/decrypts e-mails at the network level, rather than a specific client plug-in, which limits the user of Comodo SecureEmail to only a very very few e-mail clients. If you wish to understand more about Layered Service Providers please see this article: (http://www.microsoft.com/msj/0599/LayeredService/LayeredService.aspx)
Many other third party organisations also use LSPs to execute network stack monitoring (such as Antivirus or Antispam) to intercept and analyse data on a global application basis. Simply deleting an LSP from a network (by deleting registry entries) may result in an unstable system which will probably crash and should not be carried out under any circumstances.
Sometimes if one previous LSP has been removed incorrectly, for example by a spyware registry cleaner such as Spybot –which I notice you have- the correct links for LSPs up and down the chain may be broken and/or the registry may not be in a corrupt or correct state. Spyware applications often remove programs in a brutal manner and do not put back correct linkages which can leave a system unstable. The installation of subsequent LSPs may result in an unstable network system.
It is possible to restore you Winsock2 configuration fairly simply, however if other applications such as Anti-virus and Anti-Spyware are installed and use an LSP you may need to re-install them in order for them to work correctly. Please see the following article.
- WARNING: Care should be taken when editing the registry manually, please read the Microsoft instructions fully before fixing Winsock2.
“How to determine and to recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista”
The crux of the article is to execute the following at a command prompt and reboot:
netsh winsock reset
I sincerely hope this solves your problems. If you need more assistance, please post again and we’ll endeavour to assist.
Kind Regards,
Shane. :SMLR
