On Mon, 2003-01-27 at 13:29, Arthur S. Alexion wrote: > On Sun, 2003-01-26 at 18:34, Jeffrey Stedfast wrote: > > Actually, I just thought of a way that they *might* be handling it if > > indeed they do show the contents that mutt originally sent. > > > > if their parser was written where the logic is such that the last > > Content-Type header encountered is the one they use, then it's possible > > that they clobber the first Content-Type header and therefor use the > > inner Content-Type header as if it were the toplevel MIME part (which is > > wrong, btw). > > > > Because of this, they end up showing what mutt sent but truncate any > > additional parts that the mailing list software has attached. > > > > Anyways, that's just a theory. > > > > IMHO, Evolution's handling is more correct in this case. > > > Perhaps "correct" if that means strict adherence to committee > standards. But not very useful if your goal is to read your mail. IMHO > solutions that attempt to more accurately render what the sender > intended are more "useful".
sounds nice on paper, but how do you know what the user intended? :-) ah... see, now there's the question. the only thing that can be done is to adhere to the standards, if you do that then you are more likely to render the way the user intended. The more you stray, the less likely you are to render it correctly. end of thread. Jeff _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
