search

mguessan / davmail

DavMail POP/IMAP/SMTP/Caldav/Carddav/LDAP Exchange and Office 365 Gateway - Synced with main subversion repository at
http://davmail.sourceforge.net
GNU General Public License v2.0
578 stars 86 forks source link

Problems with calendar Item update #192

Open RTH-tools opened 2 years ago

RTH-tools commented 2 years ago

I've been seeing a lot of these ErrorInvalidPropertySet Set action is invalid for property. FieldURI: calendar:StartTimeZone recently. I believe that it only happens on calendar updates. Anything I can do to find out was is going on?

nlgranger commented 1 year ago

I also observe this issue.

Yamakuzure commented 8 months ago

Still present, my EWS-Calendar on Exchange2013 became useless by this. The Zone transferred is: "W. Europe Standard Time"

esabol commented 8 months ago

@Yamakuzure, a wire debug log might be helpful, as described here:

https://davmail.sourceforge.net/faq.html#Feedback

If you prefer to edit your properties file yourself, put the following lines in your properties file:

log4j.logger.httpclient.wire=DEBUG
log4j.logger.org.apache.http.wire=DEBUG

Quit and restart the DavMail application. Then have your mail program connect to DavMail and try to authenticate again. DavMail will then create a detailed log of what it is doing. This log will be stored in a davmail.log file. By default, it will be located in DavMail's current working directory on Linux and Windows or in ~/Library/Logs/DavMail/davmail.log on macOS. (The location of this file can be customized with the Log File Path setting.) This log file might include information like your password and other account details that you should not share online. If you are confident you can remove those things from the davmail.log file, feel free to post the sanitized file here. Otherwise, send the log file to mguessan@free.fr along with the URL of this GitHub issue. I hope this helps!

Yamakuzure commented 8 months ago

I do not get this error any more. To test another way of connecting to the Exchange Calendar, I removed the davmail caldav setup. After those tests I recreated my davmail caldav setup, and now I do not get the error any more.

In rare circumstances I get an "ErrorCorruptData" exception with davmail backtrace when trying to accept an invite, but that is cleary a different issue.