Re: [Evolution-hackers] MAPI support not even close... ?!?! Can I help?

[Reid Thompson <reid thompson ateb com>]

On Fri, 2009-12-04 at 09:30 +0000, Ross Burton wrote:
> On Thu, 2009-12-03 at 16:12 -0500, Reid Thompson wrote:
> > (evolution:24437): libebook-WARNING
> > **:
> ../../../../evolution-data-server/addressbook/libebook/e-book.c:2194:
> cannot activate book: The name
> org.gnome.evolution.dataserver.AddressBook was not provided by any
> .service files 
> 
> You installed evolution-data-server into a prefix that DBus doesn't
> know
> about, so it can't autostart the daemons.
> 
> I have this in my /etc/dbus-1/session.conf:
> 
>   <servicedir>/home/ross/BUILD/share/dbus-1/services/</servicedir>
> 
> Ross

I still have something a bit off...

I added   <servicedir>/opt/evo/share/dbus-1/services/</servicedir>
as shown below.  The calendar factory and the addressbook factory now
start.

Any idea why  /usr/libexec/evolution-data-server-2.28 --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_BookFactory:1.2 --oaf-ior-fd=29
would be getting started up?


calendar -> populates using Exchange OWA
         -> does not populate using MAPI

Addressbook -> personal -> works
            -> Exchange LDAP -> works
            -> OWA Contacts -> works
            -> OWA Contacts backup -> works
            -> OWA GAL -> Error loading address book.
                                This address book cannot be opened.
                                This either means that an incorrect URI
                                was entered, or the server is
                                unreachable.
           This was working in 2.28 ( perhaps I typoed something )

           -> MAPI Contacts, Contacts backup, GAL -> I get no response
of any type from any of the three.



$ cat /etc/dbus-1/session.conf 
<!-- This configuration file controls the per-user-login-session message
bus.
     Add a session-local.conf and edit that rather than changing this 
     file directly. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration
1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
<busconfig>
  <!-- Our well-known bus type, don't change this -->
  <type>session</type>

  <!-- If we fork, keep the user's original umask to avoid affecting
       the behavior of child processes. -->
  <keep_umask/>

  <listen>unix:tmpdir=/tmp</listen>

  <standard_session_servicedirs />

  <policy context="default">
    <!-- Allow everything to be sent -->
    <allow send_destination="*" eavesdrop="true"/>
[172.16.48.3]
    <!-- Allow everything to be received -->
    <allow eavesdrop="true"/>
    <!-- Allow anyone to own anything -->
    <allow own="*"/>
  </policy>

  <!-- Config files are placed here that among other things, 
       further restrict the above policy for specific services. -->
  <includedir>session.d</includedir>

  <servicedir>/opt/evo/share/dbus-1/services/</servicedir>

  <!-- This is included last so local configuration can override what's 
       in this standard file -->
  <include ignore_missing="yes">session-local.conf</include>

  <include if_selinux_enabled="yes"
selinux_root_relative="yes">contexts/dbus_contexts</include>

  <!-- For the session bus, override the default relatively-low limits 
       with essentially infinite limits, since the bus is just running 
       as the user anyway, using up bus resources is not something we
need 
       to worry about. In some cases, we do set the limits lower than 
       "all available memory" if exceeding the limit is almost certainly
a bug, 
       having the bus enforce a limit is nicer than a huge memory leak.
But the 
       intent is that these limits should never be hit. -->

  <!-- the memory limits are 1G instead of say 4G because they can't
exceed 32-bit signed int max -->
  <limit name="max_incoming_bytes">1000000000</limit>
  <limit name="max_incoming_unix_fds">250000000</limit>
  <limit name="max_outgoing_bytes">1000000000</limit>
  <limit name="max_outgoing_unix_fds">250000000</limit>
  <limit name="max_message_size">1000000000</limit>
  <limit name="max_message_unix_fds">4096</limit>
  <limit name="service_start_timeout">120000</limit>  
  <limit name="auth_timeout">240000</limit>
  <limit name="max_completed_connections">100000</limit>  
  <limit name="max_incomplete_connections">10000</limit>
  <limit name="max_connections_per_user">100000</limit>
  <limit name="max_pending_service_starts">10000</limit>
  <limit name="max_names_per_connection">50000</limit>
  <limit name="max_match_rules_per_connection">50000</limit>
  <limit name="max_replies_per_connection">50000</limit>

</busconfig>