Mailing List Archive

I believe that there are two ways to get into the address book. Exchange
5.5 has a 'GAL', the Global Address List with a proprietary
protocol, but with an optional LDAP access mode. In Exchange 2000, I
believe that the LDAP access is default via Active Directory.

As eluded to by a post a few (months?) ago, Exchange exports all of its
data via IMAP. If this is the case, we should see if there's a particular
message format that contains addresses that we can emulate.

If the only route in LDAP, then it's a more complex matter of getting
together a schema that does what Outlook expects. The Samba HEAD branch
(version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
doubt that they have the Exchange schema changes, though... I think
they're published in an MSDN document.

Aaron


On Wed, 23 Apr 2003, Jesse Norell wrote:

>
> Hello,
>
> Anyone familiar with Exchange server who could explain what is in
> their address book, and any details that would seem pertinent to dbmail
> supporting it? I'm really working on weDBmail here, but if dbmail plans
> to be Exchange compatible, and Exchange supports address books (which
> I would assume it does, but maybe not), then I might as well try to
> design the address book forward-thinking to dbmail adopting the same
> tables.
>
> Thanks,
> Jesse
>
>
> --
> Jesse Norell
> jesse (at) kci.net
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Wed, 23 Apr 2003
13:51:52 -0700 (PDT), wrote:

> I believe that there are two ways to get into the address book. Exchange
> 5.5 has a 'GAL', the Global Address List with a proprietary
> protocol, but with an optional LDAP access mode. In Exchange 2000, I
> believe that the LDAP access is default via Active Directory.
> As eluded to by a post a few (months?) ago, Exchange exports all of its
> data via IMAP. If this is the case, we should see if there's a particular
> message format that contains addresses that we can emulate.

What about MAPI and MSRPC in general?

> If the only route in LDAP, then it's a more complex matter of getting
> together a schema that does what Outlook expects. The Samba HEAD branch
> (version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
> doubt that they have the Exchange schema changes, though... I think
> they're published in an MSDN document.


cheers,
-lk

Isn't the 'API' in 'MAPI' actually for once an apt description of this
Microsoft technology? That is, MAPI is a set of library function calls
rather than a protocol... correct me if I'm wrong, however!

Getting into MSRPC might be rather difficult, and I would hope to avoid
such a beast. If that really is the way, though, there is skeleton code
in both Samba and Samba-TNG that can be leveraged to provide a framework,
then simply hang support for the appropriate MSRPC calls off of it.

Aaron


On Thu, 24 Apr 2003, lou wrote:

> In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Wed, 23 Apr 2003
> 13:51:52 -0700 (PDT), wrote:
>
> > I believe that there are two ways to get into the address book. Exchange
> > 5.5 has a 'GAL', the Global Address List with a proprietary
> > protocol, but with an optional LDAP access mode. In Exchange 2000, I
> > believe that the LDAP access is default via Active Directory.
> > As eluded to by a post a few (months?) ago, Exchange exports all of its
> > data via IMAP. If this is the case, we should see if there's a particular
> > message format that contains addresses that we can emulate.
>
> What about MAPI and MSRPC in general?
>
> > If the only route in LDAP, then it's a more complex matter of getting
> > together a schema that does what Outlook expects. The Samba HEAD branch
> > (version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
> > doubt that they have the Exchange schema changes, though... I think
> > they're published in an MSDN document.
>
>
> cheers,
> -lk
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Thu, 24 Apr 2003
05:13:26 -0700 (PDT), wrote:

> Isn't the 'API' in 'MAPI' actually for once an apt description of this
> Microsoft technology? That is, MAPI is a set of library function calls
> rather than a protocol... correct me if I'm wrong, however!

it's relevant with MSRPC. but yes you're right.

> Getting into MSRPC might be rather difficult, and I would hope to avoid
> such a beast. If that really is the way, though, there is skeleton code
> in both Samba and Samba-TNG that can be leveraged to provide a framework,
> then simply hang support for the appropriate MSRPC calls off of it.

Some more reverse engineering has to be done. Shame that MSRPC isnt a
generic dce/rpc. Also I think MSRPC should be the main concern.
On other hand, dbmail can be RAD'd to a state higher than MS Exchange. But the
compatibility with a different email clients is a different issue(excluding pop3/imap),
for Outlook it's easy to write an addin to draw the nice callendar(ie comm module) and
store all the data(let say callender data, notes so so..) into a database.

Have you seen HP OpenMail(Now Samsung Contact)?

cheers

> > In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Wed, 23 Apr
> > 2003 13:51:52 -0700 (PDT), wrote:
> >
> > > I believe that there are two ways to get into the address book. Exchange
> > > 5.5 has a 'GAL', the Global Address List with a proprietary
> > > protocol, but with an optional LDAP access mode. In Exchange 2000, I
> > > believe that the LDAP access is default via Active Directory.
> > > As eluded to by a post a few (months?) ago, Exchange exports all of its
> > > data via IMAP. If this is the case, we should see if there's a particular
> > > message format that contains addresses that we can emulate.
> >
> > What about MAPI and MSRPC in general?
> >
> > > If the only route in LDAP, then it's a more complex matter of getting
> > > together a schema that does what Outlook expects. The Samba HEAD branch
> > > (version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
> > > doubt that they have the Exchange schema changes, though... I think
> > > they're published in an MSDN document.
> >
> >
> > cheers,
> > -lk
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev@dbmail.org
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> >
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

Oh I get it, you use MSRPC to call into MAPI? So basically, we're talking
about taking the daemonizing MSRPC server from Samba and implementing
MAPI's function calls. At least it means we're not starting from the point
of a wiretap on an Outlook<-->Exchange conversation and trying to figure
that out from scratch!

Aaron

On Thu, 24 Apr 2003, lou wrote:

> In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Thu, 24 Apr 2003
> 05:13:26 -0700 (PDT), wrote:
>
> > Isn't the 'API' in 'MAPI' actually for once an apt description of this
> > Microsoft technology? That is, MAPI is a set of library function calls
> > rather than a protocol... correct me if I'm wrong, however!
>
> it's relevant with MSRPC. but yes you're right.
>
> > Getting into MSRPC might be rather difficult, and I would hope to avoid
> > such a beast. If that really is the way, though, there is skeleton code
> > in both Samba and Samba-TNG that can be leveraged to provide a framework,
> > then simply hang support for the appropriate MSRPC calls off of it.
>
> Some more reverse engineering has to be done. Shame that MSRPC isnt a
> generic dce/rpc. Also I think MSRPC should be the main concern.
> On other hand, dbmail can be RAD'd to a state higher than MS Exchange. But the
> compatibility with a different email clients is a different issue(excluding pop3/imap),
> for Outlook it's easy to write an addin to draw the nice callendar(ie comm module) and
> store all the data(let say callender data, notes so so..) into a database.
>
> Have you seen HP OpenMail(Now Samsung Contact)?
>
> cheers
>
> > > In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Wed, 23 Apr
> > > 2003 13:51:52 -0700 (PDT), wrote:
> > >
> > > > I believe that there are two ways to get into the address book. Exchange
> > > > 5.5 has a 'GAL', the Global Address List with a proprietary
> > > > protocol, but with an optional LDAP access mode. In Exchange 2000, I
> > > > believe that the LDAP access is default via Active Directory.
> > > > As eluded to by a post a few (months?) ago, Exchange exports all of its
> > > > data via IMAP. If this is the case, we should see if there's a particular
> > > > message format that contains addresses that we can emulate.
> > >
> > > What about MAPI and MSRPC in general?
> > >
> > > > If the only route in LDAP, then it's a more complex matter of getting
> > > > together a schema that does what Outlook expects. The Samba HEAD branch
> > > > (version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
> > > > doubt that they have the Exchange schema changes, though... I think
> > > > they're published in an MSDN document.
> > >
> > >
> > > cheers,
> > > -lk
> > >
> > > _______________________________________________
> > > Dbmail-dev mailing list
> > > Dbmail-dev@dbmail.org
> > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> > >
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev@dbmail.org
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> >
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Thu, 24 Apr 2003
07:48:20 -0700 (PDT), wrote:

> Oh I get it, you use MSRPC to call into MAPI? So basically, we're talking
> about taking the daemonizing MSRPC server from Samba and implementing
> MAPI's function calls. At least it means we're not starting from the point
> of a wiretap on an Outlook<-->Exchange conversation and trying to figure
> that out from scratch!
>
> Aaron

that's just a logical suggestion, that's where i got stuck - MSRPC, i didnt want to
take MSRPC's way, because a simple add-in was doing the job perfectly and comparing
msrpc-emul(code/time) vs addin(code/time), i've chosen addin.

Yeah but you still have to figure out what the calls are and alter samba's msrpc port to
do only this, that means reverse engineering or (anyone can get hold of the Outlook
code?) to find a msrpc hacker to explain the things rather than the 1st one :))

Actually that's way i mentioned HP OpenMail they already did it though.. and i have copy
anyone wants it? (i havent got much time exploring it ;/)

cheers

> > In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Thu, 24 Apr 2003
> > 05:13:26 -0700 (PDT), wrote:
> >
> > > Isn't the 'API' in 'MAPI' actually for once an apt description of this
> > > Microsoft technology? That is, MAPI is a set of library function calls
> > > rather than a protocol... correct me if I'm wrong, however!
> >
> > it's relevant with MSRPC. but yes you're right.
> >
> > > Getting into MSRPC might be rather difficult, and I would hope to avoid
> > > such a beast. If that really is the way, though, there is skeleton code
> > > in both Samba and Samba-TNG that can be leveraged to provide a framework,
> > > then simply hang support for the appropriate MSRPC calls off of it.
> >
> > Some more reverse engineering has to be done. Shame that MSRPC isnt a
> > generic dce/rpc. Also I think MSRPC should be the main concern.
> > On other hand, dbmail can be RAD'd to a state higher than MS Exchange. But the
> > compatibility with a different email clients is a different issue(excluding
> > pop3/imap), for Outlook it's easy to write an addin to draw the nice callendar(ie comm
> > module) and store all the data(let say callender data, notes so so..) into a database.
> >
> > Have you seen HP OpenMail(Now Samsung Contact)?
> >
> > cheers
> >
> > > > In some email I received from Aaron Stone <aaron@engr.Paly.NET> on Wed, 23 Apr
> > > > 2003 13:51:52 -0700 (PDT), wrote:
> > > >
> > > > > I believe that there are two ways to get into the address book. Exchange
> > > > > 5.5 has a 'GAL', the Global Address List with a proprietary
> > > > > protocol, but with an optional LDAP access mode. In Exchange 2000, I
> > > > > believe that the LDAP access is default via Active Directory.
> > > > > As eluded to by a post a few (months?) ago, Exchange exports all of its
> > > > > data via IMAP. If this is the case, we should see if there's a particular
> > > > > message format that contains addresses that we can emulate.
> > > >
> > > > What about MAPI and MSRPC in general?
> > > >
> > > > > If the only route in LDAP, then it's a more complex matter of getting
> > > > > together a schema that does what Outlook expects. The Samba HEAD branch
> > > > > (version 3 alpha) has a lot of Active Directory schemas for OpenLDAP. I do
> > > > > doubt that they have the Exchange schema changes, though... I think
> > > > > they're published in an MSDN document.
> > > >
> > > >
> > > > cheers,
> > > > -lk
> > > >
> > > > _______________________________________________
> > > > Dbmail-dev mailing list
> > > > Dbmail-dev@dbmail.org
> > > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> > > >
> > >
> > > _______________________________________________
> > > Dbmail-dev mailing list
> > > Dbmail-dev@dbmail.org
> > > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> > >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev@dbmail.org
> > http://twister.fastxs.net/mailman/listinfo/dbmail-dev
> >
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>


--
Lou Kamenov / Network Infrastructure/Security Analyst
AEYE R&D - http://www.aeye.net lou.k@hq.aeye.net
AEYE Technologies - http://www.aeye.biz lou.k@aeyetech.co.uk
phone: +44 (0) 20 8879 9832 fax: +44 (0) 7092 129079
mobile: +44 (0) 79 3945 3026 PGP Key ID - 0xA297084A

AEYE(=AI) stands for Artificial Intelligence.