Slashdot Mirror

← Back to Stories (view on slashdot.org)

IETF Drops RFC For Cosmetic Carbon Copy

Posted by CmdrTaco on from the this-never-happened dept.

paulproteus writes "Say you have an email where you want to send an extra copy to someone without telling everyone. There's always been a field for that: BCC, or Blind Carbon Copy. But how often have you wanted to do the opposite: make everyone else think you sent a copy to somebody without actually having done so? Enter the new IETF-NG RFC: Cosmetic Carbon Copy, or CCC. Now you can conveniently email all of your friends (with a convenient exception or two...) with ease!"

3 of 63 comments (clear)

  1. Enough April Fool's Already. by GrifterCC · · Score: 4, Interesting

    Do you seriously mean to tell me that there are no important tech stories taking place today? Most of these articles are barely even chuckle-worthy.

  2. not required already possible with RFC822 by Anonymous Coward · · Score: 1, Interesting

    This is already possible by putting a Cc in the RFC822 headers but not delivering to the Cc address. The delivery addresses are specified in the envelope headers (the RCPT TO: commands given in the SMTP protocol). So you can pretty much whatever you want in the RFC822 headers.. To:, Cc:, From: and deliver to whoever you want (eg none of those people, a subset of them, extra people (Bcc) etc.

  3. You can already do this.. by geniusj · · Score: 2, Interesting

    Envelope headers are different than actual recipients. Mail clients don't implement it, but there's nothing in the SMTP protocol preventing you from putting a Cc: header in your message with a list of names/email addresses, but not actually delivering the messages. It's just a matter of a mail client offering this functionality. For now, you'll have to telnet into port 25 ;)