Please don't respond to misconfigured away messages copying the mailing
list. Send a complaint to the site in question, and if it continues - to
the list owner (which has been done for the current case.)
The messages complaining about the away messages will soon start to be worse
than the away messages themselves. If you still can't stand the messages,
then take responsibility for your inbox, and simply filter on the sender's
address and send their messages to /dev/null.
If you're going to use away messages, ensure that they do not reply to
traffic containing the "Precedence: bulk" message header. All mailing list
traffic should be bulk.
Finally, as has been pointed out before - think twice before you let
50,000 of your closest friends and enemies know you're not around to hold
down the fort.
Ob firewalls: Has anyone done any work on Web-based authentication for
machines that will then open dynamic filters for IPFilter or IPFW? So
that a user can authenticate, then be allowed time or traffic-based
filtering for the address they authenticate from. Ideally with
server-pushed Web pages to notifiy of authentication expiry. I'm looking
for alternatives to allowing hosts on an external segement completely
unrestricted access. Also is NFR my best option for reporting on
traffic on an external segment outside of a commercial sniffer product?
Paul
-----------------------------------------------------------------------------
Paul D. Robertson "My statements in this message are personal opinions
[EMAIL PROTECTED] which may have no basis whatsoever in fact."
PSB#9280
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
