[Alpine-info] Sending multipart/alternative messages from pine?

[Joshua Miller]

This is going to sound like a silly request/question, but is there a
way (even if a bit complex) to send multipart/alternative messages
from alpine (with one part text/plain, and one text/html).

I've got to deal with a stupid recipient mail server that rejects
text/plain emails with "invalid body type". I've pointed it out, had
managers there request me to be whitelisted, etc, etc, and it still
rejects my emails from alpine. If it weren't work related, I would
simply stop dealing with that recipient and tell them they need to
provide an address that works if they want to hear from me, but I'm
stuck with it for the time being. Luckily, it's only one small group
in our company.

I did find a thread mentioning that one can setup a filter to apply
that'll change the mime type using a small script and:
sending-filters=/full/path/to/change_mime _TMPFILE_ _MIMETYPE_

http://groups.google.com/group/comp.mail.headers/browse_thread/thread/a59f4ad6937feb8/60cc79f8b586ecb0?lnk=gst&q=html#60cc79f8b586ecb0


Could some sort of sending filter take the plain text body, and jack
it into a multipart/alternative message (adding minor html formatting
to the text/html part - just <p> tags really)?

I've tried building one, using perl and MIME::Lite to make the
multipart body, but it just comes through as though it was a
text/plain body (displaying the message boundary and both parts raw).


I'm guessing the easiest way is just for me to use a different mail
client for those specific cases, but I'm stubborn. I've looked at the
FAQ's and searched the group archive and the web, and haven't ran into
an answer either way. It wouldn't surprise me if this is a rare case
(who the hell rejects text/plain messages!?!). I'm fluent in perl, and
willing to put together a filter to do stuff, but I want to still work
from within alpine, and I'm not sure how to hook something in.

Sorry if this message is a huge waste of your time - but if  you've
got any ideas, please let me know :-)
--
Josh I.