Attachments sent via email suddenly have video/x-flv content type

Suddenly some messages coming in via rt-mailgate are ending up with a
content type of video/x-flv even though the files that are involved are
.csv or .tiff files.
I unfortunately don’t have access to the original messages any more and
email passes through several MTAs before fetchmail delivers to a
procmail rule that calls rt-mailgate, so there’s lots of points where
this could be happening. The strange thing is that so far it appears to
be spontaneous and nothing has changed in our environment. It’s
happened from two different sources as well, but not all mail is
triggering this. Changing the ContentType of the problem entries in the
Attachments table corrected these messages, but I’m expecting for this
to continue to happen when new information comes in.
It doesn’t look to me like rt-mailgate does anything with the content
type that’s passed in the original email other than pass it along to RT,
but my perl fluency leaves a lot to be desired. At this point I’m just
trying to figure out where it makes sense to try to increase logging and
determine if this sounds at all familiar to anyone?

Thanks,
-Jon

Hi,

RT doesn’t change content type of attachments, so if “smart” MUA thinks that
csv is a flv then RT does nothing about that.

Today you can find pretty good mime type detectors and I think it’s better
to preprocess emails instead of implementing anything in RT.15.09.2010 4:23 пользователь “Jon Tollerton” jtollerton@zoominternet.net
написал:

Suddenly some messages coming in via rt-mailgate are ending up with a
content type of video/x-flv even though the files that are involved are .csv
or .tiff files.
I unfortunately don’t have access to the original messages any more and
email passes through several MTAs before fetchmail delivers to a procmail
rule that calls rt-mailgate, so there’s lots of points where this could be
happening. The strange thing is that so far it appears to be spontaneous
and nothing has changed in our environment. It’s happened from two
different sources as well, but not all mail is triggering this. Changing
the ContentType of the problem entries in the Attachments table corrected
these messages, but I’m expecting for this to continue to happen when new
information comes in.
It doesn’t look to me like rt-mailgate does anything with the content type
that’s passed in the original email other than pass it along to RT, but my
perl fluency leaves a lot to be desired. At this point I’m just trying to
figure out where it makes sense to try to increase logging and determine if
this sounds at all familiar to anyone?

Thanks,
-Jon

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year – Learn how to get the most out of RT!