On Sun, Jun 24, 2001 at 05:55:14PM +1000, Rob B wrote:
> Probably something to do with these headers
>
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
No, more likely this one, inserted by both mutt and Eudora:
Content-Type: multipart/encrypted; protocol="application/pgp-encrypted";
boundary="J2SCkAp4GZ/dPZZf"
Outlook doesn't insert or understand such headers. It uses the older
style pgp message format, simply putting these lines:
-----BEGIN PGP MESSAGE-----
message contents
-----END PGP MESSAGE-----
around the message with no special headers. Adding these rules to your
.procmailrc will insert an appropriate header and enable mutt to handle
them:
:0
* !^Content-Type: message/
* !^Content-Type: multipart/
* !^Content-Type: application/pgp
* !^From: .*[EMAIL PROTECTED]
{
:0 fBw
* ^-----BEGIN PGP MESSAGE-----
* ^-----END PGP MESSAGE-----
| formail \
-i "Content-Type: application/pgp; format=text; x-action=encrypt"
:0 fBw
* ^-----BEGIN PGP SIGNED MESSAGE-----
* ^-----BEGIN PGP SIGNATURE-----
* ^-----END PGP SIGNATURE-----
| formail \
-i "Content-Type: application/pgp; format=text; x-action=sign"
}
The exception for [EMAIL PROTECTED] is because when you edit your
zone at granitecanyon.com, they send you what looks like a pgp-signed
message which you have to send back to them to accept the changes, but
the pgp signature block actually contains the encrypted zone data and
must be returned intact. If you add the `x-action=sign' header, then
mutt, and probably other mail clients, will discard the signature when
replying.
Cheers,
John
--
whois [EMAIL PROTECTED]
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
