Are your test account and the user account on the same mailbox server and database? Just for S&G, have you tried temporarily disabling the built-in Exchange malware detection and tried it? This is a per-server setting on Mailbox servers.
On Wed, May 7, 2014 at 12:59 PM, Miller Bonnie L. < [email protected]> wrote: > Exchange 2013 cu3 (not SP1), I have one user reporting this issue with a > file that is *.xlsb. I have not heard of this, so connected remotely to > verify the issue and take screenshots: > > > > If I use an admin account to open her mailbox via OWA from another > machine, I do not have this problem with the attachment. I also had the > original sender forward the same message (with attachment) to my test > account and don't have problems there either. > > > > Doing some reading, I verified that her OWA mailbox policy is set to our > "Default" (the only one defined, so same as my test account). I also can > see that *.xlsb is allowed via these PS commands: > > Get-OwaMailboxPolicy Default | select -ExpandProperty > BlockedFileTypes (is not listed) > > And > > Get-OwaMailboxPolicy Default | select -ExpandProperty > AllowedFileTypes (is listed) > > > > Office 2010 appears to be correctly installed and otherwise working on the > Windows 7 SP1 workstation. > > > > I checked both the OWA policy and individual server virtual directory > "file access" settings via EAC and boxes are correctly checked to allow > Direct File access from both public and private devices. > > > > I'm trying to get the person to test on another machine under her account > and get access to that machine to log on my test account, but is there > anything else I can be looking at? Could *.xlsb be blocked on her account > individually somewhere (and where to look for that)? > > > > Thanks, > Bonnie > > >
