Thanks to all who replied. After upgrading to Debian Mozilla 1.2 it
started to work as expected.

Stephan

[EMAIL PROTECTED] wrote in message news:<aslr01$[EMAIL PROTECTED]>...
> Check the return email address of your friend ... Make sure that they 
> dont have a reply-to that is diff from the digital cert email address ...
> ALSO, and most important ... make certain that the email address that 
> you are putting in the TO: field matches *EXACTLY* (including 
> capitalization) of the digital cert email address ...
> 
> I have run into quite a few build that done allow [EMAIL PROTECTED] but 
> will work fine on [EMAIL PROTECTED] ... there have been bugs opened in the 
> past about that little problem ...
> 
> Andrew
> 
> Nelson B wrote:
> > Stephan,
> > 
> > Before we spend any more time trying to guess what other previously
> > reported bug might cause your problem, let's find out what symptoms
> > you're really experiencing.
> > 
> > So far, all you've told us about your experience is
> > "I'm unable to send an encrypted message".
> > You haven't told us what sort of error message or other experience
> > you're having.  
> > 
> > You've told us some of the things that are proper, such as what you've
> > found in the cert, and you've told us symptoms that were reported in
> > other bug reports, but you haven't said what you're experiencing yet.
> > 
> > You wrote that you can send yourself an encrypte message.  Assuming that
> > you mean "with mozilla", that suggests that there is no problem with your
> > own cert, but rather with the cert of your correspondent.
> > 
> > I think mozilla usually works with Thawte Freemail certs, but it might
> > help if you could attach a copy of your cprrespondent's cert, or cite
> > a URL where it could be downloaded.
> > 
> > --
> > Nelson B

Reply via email to