From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37487
Path: main.gmane.org!not-for-mail
From: Vladimir Volovich <vvv@vsu.ru>
Newsgroups: gmane.emacs.gnus.general
Subject: "Could not identify PKCS#7 type" error
Date: Sat, 04 Aug 2001 21:41:33 +0400
Message-ID: <ey3d77soxe.fsf@vsu.ru>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
X-Trace: main.gmane.org 1035172894 14167 80.91.224.250 (21 Oct 2002 04:01:34 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 04:01:34 +0000 (UTC)
Cc: Simon Josefsson <jas@extundo.com>
Return-Path: <vvv@vsu.ru>
Return-Path: <vvv@vsu.ru>
Original-Received: (qmail 20493 invoked from network); 4 Aug 2001 17:41:31 -0000
Original-Received: from relay1.vsu.ru (HELO vsu.ru) (62.76.169.14)
  by gnus.org with SMTP; 4 Aug 2001 17:41:31 -0000
Original-Received: from [62.76.169.38] (HELO video)
  by vsu.ru (CommuniGate Pro SMTP 3.5b3)
  with ESMTP id 3688264; Sat, 04 Aug 2001 21:41:29 +0400
Original-To: ding@gnus.org
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.103
Original-Lines: 38
Xref: main.gmane.org gmane.emacs.gnus.general:37487
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37487

Hi,

> when viewing s/mime encoded messages, i (still) get an error
> "Could not identify PKCS#7 type". i traced the function
> mm-view-pkcs7-get-type and it appears that it looks for the regexp
> 
> "0‚..	\\*†H†÷
"
> 
> but the buffer " *temp*" begins with
> 
> "0€	*†H†÷
"

namely, the raw message contains:

Content-Type: application/x-pkcs7-mime; name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7m"
Content-Description: S/MIME Encrypted Message

MIAGCSqGSIb3DQEHA6CAMIACAQAxggWyMIIC1QIBADCBvDCBtjELMAkGA1UEBhMCUlUxGjAY
BgNVBAgTEUJsYWNrIFNvaWwgUmVnaW9uMREwDwYDVQQHEwhWb3JvbmV6aDEiMCAGA1UEChMZ
Vm9yb25lemggU3RhdGUgVW5pdmVyc2l0eTEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2
aWNlcyBEaXZpc2lvbjEPMA0GA1UEAxMGdnN1LnJ1MRkwFwYJKoZIhvcNAQkBFgpub2NAdnN1
LnJ1AgEBMA0GCSqGSIb3DQEBAQUABIICALZwbBJ+ebt/fCwmxpX4AsvQV5lwBpYS34aH7qKe
4IIypVSsk6suyGXXm+dKVkxFIQRm/hOyf3H15rw4NazN22Oj0Y8fAeZK8xQPH6UCkBuYZUMa

[skipped]

FiWH7P9TS2XNh1/pw5aCZdAEQBts/A92+w2eUyJZUPDYpS4/4PJXcfrMVL/+AiRRHIYxcw6j
KjeXVWaQt3IdT8jo4FqddauEUcHr2hQ/7gRp4ogECBY0YNL77sCZBDCtvqSn3JWYMttPp4RI
5LklXuSia2am69SIthMYqo9tatu/qkQE44sq5A6R1xLmKEIECBPwC4bo6FHUAAAAAAAAAAAA
AA==

if you base64-decode it, you will see the starting string.
it does not match 0\202, so the regexp is buggy.

Best,
v.