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. Jeff On Sun, 2003-01-26 at 18:14, Jeffrey Stedfast wrote: > On Sun, 2003-01-26 at 16:07, Arthur S. Alexion wrote: > > On Sun, 2003-01-26 at 15:15, Jeffrey Stedfast wrote: > > > > > not evolution's fault, and I don't think it's mutt's fault either. I > > > believe that the mailing list software is at fault here. > > > > > > > I agree, not because I know a lot about multipart email structure, but > > because it makes sense in light of the fact that I only experience this > > problem with one mailing list. That said, Jeff, why, of the three MUAs > > that I regularly use (Evolution, kmail and Eudora) does only Evolution > > seem to have the problem displaying these mangled messages? > > somehow I doubt that. > > > How do > > Eudora and kmail overcome the problem, and can this be implemented in > > Eudora? > > I dunno, why don't you ask them? > > somehow I doubt they handle these types of messages either. > > Jeff -- Jeffrey Stedfast Evolution Hacker - Ximian, Inc. [EMAIL PROTECTED] - www.ximian.com _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
