Bug 22309 - content-type wrong for outgoing GPG-signed messages
content-type wrong for outgoing GPG-signed messages
Product: Red Hat Linux
Classification: Retired
Component: pine (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-12-14 14:37 EST by Tim Waugh
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-25 05:53:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2000-12-14 14:37:10 EST
When sending a GPG-signed message using Pine (via the gpg-sign filter), the
content-type is 'text/plain' rather than 'application/gpg; x-action=...'.

This means that if the receiver is using something a real mail client like
mutt ( ;-) ), they have to use procmail to fix up the content-type first
(or do it by hand).

To reproduce: send mail with pine and sign it; read the mail using mutt.
Comment 1 chappa 2000-12-27 22:34:49 EST
This is not a bug in Pine. Pine allows you to change the content/type of a
message. I would say the bug is in the gpg-sign filter or the mistake is in the
way you use it. Did you use the  _MIMETYPE_ token when sending the mail?
Comment 2 Mike A. Harris 2001-01-28 15:32:43 EST
I've read the relevant RFC's, and I agree that this is something that
should be fixed.  I don't consider it an extremely high priority though
because the pinegpg app has a few other problems and I am going to try
and find a better replacement for it if there is one out there.  If not,
I will look into this again some time before too long and fix it.


Comment 3 Mike A. Harris 2003-04-25 05:53:08 EDT
Going through deferred items.  pine is deprecated now, so closing this

Note You need to log in before you can comment on or make changes to this bug.