When gloda didn't seem to be able to finish indexing a folder, I noticed the following error message in the console: ``` TypeError: can't access property "handleSMimeMessage", mimeSvc.mailChannel.smimeHeaderSink is nullpgpmimeHandler.jsm:242:5 handleSmime chrome://openpgp/content/modules/pgpmimeHandler.jsm:242 onStartRequest chrome://openpgp/content/modules/pgpmimeHandler.jsm:195 ``` Apparently a message with an invalid signature is the cause, just selecting it throws the same error. Excerpts from this message: ``` Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----=_Part_3096197_2000219346.1400078607082" ``` ``` ------=_Part_3096197_2000219346.1400078607082 Content-Type: application/pkcs7-signature; name=smime.p7s; smime-type=signed-data Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature ```
Bug 1864149 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When gloda didn't seem to be able to finish indexing a folder, I noticed the following error message in the console: ``` TypeError: can't access property "handleSMimeMessage", mimeSvc.mailChannel.smimeHeaderSink is null pgpmimeHandler.jsm:242:5 handleSmime chrome://openpgp/content/modules/pgpmimeHandler.jsm:242 onStartRequest chrome://openpgp/content/modules/pgpmimeHandler.jsm:195 ``` Apparently a message with an invalid signature is the cause, just selecting it throws the same error. Excerpts from this message: ``` Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----=_Part_3096197_2000219346.1400078607082" ``` ``` ------=_Part_3096197_2000219346.1400078607082 Content-Type: application/pkcs7-signature; name=smime.p7s; smime-type=signed-data Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature ```