Louis -- ...and then Louis LeBlanc said... % On 11/11/01 01:54 PM, David T-G sat at the `puter and typed: % > % > Let's get back to the real issue here for a moment... % > % > ...and then Louis LeBlanc said... % > % On 11/10/01 06:08 PM, David T-G sat at the `puter and typed: % > % > ...and then Will Yardley said... % > % > % David T-G wrote: % > % > % > % > % > % > % attachments that cannot be read from some mail clients (commandline ... % > % noticed that even when you do send mail as pgp_create_traditional, it % > % still sends it as multipart. That's part of the problem. Shouldn't ... % > What does % > % > :set ?pgp_create_traditional % % pgp_create_traditional=yes
Hokay; that seems fine. % % And, :set ?charset shows: % charset=us-ascii That also seems fine. % % And I still get these headers: % % Message-ID: <[EMAIL PROTECTED]> % Mime-Version: 1.0 % Content-Type: multipart/signed; micalg=pgp-sha1; % protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" % Content-Disposition: inline % User-Agent: Mutt/1.3.23.1i Hokay. Here's what I get with pgp_create_traditional=yes: From [EMAIL PROTECTED] Tue Nov 13 02:45:30 2001 Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 8947 invoked by uid 2003); 13 Nov 2001 02:45:30 -0000 Date: Mon, 12 Nov 2001 21:45:30 -0500 From: David T-G <[EMAIL PROTECTED]> To: David T-G <[EMAIL PROTECTED]> Subject: pgp test Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: application/pgp; x-action=sign; format=text Content-Disposition: inline; filename="msg.pgp" User-Agent: Mutt/1.3.23i -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 this is a test (y/n) :-D - -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE78IlKUScpmrZtnuoRAkpwAKCrGX1ShyEVD+UMUzbNGMDhT4zJagCgiEv4 Zlt2zP0kDfi4HHQJSFE0pqY= =pnQn -----END PGP SIGNATURE----- Furthermore, this is what I get with pgp_outlook_compat=yes as well: From [EMAIL PROTECTED] Tue Nov 13 02:45:50 2001 Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 8981 invoked by uid 2003); 13 Nov 2001 02:45:50 -0000 Date: Mon, 12 Nov 2001 21:45:50 -0500 From: David T-G <[EMAIL PROTECTED]> To: David T-G <[EMAIL PROTECTED]> Subject: pgp test Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Disposition: inline; filename="msg.pgp" User-Agent: Mutt/1.3.23i Content-Type: application/pgp; format=text; x-action=sign -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 this is a test (y/y) :-D - -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE78IleUScpmrZtnuoRAngbAJ96YC24D2soQYzj4AKcCaUAEkffewCgi3Li +lVv9iuETMVDuhFcwFiVqL8= =p+iM -----END PGP SIGNATURE----- In both cases my Content-Type: is application/pgp, while you definitely have multipart/signed, so it seems as though your mutt config is wonky somehow. Of course, pinning that down is the tricky part... % % > show right after you send your message? I had a default send-hook that % > was screwing me up for a while before I found it (*blush*). % % I don't use send-hooks. I operate on folder hooks only. Still, the % same values are there afterward. Hokay. % % > Nope. Did you have any attachments, and did you use a charset other than % > us-ascii? Either of those cases, you'll note from the manual, will cause % > mutt to fall back to PGP/MIME. % % No attachments. The only content was edited from Vim, and contained % only the word 'test' and a buffer read from another file directly into % the message buffer, rather than another part. Mutt still created % separate attachments for the message and the signature. That should be simple enough. % % > I have successfully used $pgp_create_traditional, both with and without % > the patch for $pgp_outlook_compat, to generate old-style emails, so I % > know that it *can* be done. Why it isn't happening for you at the moment % > simply needs to be ferreted out. % % Cool. I hope the info above helps there. If not, let me know what is % needed. Actually, at this point I think you're out of my depth; you've done the debugging I would do except, perhaps, for starting mutt with a null muttrc like mutt -F /dev/null to avoid any sort of hooks (though, since you check ?pgp_create_traditional both before and after sending that certainly seems sure enough), and so I think we'll have to turn it over to the developers. % % I'd really like for this to *not* to turn into a philosophical debate, % or worse, a holy war, about "the right way to do things". I have no Oh, but that's what's fun, and it distracts from the real problem :-) % doubt that Mutt is doing it the right way by following the latest % accepted RFCs. Unfortunately, everyone else out there is doing it "the % wrong way", but that's no reason for us to put up an iron curtain. My % mother isn't real computer savvy (I can't seem to get her to stop % sending mail in all caps :), and her email skills are limited to "real *grin* % basic" at best, but I still like to be able to email her. And I % *absolutely do not* want to have to change clients just so we can read % each other's mail. No, no; you're right. And it's my experience that mutt *does* let you conform (deform? :-) your mail to suit another's MUA, giving us the best of both worlds. % % The only gripe I have, assuming my current problem turns out to be some % other config fubar on my behalf, is that mutt seems to make the status I sure hope that it is, because I can't figure anything else! % quo in pgp (ie. the wrong way to do it) less convenient for the mutt % user. I suppose I % could change the keybindings from <ESC>P to something easier tho, so I % guess even that doesn't really matter. If you don't like having to use esc-P you could always use the procmail recipe from PGP-Notes.txt to convert the incoming email for you... % % BTW, I have managed to get a single part message signed inline, but it % is a real pain in the ass. It involves the macro compose S "Fgpg -a % --clearsign -u . . ." method. It does the job for now, but it is % pretty ugly. There must be a cleaner way to do this. There definitely should be. Interestingly enough, though, if that works for attachments then that's the only way to go to get an encrypted email with attachment included over to an Outlook user without making it tough. I have yet to try out that one, though... % % Thanks for the help. Sorry I ran out of steam before we found the answer! % Lou % -- % Louis LeBlanc [EMAIL PROTECTED] % Fully Funded Hobbyist, KeySlapper Extrordinaire :) % http://www.keyslapper.org ԿԬ % % The light of a hundred stars does not equal the light of the moon. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg20382/pgp00000.pgp
Description: PGP signature
