On 2001.11.26, in <[EMAIL PROTECTED]>,
"Patrik Modesto" <[EMAIL PROTECTED]> wrote:
>
> There is no Content-Type header. There is:
> ...
> then few empty lines and then the encoded file above. I can get to the
> PC that sends this "attachments" so I will check it's MSOE setup.
It's not naturally MIME, but if you can always assume that uuencoded
content from MSOE is supposed to be an attached document, you can
probably fake something up with procmail. Something like this:
:0 fBH
* X-Mailer: Microsoft Outlook Express
* ^begin [0-7][0-7][0-7] [A-Za-z0-9]
| formail -I "Content-Type: application/octet-stream" \
-I "Content-Transfer-Encoding: x-uuencode"
That should make it a document containing one inline component that
mutt can decode and view using whatever your application/octet-stream
viewer is. (By default, mutt tries to treat it as text.) With a slightly
fancier bit of scripting, you could extract the filename from the begin
line, and add that to the MIME description, and you could ensure that
ONLY uuencoded material was processed, and make it attached instead of
inline... etc. But this should suit your most fundamental need. The MIME
isn't exactly perfect, but it's sufficient for this sole purpose.
--
-D. [EMAIL PROTECTED] NSIT University of Chicago
