On November 30, 1998 at 11:13, Andrew White - Sun UK - Software Developer wrote:
However we are getting attachments of a type TEXT/plain which aren't! They a
in fact Applix Word documents.
Mhonarc extracts the file as a text document but it would be nice if it would
read the 'name="logbook.aw"' and 'x-unix-mode=0700' fields in the 'Content-ty
header line and store as a file.
This applies to a few other attachments types. I could use the 'usename'
facility but this would cause problems with filenames that are the same.
Note, "usename" only works with mhexternal.pl. I.e. text/plain
messages are processed by a separate filter. The text/plain filter
always works in "inline" mode. There is no support for attachments.
mhexternal.pl always works in "attachment" mode with the exception
The issue of "text" attachments has lingered in my head for awhile
since it adds a crimp into the current processing model. To be the
most flexible, MHonArc should support the ability to specify different
filters for data with dispositions of "inline" and "attachment".
Otherwise, one encompassing filter would have to be used which puts
a damper on the extensibility of having separate filters.
Any help on this would be greatly appreciated.
The best solution is to have senders properly label the data.
Even the example you give does not have the Content-Disposition set
so any MUA would show the data inline and not as an attachment, and
what I said about "dispositions" is not even applicable in your