Can I Retrieve Email Addresses from BCC?Spoofing email From addressHow do I safely inspect a suspicious email attachment?Hotmail securityEmail Spoofing by SMTP Message-ID?Is thread's auto-login from email implementation secure/good user experience?PayPal “Confirm your email address” spam emails? I got 3 different mails within 10 hoursWebsite customer e-mail collection form getting spammed, why and what to doMail address spoofing : how to protect myselfEmail got hijacked or hacked, where to start?Can a custom return path make SPF redundant

Difference between -| and |- in TikZ

What linear sensor for a keyboard?

Have I saved too much for retirement so far?

Using a siddur to Daven from in a seforim store

Visiting the UK as unmarried couple

A Permanent Norse Presence in America

Folder comparison

Transformation of random variables and joint distributions

Why does the integral domain "being trapped between a finite field extension" implies that it is a field?

Is there a conventional notation or name for the slip angle?

What (else) happened July 1st 1858 in London?

Proof of Lemma: Every nonzero integer can be written as a product of primes

Is it possible to have a strip of cold climate in the middle of a planet?

Can someone explain how this makes sense electrically?

What does this horizontal bar at the first measure mean?

Proving a function is onto where f(x)=|x|.

Why has "pence" been used in this sentence, not "pences"?

How do I implement a file system driver driver in Linux?

In Star Trek IV, why did the Bounty go back to a time when whales were already rare?

Global amount of publications over time

Can I sign legal documents with a smiley face?

Why is Arduino resetting while driving motors?

On a tidally locked planet, would time be quantized?

Divine apple island



Can I Retrieve Email Addresses from BCC?


Spoofing email From addressHow do I safely inspect a suspicious email attachment?Hotmail securityEmail Spoofing by SMTP Message-ID?Is thread's auto-login from email implementation secure/good user experience?PayPal “Confirm your email address” spam emails? I got 3 different mails within 10 hoursWebsite customer e-mail collection form getting spammed, why and what to doMail address spoofing : how to protect myselfEmail got hijacked or hacked, where to start?Can a custom return path make SPF redundant













2















Can anyone tell me how to unmask the e-mail addresses in a bcc field when I am just a recipient? Need very simple, step-by-step instructions for someone who doesn't code. I have received a group e-mail and would really like to see the others who got it. Thank you!










share|improve this question







New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Not being able to do this is the exact point of Bcc.

    – chrylis
    10 mins ago















2















Can anyone tell me how to unmask the e-mail addresses in a bcc field when I am just a recipient? Need very simple, step-by-step instructions for someone who doesn't code. I have received a group e-mail and would really like to see the others who got it. Thank you!










share|improve this question







New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Not being able to do this is the exact point of Bcc.

    – chrylis
    10 mins ago













2












2








2








Can anyone tell me how to unmask the e-mail addresses in a bcc field when I am just a recipient? Need very simple, step-by-step instructions for someone who doesn't code. I have received a group e-mail and would really like to see the others who got it. Thank you!










share|improve this question







New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












Can anyone tell me how to unmask the e-mail addresses in a bcc field when I am just a recipient? Need very simple, step-by-step instructions for someone who doesn't code. I have received a group e-mail and would really like to see the others who got it. Thank you!







email






share|improve this question







New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 6 hours ago









Jenny BJenny B

141




141




New contributor




Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Jenny B is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Not being able to do this is the exact point of Bcc.

    – chrylis
    10 mins ago

















  • Not being able to do this is the exact point of Bcc.

    – chrylis
    10 mins ago
















Not being able to do this is the exact point of Bcc.

– chrylis
10 mins ago





Not being able to do this is the exact point of Bcc.

– chrylis
10 mins ago










2 Answers
2






active

oldest

votes


















5














You can't. You simply won't have any information about the Bcc header when you receive the mail, so you there's nothing to "unmask".



The way Bcc is designed is specified in RFC 2822, under section 3.6.3. To quote the specification:




The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains
addresses of recipients of the message whose addresses are not to be
revealed to other recipients of the message. There are three ways in
which the "Bcc:" field is used. In the first case, when a message
containing a "Bcc:" field is prepared to be sent, the "Bcc:" line is
removed even though all of the recipients (including those specified
in the "Bcc:" field) are sent a copy of the message. In the second
case, recipients specified in the "To:" and "Cc:" lines each are sent
a copy of the message with the "Bcc:" line removed as above, but the
recipients on the "Bcc:" line get a separate copy of the message
containing a "Bcc:" line. (When there are multiple recipient
addresses in the "Bcc:" field, some implementations actually send a
separate copy of the message to each recipient with a "Bcc:"
containing only the address of that particular recipient.) Finally,
since a "Bcc:" field may contain no addresses, a "Bcc:" field can be
sent without any addresses indicating to the recipients that blind
copies were sent to someone. Which method to use with "Bcc:" fields
is implementation dependent, but refer to the "Security
Considerations" section of this document for a discussion of each.



When a message is a reply to another message, the mailboxes of the
authors of the original message (the mailboxes in the "From:" field)
or mailboxes specified in the "Reply-To:" field (if it exists) MAY
appear in the "To:" field of the reply since these would normally be
the primary recipients of the reply. If a reply is sent to a message
that has destination fields, it is often desirable to send a copy of
the reply to all of the recipients of the message, in addition to the
author. When such a reply is formed, addresses in the "To:" and "Cc:"
fields of the original message MAY appear in the "Cc:" field of the
reply, since these are normally secondary recipients of the reply. If
a "Bcc:" field is present in the original message, addresses in that
field MAY appear in the "Bcc:" field of the reply, but SHOULD NOT
appear in the "To:" or "Cc:" fields.



Note: Some mail applications have automatic reply commands that
include the destination addresses of the original message in the
destination addresses of the reply. How those reply commands behave
is implementation dependent and is beyond the scope of this document.
In particular, whether or not to include the original destination
addresses when the original message had a "Reply-To:" field is not
addressed here.




In practice the case where To and Cc recipients receive no Bcc line, but each Bcc'ed address receives a Bcc line containing only their email address, is most common. This provides no indication of a Bcc to the To and Cc recipients, and indicates to the Bcc'ed recipients that they were sent the email via the use of Bcc without revealing other Bcc recipients.






share|improve this answer


















  • 2





    each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

    – Esa Jokinen
    2 hours ago












  • @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

    – Selcuk
    1 hour ago











  • The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

    – Esa Jokinen
    51 mins ago



















1














Typically not possible if you don't have control over the sender SMTP server since this field is not transmitted to the recipient SMTP server.



When sending a mail, the sender SMTP server checks the BCC field and creates a copy for each recipient listed, removing the list of other recipients.
That is the whole point of BCC functionality.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "162"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );






    Jenny B is a new contributor. Be nice, and check out our Code of Conduct.









    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f206003%2fcan-i-retrieve-email-addresses-from-bcc%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5














    You can't. You simply won't have any information about the Bcc header when you receive the mail, so you there's nothing to "unmask".



    The way Bcc is designed is specified in RFC 2822, under section 3.6.3. To quote the specification:




    The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains
    addresses of recipients of the message whose addresses are not to be
    revealed to other recipients of the message. There are three ways in
    which the "Bcc:" field is used. In the first case, when a message
    containing a "Bcc:" field is prepared to be sent, the "Bcc:" line is
    removed even though all of the recipients (including those specified
    in the "Bcc:" field) are sent a copy of the message. In the second
    case, recipients specified in the "To:" and "Cc:" lines each are sent
    a copy of the message with the "Bcc:" line removed as above, but the
    recipients on the "Bcc:" line get a separate copy of the message
    containing a "Bcc:" line. (When there are multiple recipient
    addresses in the "Bcc:" field, some implementations actually send a
    separate copy of the message to each recipient with a "Bcc:"
    containing only the address of that particular recipient.) Finally,
    since a "Bcc:" field may contain no addresses, a "Bcc:" field can be
    sent without any addresses indicating to the recipients that blind
    copies were sent to someone. Which method to use with "Bcc:" fields
    is implementation dependent, but refer to the "Security
    Considerations" section of this document for a discussion of each.



    When a message is a reply to another message, the mailboxes of the
    authors of the original message (the mailboxes in the "From:" field)
    or mailboxes specified in the "Reply-To:" field (if it exists) MAY
    appear in the "To:" field of the reply since these would normally be
    the primary recipients of the reply. If a reply is sent to a message
    that has destination fields, it is often desirable to send a copy of
    the reply to all of the recipients of the message, in addition to the
    author. When such a reply is formed, addresses in the "To:" and "Cc:"
    fields of the original message MAY appear in the "Cc:" field of the
    reply, since these are normally secondary recipients of the reply. If
    a "Bcc:" field is present in the original message, addresses in that
    field MAY appear in the "Bcc:" field of the reply, but SHOULD NOT
    appear in the "To:" or "Cc:" fields.



    Note: Some mail applications have automatic reply commands that
    include the destination addresses of the original message in the
    destination addresses of the reply. How those reply commands behave
    is implementation dependent and is beyond the scope of this document.
    In particular, whether or not to include the original destination
    addresses when the original message had a "Reply-To:" field is not
    addressed here.




    In practice the case where To and Cc recipients receive no Bcc line, but each Bcc'ed address receives a Bcc line containing only their email address, is most common. This provides no indication of a Bcc to the To and Cc recipients, and indicates to the Bcc'ed recipients that they were sent the email via the use of Bcc without revealing other Bcc recipients.






    share|improve this answer


















    • 2





      each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

      – Esa Jokinen
      2 hours ago












    • @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

      – Selcuk
      1 hour ago











    • The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

      – Esa Jokinen
      51 mins ago
















    5














    You can't. You simply won't have any information about the Bcc header when you receive the mail, so you there's nothing to "unmask".



    The way Bcc is designed is specified in RFC 2822, under section 3.6.3. To quote the specification:




    The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains
    addresses of recipients of the message whose addresses are not to be
    revealed to other recipients of the message. There are three ways in
    which the "Bcc:" field is used. In the first case, when a message
    containing a "Bcc:" field is prepared to be sent, the "Bcc:" line is
    removed even though all of the recipients (including those specified
    in the "Bcc:" field) are sent a copy of the message. In the second
    case, recipients specified in the "To:" and "Cc:" lines each are sent
    a copy of the message with the "Bcc:" line removed as above, but the
    recipients on the "Bcc:" line get a separate copy of the message
    containing a "Bcc:" line. (When there are multiple recipient
    addresses in the "Bcc:" field, some implementations actually send a
    separate copy of the message to each recipient with a "Bcc:"
    containing only the address of that particular recipient.) Finally,
    since a "Bcc:" field may contain no addresses, a "Bcc:" field can be
    sent without any addresses indicating to the recipients that blind
    copies were sent to someone. Which method to use with "Bcc:" fields
    is implementation dependent, but refer to the "Security
    Considerations" section of this document for a discussion of each.



    When a message is a reply to another message, the mailboxes of the
    authors of the original message (the mailboxes in the "From:" field)
    or mailboxes specified in the "Reply-To:" field (if it exists) MAY
    appear in the "To:" field of the reply since these would normally be
    the primary recipients of the reply. If a reply is sent to a message
    that has destination fields, it is often desirable to send a copy of
    the reply to all of the recipients of the message, in addition to the
    author. When such a reply is formed, addresses in the "To:" and "Cc:"
    fields of the original message MAY appear in the "Cc:" field of the
    reply, since these are normally secondary recipients of the reply. If
    a "Bcc:" field is present in the original message, addresses in that
    field MAY appear in the "Bcc:" field of the reply, but SHOULD NOT
    appear in the "To:" or "Cc:" fields.



    Note: Some mail applications have automatic reply commands that
    include the destination addresses of the original message in the
    destination addresses of the reply. How those reply commands behave
    is implementation dependent and is beyond the scope of this document.
    In particular, whether or not to include the original destination
    addresses when the original message had a "Reply-To:" field is not
    addressed here.




    In practice the case where To and Cc recipients receive no Bcc line, but each Bcc'ed address receives a Bcc line containing only their email address, is most common. This provides no indication of a Bcc to the To and Cc recipients, and indicates to the Bcc'ed recipients that they were sent the email via the use of Bcc without revealing other Bcc recipients.






    share|improve this answer


















    • 2





      each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

      – Esa Jokinen
      2 hours ago












    • @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

      – Selcuk
      1 hour ago











    • The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

      – Esa Jokinen
      51 mins ago














    5












    5








    5







    You can't. You simply won't have any information about the Bcc header when you receive the mail, so you there's nothing to "unmask".



    The way Bcc is designed is specified in RFC 2822, under section 3.6.3. To quote the specification:




    The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains
    addresses of recipients of the message whose addresses are not to be
    revealed to other recipients of the message. There are three ways in
    which the "Bcc:" field is used. In the first case, when a message
    containing a "Bcc:" field is prepared to be sent, the "Bcc:" line is
    removed even though all of the recipients (including those specified
    in the "Bcc:" field) are sent a copy of the message. In the second
    case, recipients specified in the "To:" and "Cc:" lines each are sent
    a copy of the message with the "Bcc:" line removed as above, but the
    recipients on the "Bcc:" line get a separate copy of the message
    containing a "Bcc:" line. (When there are multiple recipient
    addresses in the "Bcc:" field, some implementations actually send a
    separate copy of the message to each recipient with a "Bcc:"
    containing only the address of that particular recipient.) Finally,
    since a "Bcc:" field may contain no addresses, a "Bcc:" field can be
    sent without any addresses indicating to the recipients that blind
    copies were sent to someone. Which method to use with "Bcc:" fields
    is implementation dependent, but refer to the "Security
    Considerations" section of this document for a discussion of each.



    When a message is a reply to another message, the mailboxes of the
    authors of the original message (the mailboxes in the "From:" field)
    or mailboxes specified in the "Reply-To:" field (if it exists) MAY
    appear in the "To:" field of the reply since these would normally be
    the primary recipients of the reply. If a reply is sent to a message
    that has destination fields, it is often desirable to send a copy of
    the reply to all of the recipients of the message, in addition to the
    author. When such a reply is formed, addresses in the "To:" and "Cc:"
    fields of the original message MAY appear in the "Cc:" field of the
    reply, since these are normally secondary recipients of the reply. If
    a "Bcc:" field is present in the original message, addresses in that
    field MAY appear in the "Bcc:" field of the reply, but SHOULD NOT
    appear in the "To:" or "Cc:" fields.



    Note: Some mail applications have automatic reply commands that
    include the destination addresses of the original message in the
    destination addresses of the reply. How those reply commands behave
    is implementation dependent and is beyond the scope of this document.
    In particular, whether or not to include the original destination
    addresses when the original message had a "Reply-To:" field is not
    addressed here.




    In practice the case where To and Cc recipients receive no Bcc line, but each Bcc'ed address receives a Bcc line containing only their email address, is most common. This provides no indication of a Bcc to the To and Cc recipients, and indicates to the Bcc'ed recipients that they were sent the email via the use of Bcc without revealing other Bcc recipients.






    share|improve this answer













    You can't. You simply won't have any information about the Bcc header when you receive the mail, so you there's nothing to "unmask".



    The way Bcc is designed is specified in RFC 2822, under section 3.6.3. To quote the specification:




    The "Bcc:" field (where the "Bcc" means "Blind Carbon Copy") contains
    addresses of recipients of the message whose addresses are not to be
    revealed to other recipients of the message. There are three ways in
    which the "Bcc:" field is used. In the first case, when a message
    containing a "Bcc:" field is prepared to be sent, the "Bcc:" line is
    removed even though all of the recipients (including those specified
    in the "Bcc:" field) are sent a copy of the message. In the second
    case, recipients specified in the "To:" and "Cc:" lines each are sent
    a copy of the message with the "Bcc:" line removed as above, but the
    recipients on the "Bcc:" line get a separate copy of the message
    containing a "Bcc:" line. (When there are multiple recipient
    addresses in the "Bcc:" field, some implementations actually send a
    separate copy of the message to each recipient with a "Bcc:"
    containing only the address of that particular recipient.) Finally,
    since a "Bcc:" field may contain no addresses, a "Bcc:" field can be
    sent without any addresses indicating to the recipients that blind
    copies were sent to someone. Which method to use with "Bcc:" fields
    is implementation dependent, but refer to the "Security
    Considerations" section of this document for a discussion of each.



    When a message is a reply to another message, the mailboxes of the
    authors of the original message (the mailboxes in the "From:" field)
    or mailboxes specified in the "Reply-To:" field (if it exists) MAY
    appear in the "To:" field of the reply since these would normally be
    the primary recipients of the reply. If a reply is sent to a message
    that has destination fields, it is often desirable to send a copy of
    the reply to all of the recipients of the message, in addition to the
    author. When such a reply is formed, addresses in the "To:" and "Cc:"
    fields of the original message MAY appear in the "Cc:" field of the
    reply, since these are normally secondary recipients of the reply. If
    a "Bcc:" field is present in the original message, addresses in that
    field MAY appear in the "Bcc:" field of the reply, but SHOULD NOT
    appear in the "To:" or "Cc:" fields.



    Note: Some mail applications have automatic reply commands that
    include the destination addresses of the original message in the
    destination addresses of the reply. How those reply commands behave
    is implementation dependent and is beyond the scope of this document.
    In particular, whether or not to include the original destination
    addresses when the original message had a "Reply-To:" field is not
    addressed here.




    In practice the case where To and Cc recipients receive no Bcc line, but each Bcc'ed address receives a Bcc line containing only their email address, is most common. This provides no indication of a Bcc to the To and Cc recipients, and indicates to the Bcc'ed recipients that they were sent the email via the use of Bcc without revealing other Bcc recipients.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered 6 hours ago









    PolynomialPolynomial

    101k31246339




    101k31246339







    • 2





      each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

      – Esa Jokinen
      2 hours ago












    • @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

      – Selcuk
      1 hour ago











    • The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

      – Esa Jokinen
      51 mins ago













    • 2





      each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

      – Esa Jokinen
      2 hours ago












    • @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

      – Selcuk
      1 hour ago











    • The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

      – Esa Jokinen
      51 mins ago








    2




    2





    each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

    – Esa Jokinen
    2 hours ago






    each Bcc'ed address receives a Bcc line containing only their email address, is most common. Is it? That would require sending the message multiple times instead of a single message with multiple RCPT TO: commands. What MUA would do that?

    – Esa Jokinen
    2 hours ago














    @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

    – Selcuk
    1 hour ago





    @EsaJokinen What other choice does the MUA have when the recipients are on different domains? BCC simply forces that behaviour.

    – Selcuk
    1 hour ago













    The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

    – Esa Jokinen
    51 mins ago






    The MUA sends it only once to the MTA, and the MTA starts delivering it separately to all the different domains. The thing is that MTAs won't usually bother to add RCPT TO as Bcc:. It's more likely in a Received: header as for <user@example.com>.

    – Esa Jokinen
    51 mins ago














    1














    Typically not possible if you don't have control over the sender SMTP server since this field is not transmitted to the recipient SMTP server.



    When sending a mail, the sender SMTP server checks the BCC field and creates a copy for each recipient listed, removing the list of other recipients.
    That is the whole point of BCC functionality.






    share|improve this answer



























      1














      Typically not possible if you don't have control over the sender SMTP server since this field is not transmitted to the recipient SMTP server.



      When sending a mail, the sender SMTP server checks the BCC field and creates a copy for each recipient listed, removing the list of other recipients.
      That is the whole point of BCC functionality.






      share|improve this answer

























        1












        1








        1







        Typically not possible if you don't have control over the sender SMTP server since this field is not transmitted to the recipient SMTP server.



        When sending a mail, the sender SMTP server checks the BCC field and creates a copy for each recipient listed, removing the list of other recipients.
        That is the whole point of BCC functionality.






        share|improve this answer













        Typically not possible if you don't have control over the sender SMTP server since this field is not transmitted to the recipient SMTP server.



        When sending a mail, the sender SMTP server checks the BCC field and creates a copy for each recipient listed, removing the list of other recipients.
        That is the whole point of BCC functionality.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 6 hours ago









        NaoyNaoy

        212




        212




















            Jenny B is a new contributor. Be nice, and check out our Code of Conduct.









            draft saved

            draft discarded


















            Jenny B is a new contributor. Be nice, and check out our Code of Conduct.












            Jenny B is a new contributor. Be nice, and check out our Code of Conduct.











            Jenny B is a new contributor. Be nice, and check out our Code of Conduct.














            Thanks for contributing an answer to Information Security Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f206003%2fcan-i-retrieve-email-addresses-from-bcc%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

            2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

            Metrô de Los Teques Índice Linhas | Estações | Ver também | Referências Ligações externas | Menu de navegação«INSTITUCIÓN»«Mapa de rutas»originalMetrô de Los TequesC.A. Metro Los Teques |Alcaldía de Guaicaipuro – Sitio OficialGobernacion de Mirandaeeeeeee