🚀 go-pugleaf

Okay, I stumbled on the reason why my text/plain mail looked like a
binary file to vm, and was being opaquely encoded instead of
qp-encoded.

vm-pcrisis has a variable called vmpc-intangible-sig, which I had set
to t.  The setting prevents the cursor from entering the signature.
(I'm not sure why that's any great benefit.)

That setting, when combined with a message that had paragraphs longer
than six lines or so, resulted (in my case) in
vm-mime-8bit-transfer-encoding being overrided with a base64 encoding.
(Perhaps intangible-sig introduces <CR>s into the buffer??)

Anyway, that's the reason; I wish I were knowledgeable enough to
determine the cause, but I have to leave that to others.

Cheers,

        Jorge

>>>>> "Jorge" == Jorge Gonzalez <jorge@aeth.org> writes:

    Jorge> I have (setq vm-mime-8bit-text-transfer-encoding
    Jorge> 'quoted-printable) and my message composition buffers have
    Jorge> auto-fill on.

    Jorge> When I send a text-only email (with 8-bit characters), the
    Jorge> message is qp mime encoded only if the paragraphs are all
    Jorge> shorter than 6 lines.  (Paragraphs delimited by a blank
    Jorge> line.)

    Jorge> If the message has longer paragraphs, text email with 8bit
    Jorge> characters is base64 mime encoded.

    Jorge> If the message has lots of short paragraphs, the email is
    Jorge> (properly) qp encoded.

    Jorge> I'd like to avoid base64 encoding of text messages.  What's
    Jorge> overriding vm-mime-8bit-text-transfer-encoding?

-- 
Jorge Gonzalez
jorge@aeth.org