From: love.chaser@gmail.com   
      
   frg wrote:   
   > 2.53.22 switched to the nss from esr 128. 2.53.23 will soon be out and   
   > use the latest ESR 140 one. Not sure if this might cause trouble with   
   > self generated keys. I think there were some changes in this area.   
   >   
   > FRG   
   >   
   > Schugo wrote:   
   >> On 24.12.2025 15:49, A Man Without Clue wrote:   
   >>> Schugo wrote:   
   >>>> On 24.12.2025 15:20, A Man Without Clue wrote:   
   >>>>> Patrick Brunschwig wrote:   
   >>>>>> Hi,   
   >>>>>>   
   >>>>>> this looks like your private key is expired, revoked or similar. Open   
   >>>>>> the Key Manager (menu Enigmail > Key Management) and search for   
   >>>>>> your own   
   >>>>>> key. Double click it to open the Detail window that contains all   
   >>>>>> information about your key.   
   >>>>>>   
   >>>>>> -Patrick   
   >>>>>>   
   >>>>>>   
   >>>>>> On 24.12.2025 11:54, A Man Without Clue wrote:   
   >>>>>>> Hi all,   
   >>>>>>>   
   >>>>>>> I have problem sending gpg encrypted e-mail from Seamonkey.   
   >>>>>>>   
   >>>>>>> I have Seamonkey installed on my debian trixie under /opt   
   >>>>>>> Enigmail has been set up with a keypair.   
   >>>>>>>   
   >>>>>>> Now, while I can receive and decrypt e-mail. I am unable to send and   
   >>>>>>> save encrypted e-mail. Enigmail gives me an alert but the problem is   
   >>>>>>> that the alert dialog does not contain any message so I do not   
   >>>>>>> even know   
   >>>>>>> what the problem is.   
   >>>>>>>   
   >>>>>>> Does anybody have suggestion where to start?   
   >>>>>>>   
   >>>>>>> Thank you.   
   >>>>>>>   
   >>>>>>> A Man Without Clue   
   >>>>>>>   
   >>>>>>   
   >>>>>   
   >>>>> No, my key pair was newly created and other public keys are still   
   >>>>> valid.   
   >>>>> I can decrypt the messages without problem but when I try to send   
   >>>>> encrypted messages, it gives alert. Problem is I don't know what the   
   >>>>> alert is all about since the dialog window contains no messages.   
   >>>>   
   >>>> In my SeaMonkey/Enigmail Menu there is Debugging Options->View Log   
   >>>>   
   >>>> ciao...   
   >>>>   
   >>>   
   >>>   
   >>> Ok, I found the Menu and looked at it.   
   >>> Have no idea what these things are saying...   
   >>   
   >> oh yea there's a lot of extra crap..   
   >> maybe trigger the error and scroll back to the   
   >> first message in that same minute, then find something like:   
   >>   
   >> 2025-12-24 16:00:54 gpg[4872] : skipped: No public key   
   >> 2025-12-24 16:00:54 gpg[4872] [stdin]: encryption failed: No public key   
   >>   
   >> e.g. failed or error   
   >>   
   >> ciao..   
   >>   
   >   
      
   Thank you all.   
      
   something was messed up with the key pair so what I did was to delete   
   the exsiting key pair and created new one. This time I generated key   
   from gpg command, not from enigmail. It seems working ok now.   
      
   but now I got another problem....my PC monitor started blinking...now   
   the monitor is dying...one problem solved now another starts...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)