I agree with you John. If the mailserver is the first point of entry onto
our networks, then the scanning and filtering should be done there. This
should be the first line of defense, antivirus and spam filtering on the
client should be an optional second line of defense. This will save on
network traffic caused by the propagation of these mail borne viruses, and
it will serve prevent the spread external to our system via e-mail.
It would be nice if the people who provide these services to us, could
consult with I.T. and user alike, and work with us to provide a system that
will provide the necessary functionality and security.
Lee Duynslager
I.T.
Integrated Plant Systems
John Valenti writes:
> hi Rob,
>
> A quick, unofficial answer is: no, the new mail.msu.edu system doesn't
> have AV or spam filters. I think they are planned as future
> enhancements. Supposedly, someone from the mail implementation team will
> attend NCC later this summer to discuss.
>
> (the new system has about 30,000 users currently. There were some
> hardware problems and maybe some concerns that it should be solidly
> supporting 70,000 users Fall semester before adding new features)
>
> -jav
>
> PS - personally I still believe the central mail system should do AV
> scanning and spam filtering, at the user's request.
>
>
> Rob Neary wrote:
>
>> There is a rather heated discussion on one of the UofM Network Admin
>> lists right now, and I wanted to ask everyone back at MSU how this
>> ended up - ?
>>
>> I remember this was discussed by - NCC? - about a year ago. Did you
>> guys end up with A/V scanning on the new pilot-placement email
>> server? And what about SPAM filtering? And - are there any
>> policy/functionally papers I can take a look and pass along to the
>> central IT people over here?
>>
>> thanks all :)
>>
>> Rob Neary
>> Senior Computer Systems Specialist
>> Medical School Information Systems
>> email: [log in to unmask] <mailto:[log in to unmask]>
>>
|
