Greetings. I'm an old-time Unix guy who doesn't like all this
new-fangled "web" and "mime" stuff in his email So this problem is
probably a combination of stuff I don't know and stuff I configured
wrong.
I feel your pain, and a large part of the problems with nmh is bringing
it into the new reality we all live in but some of us don't want to accept.
Like this quaint idea that email is "text" :-) But I've said enough about
that in the past.
Content-Disposition: attachment; filename="encrypted.asc";
I personally think it's rather unfriendly to mark that part with a
disposition of "attachment" when it's clearly meant to be displayed
inline, but whatever.
I am not sure you can make mhshow currently cleanly display this; normally
for encrypted email you'd need to enter in your password to unlock your
private key and we don't really have a good mechanism for that currently.
It would require some smarts we don't currently have. It's on my list to
improve (but that list is long). If someone else has a better idea, please
speak up.
FWIW, for what I do is store out the part using mhstore(1); that takes
care of all of the base64 decoding for you. Then you could use gpg2 on
that normally. Yes, we should simply be able to run "mhshow" with a
little bit of configuration magic to make the right thing happen; we're
not there yet.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers