Re: [Nmh-workers] NMH Work-arounds for Exchange server mangling (OT???)

[Ken Hornstein]

>> - Maybe a Content-Type of application/octet-stream would work?
>>   If you want to do that via nmh-attachment ... from what I
>>   remember it looks those up via suffixes that are listed via the
>>   normal mhn mechanism (mhn.defaults).  Hm, I see that files that
>>   end in .sh will be sent via application/x-sh; maybe that would
>>   work?
>
>I already tried a variation on that.  I gave it a fake .exe
>extension, thinking that Exchange might look more favorably on
>it.  No joy there.

So if you tried that with nmh-attachment ... that might not have
done what you wanted.  _If_ the nmh-attachment code can't find a
matching extension in mhn.defaults (the default one doesn't have
anything that matches .exe), it looks through the file to be attached;
if there is nothing with the high bit set, it defaults to text/plain,
otherwise application/octet-stream.  So if your "fake" exe file was
really a shar file, it probably was sent as text/plain.


--Ken