Re: [802SEC] Fwd: Re: Confidentiality Notices
This sounds like a good approach. But rather than some of us rushing off to implement the same or similar approaches, I'd like to see a common approach taken by at least all of 802, if not all of the SA-related reflectors. Again, I think this merits a discussion with the SA lawyer, as first suggested in the original message on this subject.
jl
-----Original Message-----
From: owner-stds-802-sec@LISTSERV.IEEE.ORG on behalf of Tony Jeffree
Sent: Mon 4/4/2005 3:34 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Cc:
Subject: [802SEC] Fwd: Re: Confidentiality Notices
F.Y.I.-
See below the practical solution to the confidentiality notice problem that
Hal has put in place for the 802.1 exploder. This (or similar) would seem
to be something that could be replicated across the other 802 exploders to
good effect.
Regards,
Tony
>Mat -
>
> > Hal Keen, who supports the 802.1 exploder, has incorporated a set of
> > filters to do just that on the 802.1 exploder. I would suggest that
> > whomever does this job for 802.11 takes advantage of Hal's experience in
> > setting these up. I'm sure what he does is not as simplistic as triggering
> > on a single word.
> >
> > Regards,
> > Tony
>
>I have a large set of phrases, designed to match objectionable notices
>actually observed. Three of them are specific enough that they are set up
>for immediate rejection; the assumption is that the sender has mistakenly
>allowed the claims to be added, and would be able to retransmit without
>them if notice is sent.
>
>The others are more general, and are set up to force messages containing
>them to wait for me to check them. (I don't know if you have a list
>configuration that allows that; the .1 lists are
>"self-moderated"--subscribers can send freely, others need approval--as
>part of my spam defenses.)
>
>Anyway, below my signature you will find appended a copy of that portion
>of my content filters. Some of the phrases have been constrained by
>avoiding line breaks in known cases of objectionable text; I don't trust
>ListServ to match patterns across lines. Some might be improved; this has
>been developed ad hoc.
>
>Hope this helps.
>
>Hal
>Hal.Keen@ieee.org
>
>The information contained in this message may be privileged
>Action: REJECT Your email appears to have unacceptable proprietary claims.
>This message is proprietary to
>Action: REJECT Your email appears to have unacceptable proprietary claims.
>dissemination or distribution of this communication is strictly
>Action: REJECT Your email appears to have unacceptable proprietary claims.
>If you are not the intended recipient
>Action: MODERATE
>If you have received this communication in error
>Action: MODERATE
>reached you in error
>Action: MODERATE
>receiving this by mistake
>Action: MODERATE
>received this message in error
>Action: MODERATE
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.