Me too!, I would love to see a solution to this.

In a SOAP SearchCalendarResourcesRequest, the sortBy and/or sortAscending option is not working, all items in the response keep the same order no matter what attribute you put in sortBy.

Does...

Also, the sortBy option is not working, all items in the response keep the same order no matter what attribute you put in sortBy.....

You may do that with start and the number of days you want to reach into the past (example is for all appointments on the last 365 days):
...

you should do it like this:


http://server/zimbra/home/grahamb/Calendar>fmt=json&start=-16&end=-15

That should give you all calendar appointments from the 16th day in the past ( from todays...

Yes, I would like to know it there's a way to users auto accept appointments from a special user.....

Hi:

I been getting this error more a more on different appointments (one works, another won't). On the user it says "Perm Denied", on the mailbox.log I see this error:

2012-02-29 12:08:14,782...

Dino and all affected users, please vote for Bug 62123 to help solve this issue.


Thanks!

ok, I have created a bug report to see if we can solve this issue:

Bug 62123

https://bugzilla.zimbra.com/show_bug.cgi?id=62123

Thanks Dino.... I hope we get an definitive answer on a fix to this error.....

The problems still exists...

Any recommendations?

Anyone....


Any information is good....

tests is simple:

HEAD <ip address of zimbra server>


Please test it, and send results.



Thanks!

Hi

Can somebody make a HEAD request to their Zimbra 7.1.1 to see if we have this error?

Thanks!

What's the procedure to open a bug report?

Also error it's the same if you do a wget --spider domain:


Spider mode enabled. Check if remote file exists.
--2011-06-30 16:28:35-- http://maildomain:/
Connecting to 10.10.0.203:80......

The error doesn't affect the services from Zimbra.

But for monitoring, HEAD it's the best option I have and still Zimbra throws the 500 error.

Ok, new update, I applied the most recent patch (P2) to Zimbra 7.1.1, but this did not resolve the HEAD 500 error.

Should I open a bug trac on this?

Also applied latest patch with same results (same error).

Any ideas?...anyone?

This also occurs on Red Hat platform

Hi:

Since the 7.1.1 upgrade I been having this error. Currently I'm monitoring the server by HEAD command, and each time I run it I get the following error:


HEAD 10.10.0.203

500 Illegal to...

Hi:

The autocomplete function won't work with japanese kanji characters in IE (all versions).

The only way to force autocomplete is:
enter name in hiragana
hit "space" bar to convert to...