Description of problem: Evolution can't retrieve Yahoo! calendar and tasks because something is wrong with the way it determines the address. Version-Release number of selected component (if applicable): 3.16.3 How reproducible: Every time Steps to Reproduce: 1. Create a Yahoo! mail account. I use bill_chatfield 2. Select the option to sync calendar and tasks also. 3. Actual results: This is the exact error message: Unexpected HTTP status code 8 returned (Message Corrupt) for URI: https://bill_chatfield%40yahoo.com@caldav.calendar.yahoo.com/dav/bill_chatfield%40yahoo.com/Calendar/Bill_Chatfield/ Expected results: Evolution would be able to read my Yahoo! calendar and tasks without throwing an error. Additional info: N/A
Thanks for a bug report. (In reply to Bill Chatfield from comment #0) > Evolution can't retrieve Yahoo! calendar and tasks > because something is wrong with the way it determines the address. The Evolution determines the address based on the redirections the Yahoo! server provides. I know it used to work, but since some (probably) server change it stopped working and the server begun to return "Message Corrupt" error. I tried to investigate it in the past, also checking the correctness of the used addresses, but I didn't find any clear fault on the evolution(-data-server) side. If you think the address is wrong, are you aware of the correct address? I am not able to connect to Yahoo! calendar using these [1] instructions in thunderbird too. It even doesn't tell me what's going wrong, so hard to tell. [1] https://support.mozilla.org/en-US/kb/thunderbird-and-yahoo#w_sync-your-calendar
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.