TYPO3 Core

Hardcoded function sends notify mails with unproperly encoded headers. That leads to a protocol violation, when sitename contains special chars like umlauts.

"INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER SECTION"

The attached patch will work at least for TYPO3 versions 4.3.2 until current 4.4 trunk.

The RFC 5322 document specifies rules for forming internet messages.
It does not allow the use of characters with codes above 127 to be
used directly (non-encoded) in a mail header section.

If such characters (e.g. with diacritics) from ISO Latin or other
  alphabets need to be included in a header section, these characters
  need to be properly encoded according to RFC 2047. Such encoding
  is often done transparently by mail reader (MUA), but if automatic
  encoding is not available (e.g. by some older MUA) it is a user's
  responsibility to avoid using such characters in a header section,
  or to encode them manually. Typically the offending header fields
  in this category are 'Subject', 'Organization', and comment fields
  or display names in e-mail addresses of 'From', 'To' or 'Cc'.

Sometimes such invalid header fields are inserted automatically
  by some MUA, MTA, content filter, or other mail handling service.
  If this is the case, such service needs to be fixed or properly
  configured. Typically the offending header fields in this category
  are 'Date', 'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc.

(issue imported from #M14406)