Threaded to the OP, rather than a private message.
On Sun 11 Dec 2022 at 18:56:24 (-0600), Greg Marks wrote:
> Dear David,
Thanks, but please keep replies on list so others can see
solutions or join in with suggestions.
Rather than appending a piece of free-standing text to the
rest of the email, in mutt you could attach it as a file:
At the Compose Menu where you type y to send, press a and
then give the filename.
Highlight the attachment in the list, and press Ctrl-E.
Change the encoding from whatever it says, like 7-bit, to
base64, and press Return.
It now doesn't matter what was in the free-standing test:
it will arrive intact. Even though encoded, the receiver's
mutt will typically display the text attachment straight after
the email text without needing any extra commands, but it can
also be saved like any other attachment.
I've attached a mutt documentation sample file as an example.
Its entry in mutt's Compose Menu looks like:
A 2 sample.mailcap [text/plain, base64, us-ascii, 0.1K]
displays after email because ↑↑↑↑↑↑↑↑ ↑↑↑↑ I set this
Note that when sending attachments, the filename may appear
incomplete as it has to include the full path. The receiver
doesn't see the path at their end, but only the filename.
Cheers,
David.
# $Id$
text/html; netscape -remote openURL\(%s\)
image/gif; xv %s
image/jpg; xv %s
application/pgp-keys; pgp -f < %s ; copiousoutput
