On Tue, 9 Jan 2018 10:56:19 -0500 Joseph Brennan wrote: > Both FSL_MIME_NO_TEXT and MIME_NO_TEXT are very similar. Both look > for a multipart/mixed message with no "text/" part that has an > attachment. Combined score is just under 5. That's a lot. > > The case in point is an application that sends a report to a few > people as a plain text document, and the only mime part is the > attachment, which is called application/octet-stream and has a .txt > file extension. I feel like this should count in __ANY_TEXT_ATTACH.
more like __ANY_TEXT_ATTACH_DOC, but deliberately disguised text shouldn't count as text. > Using "application/" causes clients to treat a part as an attachment, What's wrong with: Content-Disposition: attachment; filename=...;
