Ticket Forward Problem With Thunderbird

Dear RT users,

We are currently running RT-3.8.1. It appears that the email content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Thanks,

Alan

I have been having the same problem and havent found a solution as of
yet.-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Alan
Cheng
Sent: 21 January 2009 19:23
To: RT Users
Subject: [rt-users] Ticket Forward Problem With Thunderbird

Dear RT users,

We are currently running RT-3.8.1. It appears that the email content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Thanks,

Alan

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

We are currently running RT-3.8.1. It appears that the email content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Hm. It sure seems to be doing MIME encoding by default for me:

It adds a single message/rfc822 part containing the original MIME message.

-> 1 I (0.1K) (text/plain, 7bit, us-ascii)
2 A forwarded message (4.7K) (message/rfc822, binary, )
3 I â”â€> (2.2K) (multipart/mixed, 7bit, )
4 I âœâ€> (0.6K) (text/plain, 8bit, utf-8)
5 I â”â€> (1.3K) (text/html, 8bit, utf-8)

Does the email display properly in Thunderbird for you?

I have forwarded and email and been able to open it in Outlook fine, but Thunderbird remains a problem.-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: 26 January 2009 18:18
To: Alex Young
Cc: RT Users
Subject: Re: [rt-users] Ticket Forward Problem With Thunderbird

We are currently running RT-3.8.1. It appears that the email content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Hm. It sure seems to be doing MIME encoding by default for me:

It adds a single message/rfc822 part containing the original MIME message.

-> 1 I (0.1K) (text/plain, 7bit, us-ascii)
2 A forwarded message (4.7K) (message/rfc822, binary, )
3 I â”â€> (2.2K) (multipart/mixed, 7bit, )
4 I âœâ€> (0.6K) (text/plain, 8bit, utf-8)
5 I â”â€> (1.3K) (text/html, 8bit, utf-8)

I am attaching the original email below to show that the attachment
"forwarded message.eml" is uuencoded. Perhaps there is an option
somewhere to change this to MIME encoding instead? The uuencoded
portion was modified a little bit to protect the content since this is a
real ticket in our system.

Message-ID: 200901271347.n0RDlUIv022736@rt.ias.edu
Cc:Subject: Fwd: [NET #774] TEST ONLY
From: netrt@ias.edu
Date: Tue, 27 Jan 2009 08:47:30 -0500
X-OriginalArrivalTime: 27 Jan 2009 13:47:33.0882 (UTC) FILETIME=[CE69DDA0:01C98085]

This is forward of transaction #5167 of a ticket #774

begin 666 forwarded message.eml
M0V]N=&5N="U4>7!E.B!T97AT+W!L86EN.R!B;W5N9&%R>3TB+2TM+2TM+2TM
M+3U?,3(S,C4V-#@R-"TX.#$P+38R(@T0V]N=&5N="U4<F%N<V9E<BU%;F-O
M9&EN9SH@8FEN8711233545AGHNFGERYEYT344#$N, T
6"U-86EL97(Z($U)
M344M=&]O;’,@-2XT,C8@$5N=&ET>2 U+C0R-BD-"E-U8FIE8W0Z($0F22!7
M96(@4V5R=F5R($)A8VMU< T
1G)O;3H@,C(-“D-O;G1E;G0M3&5N9W1H.B P
$#0H-”@``
`
end

Thanks,

Alan

Alex Young wrote:

Does the email display properly in Thunderbird for you?

I have forwarded and email and been able to open it in Outlook fine, but Thunderbird remains a problem.

-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: 26 January 2009 18:18
To: Alex Young
Cc: RT Users
Subject: Re: [rt-users] Ticket Forward Problem With Thunderbird

We are currently running RT-3.8.1. It appears that the email content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Hm. It sure seems to be doing MIME encoding by default for me:

It adds a single message/rfc822 part containing the original MIME message.

-> 1 I (0.1K) (text/plain, 7bit, us-ascii)
2 A forwarded message (4.7K) (message/rfc822, binary, )
3 I â”â€> (2.2K) (multipart/mixed, 7bit, )
4 I âœâ€> (0.6K) (text/plain, 8bit, utf-8)
5 I â”â€> (1.3K) (text/html, 8bit, utf-8)


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Alan Cheng chenga@ias.edu +1 609-734-8169
UNIX Systems Administration Institute for Advanced Study

There must be a configuration setting with the Perl mailtools
package. I have 3.8.1 stock and it forwards in MIME format. I just
tested…

3809219478]Gen-xit Netgear CISCO 3COM MRV Transition
Content-type: multipart/mixed; boundary="----------=_1233082584-11855-2"

This is a multi-part message in MIME format…

------------=_1233082584-11855-2

This is forward of transaction #144 of a ticket #6

------------=_1233082584-11855-2
Content-Type: message/rfc822
Content-Disposition: attachment
Content-Transfer-Encoding: binary
Content-Description: forwarded message

…etcOn Jan 27, 2009, at 5:54 AM, Alan Cheng wrote:

I am attaching the original email below to show that the attachment
"forwarded message.eml" is uuencoded. Perhaps there is an option
somewhere to change this to MIME encoding instead? The uuencoded
portion was modified a little bit to protect the content since this
is a real ticket in our system.

Message-ID: 200901271347.n0RDlUIv022736@rt.ias.edu
To: chenga@ias.edu
Cc:
Subject: Fwd: [NET #774] TEST ONLY
From: netrt@ias.edu
Date: Tue, 27 Jan 2009 08:47:30 -0500
X-OriginalArrivalTime: 27 Jan 2009 13:47:33.0882 (UTC)
FILETIME=[CE69DDA0:01C98085]

This is forward of transaction #5167 of a ticket #774

begin 666 forwarded message.eml
M0V]N=&5N="U4>7!E.B!T97AT+W!L86EN.R!B;W5N9&%R>3TB+2TM+2TM+2TM
M+3U?,3(S,C4V-#@R-"TX.#$P+38R(@T0V]N=&5N="U4<F%N<V9E<BU%;F-O
M9&EN9SH@8FEN8711233545AGHNFGERYEYT344#$N, T
6"U-86EL97(Z($U)
M344M=&]O;’,@-2XT,C8@$5N=&ET>2 U+C0R-BD-"E-U8FIE8W0Z($0F22!7
M96(@4V5R=F5R($)A8VMU< T
1G)O;3H@,C(-“D-O;G1E;G0M3&5N9W1H.B P
$#0H-”@``
`
end

Thanks,

Alan

Alex Young wrote:

Does the email display properly in Thunderbird for you?

I have forwarded and email and been able to open it in Outlook
fine, but Thunderbird remains a problem.

-----Original Message-----
From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: 26 January 2009 18:18
To: Alex Young
Cc: RT Users
Subject: Re: [rt-users] Ticket Forward Problem With Thunderbird

We are currently running RT-3.8.1. It appears that the email
content
(message.eml) is uuencoded when RT forwards a ticket. Thunderbird
doesn’t seem to like this and cannot display the forwarding
email. Is
there a way to configure RT to do MIME encoding instead? Any
suggestions are greatly appreciated.

Hm. It sure seems to be doing MIME encoding by default for me:

It adds a single message/rfc822 part containing the original MIME
message.

-> 1 I (0.1K) (text/plain, 7bit, us-ascii)
2 A forwarded message (4.7K) (message/rfc822, binary, )
3 I â”â€> (2.2K) (multipart/mixed, 7bit, )
4 I âœâ€> (0.6K) (text/plain, 8bit, utf-8)
5 I â”â€> (1.3K) (text/html, 8bit, utf-8)


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


Alan Cheng chenga@ias.edu +1 609-734-8169
UNIX Systems Administration Institute for Advanced Study


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness

I am attaching the original email below to show that the attachment
"forwarded message.eml" is uuencoded. Perhaps there is an option
somewhere to change this to MIME encoding instead? The uuencoded
portion was modified a little bit to protect the content since this is a
real ticket in our system.

The relevant code reads like this:
$mail->attach(
Type => ‘message/rfc822’,
Disposition => ‘attachment’,
Description => ‘forwarded message’,
Data => $entity->as_string,
);

Perhaps your local client is massaging the received message in some way.

Why don’t you try forwarding a transaction to my address?

Hi Jesse,

What a surprise!!! Indeed it looks like Thunderbird was massaging the
forwarding email… I forwarded the very same ticket to my Hotmail
account and it looked just fine. As soon as I forwarded it to my local
work email account and have Thunderbird open it, the attachment became
uuencoded. This is probably done by some plug-in? I will investigate
and report back if I find any information.

Thanks very much for your help!

Alan

Jesse Vincent wrote:

I am attaching the original email below to show that the attachment
"forwarded message.eml" is uuencoded. Perhaps there is an option
somewhere to change this to MIME encoding instead? The uuencoded
portion was modified a little bit to protect the content since this is a
real ticket in our system.

The relevant code reads like this:
$mail->attach(
Type => ‘message/rfc822’,
Disposition => ‘attachment’,
Description => ‘forwarded message’,
Data => $entity->as_string,
);

Perhaps your local client is massaging the received message in some way.

Why don’t you try forwarding a transaction to my address?

Alan Cheng chenga@ias.edu +1 609-734-8169
UNIX Systems Administration Institute for Advanced Study