#448 Improve Bcc security

mh-e-8.0.1
open
nobody
None
5
2013-02-23
2006-06-26
Bill Wohler
No

According to RFC 2822, the presence of the Bcc header
field or the absence of the recipient's address in the
recipient list are both indicators that the recipient
was sent a blind carbon copy.

During a reply, if the user was determined to be the
recipient of a blind copy, let's warn the user of the
implications of replying to the message, which will
reveal to the recipients that the blind recipient
received a copy of the message. That could get the
sender in deep doo-doo. The prompt should definitely
use yes-or-no-p.

Because the MH behavior of including a Bcc warning in
the text of the message is neither condoned by RFC
2822, nor implemented by most agents, we should not
depend on it to inform the user.

Thanks to Sergey for pointing this out.

Discussion

  • Bill Wohler

    Bill Wohler - 2006-06-26

    Logged In: YES
    user_id=93690

    It's also possible that nmh and mailutils repl already
    restrict the reply to the original sender, in which case, we
    don't need to do anything.

     
  • Bill Wohler

    Bill Wohler - 2006-06-27

    Logged In: YES
    user_id=93690

    Even so, some sort of a warning should be given since the
    user might still think that MH-E or MH is broken and cut and
    paste addresses...

     
  • Bill Wohler

    Bill Wohler - 2006-06-27

    Logged In: YES
    user_id=93690

    Note that the absence of the recipient's address in the
    recipient list is not necessarily an indication of a Bcc as
    the recipient might have been in a distribution list.

     
  • Bill Wohler

    Bill Wohler - 2011-12-27
    • status: open --> open-accepted
     
  • Bill Wohler

    Bill Wohler - 2013-02-23
    • labels: General -->
     
  • Bill Wohler

    Bill Wohler - 2013-02-23

    Ticket moved from /p/mh-e/feature-requests/126/

     
  • Bill Wohler

    Bill Wohler - 2013-02-23
    • Status: open-accepted --> open
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks