email gripe

This is a client-side issue; there is no need to uglify the rest of the email just because someone has an email reader that doesn't know what to do with URLs. Only if the mail reader already knows how to handle such horrors. And there's no reason a GUI MUA can't turn URLs in text/plain text into clickable links; I've seen it happen (over others' shoulders). Me too. Not that that is necessarily incompatible with HTML, though I am not aware of any text MUAs that do anything with HTML but display it like any other text. But, send me mail that's HTML-only and it will be refused at SMTP time; send me mail that's plain-and-HTML multipart and I will usually stop reading when I see the HTML-uglified version. (And yes, that means right at the beginning if you put the HTML part first - which would be a strange thing to do anyway, as multipart is defined to express sender preference by ordering, with later parts more preferred.) Somewhat similar here: quit the less(1) that's reading the text, run mimesplit on the message file ("mimesplit `mmpath cur`" is the usual incantation), step through and save the attachment when I get to it, then start up gs or pdftotext or whatever on it - possibly after copying it to my desktop machine, possibly running on the mail-reading machine but displaying on my desktop (those two machines sit less than a foot apart and are in the same broadcast domain on my house network). So do I: my routine mail-reading machine is the same machine that my MX record points to, the machine that handles incoming mail. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML mouse at rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B