[TYPO3-core] RFC #9523: class.t3lib_htmlmail.php produces null headers in HTML messages

[Dmitry Dulepov]

Hi!

Xavier Perseguers wrote:
> This is a SVN patch request.
> 
> Branches: 4.2
> 
> BT reference: http://bugs.typo3.org/view.php?id=9523
> 
> Problem:
> 
> When sending a multi-part message in MIME format, the 4.2.2 version of 
> class.t3lib_htmlmail.php outputs an additional semicolon on the 
> Content-Type header definition which is interpreted as a violation by 
> antispam solutions such as MailScanner as it detects a null header. This 
> leads to the message being quarantined.
> 
> Solution:
> 
> Revert to valid behaviour of 4.2.1 with attached patch.

No go :( This will still make invalid MIME. According to the [1] semicolon is possible only if parameters follow. I propose a different solution (attached). This would be correct also from logical point of view because function named getHTMLContentType() should return content type, not a composite text.

[1] http://www.w3.org/Protocols/rfc1341/4_Content-Type.html

-- 
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book
In the blog: http://typo3bloke.net/post-details/duplicate_content_with_realurl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 9523_v2.diff
Type: text/x-diff
Size: 524 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20081009/2e116cd6/attachment.diff