Re: email certificates
Phillip Jones wrote: James wrote: James wrote: Phillip Jones wrote: James wrote: Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. *Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt.* That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. How did you migrate the certificates did you do and export and then an import? Yes, I exported the certificates from Thunderbird and imported them into SeaMonkey when I decided to migrate. The more I look at it, the more of a mistake that seems to be. SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had certificate authority issued certificates. After trading signed emails, encryption was successful in both directions. Unfortunately, that does not help explain why it fails with Thunderbird. Without a fix, migrating back to Thunderbird will be necessary. My thanks to everyone that has contributed to this thread. Have you tried importing your SeaMonkey Cert to Thunderbird? It originally came from ThunderBird, so I do not anticipate any problems there. Further investigation shows that for some reason the public key is not being sent with the certificate, so when I look into the certificate file, there is nothing there from the Thunderbird client. I wonder if the Thunderbird client has correctly stored my certificate. I presume SeaMonkey automatically sends the public key with the signature, but I have been unable to verify that other than with a new correspondent (as per the latest test). I must remember to ask if the Thunderbird client has a copy of my certificate and public key. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Ray_Net wrote: James wrote: Ray_Net wrote: James wrote: Mark Hansen wrote: On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. Reading the documentation makes it seem that it is a certificate creator and manager. There is nothing that presumes the certificates will not work anywhere a certificate is used. I do not think this will solve the problem in sending certificate encrypted emails to Thunderbird and receiving certificate encrypted emails from Thunderbird. I tried again to encrypt to Thunderbird and again failed. All the other attempts succeeded. Without a definitive answer to the SeaMonkey email certificate problem, I must migrate back to Thunderbird. Personally, I believe that all internet traffic should be encrypted. Unfortunately, the majority say, I keep myself vulnerable because I want to be abused, here is my banking information. I do not wish the hackers to know that I am saying things like, Hello, how are you? in the emails I send. Let them try to decrypt it to find out there is no personal info there. So you need to sent the public key to everyone in the world - because you don't know to which person the destination of the next mail will be... Is that not how Enigmail works? You trade public keys (certificates) then you may encrypt? I have zero experience with Enigmail, Me too :-) I think that you must send public key but you should encrypt with your personal key. I never use encrypted mail to not force the recipent to install decryption software, etc ... let the people stay simple and reserve encrypted mail if you want to sent sensible data in a mail. It seems to me that Enigmail makes certificates easier to create and manage, but the signed and encrypted emails themselves are handled the same with or without Enigmail. If you would like to practice, you may send me a signed email. I will then reply signed. Then we may attempt sending each other encrypted emails. You with Enigmail and me without. It should work as we are both using SeaMonkey. I would like to test it out with someone that is using Thunderbird as I have only one correspondent that uses Thunderbird for encryption and it would be useful to find out if it works or the problem is with SeaMonkey or with Thunderbird. One point on a chart does not make a graph. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Phillip Jones wrote: James wrote: Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. *Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt.* That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. How did you migrate the certificates did you do and export and then an import? Yes, I exported the certificates from Thunderbird and imported them into SeaMonkey when I decided to migrate. The more I look at it, the more of a mistake that seems to be. SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had certificate authority issued certificates. After trading signed emails, encryption was successful in both directions. Unfortunately, that does not help explain why it fails with Thunderbird. Without a fix, migrating back to Thunderbird will be necessary. My thanks to everyone that has contributed to this thread. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Ray_Net wrote: James wrote: Ray_Net wrote: James wrote: Mark Hansen wrote: On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. Reading the documentation makes it seem that it is a certificate creator and manager. There is nothing that presumes the certificates will not work anywhere a certificate is used. I do not think this will solve the problem in sending certificate encrypted emails to Thunderbird and receiving certificate encrypted emails from Thunderbird. I tried again to encrypt to Thunderbird and again failed. All the other attempts succeeded. Without a definitive answer to the SeaMonkey email certificate problem, I must migrate back to Thunderbird. Personally, I believe that all internet traffic should be encrypted. Unfortunately, the majority say, I keep myself vulnerable because I want to be abused, here is my banking information. I do not wish the hackers to know that I am saying things like, Hello, how are you? in the emails I send. Let them try to decrypt it to find out there is no personal info there. So you need to sent the public key to everyone in the world - because you don't know to which person the destination of the next mail will be... Is that not how Enigmail works? You trade public keys (certificates) then you may encrypt? I have zero experience with Enigmail, Me too :-) I think that you must send public key but you should encrypt with your personal key. I never use encrypted mail to not force the recipent to install decryption software, etc ... let the people stay simple and reserve encrypted mail if you want to sent sensible data in a mail. It seems to me that Enigmail makes certificates easier to create and manage, but the signed and encrypted emails themselves are handled the same with or without Enigmail. If you would like to practice, you may send me a signed email. I will then reply signed. Then we may attempt sending each other encrypted emails. You with Enigmail and me without. It should work as we are both using SeaMonkey. I would like to test it out with someone that is using Thunderbird as I have only one correspondent that uses Thunderbird for encryption and it would be useful to find out if it works or the problem is with SeaMonkey or with Thunderbird. One point on a chart does not make a graph. SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had certificate authority issued certificates. After trading signed emails, encryption was successful in both directions. Unfortunately, that does not help explain why it fails with Thunderbird. Without a fix, migrating back to Thunderbird will be necessary. My thanks to everyone that has contributed to this thread. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: James wrote: Phillip Jones wrote: James wrote: Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. *Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt.* That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. How did you migrate the certificates did you do and export and then an import? Yes, I exported the certificates from Thunderbird and imported them into SeaMonkey when I decided to migrate. The more I look at it, the more of a mistake that seems to be. SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had certificate authority issued certificates. After trading signed emails, encryption was successful in both directions. Unfortunately, that does not help explain why it fails with Thunderbird. Without a fix, migrating back to Thunderbird will be necessary. My thanks to everyone that has contributed to this thread. Have you tried importing your SeaMonkey Cert to Thunderbird? -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net/ mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Ray_Net wrote: James wrote: Mark Hansen wrote: On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. Reading the documentation makes it seem that it is a certificate creator and manager. There is nothing that presumes the certificates will not work anywhere a certificate is used. I do not think this will solve the problem in sending certificate encrypted emails to Thunderbird and receiving certificate encrypted emails from Thunderbird. I tried again to encrypt to Thunderbird and again failed. All the other attempts succeeded. Without a definitive answer to the SeaMonkey email certificate problem, I must migrate back to Thunderbird. Personally, I believe that all internet traffic should be encrypted. Unfortunately, the majority say, I keep myself vulnerable because I want to be abused, here is my banking information. I do not wish the hackers to know that I am saying things like, Hello, how are you? in the emails I send. Let them try to decrypt it to find out there is no personal info there. So you need to sent the public key to everyone in the world - because you don't know to which person the destination of the next mail will be... Is that not how Enigmail works? You trade public keys (certificates) then you may encrypt? I have zero experience with Enigmail, Me too :-) I think that you must send public key but you should encrypt with your personal key. I never use encrypted mail to not force the recipent to install decryption software, etc ... let the people stay simple and reserve encrypted mail if you want to sent sensible data in a mail. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Mark Hansen wrote: On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. Reading the documentation makes it seem that it is a certificate creator and manager. There is nothing that presumes the certificates will not work anywhere a certificate is used. I do not think this will solve the problem in sending certificate encrypted emails to Thunderbird and receiving certificate encrypted emails from Thunderbird. I tried again to encrypt to Thunderbird and again failed. All the other attempts succeeded. Without a definitive answer to the SeaMonkey email certificate problem, I must migrate back to Thunderbird. Personally, I believe that all internet traffic should be encrypted. Unfortunately, the majority say, I keep myself vulnerable because I want to be abused, here is my banking information. I do not wish the hackers to know that I am saying things like, Hello, how are you? in the emails I send. Let them try to decrypt it to find out there is no personal info there. So you need to sent the public key to everyone in the world - because you don't know to which person the destination of the next mail will be... ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Ray_Net wrote: James wrote: Mark Hansen wrote: On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. Reading the documentation makes it seem that it is a certificate creator and manager. There is nothing that presumes the certificates will not work anywhere a certificate is used. I do not think this will solve the problem in sending certificate encrypted emails to Thunderbird and receiving certificate encrypted emails from Thunderbird. I tried again to encrypt to Thunderbird and again failed. All the other attempts succeeded. Without a definitive answer to the SeaMonkey email certificate problem, I must migrate back to Thunderbird. Personally, I believe that all internet traffic should be encrypted. Unfortunately, the majority say, I keep myself vulnerable because I want to be abused, here is my banking information. I do not wish the hackers to know that I am saying things like, Hello, how are you? in the emails I send. Let them try to decrypt it to find out there is no personal info there. So you need to sent the public key to everyone in the world - because you don't know to which person the destination of the next mail will be... Is that not how Enigmail works? You trade public keys (certificates) then you may encrypt? I have zero experience with Enigmail, but the documentation suggests it is a certificate generator and certificate manager add-on for Mozilla email client programs. Certificates issued by certificate authorities work to enable you to sign emails that can be sent to anyone, but both sender and recipient need each other's public keys for encryption. Trading certificates with an initial email and reply using signed emails is about as convenient as it gets before you can start sending encrypted emails. Before secure emails, you had to encrypt a file and send it as an attachment. Self-extracting files were executable (.exe) and all the emails I tried to send with an executable file were stopped. This means both need the same encryption software. Trading passwords securely may be a problem using stand alone encryption. In my experience, the majority have no idea that their emails are being routinely scanned by hackers looking for a quick profit. I keep hearing stories about people sending credit card info to a family member to make a purchase and the credit card or bank account being raided for all it is worth by a hacker even before the family member can use it. I do not even like sending unencrypted emails that have no personal information, but convincing the drooling mouth breather with a mind of a gnat that encryption is good is as harder than teaching people to breathe under water. They argue, I have nothing to hide. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Phillip Jones wrote: James wrote: Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. *Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt.* That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. How did you migrate the certificates did you do and export and then an import? Yes, I exported the certificates from Thunderbird and imported them into SeaMonkey when I decided to migrate. The more I look at it, the more of a mistake that seems to be. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Mark Hansen wrote: On 10/24/2010 1:43 PM, James wrote: Mark Hansen wrote: On 10/23/2010 6:24 PM, James wrote: I have been using email certificates for years. The only time I had email certificate problems is when I started using SeaMonkey. Have you considered using Enigmail? To be honest, I didn't even know SeaMonkey had a built-in way to send/receive encrypted e-mail messages. Enigmail provides this and has been working for me for years. I have been looking at the documentation and found no reference to how the other user would be able to use anything I sent to them encrypted. Does each party need the same program? If so, then this application will be severely limited as most of my correspondents that use certificate encryption use Outlook, Outlook Express, or some other email client program. My problem is with the Thunderbird user. I will continue to look into this and I thank you for your suggestion. From what I understand, the encrypted e-mail message is done in an industry-standard way, so anyone (with the correct public pgp key) should be able to read it. However, I don't know for sure. You might want to check with the author's site. I'm sure he has an FAQ or is willing to answer questions, etc. Good luck. You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
On 10/25/2010 12:46 PM, James wrote: You make it seem as if you never sent or received an encrypted email using your method. If you had, you would know what each participant is required to have. Still, when I have time, I will continue to research Enigmail. So far it seems it will only work with Mozilla email client programs. Actually, I sent encrypted/signed message to and received from many people. However, I don't know what they were using. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
On 10/23/2010 6:24 PM, James wrote: I have been using email certificates for years. The only time I had email certificate problems is when I started using SeaMonkey. Have you considered using Enigmail? To be honest, I didn't even know SeaMonkey had a built-in way to send/receive encrypted e-mail messages. Enigmail provides this and has been working for me for years. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue "Certificates meant for MS products will not work on Mozilla Products"? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt. That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Mark Hansen wrote: On 10/23/2010 6:24 PM, James wrote: I have been using email certificates for years. The only time I had email certificate problems is when I started using SeaMonkey. Have you considered using Enigmail? To be honest, I didn't even know SeaMonkey had a built-in way to send/receive encrypted e-mail messages. Enigmail provides this and has been working for me for years. I have been looking at the documentation and found no reference to how the other user would be able to use anything I sent to them encrypted. Does each party need the same program? If so, then this application will be severely limited as most of my correspondents that use certificate encryption use Outlook, Outlook Express, or some other email client program. My problem is with the Thunderbird user. I will continue to look into this and I thank you for your suggestion. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
On 10/24/2010 1:43 PM, James wrote: Mark Hansen wrote: On 10/23/2010 6:24 PM, James wrote: I have been using email certificates for years. The only time I had email certificate problems is when I started using SeaMonkey. Have you considered using Enigmail? To be honest, I didn't even know SeaMonkey had a built-in way to send/receive encrypted e-mail messages. Enigmail provides this and has been working for me for years. I have been looking at the documentation and found no reference to how the other user would be able to use anything I sent to them encrypted. Does each party need the same program? If so, then this application will be severely limited as most of my correspondents that use certificate encryption use Outlook, Outlook Express, or some other email client program. My problem is with the Thunderbird user. I will continue to look into this and I thank you for your suggestion. From what I understand, the encrypted e-mail message is done in an industry-standard way, so anyone (with the correct public pgp key) should be able to read it. However, I don't know for sure. You might want to check with the author's site. I'm sure he has an FAQ or is willing to answer questions, etc. Good luck. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Rick Merrill wrote: James wrote: Phillip Jones wrote: James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. We each have traded certificate and public key data, yet it does not function. No help here. I am not a novice as I have been using email certificates for years without problems until I migrated to SeaMonkey. Unless I get a solution, SeaMonkey is history as far as I am concerned. Excuse me, but did you address the issue Certificates meant for MS products will not work on Mozilla Products? The certificates worked in Thunderbird without problems. They do not work in SeaMonkey. I presume my initial inquiry was too complex. *Certificate encrypted emails from SeaMonkey to Thunderbird do not decrypt. Certificate encrypted emails from Thunderbird to SeaMonkey do not decrypt.* That is as simple as I can explain the problem. Does anyone have a solution? Since both SeaMonkey and Thunderbird are both Mozilla products, I do not see how your reference applies. I do not use Micro$oft products unless I require a function found there that is not available elsewhere. For instance, I use Micro$oft Internet Explorer for those web pages that do not function using any other browser. Another example is that I only use Micro$oft Word when I must manipulate lists where tabs and paragraph marks must be used in 'search and replace' operations as Open Office does not support that function. How did you migrate the certificates did you do and export and then an import? -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net/ mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net/ mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. I have been using email certificates for years. The only time I had email certificate problems is when I started using SeaMonkey. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: email certificates
James wrote: Phillip Jones wrote: James wrote: I set up SeaMonkey with certificates for each email account. The major problem is to get the certificates recognized in Thunderbird and vice versa. I keep getting the broken key symbol. Something similar happens on the other end. The certificates are functional between the accounts I manage, but I do not have any external correspondents with other certificate enabled email clients to extend my range of testing. Unless I get a solution soon, I must abandon SeaMonkey. Has anyone compiled a list of email certificate problems, with or without solutions? The same certificates will work just as good SeaMonkey as in Thunderbird. export your personal certificates (from Versign or thawte) to folder (directory) on your hard drive. you will have to supply your password used to create the certificate. and in some cases if you have password protected Thunderbird you'll have to supply that as well. When you import into SM you have to supply those password(s) again. Certificate meant for MS products will not work on Mozilla Products. The certificate have to be customized by the company (Thawte / Versign) for the email Client and the OS. But any customized for Mozilla (or Netscape) works on any Mozilla Product. You misunderstand. The certificates are properly installed and working, but a recipient that is using Thunderbird can not read encrypted email sent to him and I can not read encrypted email received from him. SeaMonkey to SeaMonkey works fine. SeaMonkey to or from Thunderbird does not work at all. Oh you and he is supposed to send you public key to each other. The public key that each other receives works with the private keys if they fit you can talk. Go to Versign and look up Private key and Public key also look in SeaMonkey's help. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net/ mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
