Zimbra 10.1.10 Released - Please Post Your Patch/Upgrade Results Here

[liverpoolfcfan]

What is listed in the table in the main page you referenced as "Protocol Revision" is only a document control reference of some sort.

Each "ActiveSync Protocol Version" gets multiple document revisions during it's lifetime as they fix invalid references/typos/etc.

There have only ever been 7 ActiveSync Protocol Versions published. 2.5, 12, 12.1, 14, 14.1, 16 and now 16.1 is the latest.

[L. Mark Stone]

The “Cannot send email” over ActiveSync is a known issue. I opened a Support Case and have sent Zimbra lots of logs and details.

Since it is not reproducible on demand I suspect it’s a bit of a challenge to find the root cause.

So... Aren't you finding this issue only when an email is forwarded?

Forwarding was the first reporter. Other customers report the error on sending as well too now.

[adrian.gibanel.btactic]

That's interesting. Why do I find SmartForward in the Activesync Protocol 12.0 spec then?

If I go to: [MS-ASCMD]: Exchange ActiveSync: Command Reference Protocol and I click on the 12.0 version PDF I can see SmartForward command in page 75 of 360.

If you go to the document you referenced, and without changing versions, navigate in the left panel to
Expand
2. Messages
2.2 Message Syntax
2.2.1 Commands
2.2.1.19 SmartForward

You will see the first Element in the Table is the SmartForward element referencing - section 2.2.3.169

Click on it, or navigate to that section in the left panel.

You will see that the SmartForward Element it is only supported in ActiveSync protocols 14 and above.

Edit: Fixed typo

I see there is an old Activesync SmartForward which expects a MIME (less than protocol 14) and a new one which expects a WBXML (XML Elements) (higher or equal than protocol 14).

Apparently when some Activesync clients send the SmartForward command with protocol 12.1, well, it says it's an invalid command not supported in this activesync version. I now suspect that what it does not like is its argument type (either MIME or WBXML), the logs message might be a default exception error message triggering which hides the actual problem.

Anyways, let's wait for Zimbra developers to find out what's going on with all of this because I get different errors (500 error) when the ActiveSync client uses Protocol 16 and, well, Mark says that his ActiveSync clients cannot even send.

So far (from the outside) I count 3 different issues regarding ActiveSync in this version.

[Klug]

The ActiveSync issue is supposed to be fixed (for iOS) in 10.1.11 (out today).

[marco76mk]

Hi Klug

I confirm that the bug has been fixed with patch 10.1.11
Already tested

[adrian.gibanel.btactic]

Apparently when some Activesync clients send the SmartForward command with protocol 12.1, well, it says it's an invalid command not supported in this activesync version. I now suspect that what it does not like is its argument type (either MIME or WBXML), the logs message might be a default exception error message triggering which hides the actual problem.

Anyways, let's wait for Zimbra developers to find out what's going on with all of this because I get different errors (500 error) when the ActiveSync client uses Protocol 16 and, well, Mark says that his ActiveSync clients cannot even send.

So far (from the outside) I count 3 different issues regarding ActiveSync in this version.

I just wanted to update you about my ActiveSync issues in ZCS NE 10.1.9 and also ZCS NE 10.1.10.

The only actual issue that we had was with ZCS NE 10.1.10. Forwarding in iOS issued an error but it forwarded the email properly. This was fixed in ZCS NE 10.1.11.

The other issues regarding Samsung Email app and Gmail app also regarding forwarding emails... were a consequence of a migration from Activesync NG to Activesync NE.

---

In the Activesync NG to Activesync NE transition:
- Some of the ActiveSync device accounts were not removed and added again.
- zimbraMobileForceSamsungProtocol25 was not set to TRUE for Samsung Email apps (as Zimbra recommends).

Somehow when the iOS forwarding issue happened in ZCS NE 10.1.10 those forwarding issues arose/were found in Samsung Email app/Gmail app.