From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/60624 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: oddies with enigmail Date: Sun, 24 Jul 2005 16:45:33 +0200 Message-ID: References: <87slyqs9z9.fsf@mat.ucm.es> <87r7e3ok3p.fsf@wheatstone.g10code.de> <87oe96pnkg.fsf@mat.ucm.es> <87hderos59.fsf@wheatstone.g10code.de> <87u0iqk7sf.fsf@mat.ucm.es> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1122216589 19711 80.91.229.2 (24 Jul 2005 14:49:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 24 Jul 2005 14:49:49 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M9152@lists.math.uh.edu Sun Jul 24 16:49:40 2005 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DwhnP-00009o-0g for ding-account@gmane.org; Sun, 24 Jul 2005 16:49:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1Dwhk4-0001cw-00; Sun, 24 Jul 2005 09:46:12 -0500 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1Dwhjv-0001cm-00 for ding@lists.math.uh.edu; Sun, 24 Jul 2005 09:46:03 -0500 Original-Received: from quimby.gnus.org ([80.91.224.244]) by util2.math.uh.edu with esmtp (Exim 4.30) id 1Dwhju-0003E9-E9 for ding@lists.math.uh.edu; Sun, 24 Jul 2005 09:46:02 -0500 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Dwhjo-00066Y-00 for ; Sun, 24 Jul 2005 16:45:56 +0200 Original-Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3) with ESMTP id j6OEjhaZ023147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 24 Jul 2005 16:45:44 +0200 Original-To: Uwe Brauer OpenPGP: id=B565716F; url=http://josefsson.org/key.txt X-Hashcash: 1:21:050724:oub@mat.ucm.es::dG8pQDWkn+rIv8CJ:0OHq X-Hashcash: 1:21:050724:ding@gnus.org::ySJ0+JaCvGHy4uaL:4NQT In-Reply-To: <87u0iqk7sf.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 19 Jul 2005 17:46:56 +0000") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=failed version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yxa-iv X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on yxa.extundo.com X-Virus-Status: Clean X-Spam-Score: -4.9 (----) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:60624 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:60624 Uwe Brauer writes: >>>>>> "Simon" == Simon Josefsson writes: > > Simon> Werner Koch writes: > >> On Wed, 13 Jul 2005 18:29:03 +0000, Uwe Brauer said: > >> > >>> The question is can I clear sign the message such that > >>> enigmail would not complain? > >> > >> Do you say that pgg inserts the Hash line? This is obviously > >> wrong - it is best to let gpg create the cleas signed message. > >> This will make sure that the correct header is used. > > Simon> PGG doesn't insert nor remove any Hash: lines. The output > Simon> from gpg is used directly, except for QP encoding when > Simon> needed. Gnus will QP encode the output from gpg, so the > Simon> receiver till have to perform QP decode before it looks > Simon> like a valid OpenPGP packet. This might break some MUAs > Simon> that expect the OpenPGP armor to not be QP escaped, but > Simon> rather, only the signed data. But such a message wouldn't > Simon> conform to MIME specs (the '=' in the CRC24 tag is invalid > Simon> QP unless escaped), and some MTAs bounce those messages... > > Simon> That the morale is to use PGP/MIME instead is hopefully obvious. > > Well that is what I used > mml-secure-message-sign-pgpmime Oh. Ok. Still, PGG shouldn't alter any Hash: headers. Was that definitely the problem here? Perhaps something else is somehow modifying that header.