From: Richard Joyce <Richard.Joyce@cportcorp.com>
To: "'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Cc: "'sourcenav-owner@sourceware.cygnus.com'"
<sourcenav-owner@sourceware.cygnus.com>
Subject: virus forwarded by a mailing list program is unacceptable: I am unsubscribing
Date: Wed, 25 Jul 2001 08:12:00 -0000 [thread overview]
Message-ID: <50A89B19AEAAD411B9D200A0C9FB5699FFC4D8@craius.cportcorp.com> (raw)
Sirs:
With all due respect I must unsubscribe to limit my exposure. My company
goes to great pains to protect its network against viruses, but I cannot
risk being a member of any mailing list until this issue is resolved.
The following response from Mo De Jong is quite unnerving. While I do not
know for sure if there is anything that can be done to block a virus on a
digest message, I believe that the parties responsible for promoting and
supporting the sourcenav mailing list must do more than what is suggested
below.
...from Mo De Jong 7/24/01
"Yes, people are sending that virus around on mailing lists. If folks are
foolish enough to use Windows to read email, there is not much we can do to
help. The best advice is don't open attachments you get in email, or simply
don't use Windows. This is not a new problem. "
reply other threads:[~2001-07-25 8:12 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=50A89B19AEAAD411B9D200A0C9FB5699FFC4D8@craius.cportcorp.com \
--to=richard.joyce@cportcorp.com \
--cc=sourcenav-owner@sourceware.cygnus.com \
--cc=sourcenav@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).