Red Hat Bugzilla – Bug 217713
Kontact Exchange Calander Function tries to use webdav all the time, even if Exchange only wishes http
Last modified: 2008-05-06 12:59:13 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:220.127.116.11) Gecko/20061107 Fedora/18.104.22.168-1.fc6 Firefox/22.214.171.124 pango-text
Description of problem:
When I try to connect to my Exchange Calander using kontact (calander function), it can see that the service is there (mailbox) because it uses the correct http form to get that information (much like Evolution Connector does), but when I try to download anything from the calander, it tries to use webdav as the protocol of choice, and our exchange servers do not have this as an option. Is there no way to use the http protocol instead?
Also, just as a wish list, is there some way in the future to integrate the Evolution Connector functionality into kontact. I prefer kontacts search, archive, and overall look compared to evolution, but our admins have internally disabled IMAP, so we can no longer get to our exchange using kontact. Just a wish list there...
Thanks for your help,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Choose correct mailbox
2. Verify mailbox (uses correct http settings and finds mailbox)
3. Try to download calander events... Fails due to unsupported webdav (on server side, even though the server asks for authentication)
I get the following if I try this with konqueror:
An error occurred while loading webdav://hoexmb9.conoco.net/exchange/weathnr:
The file or folder webdav://hoexmb9.conoco.net/exchange/weathnr does not exist.
If it worked correctly, hopefully I would get my calander events in kontct.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.