Hi List,<br><br><br>I think there is a problem with mime-encoded header handling.<br>The following code (and comments) are in I18N.pm file (3.8.7):<br>-----<br># It's legal for headers to contain mime-encoded commas and semicolons which<br>
# should not be treated as address separators. (Encoding == quoting here)<br>#<br># until this is fixed, we must escape any string containing a comma or semicolon<br># this is only a bandaid<br># Some _other_ MUAs encode quotes _already_, and double quotes<br>
# confuse us a lot, so only quote it if it isn't quoted<br># already.<br>$enc_str = qq{"$enc_str"} if $enc_str =~ /[,;]/ and $enc_str !~ /^".*"$/;<br>-----<br>It is good for To, Cc and other fields because non-ascii, encoded names before email<br>
addresses can containt commas and semicolons, for example:<br>NonAscii, Name <<a href="mailto:foo@bar.com">foo@bar.com</a>><br>becomes<br>"NonAscii, Name" <<a href="mailto:foo@bar.com">foo@bar.com</a>><br>
and that's why commas don't cause problems, but it's not good for subject.<br>If I have a non-ascii subject with comma or semicolon it will be quoted.<br>Non-ascii, subject<br>becomes<br>"Non-ascii, subject"<br>
It's not good but tolerable. But if I have a long non-ascii subject, I will get<br>a worse thing:<br>It is a very long non ascii subject with commas, in the header, it will be encoded and multiline<br>becomes something like this:<br>
"It is a very long non ascii subject with commas, in"" the header, it will be encoded and multiline"<br>It's not good if you parse the subject, and may annoy your users.<br><br>I attached a patch that I use to avoid this problem. It's maybe useful but maybe you have a better solution<br>
or opinion about this problem. Please let me know if there is!<br><br><br>Thanks,<br clear="all">--<br>Bekeny<br>Docca OutSource IT Ltd<br>