topic Re: Z1 Compact Problem With EAS in XPERIA archive

Z1 Compact Problem With EAS

gkri — Thu, 02 Oct 2014 11:44:17 GMT

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

Re: Z1 Compact Problem With EAS

gkri — Fri, 03 Oct 2014 18:46:06 GMT

Come on!!!

No answer?

This supposed to be a support forum.

Also my problem is for a corporative environment is critical that the phone works with EAS, in order to use it in our company.

Please, Help.

Re: Z1 Compact Problem With EAS

SergioPL1 — Sat, 04 Oct 2014 08:30:19 GMT

Hi!

The problem is that both parties (Icewarp and Sony) are compatible with EAS. In theory everything should work fine but sometimes two compatible devices have some bugs that prevents them from working properly. My Z1C works great with Office365 implementation of EAS.

I suggest you to contact Xperia Care because we are users to users support forum not runned by Sony employees.

Re: Z1 Compact Problem With EAS

gkri — Mon, 06 Oct 2014 01:34:02 GMT

No, the problem is with Sony's Implementation od EAS. I test with 6 different Phones and the only that present the problem is Sony Z1 Compact.

Re: Z1 Compact Problem With EAS

gkri — Mon, 06 Oct 2014 22:50:34 GMT

Please, Help!!

Any Sony Expert here?

Re: Z1 Compact Problem With EAS

Rickard — Tue, 07 Oct 2014 09:09:52 GMT

Sorry to hear that you're having issues with ActiveSync.
It's not a known issue and it works fine when i test this here with MS Exchange. Would it be possible for you to provide me with a test account for further investigation?

Re: Z1 Compact Problem With EAS

gkri — Wed, 08 Oct 2014 20:40:08 GMT

Richard,

Thanks for your answer.

Can you send me a PM and I send you an account info for testing.

Best regards,

Gerardo Kri

Re: Z1 Compact Problem With EAS

gkri — Sun, 12 Oct 2014 01:46:12 GMT

Until now...... cero support.

Sony???

Re: Z1 Compact Problem With EAS

Rickard — Mon, 13 Oct 2014 07:56:19 GMT

I sent you a PM 4 days ago but you haven't responded yet?

Re: Z1 Compact Problem With EAS

gkri — Tue, 14 Oct 2014 14:34:45 GMT

Richard,

Sorry, my bad, I miss your PM.

I'm sending now the dta for the test account.

Best regards,

Gerardo Kri

Re: Z1 Compact Problem With EAS

gkri — Fri, 17 Oct 2014 21:43:13 GMT

Any news?

The test account is working OK?

Re: Z1 Compact Problem With EAS

gkri — Mon, 27 Oct 2014 01:04:49 GMT

Any news?

Re: Z1 Compact Problem With EAS

Rickard — Tue, 28 Oct 2014 08:36:32 GMT

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();

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.

Re: Z1 Compact Problem With EAS

gkri — Wed, 29 Oct 2014 19:55:55 GMT

Rickard,

Thank very much for your help.

I will be passing this information to Icewarp Support.

Best regrads,

Gerardo