Hmm, lemme try this a third time.. I would really appreciate some help. Basically, images and PDFs that are attached to requests or added as attachments later through the web interface are stored and retrieved without any issues. Any other type: zip files, office documents, etc, get stored in the Attachments table as text/plain whether they are added via e-mail request or via the web interface.
Why is the content type not being identified or recorded correctly in the database? Where should I look to debug this problem further? That charset="utf-8" looks suspicious... I *think* I've done all the upgrades properly... ran the upgrade schema script... I'm on perl 5.10.0.x, Mysql 5.0.84, rt 3.8.2 Thanks for any help you folks can give! -Eric Here is a sample entry from the Header column in the Attachments table with an office document. MIME-Version: 1.0 Subject: Checklist_for_Booster_Application.doc X-Mailer: MIME-tools 5.427 (Entity 5.427) Content-Type: text/plain; charset="utf-8"; name="Checklist_for_Booster_Application.doc" Content-Disposition: inline; filename="Checklist_for_Booster_Application.doc" Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 Content-Length: 35778 Here is one for a PDF file that I added to that same ticket mere moments earlier. MIME-Version: 1.0 Subject: 2009 Home School Flyer.pdf X-Mailer: MIME-tools 5.427 (Entity 5.427) Content-Type: application/pdf; name="2009 Home School Flyer.pdf" Content-Disposition: inline; filename="2009 Home School Flyer.pdf" Content-Transfer-Encoding: base64 Content-Length: 988569 _______________________________________________ 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
