• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

any way to find out the BCC:'s on an email

I highly doubt that. I mean, it's the point of it, after all.

There might be a way if you have access to the outgoing email server.
 
i know, because i want to see if what was sent to me was also sent to someone else.......no way to "hack" it?
 
Originally posted by: gopunk
Originally posted by: slycat
how do u know if there were any.
Click to expand...

because if nobody is specified in the to: field it says "undisclosed recipients" or something to that effect
Click to expand...

well,..usually theres 1-2 in the To: and the others in the BCC:
Thats how i do it...then no one knows.
 
Originally posted by: kermalou
i know, because i want to see if what was sent to me was also sent to someone else.......no way to "hack" it?
Click to expand...

I don't even think the bcc information gets sent to the to or cc recipients. You can't hack what's not there.
 
Here's an example. I hand-write a letter and mail it to you. You suspect that I also photocopied it and mailed it to several other people so they could have a laugh at your expense. How can you find out whether I did without doing one or more of the following:

a. asking the sender
b. asking the other recipients (assuming you know or suspect who they'd be)
c. infiltrate the sending post office's mail logs (assuming there were such a thing)

That's it. E-mail works the same way. The addresses of BCC recipients aren't included anywhere on the e-mail you received.

l2c
 
Your answer has already been answered many times, but you can also read RFC 934 to at least get an idea of how BCC came about, and better understand potential implementations of it by user-agents and SMTP servers.

It's certainly possible that a malformed user-agent and/or SMTP server could expose the necessary information by adding their own headers, and things like this have been the source for well-known information leak vulnerabilities.
 
hmmm how many different ways of saying no will it take to get the point across...and to boot he offends the very people he is trying to get information from by calling them uneducated.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top