Looking at the code for 3.8.6, it looks like something has changed in that
code, but I'm not sure this issue is fixed.

Here's the structure of an email where this happens:

   ID PARENT SUBJECT         FILENAME            CONTENTTYPE
----- ------ --------------- ------------------- ---------------------
53345      0 email subject   NULL                multipart/mixed
53346  53345 NULL            NULL                multipart/alternative
53347  53346 NULL            NULL                text/plain
53348  53346 NULL            NULL                text/html
53349  53345 NULL            filename.txt        text/plain

But if RT sees a multipart/* as the main message, it assumes the first
text/plain it finds is the right one. But if the first attachment is in a
multipart/mixed is a multipart/alternative, then you have to get the first
text/plain in there.

--
Mathieu Longtin
1-514-803-8977


On Wed, Nov 11, 2009 at 9:22 AM, Potla, Ashish Bassaliel <
[email protected]> wrote:

>  I see this too. Is there any fix out there for this?
>
> -Ashish
>  ------------------------------
> *From:* [email protected] [
> [email protected]] On Behalf Of Mathieu Longtin [
> [email protected]]
> *Sent:* Wednesday, November 11, 2009 7:43 PM
> *To:* RT Users Mailing List (E-mail)
> *Subject:* [rt-users] text attachment get mixed up
>
>  When a text attachment is added to a ticket, the emails RT sends put the
> attachment as body, and the actual message as an attachment.
>
> It does that both when creating a ticket using the web interface, and when
> sending an email with an attachment.
>
> It's probably that the code doesn't pick the right plain/text attachment.
>
> This is RT 3.8.5.
>
> --
> Mathieu Longtin
> 1-514-803-8977
>
_______________________________________________
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

Reply via email to