Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Karl Eichwalder]

These days quite some mails or postings are decorated with crap like
this:

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    [...]
    - -- 
    Marco Parrone - marc0@autistici.org
    www.autistici.org/marc0
    2143 9E77 D5E6 115A 48AD  A170 D0EE F736 (4E88 99C2)
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.0.7 (GNU/Linux)
    Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
    [...]

1. Mailcrypt/gnupg seem to ignore signature separators :-(
2. Is there a Gnus function I can activate to hide this boring details?
3. If the answer is "no", is there a procmail recipe to throw away this
stuff?

Thanks for your time!

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Jesper Harder]

Karl Eichwalder <keichwa@gmx.net> writes:

> These days quite some mails or postings are decorated with crap like
> this:
>
>     -----BEGIN PGP SIGNED MESSAGE-----
>     Hash: SHA1
>
> 2. Is there a Gnus function I can activate to hide this boring
> details?

This should happen automatically in the default setting.  But it's
currently broken if the message is sent as format=flowed.  Is that the
case in the examples you've seen?

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Karl Eichwalder]

Jesper Harder <harder@myrealbox.com> writes:

> This should happen automatically in the default setting.  But it's
> currently broken if the message is sent as format=flowed.  Is that the
> case in the examples you've seen?

No, it also happens for me with this message and other messages by
Norman Walsh:

X-From-Line: docbook-apps-errors@lists.oasis-open.org  Sun Mar 16 00:15:53 2003
Return-Path: <docbook-apps-errors@lists.oasis-open.org>
Delivered-To: ke@tux.gnu.franken.de
Received: by tux.gnu.franken.de (Postfix, from userid 10)
	id 3B1ADA43E6; Sun, 16 Mar 2003 00:15:52 +0100 (CET)
Received: from one.elistx.com ([209.116.252.130])
	by elvis.franken.de with esmtp (Exim 3.36 #1)
	id 18uInw-0000A9-00
	for ke@gnu.franken.de; Sat, 15 Mar 2003 22:02:56 +0100
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBT00B016FT1D@eListX.com>
 (original mail from ndw@nwalsh.com) for ke@gnu.franken.de; Sat,
 15 Mar 2003 16:02:20 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBT00B016FS1C@eListX.com> for
 docbook-apps-1136-outbound@reprocess.eListX.com
 (ORCPT docbook-apps@lists.oasis-open.org); Sat,
 15 Mar 2003 16:02:16 -0500 (EST)
Received: from ELIST-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBT00B066FS18@eListX.com> for
 docbook-apps-1136-outbound@reprocess.eListX.com
 (ORCPT docbook-apps@lists.oasis-open.org); Sat,
 15 Mar 2003 16:02:16 -0500 (EST)
Received: from CONVERSION-DAEMON.eListX.com by eListX.com
 (PMDF V6.0-025 #44856) id <0HBT00B016FR16@eListX.com> for
 docbook-apps@elist.lists.oasis-open.org
 (ORCPT docbook-apps@lists.oasis-open.org); Sat,
 15 Mar 2003 16:02:16 -0500 (EST)
Received: from DIRECTORY-DAEMON.eListX.com by eListX.com (PMDF V6.0-025 #44856)
 id <0HBT00B016FR15@eListX.com> for docbook-apps@elist.lists.oasis-open.org
 (ORCPT docbook-apps@lists.oasis-open.org); Sat,
 15 Mar 2003 16:02:15 -0500 (EST)
Received: from dc-mx15.cluster1.charter.net
 (dc-mx15.cluster1.charter.net [209.225.8.25])
 by eListX.com (PMDF V6.0-025 #44856) with ESMTP id <0HBT005I26FRKD@eListX.com>
 for docbook-apps@lists.oasis-open.org; Sat, 15 Mar 2003 16:02:15 -0500 (EST)
Received: from [68.118.253.182] (HELO mercury)  by dc-mx15.cluster1.charter.net
 (CommuniGate Pro SMTP 3.5.9)  with ESMTP id 57080960; Sat,
 15 Mar 2003 16:01:26 -0500
Received: from ndw by mercury with local (Exim 3.35 #1 (Debian))
 id 18uImK-0004OC-00; Sat, 15 Mar 2003 16:01:16 -0500
X-URL: http://nwalsh.com/
Date: Sat, 15 Mar 2003 16:01:16 -0500
From: Norman Walsh <ndw@nwalsh.com>
Subject: Re: empty tags in html transformation
In-reply-to: <iso-8859-1?q?@dc-mx15.cluster1.charter.net>
To: =?iso-8859-1?q?Fr=E9d=E9ric?= Glorieux <f.glorieux@free.fr>
Cc: docbook-apps@lists.oasis-open.org
X-Gnus-Mail-Source: file:/var/spool/mail/ke
Message-id: <8765qkpco3.fsf@nwalsh.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.1
References: <000001c2eaf5$5e6b4290$05cf933e@FENELON>
List-Owner: <mailto:docbook-apps-help@lists.oasis-open.org>
List-Post: <mailto:docbook-apps@lists.oasis-open.org>
List-Subscribe: <http://lists.oasis-open.org/ob/adm.pl>,
 <mailto:docbook-apps-request@lists.oasis-open.org?body=subscribe>
List-Unsubscribe: <http://lists.oasis-open.org/ob/adm.pl>,
 <mailto:docbook-apps-request@lists.oasis-open.org?body=unsubscribe>
List-Archive: <http://lists.oasis-open.org/archives/docbook-apps/>
List-Help: <http://lists.oasis-open.org/elists/admin.shtml>,
 <mailto:docbook-apps-request@lists.oasis-open.org?body=help>
List-Id: <docbook-apps.lists.oasis-open.org>
Lines: 30
Xref: tux.gnu.franken.de list.docbook-apps:7040

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ Fr=81=E9d=81=E9ric Glorieux <f.glorieux@free.fr> was heard to say:
| =09Instead of xhtml transformations, I prefer use common html with
| an xml output, and no namespace declaration. OK, it's not correct, =
but
| works quite correctly under NS4 _and_ IE; and very useful for later
| pipes.

Why are you doing this instead of using the XHTML stylesheets?

                                        Be seeing you,
                                          norm

- --=20
Norman Walsh <ndw@nwalsh.com>      | God, root, what is difference?"
http://www.oasis-open.org/docbook/ | --Pitr, User Friendly; "God is
Chair, DocBook Technical Committee | more forgiving." -- Dave Aronson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.n=
et/>

iD8DBQE+c5ScOyltUcwYWjsRAkdEAJ4lfANYzWg0iCL/A2U45DAFJ0LD1ACfSq67
r1e8aluFjje8a7zr/R0Rvjg=3D
=3DVPSZ
-----END PGP SIGNATURE-----




-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Jesper Harder]

Karl Eichwalder <keichwa@gmx.net> writes:

> Jesper Harder <harder@myrealbox.com> writes:
>
>> This should happen automatically in the default setting.  But it's
>> currently broken if the message is sent as format=flowed.  Is that the
>> case in the examples you've seen?
>
> No, it also happens for me with this message and other messages by
> Norman Walsh:

I can't reproduce it.  PGP signature hiding works for me in that
message.  

Have you disabled detection by setting `gnus-article-emulate-mime' to
nil?  Is pgp-signed in `mm-uu-configure-list'?

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Norman Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ Karl Eichwalder <keichwa@gmx.net> was heard to say:
| Jesper Harder <harder@myrealbox.com> writes:
|
|> This should happen automatically in the default setting.  But it's
|> currently broken if the message is sent as format=flowed.  Is that the
|> case in the examples you've seen?
|
| No, it also happens for me with this message and other messages by
| Norman Walsh:

Hmm. They look ok to me in Oort v0.15. :-)

                                        Be seeing you,
                                          norm

- -- 
Norman Walsh <ndw@nwalsh.com> | Resist the urge to hurry; it will only
http://nwalsh.com/            | slow you down--Bruce Eckel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+dKlSOyltUcwYWjsRAqO6AJ0cu0jyQUZwPfzOtOByG1c9tLAJvQCbB5qi
IBA3fCtLpoiqF0LQbu13iPI=
=/zsd
-----END PGP SIGNATURE-----

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Karl Eichwalder]

Jesper Harder <harder@myrealbox.com> writes:

> Have you disabled detection by setting `gnus-article-emulate-mime' to
> nil?

No, it's t.

> Is pgp-signed in `mm-uu-configure-list'?

Okay, this is the problem; using this setting it works:

(setq mm-uu-configure-list
    '((pgp-signed . t)
     (shar . disabled)))

I don't remember that I've had changed this option somewhere.

Norman Walsh <ndw@nwalsh.com> writes:

> Hmm. They look ok to me in Oort v0.15. :-)

You are using terribly outdated software ;) Thanks for posting this test
message!

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

Re: Ugly decorations: BEGIN PGP SIGNED MESSAGE etc. pp.

[Jesper Harder]

Karl Eichwalder <keichwa@gmx.net> writes:

> Okay, this is the problem; using this setting it works:
>
> (setq mm-uu-configure-list
>     '((pgp-signed . t)
>      (shar . disabled)))
>
> I don't remember that I've had changed this option somewhere.

Strange.  I haven't changed this option -- doesn't it work if you don't
modify it at all?