From xemacs-m  Tue Sep 23 21:18:03 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA24638
	for <xemacs-beta@xemacs.org>; Tue, 23 Sep 1997 21:18:02 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.7/8.8.7) id TAA04229;
	Tue, 23 Sep 1997 19:24:03 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 19.16-pre3 can't do PGP-MIME sigs
References: <9709240143.AA13150@salbuild.lehman.com>
X-Face: (:YAD@JS'&Kz'M}n7eX7gEvPR6U1mJ-kt;asEc2qAv;h{Yw7ckz<7+X_SYeTNAaPui:e~x$
 ,A=gkt*>UPL/}\a/#C~v2%ETiAY_sx;xve0yL??JWTtX_-NUzXyP38UdW#cmN1\4(X!c3m#%IbtB-3
 Z-!xpZi!`E.s{(;aP=b11"!3wQu]1j@^V|;n=B|{l<bZV1.AI`zWV%kPCnUhcgEe\(}/_kNd6,*3ZJ
 Q3o<YQ3^u;7jS=:p0--u3msQO
X-Attribution: sb
From: SL Baur <steve@xemacs.org>
In-Reply-To: Rick Campbell's message of "Tue, 23 Sep 1997 21:43:11 -0400"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 23 Sep 1997 19:24:02 -0700
Message-ID: <m2souvo3el.fsf@altair.xemacs.org>
Lines: 24
X-Mailer: Quassia Gnus v0.10/XEmacs 20.3(beta24) - "Ljubljana"

Rick Campbell <rickc@lehman.com> writes:

> As was the case with 19.16-b91, 19.16-pre3 breaks PGP-MIME signature
> checking that worked fine in 19.15.

O.K.  This is something which should be fixed before release and it is 
unlikely to be fixed in pre4 which didn't contain any code changes
beyond build tweaking.

Did you ever post a stack-backtrace or more information about this?
I see a vague report <9709040541.AA18063@cfdevx1.lehman.com> dated
September 4th and posted to xemacs-beta originally reporting this,
but nothing with enough detail to tell exactly what is going wrong.

I don't see anything in the b90-b91 patch which would have caused
this.  Did b90 or any of the p's work?  What mailer are you using?

> Is anyone else using 19.16-b91 with tm and mailcrypt?

> I need to investigate more, but with the same init file and the same
> message, 19.15 correctly verifies a signature with
> mime-viewer/extract-content and 19.16-b91 seems to be looking at the
> wrong thing.  At first glance, it looks like it's extracting the
> previous content instead of the signature.

