RT makes all messages multipart/mixed -- why?

RT Users
1

Would it be possible to make RT send out messages with just a single
attachment (principally messages where the content-type is text/plain)
with that content-type, instead of as multipart/mixed with a single
part? Or is there some reason not to do this? Specifically, the mail
gateway changes messages of the former form to the latter form.

-Dan

2

Would it be possible to make RT send out messages with just a single
attachment (principally messages where the content-type is text/plain)
with that content-type, instead of as multipart/mixed with a single
part? Or is there some reason not to do this? Specifically, the mail
gateway changes messages of the former form to the latter form.

It’s a side-effect of RT3’s attachments support. There’s an open bug to
use MIME::Entity’s make_singlepart() method to smash messages down to
single-part where possible.

-Dan

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

3

Would it be possible to make RT send out messages with just a single
attachment (principally messages where the content-type is text/plain)
with that content-type, instead of as multipart/mixed with a single
part? Or is there some reason not to do this? Specifically, the mail
gateway changes messages of the former form to the latter form.

It’s a side-effect of RT3’s attachments support. There’s an open bug to
use MIME::Entity’s make_singlepart() method to smash messages down to
single-part where possible.

Oh, sounds good.

-Dan

4

Daniel E. Eisenbud scripted ::

It’s a side-effect of RT3’s attachments support. There’s an open bug to
use MIME::Entity’s make_singlepart() method to smash messages down to
single-part where possible.

Oh, sounds good.

-Dan

Great, any idea what the time frame will be?