RFC problems ...

[Yann Bachy]

Hello to you all, I've got a slight RFC problem:

My horde used to send attachments of which the filename contains  
accents by the RFC2231 format (header) ... this isn't supported by  
exchange so I activated HORDE's brokenrfc2231 option so it will send  
the RFC2231 header AND the RFC2047 header.

my header now looks like this:
--=_2qw5ii3ew2uo
Content-Type: application/vnd.oasis.opendocument.spreadsheet;
  name="=?utf-8?b?dMOpdMOpw6Aub2Rz?=";
  name*="utf-8''t%C3%A9t%C3%A9%C3%A0.ods"
Content-Disposition: attachment;
  filename="=?utf-8?b?dMOpdMOpw6Aub2Rz?=";
  filename*="utf-8''t%C3%A9t%C3%A9%C3%A0.ods"
Content-Transfer-Encoding: base64

this still doesn't work so I changed HORDE's source to ONLY send  
RFC2047 headers, so my header look like this now:

--=_5jfo4nzjsgi3
Content-Type: application/vnd.oasis.opendocument.spreadsheet;
  name="=?utf-8?b?dMOpdMOpw6Aub2Rz?="
Content-Disposition: attachment;
  filename="=?utf-8?b?dMOpdMOpw6Aub2Rz?="
Content-Transfer-Encoding: base64

the problem I've got is that now MailScanner refuses to analyse the  
message and blocks it automaticly ... is there anyone that has got an  
idea?

Thanks,


--
Yann Bachy