RT doesn't decode attachment file names

RT Users
1

One of our transactions has an attachment with the name
“FS BIO =?iso-8859-1?Q?PR=C4SENTIERT2=2Edoc?=” - RT (or whatever
module RT uses for MIME parsing) obviously forgot to decode this.

Is this caused by a problem in my installation, or is it a bug? If
it’s a bug, where/how do I report it?

Sebastian Flothow
sebastian@flothow.de
#include <stddisclaimer.h>

2

One of our transactions has an attachment with the name
“FS BIO =?iso-8859-1?Q?PR=C4SENTIERT2=2Edoc?=” - RT (or whatever
module RT uses for MIME parsing) obviously forgot to decode this.

Depends, are you running any mods to deal with non-us-ascii charsets (the
iso-8859-1 bit) ? (which normally don’t touch the apparent filename)

Is this caused by a problem in my installation, or is it a bug? If
it’s a bug, where/how do I report it?

To report a bug in RT, you must first obtain two chickens, three brown
eggs, 12 black candles and a well thumbed copy of the MySQL reference
manual. On page 666 of this document is a small footnote describing what
to do with two chickens and 3 eggs. Some extra equipment may be required,
and your local kitchen supply store is the best bet for this.

Once you have enjoyed your repast (for it is written, do not attempt to
report a bug on an empty stomach), log onto your computer using the 12
candles arranged in a careful floral arrangement for illumination.
Depending on your $LOCALE, curious side effects may occur in an attempt to
distract you. Do not let these edge daemons divert you from your
annointed task.

With great care and precision, that is, fully and carefully, describe in
full the problem to the best of your ability in an email to
‘rt-2.0-bugs@fsck.com’. Through the magic of RT itself, right before your
very eyes, a ticket number will be generated.

A horde of daemons will then try to replicate your bug (gene splicing on
these babies is a hard job, let me tell you!), and will eventually respond
with one of ‘that sounds like bug #1234 or a varient thereof, try [complex
notation]’ or ‘hrm, thats a new one, try [complex notation]’.

Once you have received [complex notation], you will require further
Illumination. Begin with Trimethylxanthine[1], then proceed up your
preferred stimulant chain until Illumination is thus achieved.

( or in other words, find out as much as you can about the bug, and dash
it off to rt-2.0-bugs@fsck.com )

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations

[1] Caffiene for those not keeping up with basic biochemistry.

3

One of our transactions has an attachment with the name
“FS BIO =?iso-8859-1?Q?PR=C4SENTIERT2=2Edoc?=” - RT (or whatever
module RT uses for MIME parsing) obviously forgot to decode this.

Is this caused by a problem in my installation, or is it a bug? If
it’s a bug, where/how do I report it?

And on a serious note, a few flaws in MIME::Tools has just been reported
to Bugtraq (Florian probably knows this already :wink: ), including:

Problem 3: Incorrect concatenation of encoded MIME words.
MIME::Tools does not remove the space from this example:

    	(=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=)

to yield (ab); instead, it yields "(a b)"  Some MUA's use encoded MIME
words in the Content-Type or Content-Disposition fields.  Although
this is specifically disallowed by RFC 2047, again, some Windoze mail
clients may make the "obvious" interpretation and decode the words.

So, not a bug with RT, but the underlying module it depends on.

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B                      Operations
4

One of our transactions has an attachment with the name
“FS BIO =?iso-8859-1?Q?PR=C4SENTIERT2=2Edoc?=” - RT (or whatever
module RT uses for MIME parsing) obviously forgot to decode this.
[SNIP]
words in the Content-Type or Content-Disposition fields. Although
this is specifically disallowed by RFC 2047, again, some Windoze mail
clients may make the “obvious” interpretation and decode the words.

So, not a bug with RT, but the underlying module it depends on.

Not even so much a bug with the module, as it is yet another failure
of Microsoft to comply with Internet standards…

Derek Martin
Lead Network Engineer
ddm@skillsoft.com
(603)324-3000 x516