Bug 474257
Summary: | Evolution cannot filter Exchange folders | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bojan Smojver <bojan> |
Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | mbarnes, mcrha, redhat-bugzilla, sb |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-03 11:11:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bojan Smojver
2008-12-03 00:29:41 UTC
Thanks for the bug report, this seems to be the upstream bug [1]. We are trying to get this fixed soon. It'll be included in 2.24.3 release, maybe sooner (no promises here). I'm sorry for the inconvenience. [1] http://bugzilla.gnome.org/show_bug.cgi?id=552583 Thanks. I find Evo 2.24 of really poor quality - it has vast number of problems. Just yesterday, I was playing with the Exchange setup and switched authentication to "Secure Password". After that, my calendar and address book stopped working. And I'm sure this Exchange supports NTLM (which doesn't?). Just ranting... *** Bug 472838 has been marked as a duplicate of this bug. *** *** Bug 474520 has been marked as a duplicate of this bug. *** Given that bug #472838 and bug #474520 have been marked as dups, perhaps this is in turn a dup of bug #476288 ? Anyway, following the advice in bug #476288 I updated to evolution-2.24.2-2.fc10 from updates-testing, and the problems I was experiencing went away. The changelog says it's carrying an update for this bugs upstream parent - bug watchers here may want to test this update. Yes, it's the other issue, caused by the same thing. The difference with this bug is that it points to the upstream bug, thus one can look for the progress there too. Anyway, you've right I should mention here that the update is available in a testing repo. I'm sorry I forgot to do that. |