← Back to team overview

desktop-packages team mailing list archive

[Bug 770623] evolution doesn't disconnect MAPI/Exchange connection when MAPI account is disabled

 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the stable
release - Oneiric Ocelot. It would help us greatly if you could test
with it so we can work on getting it fixed. You can find out more about
the development release at http://www.ubuntu.com/testing/ . Thanks again
and we appreciate your help.

** Changed in: evolution (Ubuntu)
   Importance: Undecided => Low

** Changed in: evolution (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/770623

Title:
  evolution doesn't disconnect MAPI/Exchange connection when MAPI
  account is disabled

Status in “evolution” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: evolution

  Evolution 2.30.3 on Ubuntu 10.10.

  I was playing around with MAPI setup and had  successfully connected
  to an exchange server, and also had a previous IMAP account working. I
  decided to disable the MAPI for now and come back to using it later.
  However, I noticed that connections to MAPI server continued to exist
  after I disabled the feature in the UI several days earlier. A restart
  of evolution cleared the following connections up.

  Evolution should not keep lingering connections to an account once
  that account has been disabled.

  lsof -Pnl +M -i4 dump:
  evolution  3007    16430   56u  IPv4  208421      0t0  TCP my-machine:55057->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   58u  IPv4  208435      0t0  TCP my-machine:45489->exchange-host:36410 (ESTABLISHED)
  evolution  3007    16430   61u  IPv4  208467      0t0  TCP my-machine:55063->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   64u  IPv4  208495      0t0  TCP my-machine:55067->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   66u  IPv4  208509      0t0  TCP my-machine:45499->exchange-host:36410 (ESTABLISHED)
  evolution  3007    16430   71u  IPv4  208843      0t0  TCP my-machine:46838->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   74u  IPv4  208879      0t0  TCP my-machine:46842->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   76u  IPv4  208893      0t0  TCP my-machine:33355->exchange-host:36410 (ESTABLISHED)
  evolution  3007    16430   77u  IPv4  400716      0t0  TCP my-machine:54466->imap-host:143 (ESTABLISHED)
  evolution  3007    16430   82u  IPv4  400745      0t0  TCP my-machine:43323->exchange-host:36390 (ESTABLISHED)
  evolution  3007    16430   86u  IPv4  400759      0t0  TCP my-machine:36881->exchange-host:36410 (ESTABLISHED)
  evolution  3007    16430   87u  IPv4  400763      0t0  UDP my-machine:2500

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: evolution 2.30.3-1ubuntu7.3
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-28-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Apr 25 18:24:16 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/770623/+subscriptions