Re: [rt-users] Corrupt attachments
The .docx/.xml thing is related to apache's MIME-Type settings. You essentially have to add all the microsoft 2007/10 extensions. It's something to do with .docx files being zipped xml files or something like that... I don't recall the details, but Google will help you. Mike. On Wed, May 2, 2012 at 5:26 PM, Jennings, Barbara wrote: > Folks – we are running 4.0.1 RT and 5.8.8 red hat perl. Larger > attachments are getting corrupted when they are sent out. And from time to > time we get .docx files that are label as .xml and come through burst into > sub dirs. Has anyone else come across this problem? > > Thanks > > Barbara Jennings > Sandia National Laboratories - Albuquerque > Organization 6924 - Policy and Decision Analytics > (505)845-8554 > bjje...@sandia.gov > > > > -- Mike Johnson Datatel Programmer/Analyst Northern Ontario School of Medicine 955 Oliver Road Thunder Bay, ON P7B 5E1 Phone: (807) 766-7331 Email: mike.john...@nosm.ca
[rt-users] Corrupt attachments
Folks - we are running 4.0.1 RT and 5.8.8 red hat perl. Larger attachments are getting corrupted when they are sent out. And from time to time we get .docx files that are label as .xml and come through burst into sub dirs. Has anyone else come across this problem? Thanks Barbara Jennings Sandia National Laboratories - Albuquerque Organization 6924 - Policy and Decision Analytics (505)845-8554 bjje...@sandia.gov
[rt-users] Corrupt Attachments.. but wait
I'm at RT 3.8.2, running on a Fedora core 10 system with perl 5.10.0 and mysql 5.0.84. Ok, ok, I know you all will pound me over the head with suggestions to run UPGRADING.mysql and changing Attachments.Contents to a longblob and setting default character sets to latin1. Maybe I am just not getting something, and maybe I need to be pounded.. I searched and saw a bunch of "you didn't run UPGRADING, go run it... thanks that fixed it" messages... but... that ain't workin for me. Some binary attachments are getting corrupt. Not PDFs. Not PNGs/JPGs/GIFs. It seems only Office type documents are impacted (I suspect all uncommon binary types). I ran UPGRADING.mysql until all it did was create ALTER statements to set the default character set. And yes, I applied the output to my database. without errors. Yes, each time I made a change, I restarted RT3 and restarted the database to avoid caching issues. Interesting points: 1) UPGRADING makes a big deal about setting default character sets to latin1 (and NOT to utf8), but then produces a bunch of ALTER statements that set the default encoding to utf8... did I maybe do something wrong there? 2) The MIME types in the database for the corrupted attachments are text/plain. All others are as appropriate for the type (e.g. image/jpg, etc).. could this be a clue? 3) Since I used the RPM to install RT3, I ran UPGRADING only after the fact. Could this have caused issues? Does anyone have any suggestions? Did I not look in the right place for what I need? Thanks for the help! Here is my create table line for attachments (I just now forced my character_set_client to be latin1 and just noticed the default set below is latin1; it has been utf8 all day... still, no Office document attachments are getting through with readability intact). | Attachments | CREATE TABLE `Attachments` ( `id` int(11) NOT NULL auto_increment, `TransactionId` int(11) NOT NULL default '0', `Parent` int(11) NOT NULL default '0', `MessageId` varchar(160) default NULL, `Subject` varchar(255) default NULL, `Filename` varchar(255) default NULL, `ContentType` varchar(80) default NULL, `ContentEncoding` varchar(80) default NULL, `Content` longblob, `Headers` longtext, `Creator` int(11) NOT NULL default '0', `Created` datetime default NULL, PRIMARY KEY (`id`), KEY `Attachments2` (`TransactionId`), KEY `Attachments3` (`Parent`,`TransactionId`) ) ENGINE=InnoDB AUTO_INCREMENT=7620 DEFAULT CHARSET=latin1 | ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Corrupt Attachments in 3.8.1
I am experiencing the dreaded Attachment Corruption issue with an upgraded 3.8.1 RT. Upgraded from 1.4.3, DID run the DB patch script. Does anyone know of a solution I could try for this issue? Software Versions: RT: 3.8.1 Perl: 5.8.8 Apache: 2.0.54 MySQL: 4.1.20 Thank you in advance. <><><><><><><><> Lorand S. D'Caltan Systems Engineer iSystems LLC (802) 655-8347 x157 <><><><><><><><> CONFIDENTIALITY: The information contained in this message may be privileged and confidential and protected from disclosure. No confidentiality or privilege is waived or lost by any mistransmission. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. Please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Thank you. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
