>These tend to show that the problem is not with chrome, or firefox but >either with something in my enviroment, or in nmh itself.
Ah, okay. I see the problem. I ... can explain it, but didn't you just say that you were giving up on trying to understand MIME? It's technically a nmh problem (although I thought we had fixed that; the offending message displays fine for me, but it really depends on the configuration of the text/html converter). --Ken _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
