On 03 May 2002, Matt Sergeant wrote:
> On Fri, 2002-05-03 at 12:31, Daniel Pittman wrote:
>> >> Cool. Does it correctly handle cases such as MIME digest messages
>> >> containing nested multipart/related and multipart/alternative
>> >> content?
>> >
>> > Well we don't care if there's multiply nested stuff - because
>> > anything deeper than the first level is just an attachment
>>
>> Bzzzt. Wrong. That, there, is the sort of thinking that results in
>> quite a number of broken MUA implementations.
>
> Perhaps you could enlighten me then? At the moment it parses
> recursively until it either finds the first text/* parts and creates
> body sections out of those, and then makes attachments from the rest,
> all following the MIME rfcs. Now you've got me wondering whether it
> does the right thing or not.
Any MIME part with a "Content-Disposition: inline" should be displayed
as inline text by the MUA. This is used, for example, to send messages
that contain two different character encodings in the one message.
Daniel
--
In a minute there is time
For decisions and revisions which a minute will reverse.
-- T.S. Eliot
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
