Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Communications The Internet Technology

MIME Attachments Are 20 Years Old Today 82

judgecorp writes "MIME email attachments have been around for 20 years, and we now send a trillion every day. The mountains of emails in corporate archives now contain vital information, says MIME inventor Nathaniel Borenstein, which can be mined to expose conspiracies and make businesses more efficient. He also says a one-penny tax on attachments would make him as rich as Germany — if it weren't for the fact that such a charge would have killed MIME."
This discussion has been archived. No new comments can be posted.

MIME Attachments Are 20 Years Old Today

Comments Filter:
  • uuencode FTW! (Score:5, Interesting)

    by jtownatpunk.net ( 245670 ) on Sunday March 11, 2012 @11:20AM (#39317959)

    I was trying to remember how I emailed binaries back in the day then I remembered piping uuencode into mail and addresses with bangs and hoping some grouchy admin along the UUCP trail didn't bitch about the traffic. Get off my lawn!

  • by Anonymous Coward on Sunday March 11, 2012 @11:57AM (#39318147)

    Half of the first page is about how great and amazing Steve Jobs was, despite the fact that he wanted to cock up everything. Can journalists really not write an article about him without sucking up to the guy, even when it's about something he did (or tried to do) WRONG?

  • by dskoll ( 99328 ) on Sunday March 11, 2012 @12:34PM (#39318283) Homepage

    MIME is quite amazing, but some of the RFCs such as RFC 2231 [ietf.org] are a real WTF. I took over maintainership of the MIME::tools Perl module and felt murderous sentiments towards the authors of that RFC...

  • by dskoll ( 99328 ) on Sunday March 11, 2012 @01:48PM (#39318651) Homepage

    What's bad about it is coming up with sane ways to deal with malformed parameter values while minimizing security risks. There are many ways to abuse that spec (for example) to specify something that Outlook sees as "filename.exe" while your security scanner sees "innoccuous.txt", depending on how the malformed parameter is interpreted.

    Handling well-formed MIME is easy. Dealing safely with malformed MIME is a nightmare. And unfortunately, because of piles of bad software, you can't be pedantic and simply reject malformed MIME; end-users will riot.

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...