Binary attachment transformed (and damaged)

Hi,

I also have a problem with attachments. Maybe it’s a new angle on the
problem, maybe its old.

I have received attachments in e-mail which are correct. However, the
attachment stored in the database and sent out in the mail to our
support staff if different and incorrect. I know for sure because
every incoming e-mail is saved on file before it’s sent on to RT.

I cannot send you the complete e-mail, but here is some description of
the differences between incoming and outgoing e-mail:

  • The MIME “wrapping” of the attachment is slightly different.
  • The line wrapping of the BASE64 encoded data is different.
  • The last part (at least) of the BASE64 encoded data is different.

Here are parts of the e-mails to show the differences. Original e-mail:

------_=_NextPart_001_01C3F0CA.72E1BFFE
Content-Type: application/x-zip-compressed;
name="VMA.zip"
Content-Transfer-Encoding: base64
Content-Description: VMA.zip
Content-Disposition: attachment;
filename=“VMA.zip”

UEsDBAoAAAAAABdLSjAAAAAAAAAAAAAAAAASAAAAVk1BL0FyY2hpdGVjdHVyZXMvUEsDBBQAAAAI
ABdLSjBP1R9j3QYAALArAAAoAAAAVk1BL0FyY2hpdGVjdHVyZXMvQ29udmVudGlvbmFsVmVoaWNs
ZS5tb8VaW0/jOBR+X2n/g8UTSG2UpHehPjAw2pdFGmlH8zJCKE1NG5HGXSeF5d+v75fEcUI7nSJB

AhQAFAAAAAgAkExJMMlLXHUeBQAAJBYAABAAAAAAAAAAAQAgALaBJeQBAFZNQS9UZXN0U3VpdGUu
bW9QSwECFAAUAAAACAAkXEQwvZrkxnIlAABmdQAAEwAAAAAAAAAAACAAtoFx6QEAVk1BL3RyYW5z
X3NtYWxsLmJtcFBLAQIUABQAAAAIABdLSjBmqdb1KwIAAFwHAAAMAAAAAAAAAAEAIAC2gRQPAgBW
TUEvVHlwZXMubW9QSwECFAAKAAAAAAATTUowAAAAAAAAAAAAAAAABAAAAAAAAAAAABAA/0FpEQIA
Vk1BL1BLBQYAAAAAeQB5AD8mAACLEQIAAAA=

------_=_NextPart_001_01C3F0CA.72E1BFFE–

And here are the corresponding parts from the e-mail that was sent from RT:

------------=_1076522667-24528-5
Content-Type: application/x-zip-compressed; name="VMA.zip"
Content-Disposition: inline; filename="VMA.zip"
Content-Transfer-Encoding: base64

UEsDBAoAAAAAABdLSjAAAAAAAAAAAAAAAAASAAAAVk1BL0FyY2hpdGVjdHVy
ZXMvUEsDBBQAAAAIABdLSjBPw5UfY8OdBgAAwrArAAAoAAAAVk1BL0FyY2hp
dGVjdHVyZXMvQ29udmVudGlvbmFsVmVoaWNsZS5tb8OFWltPw6M4FH5facO/
woPDhRNIbcKUwqR3wqE+MDDDmsKXRRppR8OzMkIoTU0bwpHDhl0nwoXDpcOf

eXN0ZW1zL1ZlaGljbGVDb250cm9sbGVyU3Vic3lzdGVtLm1vUEsBAhQAFAAA
AAgAwpBMSTDDiUtcdR4FAAAkFgAAEAAAAAAAAAABACAAwrbCgSXDpAEAVk1B
L1Rlc3RTdWl0ZS5tb1BLAQIUABQAAAAIACRcRDDCvcKaw6TDhnIlAABmdQAA
EwAAAAAAAAAAACAAwrbCgXHDqQEAVk1BL3RyYW5zX3NtYWxsLmJtcFBLAQIU
ABQAAAAIABdLSjBmwqnDlsO1KwIAAFwHAAAMAAAAAAAAAAEAIADCtsKBFA8C
AFZNQS9UeXBlcy5tb1BLAQIUAAoAAAAAABNNSjAAAAAAAAAAAAAAAAAEAAAA
AAAAAAAAEADDv0FpEQIAVk1BL1BLBQYAAAAAeQB5AD8mAADCixECAAAA

------------=_1076522667-24528-5–

I run RT 3.0.8 with MySql 4.0.13 and mod_perl 1.x, RedHat 7.2.
The damaged attachment is about 200 KB, my attachment limit is 10 MB.
To please our e-mail readers I have set

Set($EmailOutputEncoding , 'iso-8859-1');

instead of utf-8 in RT_SiteConfig.pm.

Best regards,

Dag Br�ck
Dynasim AB
Lund, Sweden

Hi,

I also have a problem with attachments. Maybe it’s a new angle on the
problem, maybe its old.

I have received attachments in e-mail which are correct. However, the
attachment stored in the database and sent out in the mail to our
support staff if different and incorrect. I know for sure because
every incoming e-mail is saved on file before it’s sent on to RT.

I run RT 3.0.8 with MySql 4.0.13 and mod_perl 1.x, RedHat 7.2.
The damaged attachment is about 200 KB, my attachment limit is 10 MB.
To please our e-mail readers I have set

Set($EmailOutputEncoding , 'iso-8859-1');

I’m going to take a wild guess that you’re not running perl 5.8.3. It
turns out that using MIME-Tools with perl and unicodetickles a bug in the perl
core that’s broken in all releases before 5.8.3

instead of utf-8 in RT_SiteConfig.pm.

Best regards,

Dag Br�ck
Dynasim AB
Lund, Sweden


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

I’m going to take a wild guess that you’re not running perl 5.8.3.
It turns out that using MIME-Tools with perl and unicode tickles a
bug in the perl core that’s broken in all releases before 5.8.3

That is indeed true. Shouldn’t the RT installation procedure require
perl 5.8.3 then?

Dag Br�ck
Dynasim AB, Sweden

I’m going to take a wild guess that you’re not running perl 5.8.3.
It turns out that using MIME-Tools with perl and unicode tickles a
bug in the perl core that’s broken in all releases before 5.8.3

That is indeed true. Shouldn’t the RT installation procedure require
perl 5.8.3 then?

RT 3.0.8 came out before Perl 5.8.3, but yes, that should probably be
updated.