9124 was a dream come true, I'm hoping that trend continues... Yes, I +1 OP...
Please let us know how your 9147 experience is going

9124 has been a good one. Testing the 9147 build today...

I can't give definitive results because I have too little feedback for now, but it seems to be going much better...

Today I'm trying to update a production server with few users and let's see how it goes...

Well, we have problems with MAPI:

Shares Calendar as well as folder permissions seems to be not applicated means:

I have users with full access rights on a calendar, however for them, it shows only "occupied" and they have no ability to add something because they seem to have not enough rights.

For calendar invites, we have disappearing calendar items (it seems to get worse if the calendar objects are part of a series).

All shared calendars is shown as busy and not detailed and not able to edit/change permissions in webmail.

My colleagues is experiencing the same and its server wide. I will try to change permissions in outlook to se if it can be changed.

Picture is from a small clients mail.

This is his permissions in outlook

Its not working

Downgraded to 9124....and its working again.

Submitted a ticket for this

0E0-2F20DA37-0002

Oh, no, Fuck! This 9147 solved my "MAPI MAIL SYNC" issue, but introduce this new blocking issue in CALENDARS so (again...) I cannot update my production server...

I have to stay on 8930 again...

So far I'm not able to reproduce this in house. Did the users who are able to see availability information have access to the shared resources in the past or have they never had access?

For me they have had full acces (owner) (and it was working fine until i did the upgrade)

(I also tried to remove and readd the permissions but it does not change)

Thanks Daniel, I'll do some testing and let you know what I come up with!

I have this replicated now, sorry for the confusion. I had thought the issue was users seeing calendar entries they shouldn't rather than the reverse. I just set up a Manage permission shared calendar in my MAPI client and see only availability, so I should have enough to get this over to development now.

If you go into Folder View within your Outlook and find the shared calendar under Public Folders > Right click on the shared calendar and go to Add to favorites, do you still see the same behavior?

The issue appears to be that the view permissions aren't being applied on the Outlook MAPI side. I was able to replicate with Read Only as well so I've noted this with development and have the issue escalated now.

I can't believe it. We recently had to force a customer to move from using EAS in his Outlook Desktop, to MAPI, because it seems there is an issue with SmarterMail EAS implementation and recurring events and/or all day appointments that were shifted a day in the past.

We're also always told that EAS is deprecated on Outook Desktop, but it works like a charm with other products like sOGO's implementation of EAS...

So after the user migrated to MAPI it seems indeed to fix the day shift issue, but now the customer can't use the shared calendars he had setup as they appear like if they were read only in his Outlook, when this was working correctly with EAS!

We run build 9147 which was supposed to fix the EAS issue but it didn't and seems it added this new issue.

This is unacceptable. We look like a joke to our customers.

Downgrade to 9124 and it works again no issues.

Well yes, but I'm really tired to play this upgrade -> pray -> cry -> downgrade game and having to wake up in the middle of the night almost every week to do the upgrades/downgrade.

We unfortunately can't affrord a service interruption during the day.

Of course annoying bugs in software can occurs. But here it's always deal breakers bugs and constantly. Really most of the time the fixes in new releases are fixes for issues introduced in previous build.

Sorry for the rant but I am very angry and need to release the pressure

I think most of the pro userbase feels the same way Sebastien.

EAS doesn't support read-only shares. Infact native EAS doesn't support shares at all, we just treat Full-Access as a regular folder and that lets it show up in EAS despite not even have sharing functionality at all. I'm talking about native EAS, not some plugin you add onto outlook.

also... WE were told BY MICROSOFT that EAS in Outlook is deprecated. So it may seem fine and dandy, until Microsoft decides to pull the rug in X years, like they are already doing with their current apps.

Heyy Matt. Nobody is throwing rocks here but heyy... should an issue like permissions on shared services slip through QC??

Why did nobody at SM pick this up in testing? It shows right away when opening shared calenders and is replicable for all users.

I get that some of the minor things can slip through but this is business critical to many users and providers.

We look like idiots to our customers. Thats the real issue here...

MAPI is not an easy protocol, and Microsoft themselves have moved on from it, Outlook has like 3 different types of versions depending on how you chose to give them money, each with their own versioning track, it works different in some aspects on OS's of an alternative language, Outlook will make artitrary changes like moving functionality that was in MAPI into being called via EWS instead (depending on the 'flavor' of Outlook), it's a binary protocol, not everything is in the online documentation, I could go on and on...

It's impossible to test every edge case with every change. Granted this was a more notificible and isn't a small edge case and we're already triaging a fix for it.

This is the exact reason why we are calling for an LTSC release and an DEV release channel.

We run this is production and running LTSC on everything else only running those updates that are bulletproof and not pissing our cutsomers off.

:)

If you were a carmaker then right now it looks like every release of updates for the car brings other issues or recurring issues.

No one that buys a car would live with that. To do a comparison... the last update is a drivable car but the aircon doesnt work and the seats are gone...

You can drive it, but it sucks to everyone.

Now lets have a good release with no errors and everything MAPI/EAS related working.

We need that.

By the way... 9124 is currently working well for us with very minor issues.

Congrats on your new president today.

Send custom build ASAP