-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> As you seem to have found, it does your company more harm than good in the
> damage to its reputation for running such an ill-behaved email system.
..not to mention, since the disclaimer was attached to the bottom of
a message destined for a public mailing list, which is archived and stored
elsewhere, and is publically viewable in two locations (on the rubberchicken
mailing list Mailman archives, as well as those on mail-archive.com), it
puts the email in violation of it's own disclaimer about reproducing or
copying the content.
There's quite a few precedents here that define how email-based
disclaimers do not release a company from liability or legal prosecution,
and do not in any way, protect them from the same. This stemmed from a time
when disclaimers had to be sent with FAX transmissions, so if the wrong
number was dialed, it would be legally excusable. Using them for email
"transmissions" is simply incorrect.
With email, and especially email on public mailing lists, these
disclaimers amount to exactly nothing, except a substantial waste of space
and bandwidth.
d.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9bLLZkRQERnB1rkoRAgAEAKDahfZGblsE6c7NQjlodWlMYwROAgCgu/Iu
eOTxSufgn5RLWYwtUwx3ChY=
=oNAS
-----END PGP SIGNATURE-----
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
