#713 Unable to send signed messages.

[Matthew Kosmoski]

Upon update of Thunderbird, I'm no longer able to send signed messages. My key is on a yubikey, and I get prompted for PIN and can decrypt messages. I can also send unsigned, encrypted messages. Attempting to send signed emails (both encrypted and not) results in a "Sending of the message failed." error. This worked prior to upgrading to 52.4, although I do not recall which version I was previously running.

Application Basics

Name: Thunderbird
Version: 52.4.0
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
Profile Folder: Open Folder

          (Local drive)
Application Build ID: 20171004092449
Enabled Plugins: about:plugins
Build Configuration: about:buildconfig
Memory Use: about:memory
Profiles: about:profiles

Mail and News Accounts
[REDACTED -- gmail and imap accounts]

Crash Reports
https://crash-stats.mozilla.com/report/index/bp-bca9f786-52f4-45a6-b93c-cb4560171010 (2017-10-10)

Extensions
Enigmail, 1.9.8.3, true, {847b3a00-7ab1-11d4-8f02-006008948af5}
gContactSync, 2.0.12, true, gContactSync@pirules.net
Lightning, 5.4.4, true, {e2fda1a4-762b-4020-b5ad-a41df1933103}

Important Modified Preferences

Name: Value

  accessibility.typeaheadfind.flashBar: 0
  browser.cache.disk.capacity: 358400
  browser.cache.disk.filesystem_reported: 1
  extensions.lastAppVersion: 52.4.0
  font.internaluseonly.changed: false
  font.name.monospace.el: Consolas
  font.name.monospace.x-cyrillic: Consolas
  font.name.monospace.x-unicode: Consolas
  font.name.monospace.x-western: Consolas
  font.name.sans-serif.el: Calibri
  font.name.sans-serif.x-cyrillic: Calibri
  font.name.sans-serif.x-unicode: Calibri
  font.name.sans-serif.x-western: Calibri
  font.name.serif.el: Cambria
  font.name.serif.x-cyrillic: Cambria
  font.name.serif.x-unicode: Cambria
  font.name.serif.x-western: Cambria
  font.size.fixed.el: 14
  font.size.fixed.x-cyrillic: 14
  font.size.fixed.x-unicode: 14
  font.size.fixed.x-western: 14
  font.size.variable.el: 17
  font.size.variable.x-cyrillic: 17
  font.size.variable.x-unicode: 17
  font.size.variable.x-western: 17
  mail.openMessageBehavior.version: 1
  mail.winsearch.firstRunDone: true
  mailnews.database.global.datastore.id: 8f90ad2b-c339-4000-b16c-7b61ca222ab
  mailnews.database.global.views.conversation.columns: {"threadCol":{"visible":true,"ordinal":"1"},"flaggedCol":{"visible":true,"ordinal":"3"},"attachmentCol":{"visible":false…
  media.gmp.storage.version.observed: 1
  network.cookie.prefsMigrated: true
  network.predictor.cleaned-up: true
  places.database.lastMaintenance: 1505781017
  places.history.expiration.transient_current_max_pages: 122334
  security.sandbox.content.tempDirSuffix: {e448409f-781d-4f9f-b23c-ec47989643c5}

Graphics

  GPU #1
  Description: NVIDIA GeForce GTX 1060 6GB
  Vendor ID: 0x10de
  Device ID: 0x1c03
  RAM: 6144
  Drivers: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumdx.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumd.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvldumd.dll
  Driver Version: 22.21.13.8253
  Driver Date: 6-7-2017

  Features
  Direct2D: false
  DirectWrite: true (10.0.15063.413)
  WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 1060 6GB Direct3D9Ex vs_3_0 ps_3_0) -- OpenGL ES 2.0 (ANGLE 2.1.0.2a250c8a0e15)

  AzureCanvasBackend: skia
  AzureCanvasAccelerated: 0
  AzureFallbackCanvasBackend: cairo
  AzureContentBackend: skia

JavaScript

Incremental GC: 1

Accessibility

Activated: 0
Prevent Accessibility: 0

Library Versions

  Expected minimum version
  Version in use

  NSPR
  4.13.1
  4.13.1

  NSS
  3.28.6
  3.28.6

  NSS Util
  3.28.6
  3.28.6

  NSS SSL
  3.28.6
  3.28.6

  NSS S/MIME
  3.28.6
  3.28.6

[Patrick Brunschwig]

There should be some error in the Thunderbird Error Console (menu Tools > developer tools > Error Console), which should tell you what failed. If you can't see anything in there, please attach a debug log file (menu Enigmail > Debugging options > Debug log).

[no_spam_me]

I'm not the OP, but I'm using Thunderbird 52.5 and Enigmail 1.9.9 on Linux 64-bit, and experiencing the same symptoms. I'm not sure if it's related, but I also can't see any keys to select underneath the "Use specific OpenPGP key id" menu in Account Settings. The "Select a Secret OpenPGP Key to Sign Your Messages" box is just blank; error follows.

When signing, the enigmail debug log shows nothing and the enigmail console shows this:

enigmail> /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --use-agent --batch --no-tty --status-fd 2 --fixed-list-mode --with-colons --list-config

The Thunderbird Error Console shows this, with the above-mentioned error popup.

mimeEncrypt.js: caught exception: undefined
Message: 'undefined'
File:    undefined
Line:    undefined
Stack:   undefined
  (unknown)
uncaught exception: 2147500037  (unknown)

As for the problem selecting keys, this is the Error Console output:

TypeError: aUserList.sort is not a function[Learn More]  enigmailKeySelection.js:484:3
    buildList chrome://enigmail/content/enigmailKeySelection.js:484:3
    onLoad chrome://enigmail/content/enigmailKeySelection.js:72:3
    onload chrome://enigmail/content/enigmailKeySelection.xul:1:1
    Enigmail.edit.selectKeyId chrome://enigmail/content/enigmailEditIdentity.js:190:5
    oncommand chrome://enigmail/content/am-enigprefs.xul:1:1
    MsgAccountManager chrome://messenger/content/accountUtils.js:255:9
    oncommand chrome://messenger/content/messenger.xul:1:1

[Patrick Brunschwig]

I assume you do have keys on your keyring? Can you please attach a debugging log file?
See https://enigmail.net/index.php/en/faq-en?view=topic&id=15 for how to create a debugging log file.

[no_spam_me]

Yes, in the Key Management window of Enigmail and the linux key utility the keys appear just fine. It seems like there's an error specifically in Enigmail's javascript for both of the issues I mentioned. Attached is the debugging log file, but it doesn't display anything new when I attempt to send a signed message. In fact, it doesn't even display anything when I successfully send an encrypted message. From the logs I've seen, the JS one pasted above is probably the most helpful.

[no_spam_me]

Figured out what the core issue likely was. I simply can't sign anything with this key: either I messed up in the key creation process, or enigmail's wizard is buggy, because the key capabilities simply don't include the "S" which indicates signing capability.