Content-Type: text

[David Relson]

At 09:54 PM 7/20/03, Matthias Andree wrote:
>David Relson <relson at osagesoftware.com> writes:
>
> > 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?
>
>No slash -> spamicity := 1.

It's tempting :-)

><ducks & runs for cover>
>
>Seriously, we should accept text and treat it as text/plain. Any other
>types that we guess shall be application/octet-stream.

File mime.c has been modified, "make check" has succeeded, and the code has 
been submitted to cvs.