Deane <deane(_at_)gem(_dot_)bekkoame(_dot_)or(_dot_)jp> writes:
...
I am still baffled by how to write a recipe that will take a MIME BASE
64 encoded file (originally an application form prepared in MS-Word)
and attach it to a text file message sent back by an auto responder.
The autoresponder recipe I have written works fine. But I have been
unsuccessful in having my e-mail client detect the MIME attachment and
un-encoding it. It comes back to me as one long text file with the
encoded text as is. I have to use another program, such as Wincode to
convert it back into the original Word doc file.
The problem is almost certainly that you're not including the proper
MIME headers that identify the body of the message as a base64 encoded
file. You'll need to give the message the correct content-type and
encoding by feeding the header through formail, say:
:0 fhw
|formail -I"Mime-Version: 1.0" \
-I"Content-Type: application/msword" \
-I"Content-Transfer-Encoding: base64" \
-I"Content-Disposition: attachment filename=\"whatever.doc\""
Is there a way to attach to the text message encoded application form
such that any mail client that can decode a MIME attachment will
un-encode it and present it as the original Word document file? Then
the recipient would only need to open the document in Word and all
formatting/spacing problems would be solved.
MSWord is not the solution to all formatting/spacing problems.
Philip Guenther