From: Jim Choate <ravage@einstein.ssz.com>
To: <discuss@effaustin.org>
Cc: <9fans@cse.psu.edu>
Subject: [9fans] virus filtering (fwd)
Date: Wed, 24 Sep 2003 10:34:46 -0500 [thread overview]
Message-ID: <Pine.LNX.4.33.0309241034050.3289-100000@einstein.ssz.com> (raw)
Somebody with a clue...I salute them!
---------- Forwarded message ----------
Date: Wed, 24 Sep 2003 18:21:56 +0300
From: Aharon Robbins <arnold@skeeve.com>
Reply-To: 9fans@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: [9fans] virus filtering
As BWK once said, "Let someone else do the hard part." I just called my
ISP. For a mere $2 a month, *they* will filter out the viruses etc.
I deduct those expenses, and the time I don't have to spend putting a
filter in place is worth the cost.
So, thought I'd pass that idea along.
Arnold
reply other threads:[~2003-09-24 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.33.0309241034050.3289-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--cc=9fans@cse.psu.edu \
--cc=discuss@effaustin.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).