2014-09-24 Today, I did work again on mmh! What else do I need to add to this great news? It's been one and a half year since my last development work. I'm so happy today! Besides some minor stuff to get used to the code again, I tracked down a problem that occured when attaching tarballs. The problem was not at all specific to tarballs. I was mislead by the fact, that I removed some special-case handling for tarballs some time ago. This wasn't related. The relevant point was, that tarballs usually contain (lots of) NUL characters. Often (?) all the other characters are part of ASCII. This made mmh think the file would be plain text, thus it would copy it with stdio, and consequently fail on the NUL bytes. The easy solution is to base64-encode all that stuff. This is something I don't like. Base64 encoding should only be used if the content is unreadable anyway. If the content is well read- able, apart from some non-ASCII characters, quoted-printable en- coding is a much better choice. As get in contact with the email source format regularly, I value such reasonable behavior. Howev- er, as the sane solution seemed to complicated and it wasn't clear how to implement it reliably, I went for the easy approach to encode all MIME parts of type `application' with base64. Im- provements can be done later; now it's important that I move for- ward. (I already have a list of bug reports and notes to attack.) http://marmaro.de/lue/ markus schnalke