Content-Type: text

David Relson relson at osagesoftware.com
Sun Jul 20 23:24:19 CEST 2003


Greetings,

Apparently some mailers generate invalid Content-Type 
headers.  Specifically, "Content-Type: text" has been seen.  It's invalid 
because the spec (rfc2045) requires 'type "/" subtype.  (See below for a 
quote from rfc2045).

Currently bogofilter requires the slash and will skip a mime part whose 
content lacks the slash.  It has been suggested that bogofilter be changed 
to accept messages with non-conformant lines.

The question is:  Should bogofilter continue to require the slash, or not?

David

*** RFC2045 ***

5.1.  Syntax of the Content-Type Header Field

    In the Augmented BNF notation of RFC 822, a Content-Type header field
    value is defined as follows:

      content := "Content-Type" ":" type "/" subtype
                 *(";" parameter)
                 ; Matching of media type and subtype
                 ; is ALWAYS case-insensitive.

...

    Note also that a subtype specification is MANDATORY -- it may not be
    omitted from a Content-Type header field.  As such, there are no
    default subtypes.





More information about the Bogofilter mailing list