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
576 stars 85 forks source link

O365 Calendar parsing error #325

Open konzertnr9 opened 8 months ago

konzertnr9 commented 8 months ago

I'm using davmail 6.2.1.

Recently I am having an issue where Thunderbird fails to load my calendar events due to a parsing error: image

Basically an apparent error message from the O365 server "申し訳ありません。このURLは無効または期限切れです" (which means "Sorry this URL is invalid / expired" in Japanese) is fed into the parser instead of a line of ICS data.

I'd be happy to help troubleshoot if needed.

mguessan commented 8 months ago

Can you please check davmail.log for more details on the error ? Not sure if it's a failed request or malformed event

konzertnr9 commented 8 months ago

Thank you for yor comment. What level of log should I get?

esabol commented 8 months ago

@konzertnr9 asked:

What level of log should I get?

I recommend creating a wire debug log, as described here:

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

If you prefer to edit your properties file yourself, put the following line 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!