Dear OTRS-Users/-Admins,
we actually use OTRS 5.0.22.
We recognise problems regarding the mime encoding of the subject line when
creating new email tickets. As germans we sometimes use 8-bit encodings (UTF-8)
when creating tickets. If the tickets subject contains several words and more
than one word contains a non-ascii character, each word for itself is base64
encoded instead of the whole subject line.
This is not compliant to RFC 2047 as stated in the manual page of perl module
MIME::Words:
"Warning: this is a quick-and-dirty solution, intended for character sets which
overlap ASCII. It does not comply with the RFC 2047 rules regarding the use of
encoded words in message headers. You may want to roll your own variant, using
encode_mimeword(), for your application. Thanks to Jan Kasprzak for reminding
me about this problem."
I patched this behaviour by changing Kernel/System/Email.pm using
encode_mimeword instead of encode_mimewords
sub _EncodeMIMEWords {
my ( $Self, %Param ) = @_;
# return if no content is given
return '' if !defined $Param{Line};
return MIME::Words::encode_mimeword(
Encode::encode(
$Param{Charset},
$Param{Line},
),
'Q', $Param{Charset},
);
}
I think/hope that this solution implements RFC compliant behaviour. Maybe this
version should be included in future otrs releases?
--
Kind regards
Christoph
_________________________________________
Uni Koblenz, Computing Centre, Office A 022
Postfach 201602, 56016 Koblenz
Fon: +49 261 287-1311, Fax: -100 1311
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
