From: Ralf Staudemeyer <rstaudemeyer@uwc.ac.za>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] management of virus and p2p-traffic
Date: Tue, 22 Jun 2004 10:34:57 +0000 [thread overview]
Message-ID: <1087918842.2861.14.camel@turtle> (raw)
In-Reply-To: <1087839362.4786.0.camel@turtle>
On Mon, 2004-06-21 at 17:06, Ed Wildgoose wrote:
> >The Windows machines with their viruses give me a
> >headache. I do not want to enforce remote Windows patching and
> >virusscanner updating. It should also be taken into account that there
> >is nearly no money available for any special equipment. Best would be to
> >get this job done with a couple of old computers.
> >
> >
>
> One thing you could address is that most virus's arrive via smtp. Can
> you scan inbound smtp traffic, perhaps with clamav? Or do users have
> their own external email accounts?
>
>
We have a Novel Groupwise service that should be used for email (via the
managed 3Mbit connection). That system supports spam-filtering and
virus-scanning. Unfortunately that service does not support any security
functions and is not reliable. There will be not much change about that.
So I want and I must support users who use their external email
accounts.
Ralf
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-22 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 17:36 [LARTC] management of virus and p2p-traffic Ralf Staudemeyer
2004-06-21 21:06 ` Ed Wildgoose
2004-06-22 4:59 ` Jason Boxman
2004-06-22 10:34 ` Ralf Staudemeyer [this message]
2004-06-22 11:20 ` Ed Wildgoose
2004-06-22 15:05 ` Ralf Staudemeyer
2004-06-22 16:01 ` Ed Wildgoose
2004-06-22 16:45 ` Ralf Staudemeyer
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=1087918842.2861.14.camel@turtle \
--to=rstaudemeyer@uwc.ac.za \
--cc=lartc@vger.kernel.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