[rt-users] MIME parsing not recursive?

[Smylers]

Bruce Campbell wrote:

> On Fri, 12 Jul 2002, Stephane Bortzmeyer wrote:
>
> > But, if the attachement is itself made of parts (MIME is recursive)
> > ... RT only displays the "top level" part, when the user clicks on
> > it, it sees the encoded subparts.
> >
> > Is it a limit of RT, a feature or a misconfiguration from me?
>
> I think RT is only going one level down.  The table structure
> encourages nested attachments, but the process putting them in
> doesn't.  RT bug.

I think we've encountered another 'RT' limit with nested mime parts.
I'm not completed sure yet[*0], but it's possibly something like this:

  * If somebody sends an attachment the mail has a media type of
    multipart/mixed, the first part of which is text/plain and gets
    forwarded in templates as {$Transaction->Content()}.

  * If somebody sends plain and HTML mail then the media type is
    multipart/alternative, the text/plain part of which gets forwarded
    in {$Transaction->Content()}.

  * If somebody has the temerity to do both of the above then the mail
    has a media type of multipart/mixed, the first part of which has a
    media type of multipart/alternative, which in turn contains the
    actual message.  {$Transaction->Content()} is empty, so the
    forwarded mail appears to be messageless.

The result of the above is that we have a tendency to ignore messages
from people who send HTML mails with 'Word' documents attached.
Actually, maybe that isn't such a bad thing ...

[*0]  And I fear that I'll have to find a Windows computer with a
sufficiently broken MUA to try it out.

Smylers
-- 
GBdirect
http://www.gbdirect.co.uk/