An update about the Outlook 2013 folder pane issue

Just another +1 for the "get your act together" comments. Between the massive increase in defective software updates and the off-shoring and huge quality degradation of Pro Support, you're making it very, very difficult to support your products. A company as wildly profitable as MS should not have these issues: Quality and well-tested software along with top-end support for your partners should be the norm, not the exception. O365 isn't any better: Tech support for it is among the worst I've ever experienced.

support.microsoft.com/.../2825632

tt,

I believe the feature you are looking for is the "tips" and that feature already exists in Exchange 2010 and 2013. It will inform the user that they are sending to more than 100 recipients and if they try, you can prevent it. In addition, with Exchange 2013

you can also create policy tips as well.

technet.microsoft.com/.../jj649091(v=exchg.150).aspx

Would this solve you problem?

:)

Hi all.  Our environment is enterprise and we have phishing attacks which compromise accounts which send spam which then get us black listed.  This is unfortunate.  I'd like to see Exchange do the following: An administrator can set a blanket filter limit on all accounts so if one email from an account is mailed to more than a variable set number of people, say 100 people, approval is required by an administrator before the email can be sent.  The administrator phones the user to confirm the actual user is sending the email.  Exceptions can be made for specific users or limits can be changed for specific users.  The user is able to determine a set number of people who can provide a secondary approval as an alternative to the always optional administrator.   This would make it impossible for spammers to send a single email to high numbers of people without getting approval from a secondary account.

We all know there are super-smart people at Microsoft who can solve this problem.  We all know that some of the smartest people walking the planet work at MS.  

This is NOT a developer or talent issue.  This is a MANAGEMENT ISSUE.  Once again, developers at MS and the customers of MS are feeling the horror of some moronic bean counter who thinks they know more than anyone else.  The result is that the MS developers who can fix this in 5 minutes have their hands tied and we customers get to pay for it all.  Amazing how often things like this happen.

JamesNT

Even MS developers are coming out about the backdoors and workarounds that have been implemented under their watch. It is not a secret anymore. Which CU or SP will remove the security holes in Exchange 2013 so people will want to start buying this software again? As a MS partner our sales of MS services has dropped in half over this problem. It is not worth it. You are losing billions.

Y'all on the Exchange team need to fix this problem asap. We can't have Exchange servers and Outlook client completely shatting all over themselves every single damn month when we are trying to run a business.

STOP RELEASING UPDATES THAT YOU DO NOT TEST PROPERLY!!!!!!!!!

Beyond stupid. Whomever is going along with this methodology really needs to reconsider that it has been a complete fail of a process ever since Exchange 2013 was RTM. Not a single patch or update goes by that doesn't cause problems or break things.

GET YOU SHIP IN ORDER AND START PRODUCING QUALITY PRODUCTS!!!!!!!!

"I'm guessing here, but I do think that it must be on senior management radar as a big problem to address. I have no doubt that they're getting lots of complaints, and not just from nobodies posting on support threads, but from large corporate customers, the ones Microsoft listens to carefully. This problem can't be allowed to continue."

www.zdnet.com/why-all-the-errors-in-microsoft-updates-lately-7000020628

Agree. Enough is enough. Either test the patch correctly or do not issue the patches at all. Your current patch testing methodology sucks and someone needs to be shown the door.

Problem is: It's not Exchange/Outlook. It's everywhere (blogs.technet.com/.../update-rollup-3-for-system-center-2012-data-protection-manager-service-pack-1-has-been-re-released.aspx as another sample).

4 options I can see:

- Forcing customers to their cloud

- Wrong manager/programmer ratio

- MS feeling like the big shepherd - we have to follow anyway

- Complexity: The whole concept 'Windows' is starting to fail

Had a few customers experience this problem yesterday and just this morning. Uninstalling seems to fix the problem. Not sure this is an Exchange team specific issue because it was with Outlook, but...ummm....

...someone really needs to get on the ball at Microsoft in general. We can't be having problems every single month with patches. It's just killing customer satisfaction with Exchange.