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. I think "multipart/mixed" allows a message with one part. Using "application/" causes clients to treat a part as an attachment, and I think the generic "octet-stream" is correct since there is no specific software that must be used for a plain text file. (I'm actually surprised that there is nothing like application/plaintext for this case, but I could not identify such a type in a web search.) Comments? -- Joseph Brennan Columbia University
