 |
 |
Interesting. But I myself am still one of those throwbacks who refuses to use .docx and .xlsx as long as I can. Irrational, I know, but there it is. -- dkm On 2016-08-11 8:28 AM, Jensen, Kenneth wrote: > I can’t help with what may or may not be being blocked. But doc and docx files are very different. Doc are binary files that can contain macros which are VBA code which can do anything they want. Docx files are basically zip files that make up the whole document. They can’t contain code, that is a different extension. They can also be scanned easily by virus scanners since they can be opened like a zip file and all the pieces scanned. Excel files and some others using the new extensions work the same way. These files are more stable and often smaller in size. Everything should use these if able. > > Ken > > From: STeve Andre' [mailto:[log in to unmask]] > Sent: Wednesday, August 10, 2016 8:50 PM > To: [log in to unmask] > Subject: Re: [MSUNAG] list of file extensions blocked by msu mail? -- follow up > > 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<tel: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' > >