---- Reported by jingke.zhang@intel.com 2010-04-19 19:56:51 +0000 ----

This is from http://bugzilla.moblin.org/show_bug.cgi?id=7806

   Description  From  pohly   2009-11-04 06:28:56 PST   (-) [reply]

We have a few open issues were we are waiting for comments from Funambol.
Stefano Maffuli wanted to bring them up with the Funambol developers:
* if a certain message is lost and then resent by the client, the Funambol
server
  goes into an infinite Status 222 loop
* a recurring event with alarm created in the Funambol portal is sent to
  the client as one-time TRIGGER with UTC time. The time was wrong and
  did not recurr. The alarm should have been relative to the start of the
  meeting.
* detached recurrences are not support, causing the portal to show events twice

For the last two issues, see
http://article.gmane.org/gmane.comp.mobile.syncevolution/493

------- Comment #1 From pohly 2009-12-10 04:45:35 PST (-) [reply] -------

(In reply to comment #0)
> * a recurring event with alarm created in the Funambol portal is sent to
>   the client as one-time TRIGGER with UTC time. The time was wrong and
>   did not recurr. The alarm should have been relative to the start of the
>   meeting.

It's not just the portal which gets this wrong. Events sent to the server via
SyncML are also modified so that they end up with a fixed one-time UTC TRIGGER.

------- Comment #2 From pohly 2010-04-19 05:15:19 PST (-) [reply] -------

* message resents are not handled correctly, worked around by not resending
  (BMO#10451)



--- Bug imported by patrick.ohly@gmx.de 2012-08-19 20:56 UTC  ---

This bug was previously known as _bug_ 1010 at https://bugs.meego.com/show_bug.cgi?id=1010

Unknown platform unknown. Setting to default platform "".
Unknown operating system unknown. Setting to default OS "".