Yes. If your client requires this for EAS 2.5 then it's broken, or
doesn't support 2.5.

I think we can close this bug. The user manual for the DesireHD states
that Exchange 2003 Sp2 is supported. I will reset my phone and see if
that fixes my problems. If i find any solution i will just post it.

I have only problems with them on my DesireHD. I tested with an
iphone and it works out of the box. In the ActiveSync properties of
the device i have the following Entry:
Programm:Android-EAS/3.10.000.037285.405.

When i apply the patch to send the dayofmonth and monthofyear for the
monthly and yearly events, they occur in the calendar. It seems that
the sync on the DesireHD just throws the events away when these
properties are not set.

If you are talking about recurrence_month_date events, then your
client is broken.

Furthermore, exchange does not send these fields in this case either.

So i think they should be sent.

Impossible, it's not defined in any of the wbxml codepages/schema for EAS 2.5

I have only problems with them on my DesireHD. I tested with an
iphone and it works out of the box. In the ActiveSync properties of
the device i have the following Entry:
Programm:Android-EAS/3.10.000.037285.405.

When i apply the patch to send the dayofmonth and monthofyear for
the monthly and yearly events, they occur in the calendar. It seems
that the sync on the DesireHD just throws the events away when these
properties are not set.

If you are talking about recurrence_month_date events, then your
client is broken. These properties make no sense with this recurrence
type. For the recurrence_month_day type, they are already sent.

The notes/changes section of the reference also does not mention
that this fields are not supported on older revisions of active sync
like for CalendarType.

Yes, it does. I'm on my mobile right now so I can't give a link, but
it's there.

So i think they should be sent.

Impossible, it's not defined in any of the wbxml codepages/schema for EAS 2.5

I don't have a

proof for it but that it works for me when they are sent. Can also
be a buggy implementation of the sync for the DesireHD

Yes. If your client requires this for EAS 2.5 then it's broken, or
doesn't support 2.5.

I do not know a case where it fails. My problem is that the
reference does not exactly define the week of the month. You can on
the one hand say the first week are the first seven days. You can
also define the first week as the first monday to sunday. So if the
month starts on a friday only the first three days are the first
week. Just a matter of definition. It seems to work so it does not
need to be changed.

In this context, It's the first week with any days in the month.
Nothing else would make sense since the recurrence types that use this
recur on e.g., the first tuesady of the month. Any other definition
would potentially miss days in the first week.

AFAIK, this type is for the same _date_, not the dayofyear.

If we can not create such an event on outlook then we do not need to
sync it. The only problem for me is that you can create an event on
the web client that will never show up on the sync clients. Is there
an easy way to remove this type of event or to prevent the users to
create such an event?

Not without hacking the kronolith code. I agree it's a potential
issue, but don't think we shuld limit our feature set based on a
limited sync protocol.

Can you provide an example event that this fails for? All monthly
recurring events I have tested are working fine for me.

I have only problems with them on my DesireHD. I tested with an iphone
and it works out of the box. In the ActiveSync properties of the
device i have the following Entry:
Programm:Android-EAS/3.10.000.037285.405.

When i apply the patch to send the dayofmonth and monthofyear for the
monthly and yearly events, they occur in the calendar. It seems that
the sync on the DesireHD just throws the events away when these
properties are not set.

The notes/changes section of the reference also does not mention that
this fields are not supported on older revisions of active sync like
for CalendarType. So i think they should be sent. I don't have a proof
for it but that it works for me when they are sent. Can also be a
buggy implementation of the sync for the DesireHD

I am not really sure about the weekofmonth calculation. The reference
which i linked in my first post does not state whether a week starts

Can you provide an example where this calculation fails? We have
been using this calculation in our recurrence code for ages.

I do not know a case where it fails. My problem is that the reference
does not exactly define the week of the month. You can on the one hand
say the first week are the first seven days. You can also define the
first week as the first monday to sunday. So if the month starts on a
friday only the first three days are the first week. Just a matter of
definition. It seems to work so it does not need to be changed.

[Show Quoted Text - 12 lines][Hide Quoted Text]

I found also another Bug. If you set the recurrence to yearly and to
same day of the year (Type 6 in Recurrence.php), no recurrenc type

This type of recurrence is not supported AFAIK by AS 2.5. Using a
real exchange 2003 server and outlook I cannot create this type of
recurrence series. If you have a working patch that this works for,
along with a test event to prove it, I can look into adding.

ist sent. I think we can use the active sync type 5 (TYPE_YEARLY) to
send it to the device.

AFAIK, this type is for the same _date_, not the dayofyear.

If we can not create such an event on outlook then we do not need to
sync it. The only problem for me is that you can create an event on
the web client that will never show up on the sync clients. Is there
an easy way to remove this type of event or to prevent the users to
create such an event?

Can you provide an example event that this fails for? All monthly
recurring events I have tested are working fine for me.

I am not really sure about the weekofmonth calculation. The
reference which i linked in my first post does not state whether a
week starts

Can you provide an example where this calculation fails? We have been
using this calculation in our recurrence code for ages.

I found also another Bug. If you set the recurrence to yearly and to
same day of the year (Type 6 in Recurrence.php), no recurrenc type

This type of recurrence is not supported AFAIK by AS 2.5. Using a
real exchange 2003 server and outlook I cannot create this type of
recurrence series. If you have a working patch that this works for,
along with a test event to prove it, I can look into adding.

ist sent. I think we can use the active sync type 5 (TYPE_YEARLY)
to send it to the device.

AFAIK, this type is for the same _date_, not the dayofyear.

By the way: do you hav another source than the one posted by me to
get the command reference for active sync 2.5? This version is not
really mentioned in the reference, only the newer ones.

Unfortunately, not a single soource. You need to read the
footnotes/changes section. There are also some postings linked to in
the wiki that give some overviews of the different versions, but not
that detailed. Also, when in doubt, I just sniff the traffic of a real
exchange 2003 server.

After trying your git commit i still cannot see the monthly events.
Sorry that the patch was not attached, was really late today in the
morning here. I adapted the patch to your changes.

I am not really sure about the weekofmonth calculation. The reference
which i linked in my first post does not state whether a week starts
alwas on a given day or if we can only divide by 7. That is the reason
why i used the posted function to calculate it.

I found also another Bug. If you set the recurrence to yearly and to
same day of the year (Type 6 in Recurrence.php), no recurrenc type ist
sent. I think we can use the active sync type 5 (TYPE_YEARLY) to send
it to the device.

By the way: do you hav another source than the one posted by me to get
the command reference for active sync 2.5? This version is not really
mentioned in the reference, only the newer ones.

The problem is not really fixed. I am still not able to sync the
yearly and daily events with the git version.

I added the missing properties to
framework/ActiveSync/lib/Horde/ActiveSync/Message/Appointment.php. The
patch is attached.

This is only a quick and dirty! patch to make it work with the android
sync. It should seriously be reviewed!! I had no good idea how to
extract the day an mont number from the starttime so i just exploded
the string.

CalendarType is not required. It was added in EAS Version 14 (Exchange
Server 2010), we currently only support EAS Version 2.5 (Exchange
2003sp2). You can verify this yourself by looking at the footnotes in
the document you linked to.

I will look into the other reports, though on initial inspection I
can't reproduce all of them.