通过ActiveSync同步ConversationId属性中的更改 [英] Synchronising a change in the ConversationId property via ActiveSync

查看:66
本文介绍了通过ActiveSync同步ConversationId属性中的更改的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


我们正在我们自己的服务器中实现ActiveSync 14.



到目前为止,我们一直无法说服任何ActiveSync客户端(iOS Mail.app,Outlook iOS)更改电子邮件项目的ConversationId属性  一次
项目已到达客户端
 (邮件项目X与会话ID Y同步稍后在服务器上重新计算会话ID到Z)。



此时我们想知道是否可以通过普通同步机制(同步读/未读或标记状态时使用的那个)更改邮件项的ConversationId属性)。规范说客户必须通过更改ConversationId来阻止
,但它没有说服务器应该或不应该更改它(MS-ASEMAIL 2.2.2.21)。



ConversationId属性在ActiveSync中被认为是不可变的吗?

解决方案

CristianDr,



感谢您的提问。工程师会尽快与您联系。



We are working in implementing ActiveSync 14 in our own server.

So far we have been unable to convince any ActiveSync client (iOS Mail.app, Outlook iOS) to change the ConversationId property for an email item once the item has arrived on the client (mail item X is synced with conversation id Y and later on the server re-computes the conversation id to Z).

At this point we are wondering if it's at all possible for a mail item's ConversationId property to be changed through the normal sync mechanism (the one that is used when syncing the read/unread or flagged state). The spec says the client must be prevented from changing the ConversationId but it doesn't say that the server should or should not change it (MS-ASEMAIL 2.2.2.21).

Is the ConversationId attribute considered immutable in ActiveSync?

解决方案

CristianDr,

Thank you for your question.  An engineer will contact you soon.


这篇关于通过ActiveSync同步ConversationId属性中的更改的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆