BODYSTRUCTURE question

[Rob Mueller]

> As of RFC 2045, Content-Type syntax should be:
> content := "Content-Type" ":" type "/" subtype *(";" parameter)
>
> Shouldn't cyrus still interpret this as text/html, despite the illegal " 
> boundary..." line following Content-Type ?

I've noticed this too, and while it clealy is broken with respect to the 
RFC, it's annoying to deal with. In the meantime, I fix up these headers in 
our custom perl lmtp proxy system with a regexp like this on Content-Type 
headers...

  # Fix up broken Content-Type headers missing ; between
  # type and first parameter
  s{^([\w\-]+/[\w\-]+)(\s+[\w\-]+\s*=)}{$1;$2};

Rob