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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.0402271616330.12023@catbert.rellim.com>
From: gem at rellim.com (Gary E. Miller)
Subject: a question about e-mails

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yo Remko!

On Sat, 28 Feb 2004, Remko Lodder wrote:

> I recall a message from earlier today stating an RFC about BCC,
> think it was from valdis but not sure (recieved a lot of mail and
> deleted the one i mentioned)

I sent it, RFC 2821, Appendix B.1  ( I mistakenly referred to is as
RFC2882 in my previous post).

   1. Each recipient address from a TO, CC, or BCC header field SHOULD
      be copied to a RCPT command (generating multiple message copies if
      that is required for queuing or delivery).  This includes any
      addresses listed in a RFC 822 "group".  Any BCC fields SHOULD then
      be removed from the headers.  Once this process is completed, the
      remaining headers SHOULD be checked to verify that at least one
      To:, Cc:, or Bcc: header remains.  If none do, then a bcc: header
      with no additional information SHOULD be inserted as specified in
      [32].



RGDS
GARY
- ---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
	gem@...lim.com  Tel:+1(541)382-8588 Fax: +1(541)382-8676

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAP96p8KZibdeR3qURAgCwAJ9f2Kr2bJD6jpIlvfI79nFQ3/AZrwCfVL7h
c/ilizmPs9XJGs2hqzi5I8c=
=kk2l
-----END PGP SIGNATURE-----