On 3/31/2016 1:34 PM, RW wrote:
They have something like:
Content-Type: text; charset="utf-8"
rather than
Content-Type: text/plain; charset="utf-8"
It's probably a rare mistake, but I was thinking of a rule like:
header __MISSING_SUBTYPE_1 Content-Type =~ /^\w+[;\s]/
mimeheader __MISSING_SUBTYPE_2 Content-Type =~ /^\w+[;\s]/
meta MISSING_SUBTYPE __MISSING_SUBTYPE_1 || __MISSING_SUBTYPE_2
Definitely sounds odd. I think the relevant spec is RFC 2045 which is
clear that the subtype is expected. There are references as well that
the subtype is mandatory with no defaults.
I would consider this an invalid header though I believe that should
then be treated as Application/octet-stream
and "a subtype specification is MANDATORY. There are no default subtypes. "
https://www.ietf.org/rfc/rfc2045.txt for those who want to dig deeper.
I think you found a bug in sendmail (or something munging things along
the way.)
Does this need a rule?
Regards,
KAM
