Re: Multiple Content-Location headers

>But back to the present: Mail archives in the Web are typically handled
>by a program that takes mail messages as input and generates HTML as a set
>of Web documents. An equally plausible extension to handle mhtml is
>to retrieve the attached documents at the time the HTML is generated
>from the mail message, rather than presuming the data is inline.
>This requires no protocol support beyond what exists today (though
>arguably is not as atomic in nature). 

Interestingly enough, one MIME-SGML proposal (the one that MIME-HTML
is *not* based upon) could handle both cases perfectly well, even
without multipart/related.