Bad MIME handling HTML emails?

RT Users
1

Hello,

I have a strange problem probably MIME handling related. Sometimes when
user creates ticket via email and someone tries to reply to this
transaction body of requestors email is not included or plain text
attachment is included instead of body content (quoted) as required.
It seems like RT has problem handling mails with HTML attachments. May I
update MIME::Tools ?

RT3.2.2, Perl 5.8.4, MIME::Tools 5.413

+++ MAIL 1 +++ Mon May 23 08:57:26 2005
When I try to reply on mail1, requestor text is not included in. Strange
is that attachments in requestors corespondence are before mail body
(text or html).

X-Mimeole: Produced By Microsoft Exchange V6.5.7226.0

Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C55F64.AB3C7916"
Content-Description: Nov� obr�zek.jpg
Content-Type: "Nov� obr�zek.jpg"
Content-Disposition: "Nov� obr�zek.jpg"
Content-Transfer-Encoding: base64
Content-Length: 237891

Content-Description: GHJ II 4361-doplneni+gesce.doc
content-type: application/msword; name="GHJ II
4361-doplneni+gesce.doc"
content-disposition: attachment; filename="GHJ II
4361-doplneni+gesce.doc"
Content-Transfer-Encoding: base64
Content-Length: 51712

Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C55F64.AB3C7916"
content-type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-2
Content-Length: 3928

Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-2
Content-Length: 8277

+++ MAIL 2 +++ Mon May 23 11:50:17 2005
Same ticket, owner did a reply to requestor and requestor reply also
(mail2). Afaik same MUA used (There is no html alternative part, i think
its because requestor has something like “send plain text only in reply
to plain text emails” and “send html + text by default”). When i hit a
reply everything is ok. (note that attachments are after email body)

X-Mimeole: Produced By Microsoft Exchange V6.5.7226.0

Content-Type: multipart/mixed;
boundary="----_=_NextPart_001_01C55F75.CB395BD6"
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-2
X-RT-Original-Encoding: utf-8
Content-Length: 1530

Content-Description: P�eklopeno do 20050523.jpg
Content-Type: "P�eklopeno do 20050523.jpg"
Content-Disposition: "P�eklopeno do 20050523.jpg"
Content-Transfer-Encoding: base64
Content-Length: 286388

Content-Description: P�eklopeno a smaz�no 20050523.jpg
Content-Type: "P�eklopeno a smaz�no 20050523.jpg"
Content-Disposition: "P�eklopeno a smaz�no 20050523.jpg"
Content-Transfer-Encoding: base64
Content-Length: 325148

+++ MAIL 3 +++
When I try to reply on next mail (mail 3) content of LogFile.txt is
quoted! instead of mail body. Interesting that via web everything is OK
(body is displayed as body).

Content-Type: multipart/mixed; boundary="=mixed 0022102DC1256FEA="
MIME-Version: 1.0
Content-Type: text/html; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: ISO-8859-2
X-RT-Original-Encoding: ISO-8859-2
Content-Length: 815

content-type: application/octet-stream;
name="ControlFile.ini"
content-disposition: attachment; filename="ControlFile.ini"
Content-Transfer-Encoding: base64
Content-Length: 440

content-type: application/octet-stream;
name="UY-SAK-04-O-20050098234098230492000000[1].cab.osf"
content-disposition: attachment;
filename="UY-SAK-04-O-20050098234098230492000000[1].cab.osf"
Content-Transfer-Encoding: base64
Content-Length: 114926

content-type: application/octet-stream;
name="ENVELOPE_XY.file"
content-disposition: attachment; filename="ENVELOPE_XY.file"
Content-Transfer-Encoding: base64
Content-Length: 1955

content-type: text/plain; charset=“utf-8”;
name="LogFile.txt"
content-disposition: attachment; filename="LogFile.txt"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-1
X-RT-Original-Encoding: utf-8
Content-Length: 5486

content-type: application/octet-stream;
name="DF02339[1].SH09.DOC"
content-disposition: attachment; filename="DF02339[1].SH09.DOC"
Content-Transfer-Encoding: base64
Content-Length: 62464

content-type: text/html; name="UD0i73261].VB02.HTM"
content-disposition: attachment; filename="UD0i73261].VB02.HTM"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: iso-8859-1
X-RT-Original-Encoding: iso-8859-1
Content-Length: 64990

content-type: application/octet-stream;
name="AK07923[1].NB02.PDF"
content-disposition: attachment; filename="AK07923[1].NB02.PDF"
Content-Transfer-Encoding: base64
Content-Length: 87524

content-type: text/plain; name="Subject.txt"
content-disposition: attachment; filename="Subject.txt"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
Content-Length: 101

Thanx for your help
Ruza

2

I have a strange problem probably MIME handling related. Sometimes when
user creates ticket via email and someone tries to reply to this
transaction body of requestors email is not included or plain text
attachment is included instead of body content (quoted) as required.
It seems like RT has problem handling mails with HTML attachments. May I
update MIME::Tools ?

RT3.2.2, Perl 5.8.4, MIME::Tools 5.413

We’ve improved this a lot in RT 3.4. Give 3.4.2 a shot?

Jesse

3

Jesse Vincent wrote:

I have a strange problem probably MIME handling related. Sometimes when
user creates ticket via email and someone tries to reply to this
transaction body of requestors email is not included or plain text
attachment is included instead of body content (quoted) as required.
It seems like RT has problem handling mails with HTML attachments. May I
update MIME::Tools ?

RT3.2.2, Perl 5.8.4, MIME::Tools 5.413

We’ve improved this a lot in RT 3.4. Give 3.4.2 a shot?

Jesse

No :frowning: I upgraded 3.2.2 to 3.4.2 on my development machine to different
directory, did db objects upgrade:

~/rt-3.4.2# for i in 3.3.0 3.3.11;do
/opt/rt_34/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action schema --datadir etc/upgrade/$i ;
/opt/rt_34/sbin/rt-setup-database --dba root --prompt-for-dba-password
–action acl --datadir etc/upgrade/$i;/opt/eu_rt/sbin/rt-setup-database
–dba root --prompt-for-dba-password --action insert --datadir
etc/upgrade/$i;done

and behavior is still the same. I also tried upgrade MIME::Base64 5.411 → 5.417 and MIME::Tools 3.01 → 3.05.

Ruza

4

Jesse Vincent wrote:

I have a strange problem probably MIME handling related. Sometimes when
user creates ticket via email and someone tries to reply to this
transaction body of requestors email is not included or plain text
attachment is included instead of body content (quoted) as required.
It seems like RT has problem handling mails with HTML attachments. May I
update MIME::Tools ?

RT3.2.2, Perl 5.8.4, MIME::Tools 5.413

We’ve improved this a lot in RT 3.4. Give 3.4.2 a shot?

Jesse

Can you send a sample message to me?

5

Sent to Jesse.

mail to Jesse

Hello,

problematic mail I reported contains sensitive information, so I did
some test mails which acts the same in RT3 web interface (content of
text attachment is offered as quoted instead of mail body in Reply action).

Two are from Outlook Express 6 (Win XP) and one from ThunderBird (Linux)

It seems to me, RT3 have a problem if mail body contains html form and
plain text file is attached.

Thanks a lot
Ruza

Jesse Vincent wrote:

Jesse Vincent wrote:

I have a strange problem probably MIME handling related. Sometimes when
user creates ticket via email and someone tries to reply to this
transaction body of requestors email is not included or plain text
attachment is included instead of body content (quoted) as required.
It seems like RT has problem handling mails with HTML attachments. May I
update MIME::Tools ?

RT3.2.2, Perl 5.8.4, MIME::Tools 5.413

We’ve improved this a lot in RT 3.4. Give 3.4.2 a shot?

Jesse

Can you send a sample message to me?

Pavel Ruzicka, ICZ