 |
 |
Interesting, does kinda look like it might have been false positives. As far as I can tell, this morning the same files are going through without a problem. I'd checked them yesterday to make sure they were clean (and it was multiple .doc files that were causing problems), and if I took one and just saved it out as a .docx it went through fine. Oh well, the oddities of virus scanning. On Wed, Aug 10, 2016 at 8:49 PM, STeve Andre' <[log in to unmask]> wrote: > On 08/10/16 16:42, Gary Schrock wrote: > > Anyone know if there's a list of file extensions that msu's email blocks? > doc appears to be blocked, although docx isn't blocked, just kinda > wondering what else might be. The message you get when they're blocked > refers to a msu page on virus's that doesn't exist anymore. > > I'm not particularly surprised that doc is blocked, I was actually a > little surprised that the documents that someone in my department was > trying to send were still doc and not docx. I was a little surprised that > given doc is blocked, docx isn't. (Of course, now I'll probably have > everyone annoyed with me when the msu mail team realizes that it wasn't and > should have been, and fixes that problem :) ). > > (It's also a little annoying when the block message says it's being > blocked because of a virus, and it's not really true.) > > 550 Virus found see http://help.msu.edu/mail/virus/ or call 517-432-6200 > > And of course, that web link doesn't exist anymore. > > > I just talked with one of my faculty about exactly this. He had the > same problem trying to send a file. As a test, we renamed the > .doc file in question to ".d" and still the same error, though two > other .doc files went through. I can't see the file in question, but > this person doesn't have a history of viri, etc. > > So I think there is an intermittent false-positive viri detection problem > at the moment, unless the Perseids are bringing viri. ;-) > > --STeve Andre' > > >