Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Buttonizing and decoding based on message part contents?
Date: Wed, 17 Dec 2003 10:43:03 -0500	[thread overview]
Message-ID: <m365gf30xk.fsf@asfast.com> (raw)
In-Reply-To: <m3smjj7a0z.fsf@defun.localdomain>

Jesper Harder <harder@ifa.au.dk> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>
>> [ ... ]
>
>> But this particular piece of obsolete functionality has no
>> replacement, correct?
>
> Well, I don't actually know if `article-hide-pgp' did anything useful
> for multiparts.
>
> [ ... ]
>
> The problem is really that people stick old-style PGP inside MIME
> parts -- the purpose of MIME is to get rid of silly magic strings like
> "-----BEGIN PGP MESSAGE".  In a multipart message you should use
> pgp/mime.

Yes, in an ideal world that would be the way it's done.  I usually send
out messages in that format; but sadly, there are lots of people who
send messages to _me_ who use the "-----BEGIN PGP MESSAGE-----" magic
string within text/plain or application/octet-stream attachments.  The
chances of my getting each of these people to change their software and
resubmit each individual encrypted message of theirs to me in a timely
fashion is next to nil.

If there was a hook function that gets called for each message part (and
which allows me to set the display and buttonizing status for each
part), I could then write my own, personal code to handle this case, and
at the same time avoid polluting the Gnus code base with this
anachronism.


-- 
 Lloyd Zusman
 ljz@asfast.com




  reply	other threads:[~2003-12-17 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 18:33 Lloyd Zusman
2003-12-16 23:08 ` Jesper Harder
2003-12-17 13:19   ` Lloyd Zusman
2003-12-17 13:49     ` Jesper Harder
2003-12-17 14:04       ` Lloyd Zusman
2003-12-17 15:13         ` Jesper Harder
2003-12-17 15:43           ` Lloyd Zusman [this message]
2003-12-17 22:13             ` Jesper Harder
2003-12-18 17:30               ` Lloyd Zusman
2003-12-19  1:17                 ` Jesper Harder
2003-12-19 18:26                   ` Lloyd Zusman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m365gf30xk.fsf@asfast.com \
    --to=ljz@asfast.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).