-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
I recently updated our installation from 2.1.6 to 2.1.7. After the
smooth update our users started to complain about binary attachments
being mangled when send via email.
After some checking I found out, that attachments which are send via
email will be encoded by the Send() function in the Email objects at
around line 269:
<snip>
# content encode
$Self->{EncodeObject}->EncodeOutput(\$Upload{Content});
# attach file to email
</snip>
I did double-check and the otrs did this at least back to 2.1.2, but
only on the way from 2.1.6 to 2.1.7 the behaviour caused problems on our
site.
I "fixed" our issue by commenting the line out, but I'm not sure whether
I just opened up a can of worms.
Could somebody with a more in-depth view of the relevant code paths
please explain to me why the encoding is neccessary at this point?
BTW, we're using UTF-8 for everything and perl 5.8.5 on linux.
- --
Regards,
Wiktor Wodecki
net mobile AG, Zollhof 17, 40221 Duesseldorf, Germany
923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG55v86SNaNRgsl4MRAkdfAJ0T0sukYbyy3WcyUIb3gBxO2yafswCglkLY
OdJay/o2HdydczUv0OBeUWQ=
=uv4m
-----END PGP SIGNATURE-----
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
