[sylpheed:30661] Re: MIME decoding is not done

[Joachim Selinger]

Hallo Stefaan!

On Sat, 30 Dec 2006 20:03:29 +0100
Stefaan A Eeckels <Stefaan.Eeckels at ecc.lu> wrote:

SAE> On Fri, 29 Dec 2006 21:51:45 +0100
SAE> Joachim Selinger <selinger at bawue.de> wrote:
SAE> 
SAE> > I'm sure the sender is in error and violates tons of RFCs ;-) but
SAE> > would anyone be able to tell me what the violation is, so that I can
SAE> > complain competently to the sender? It's an automated system telling
SAE> > me about my ordered photo prints.
SAE>
SAE> The problem is in the following header line:
SAE> 
SAE> Content-Type: multipart/mixed;
SAE>               boundary = b38d8690f68df47e892692bd82cda2ff7
SAE> 
SAE> Notice the spaces around the equals sign. If you remove them:
SAE> 
SAE> Content-Type: multipart/mixed;
SAE>               boundary=b38d8690f68df47e892692bd82cda2ff7
SAE> 
SAE> Sylpheed decodes the message correctly. 

You are right. I can confirm that. :-)

SAE> I believe that the spaces surrounding the equals sign are a violation
SAE> of RFC2045, which says the following about the "Content-Type" syntax
SAE> (section 5.1):
SAE> 
SAE> | parameter := attribute "=" value
SAE> 
SAE> Notice that spaces are not allowed between "attribute" and "value". 
SAE> 
SAE> A happy and prosperous 2007 to all Sylpheed users, and special wishes
SAE> for a fun and productive coding year go, of course, to Hiroyuki. 

Thanks for confirming my suspicion. :-) I will e-Mail pixelnet about
it and hope that they'll fix it. 

A happy New Year to all of you!

Jocki