Re: [Changing Kannel MIME parsing] (was: Re: Wappush Problems)

Paul Keogh wrote:
> 
> My understanding is that the MIME RFCs specify a canonical encoding of
> a "blank line" or separator of <cr><lf>. The obvious use of this is
> to get around differences across operating systems in this regard.
> (Think UNIX vs. Microsoft).
> 
> So accepting a <lf> as a MIME separator may well get you over the
> problem of a broken peer implementation but it will potentially
> cause problems elsewhere. So, as Aarno suggests, if you need
> to break MIME functionality, you should have to explicitly turn it
> on, in the full knowledge of what you are doing. It should not
> go into the code base as a default behaviour.

ok, as Paul vetoes for this, I'm also for a config directive.

Aarno, can you add the 

  strict-mime-parsing = [yes|no] 

as boolean config directive and make it default to yes, hence leaving
the existing behaviour?

To which group should this go? wapbox? 

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are