> I wish I could get THAT far. I'm still hosed up by the whole ssl > thing. Latest update at least had my mailbox correct (instead of some > global list I happen to own on the exchange server) so that's major > improvement. But it still refuses to use SSL (non-ssl is prohibited > here - not up for discussion and I agree with the management on that > point 1000 percent) even though I can authenticate using SSL. The > account edit always shows http: for the OWA URL (even though it even > says "use_ssl=always" in the gconf registry for that account) and I > can't authenticate against that. Change it to "https:" and I can > authenticate, but then then Ok button is grayed out and nothing I do > will re-enable that button. I have no choice but to cancel and then I > can't authenticate because non-ssl is prohibited (it can't even connect > to an non-ssl port so it bitches that the URL may be bad). Last version > where I was even able to get this two work was ages ago when the dialog > had a "use_ssl" option you could set to "always" and THAT worked. > Hasn't worked since that dialog object disappeared. Downgrading to > 2.6.0 won't resolve that (and downgrading far enough to resolve the ssl > problem would break in-line gpg which is even worse for me). >
Please try using 2.6.3 and don't try changing the gconf flags. Disable the account you are already having and try creating a new account using "https://"; in URL and if you fail to authenticate please file a bug report in bugzilla.gnome.org, specifying the error you are getting and also E2K_DEBUG traces for Evolution. for getting debug traces, set E2K_DEBUG=4 in a console and run Evolution See http://www.gnome.org/projects/evolution/bugs.shtml for more details. Thanks, Sushma. On Fri, 2006-06-09 at 17:15 -0400, Michael H. Warfield wrote: > On Fri, 2006-06-09 at 22:39 +0530, Harish Krishnaswamy wrote: > > Can you get the exchange hackers the relevant crash dumps ? > > Is there a bug report in bugzilla.gnome.org ? > > The only way I've been able to get Evolution to talk to our exchange > server lately (as in JUST lately today with this latest bug fix for the > dain bramaged mailbox bug) is with a major butt-ugly hacking using > stunnel on my local machine and jacking around with the local > static /etc/hosts file to redirect the exchange server name to a > loopback address on the local system and then through stunnel to the > actual exchange server. Gag... With that hack, I can, once again, > browse my folders on Exchange. We'll see if anything crashes but how do > you debug something when you have to work with such a hack to make it > work in the first place? > > > Sushma/Sankar : Can you follow this up, please ? > > > --Harish > > On Fri, 2006-06-09 at 12:05 -0400, kar wrote: > > > I'm having issues after upgrading with yum too. > > > > > > Anyone know how to roll back to the previous version? > > > > > > On Fri, 2006-06-09 at 06:46 -0700, Shawn Badger wrote: > > > > I have similar problems with evolution. My exchange connector was > > > > working ok with a few crashes every other day, until I installed 2.6.2. > > > > After that the exchange portion didn't crash, but maybe that was because > > > > every time I clicked into an exchange folder evolution would crash. I > > > > did a yum install evolution* out of desperation and installed all the > > > > debug and dev packages. So far no problems other than I can't seem to be > > > > able to open any bodies shared calenders yet. > > > > > > > > > > > > On Fri, 2006-06-09 at 14:34 +0200, Øyvind Gjerstad wrote: > > > > > On 6/9/06, Pete Biggs <[EMAIL PROTECTED]> wrote: > > > > > > On Thu, 2006-06-08 at 13:53 -0700, Paul Lemmons wrote: > > > > > > > <violin> > > > > > > > > > > > > > > When I upgraded to Fedora Core 5 I got Evolution 2.6.1. The > > > > > > > exchange-connector was broken. Actually it was libsoup that was > > > > > > > broken. > > > > > > > I stuck with it anyway, though. I found that if I restarted > > > > > > > Evolution > > > > > > > often enough that it would eventually come up. It was very > > > > > > > frustrating. > > > > > > > > > > > > > > Several days ago libsoup was fixed and life was finally good! No > > > > > > > more > > > > > > > crashes! On that same day 2.6.2 was also released but it had > > > > > > > trouble > > > > > > > installing due to dependencies. My global address book was still > > > > > > > broken > > > > > > > so I looked forward to the dependencies being resolved in hopes > > > > > > > that not > > > > > > > only would it be stable but it would work like it used to before > > > > > > > the > > > > > > > upgrade. > > > > > > > > > > > > > > Well 2.6.2 went on and everything has gone down the drain again. > > > > > > > Right > > > > > > > now, my machine is running at 100% busy doing what appears to be > > > > > > > nothing. If that were not the case then I would see it either > > > > > > > filtering > > > > > > > or downloading and stalling forever. Attempts to close the > > > > > > > application > > > > > > > gracefully fail. It simply ignores the fact that I click on the > > > > > > > "X". I > > > > > > > want to scream. > > > > > > > > > > > > > > It has gone from extremely bad to pretty good to absolutely > > > > > > > unusable. > > > > > > > The progression should be from really good towards excellent. Not > > > > > > > this > > > > > > > rollercoaster ride at the bottom end of acceptability. > > > > > > > > > > > > > > Is there not some way to keep this from happening? I am a devoted > > > > > > > user > > > > > > > but this is becoming intolerable. > > > > > > > > > > > > > > > > > > > It might be that you've got miss-matched versions of evolution and > > > > > > its > > > > > > backend components after the upgrade (i.e. the backends are still > > > > > > the > > > > > > ones running from 2.6.1). Try doing 'evolution --force-shutdown' > > > > > > in a > > > > > > terminal and restarting evo to see if it's any better. > > > > > > > > > > I upgraded my FC5 installation with yum update (to evo 2.6.2) . I'm > > > > > also using exchange connector, and now I don't get any new mails! To > > > > > be more precise, the folder (Inbox) lists unread messages, but they do > > > > > not appear in the message pane. If I quit evolution and restart I get > > > > > those mails, but mails that arrive after that are just listed in the > > > > > number behind Inbox. > > > > > > > > > > As fas as I can tell all my Evolution components are 2.6.2. I have > > > > > also restarted everything (and also rebooted). > > > > > > > > > > How do I debug this? > > > > > > > > _______________________________________________ > > > > Evolution-list mailing list > > > > [email protected] > > > > http://mail.gnome.org/mailman/listinfo/evolution-list > > > > _______________________________________________ > > Evolution-list mailing list > > [email protected] > > http://mail.gnome.org/mailman/listinfo/evolution-list _______________________________________________ Evolution-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/evolution-list
