-----BEGIN PGP SIGNED MESSAGE-----
Dave Sill writes:
> So it doesn't apply to random files sitting on someone's disk. E.g.,
> if I have a file that contains the string "de5@xxxxxxxx", that *file*
> doesn't violate RFC 822 because RFC 822 only applies to e-mail
A digest is composed of a number of e-mail messages. Where that digest
resides or how it gets to a recipient is irrelevant, as you pointed out.
> If I take a valid e-mail message, cloak the e-mail addresses, and make
> it available via ftp, http, or even smtp, it still doesn't violate RFC
> 822 because it's no longer an e-mail message--it's just the *body* of
> an e-mail message. RFC 822 only cares about the format of e-mail
> addresses in the *header fields*, not the body.
Only if you utterly ignore the digest standards, which do not allow for
modification of headers (with the exception of stripping certain headers,
such as Received) within the body. A proper digest can be exploded, and
the resulting messages should be effectively indistinguishable from the
originals. This cannot be done with a "cloaked" digest.
-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
-----END PGP SIGNATURE-----
Rich Pieri <email@example.com> / When not in use, Happy Fun Ball
Sysmonster, Unix Wrangler / should be returned to its special
Prescient Technologies, Inc. / container and kept under
I speak for myself, not PTI or SWEC / refrigeration.