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

[Martin Kutschker]

Xavier Perseguers schrieb:
> Hi,
> 
>>> Solution:
>>>
>>> Revert to valid behaviour of 4.2.1 with attached patch.
>>
>> The fix seems pretty obvious, but the extra semi-colon was introduced
>> in revision 3937, that fixed bug #8255: Problems with PHP mail
>> function on Windows. The final patch was reviewed and updated by
>> Dmitry. It would be interesting to have his opinion about this
>> semi-colon problem. Will removing it "unfix" bug #8255?
> 
> OK. That's pretty strange because the method getHTMLContenttype, a few
> lines above already outputs this semicolon. This is not part of the
> specification of email and MailScanner detects it as the null
> MIME-boundary vulnerability that try to bypass spam and virus detection
> systems. As such it generates a "can't analyse message" error and
> quarantine it.

Ah, so the problem is we get *two* semi colons? That is of course
nonense. If getHTMLContenttype() will always add a semi colon we don't
need to add it here again.

Question: What does MailScanner think of single-line headers ending with
a single semi colon?

Masi