iMS 5.1 : uuencoded attachments bypass conversion channel ?!

it seems that uuencoded attachments, having a mime header of

--Boundary_(ID_us9m7TkTL9RgCQ1Ho9qBjg)

Content-type: application/pdf; name="Unix-SedOneLiners_en.pdf"

Content-transfer-encoding: x-uuencode

Content-disposition: attachment; filename="Unix-SedOneLiners_en.pdf"

are not recognized by the conversion channel, which passes them right away. having set master_debug and slave debug on the conversion channel, i see this in the log :

13:20:16.22: Processing part 2.

13:20:16.22:Content-transfer-encoding is bogus; no conversion possible.

13:20:16.22:Performing simple bodypart copy.

13:20:16.24: Finished with this part.

13:20:16.26: Processing successful. Terminate submission.

As the the conversion channel seems to be the most easy way to implement an email virusscanner, this means that uuencoded attachments are not checked by the conversion channel.

The same goes if you use the "secret" thurman keyword to correctly split uuencoded part which are stuck in the main body of the message. Those "corrected" attachments are also "content-type-encoding is bogus"

anybody has a way howto correctly pass uuencoded attachments via the conversion channel ?

[1250 byte] By [709040] at [2007-11-25 7:09:31]
# 1

I do not think you have to worry about what you are seeing. Rather the conversion channel will hand off this part to your virus scanner which then has to deal with it. If you were trying to actually perform some conversion from say wordperfect to staroffice then you'd have to be concerned.

I just tested thurman on 5.1 and it works, the x-uuencode is converted over to base64 before the message arrives at the conversion channel. Rememeber to place the thurman keyword on the source channel.

708686 at 2007-6-29 17:41:07 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...