That's only partially true. The virus blocking will affect all mail sent
to [log in to unmask] (Pilot or otherwise). It will not affect mail sent to
[log in to unmask], unless it goes through mail.msu.edu for some reason
(e.g. the sender is using mail.msu.edu).
> However, for what it's worth, the virus blocking will affect Pilot accounts
> as well as mail.msu.edu accounts. The announcement sent to deans,
> directors, etc. glosses over this fact, making it sound as though the virus
> blocking only affects those who have converted.
> At 09:59 AM 12/9/2003, George J. Perkins wrote:
> >The loophole was that the soon-to-be-announced-at-that-time upgrade to
> >mail.msu.edu was considered as setting up a new system, so a user making
> >the switchover could look at the fine print (somewhere) and see that the
> >possibility for anti-virus scanning was part of the system and, by
> >continuing to make the switchover, implicitly opt in to that behavior
> >(whether it was actually activated at the time or not).
> >So, as long as the mail.msu.edu upgrade procedure or documentation mention
> >anti-virus scanning somewhere, it's probably not an issue (at least not a
> >major one).
> Chris Wolf Computer Service Manager
> Agricultural Economics [log in to unmask]
> Michigan State University 517 353-5017
Doug Nelson [log in to unmask]
Network Manager Ph: (517) 353-2980
Computer Laboratory http://www.msu.edu/~nelson/
Michigan State University