Re: Comments on Malformed Message BCP draft

On 4/15/2011 7:09 PM, [email protected] wrote:
> More like "almost always". I estimate we average one complaint that turns out
> to be message maformation every week or two, and it's been this way for almost
> two decades. But despite the fact we as a matter of policy *always* push back
> saying "fix the actual problem", I can't recall more than a handful of cases
> where this resulted in the actual problem being tracked down and fixed.
> Workarounds are a lot easier than, say, getting a printer manufacturer
> to update their firmware so it doesn't produce this content-type header:


Receive-side workarounds, rather than rejections of protocol/format violations, 
seems to be an inherent state of affairs for apps protocols.  No one likes that 
fact, but no one has come up with a way to change the reality.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net