Join now - be part of our community!

Z1 Compact Problem With EAS

gkri
Visitor

Z1 Compact Problem With EAS

I have problems to correctly make my Xperia Z1 Compact works with EAS (Exchange Active Sync).

My Xperia is on latest firmware 14.4.A.0.108.

My Server is an implementation of Icewarp (Version 11.0.1.2), with full support for EAS (Protocols 2.5, 12, 12.1, 14 and 14.1) with s/mime; and pass all the Microsoft EAS and auto provisioning connectivity test.

The problem is:

  • All messages in Xperia are in Plain Text and no in HTML.

Details:

  • The problem are in EAS version 12, 12.1, 14 and 14.1
  • The messages are OK in EAS version 2.5
  • The messages are OK with IMAP
  • At server level, there are NO restriction to the message format.
  • At server level Truncate are set at NOT Truncate (-1)
  • The server use a Self-Signed Certificate.

I have several other devices connected with EAS without a problem (Windows, IOS, Android), the problem only exist with Xperia Z1 Compact.

According with Icewarp support, the problem is a faulty implementation of EAS on Sony’s side.

I really need your help.

Best regards,

Gerardo

13 REPLIES 13
gkri
Visitor

Any news?

The test account is working OK?

gkri
Visitor

Any news?

Rickard
Master

Our developers have investigated this and they are sure this is not a problem in our software. From what they can see the issue is that Icewarp doesn't follow the EAS protocol properly.

You need to contact Icewarp again regarding this issue.

If needed, provide them with the following information:

1. No attachments are sent via the sync Add(Sync) element when specifying mime always in the mime support tag and mime in the body type in the Sync command. Even though you can get the attachments from the raw mime data, there is a possibility to do a truncated MIME sync (which we are doing) and then you will not be able to retrieve the attachments from the raw mime data as it is truncated. So you always need to send the attachments even if mime is requested as a body type. This is how all microsoft servers work and all other third party exchange servers we have tested, except IceWarp server and the Zarafa server. And they have an open bug in their backlog about this. (https://jira.zarafa.com/browse/ZP-534).

2. We are using ItemOperations command to retrieve the body. In the options tag for the item operations we specify options like below:

        s.start(Tags.ITEMS_OPTIONS);

        if (mIsSmimeEnabled) {

            s.data(Tags.SYNC_MIME_SUPPORT, Eas.MIME_BODY_PREFERENCE_MIME_IF_SMIME);

            s.start(Tags.BASE_BODY_PREFERENCE);

            s.data(Tags.BASE_TYPE, Eas.BODY_PREFERENCE_MIME);

            s.end();

        }

        if (mAllowHtml) {

            s.start(Tags.BASE_BODY_PREFERENCE);

            s.data(Tags.BASE_TYPE, Eas.BODY_PREFERENCE_HTML);

            s.data(Tags.BASE_TRUNCATION_SIZE, mHtmlLimit);

            s.end();

        }

        s.start(Tags.BASE_BODY_PREFERENCE);

        s.data(Tags.BASE_TYPE, Eas.BODY_PREFERENCE_TEXT);

        s.data(Tags.BASE_TRUNCATION_SIZE, mTextLimit);

        s.end();

        s.end();

This is valid to do according to the EAS specification. But when this is done IceWarp always return plain text data for the body. I tested to only specify the HTML body type and then IceWarp sent HTML back. But this should not be needed, you should be able to send body preference tags for all body types. All microsoft servers and all other third party exchange servers we have tried supports this.

gkri
Visitor

Rickard,

Thank very much for your help.

I will be passing this information to Icewarp Support.

Best regrads,

Gerardo