Vincent Lefevre wrote in <[email protected]>: ... |So what was needed was just a transition from old problematic methods |to the general use of Content-Length *locally*. But MUAs should still |support (old) mbox files where Content-Length is not used.
You can come over with such any way you want, but i say once again that (by the end of that very same year) the IETF made shit decisions with their MIME standards 204[5679] in that they did not invent yet another content-transfer-encoding which does nothing but quoting ^From_, in the very same sense how SMTP quotes a ^. by doubling it; no more, no less. MIME was in the works for years, the problem of ^From_ was known for many years (when did nmh introduce their special marker to avoid the problem?), so again *IETF shit brainfuck decisions*, as are currently in the works again. I mean, hey -- Rome wanted to change the world, but thanks to Asterix et al a little village survived "almost as-is", right? What the heck are you all talking about? No!!! So all you can really do is to enforce heavy and large quoted-printable or base64 encoding, and those fuckers who dream of 8bit have no idea what they are talking about. And i am thankful that certain security-affine parts of the IETF go there, *necessarily* they do. Btw as i found out in the meantime mutt does not do anything when copying over, which Gunnar Ritter implemented right from the start for the MUA i maintain; unfortunately the software cannot reencode because of MIME restrictions, whereas mutt has a proper MIME thing with objects and such, and surely could. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
