full-disclosure - a question about e-mails

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]

From: nion at gmx.net (Nico Golde)
Subject: a question about e-mails

Hallo Chris,

* Chris Smith <chris.rs@...a.co.nz> [2004-02-26 13:50]:
> > 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.

I tested it on my system.
i send a mail to nico and bcc root.
here is the mail header:
	From nion@....net Thu Feb 26 14:28:30 2004
	Return-Path: nion@....net
	Received: by
	        via sendmail from stdin
	        id <m1AwLZ0-001n35C@...lde.de> (Debian Smail3.2.0.114)
	        Thu, 26 Feb 2004 14:28:30 +0100 (CET)
	Date: Thu, 26 Feb 2004 14:28:30 +0100
	From: Nico Golde <nion@....net>
	To: nico
	Bcc: root

^^^^^^^^^
here is the bcc line


	Subject: test
	Message-ID: <20040226132830.GA829@...lde.de>

[...] 
regards nico
-- 
Nico Golde nico <at> ngolde <dot> de
public key available on:
http://www.ngolde.de/gpg.html
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040226/209a9ecd/attachment.bin