"Neil Durant" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Garth Wallace <[EMAIL PROTECTED]> writes
> >> In particular, if you send a multipart message of the form:
> >>
> >> Paragraph of text
> >>
> >> ## (this is some attachment)
> >>
> >> Paragraph of text
> >>
> >> ..then the 2nd paragraph of text should appear in exactly the same form
> >> in the message (in raw form) than the first paragraph, so it's no more
> >> likely to be intended to be a text attachment than the first paragraph,
> >> which is generally shown as text.
> >
> >Again, depends on Content-Disposition. That's what that
> >header is for.
>
> So if the text parts (the surrounding paragraphs) have no
> Content-Disposition header? My understanding of the RFCs is for such
> text parts to be displayed the same as each other, if they have the same
> part headers. This is where many user agents break down, showing the
> first as an inline paragraph of text and the second as a separate text
> attachment.
If there's no Content-Disposition header, it's up to the UA.
AIUI, it's perfectly legitimate for a UA to display a text
part of a multipart message as an attachment if the sender
did not express a preference.
