smime failure: invalid mime type text/plain
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| VM |
Confirmed
|
Medium
|
Arik | ||
Bug Description
On experimenting with some s/mime signed messages, I have a signed messaged marked as failing verification, but it works manually with openssl on the command line.
The *OpenSSL output* buffer reports:
Error reading S/MIME message
872466152:
And *Messages*:
/h/jhein/
xxxxsm3: 1 message, 0 new, 0 unread, 0 deleted
xxxxsm3: Generating summary... 0
xxxxsm3: Decoding MIME message...
OpenSSL: One of the input files could not be read.
xxxxsm3: Decoding MIME message... done
End of message 1 from Kevin Day...
xxxxsm3: 1 message, 0 new, 0 unread, 0 deleted
xxxxsm3: Checking for new mail...
xxxxsm3: 1 message, 0 new, 0 unread, 0 deleted
But openssl succeeds:
openssl smime -verify -text -out /dev/null -in ~/gen/mbox/xxxxsm3
Verification successful
I set smime-CA-file (pointed to mozilla CA bundle) and vm-mime-
Using vm trunk version 1484.
I'll attach the message separately.
| John Hein (xpqheqdvq4) wrote | #2 |
| Uday Reddy (reddyuday) wrote | #3 |
| Changed in vm: | |
| assignee: | nobody → Arik (akwm) |
| Changed in vm: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Attached is the offending message (in mbox format) obtained from a public mailing list. Let's see - how to mark it private - so I don't further expose this unsuspecting author's info.