lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <403DDFCE.2070509@nospam.wafel.org>
From: full-disclosure at nospam.wafel.org (Jorrit Kronjee)
Subject: a question about e-mails

Chris Smith wrote:

> On Thursday 26 February 2004 08:15, ASLI Unur wrote:
> 
>>Hi
>>I have a question for it experts. I want to learn if there is any way of
>>understanding/finding the e-mail addresses at BCC part on an e-mail that is
>>send to you.
>>
>>Thanks for your consideration.
> 
> 
> Um, AFAIK the headers are stripped by the MTA on delivery to recipients 
> (except perhaps the recipient who was listed in the BCC field, but I'm not 
> sure and will most likely vary between MTA).
> 
> I'm sure the SMTP RFC would probably help out on this.
> 
> Cheers,
> Chris.

Actually, an MTA doesn't care one bit about what you put in To:, From:, 
Cc: Bcc: or whatever. An MTA knows where to deliver the mail by the RCPT 
TO: command (which is defined in the SMTP RFC).

The Bcc:-field is already stripped by the sending MUA.

Jorrit Kronjee


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ