Accodring to http://msdn2.microsoft.com/en-us/library/ms530980.aspx the
following are all valid examples of PR_EMAIL_ADDRESS:

network/postoffice/user

/c=US/a=att/p=Microsoft/o=Finance/ou=Purchasing/s=Furthur/g=Joe

This suggests that mapping this property via RDOAddressEntry.Address may not
always match the x500 format of AD's LegacyExchangeDN (although maybe it does
for Exchange addresses, I don't know). If this is true I think it would be
safer to map RDOAddressEntry.SMTPAddress to AD's ProxyAddresses even though
the filter may be a bit more work.



"Dmitry Streblechenko" wrote:

Redemption returns PR_EMAIL_ADDRESS property from the corresponding
IMailuser object

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
Here is what I learned today from an MS employee on AD's Mail,
ProxyAddresses
and LegacyExchangeDN attributes:

"Normally, the AD Mail attribute will match up with the Primary SMTP
Address
that is viewed under the ProxyAddresses attribute. Exchange does not use
the
Mail field, though, so I cannot guarantee it will always match.

As far as the ProxyAddresses attribute goes, if you look at the entries,
you
will see that one of the SMTP entries will be capitalized.

i.e. as follows

SMTP:
smtp:
smtp:

The address that shows SMTP in all caps is the primary (reply-to) address.
All other secondary addresses will have smtp listed in lowercase.

The LegacyExchangeDN normally should not match up to any current e-mail
address entries. The format of the legacyExchangeDN is an x500 format.
If
you have done a cross-organization mailbox move, the OLD legacyExchangeDN
should show up as an X500 entry to preserve the ability to reply to old
messages."


(Dimitry, how does Redemption get RDOAddressEntry.Address, which appears
the
same as legacyExchangeDN?)


"Dmitry Streblechenko" wrote:

legacyExchangeDN is p robably teh way to go.
AFAIK legacyExchangeDN is what Exchange itself uses to map a mailbox to
an
AD user.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
This is related to a question that we corresponded on last week. The
user's
mailbox contains a number of useful AD properties like :

msExchRecipientDisplayType (eg ConferenceRoomMailbox)
msExchRecipientTypeDetails (eg RoomMailbox)
msExchResourceCapacity (integer indicating how many people the room
holds)

I can use .Net's DirectoryServices classes to get these properties but
I
need some way to relate the GAL entry to the AD directory entry. Using
ADSIEdit, it appears that the AD directory entry "legacyExchangeDN" is
equivalent to the Address property of an AddressEntry or Recipient
object;
However, I'm not sure how reliable this mapping is and I have only
checked
on
an Exchange 2007 (where the mailboxes were created and not migrated
from
an
earlier Exchange server).

"Eric Legault [MVP - Outlook]" wrote:

Can you tell me more about how a user's mailbox fits into your
solution,
as
well why you need to associate a recipient with an AD property? This
will
better allow me to validate your approach.

--
Eric Legault - Outlook MVP, MCDBA, MCTS (SharePoint programming, etc.)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"Tadwick" wrote:

I have an app that runs in Outlook and allows the user to retrieve
recipients
via the GAL. (I'm using Redemption to do this.) So far I have been
using
the EntryID as a unique identifier for a mailbox; however, I gather
this
property is not static so I'm wondering how best to map a GAL
recipient
to an
AD property like a GUID.

Any assistance with this would be appreciated.


Thanks, Tad

That is exactly how RDOAddressEntry.SMTPAddress works (but your original
question was about RDOAddressEntry.Address ) - Redemption retrieves the
address prefixed with "SMTP:" (all caps) from the PR_EMS_AB_PROXY_ADDRESSES
multivalued property.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
Accodring to http://msdn2.microsoft.com/en-us/library/ms530980.aspx the
following are all valid examples of PR_EMAIL_ADDRESS:

network/postoffice/user

/c=US/a=att/p=Microsoft/o=Finance/ou=Purchasing/s=Furthur/g=Joe

This suggests that mapping this property via RDOAddressEntry.Address may
not
always match the x500 format of AD's LegacyExchangeDN (although maybe it
does
for Exchange addresses, I don't know). If this is true I think it would
be
safer to map RDOAddressEntry.SMTPAddress to AD's ProxyAddresses even
though
the filter may be a bit more work.



"Dmitry Streblechenko" wrote:

Redemption returns PR_EMAIL_ADDRESS property from the corresponding
IMailuser object

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
Here is what I learned today from an MS employee on AD's Mail,
ProxyAddresses
and LegacyExchangeDN attributes:

"Normally, the AD Mail attribute will match up with the Primary SMTP
Address
that is viewed under the ProxyAddresses attribute. Exchange does not
use
the
Mail field, though, so I cannot guarantee it will always match.

As far as the ProxyAddresses attribute goes, if you look at the
entries,
you
will see that one of the SMTP entries will be capitalized.

i.e. as follows

SMTP:
smtp:
smtp:

The address that shows SMTP in all caps is the primary (reply-to)
address.
All other secondary addresses will have smtp listed in lowercase.

The LegacyExchangeDN normally should not match up to any current e-mail
address entries. The format of the legacyExchangeDN is an x500 format.
If
you have done a cross-organization mailbox move, the OLD
legacyExchangeDN
should show up as an X500 entry to preserve the ability to reply to old
messages."


(Dimitry, how does Redemption get RDOAddressEntry.Address, which
appears
the
same as legacyExchangeDN?)


"Dmitry Streblechenko" wrote:

legacyExchangeDN is p robably teh way to go.
AFAIK legacyExchangeDN is what Exchange itself uses to map a mailbox
to
an
AD user.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
This is related to a question that we corresponded on last week.
The
user's
mailbox contains a number of useful AD properties like :

msExchRecipientDisplayType (eg ConferenceRoomMailbox)
msExchRecipientTypeDetails (eg RoomMailbox)
msExchResourceCapacity (integer indicating how many people the room
holds)

I can use .Net's DirectoryServices classes to get these properties
but
I
need some way to relate the GAL entry to the AD directory entry.
Using
ADSIEdit, it appears that the AD directory entry "legacyExchangeDN"
is
equivalent to the Address property of an AddressEntry or Recipient
object;
However, I'm not sure how reliable this mapping is and I have only
checked
on
an Exchange 2007 (where the mailboxes were created and not migrated
from
an
earlier Exchange server).

"Eric Legault [MVP - Outlook]" wrote:

Can you tell me more about how a user's mailbox fits into your
solution,
as
well why you need to associate a recipient with an AD property?
This
will
better allow me to validate your approach.

--
Eric Legault - Outlook MVP, MCDBA, MCTS (SharePoint programming,
etc.)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"Tadwick" wrote:

I have an app that runs in Outlook and allows the user to
retrieve
recipients
via the GAL. (I'm using Redemption to do this.) So far I have
been
using
the EntryID as a unique identifier for a mailbox; however, I
gather
this
property is not static so I'm wondering how best to map a GAL
recipient
to an
AD property like a GUID.

Any assistance with this would be appreciated.


Thanks, Tad

Thanks for clarifying that Dimitry.

"Dmitry Streblechenko" wrote:

That is exactly how RDOAddressEntry.SMTPAddress works (but your original
question was about RDOAddressEntry.Address ) - Redemption retrieves the
address prefixed with "SMTP:" (all caps) from the PR_EMS_AB_PROXY_ADDRESSES
multivalued property.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
Accodring to http://msdn2.microsoft.com/en-us/library/ms530980.aspx the
following are all valid examples of PR_EMAIL_ADDRESS:

network/postoffice/user

/c=US/a=att/p=Microsoft/o=Finance/ou=Purchasing/s=Furthur/g=Joe

This suggests that mapping this property via RDOAddressEntry.Address may
not
always match the x500 format of AD's LegacyExchangeDN (although maybe it
does
for Exchange addresses, I don't know). If this is true I think it would
be
safer to map RDOAddressEntry.SMTPAddress to AD's ProxyAddresses even
though
the filter may be a bit more work.



"Dmitry Streblechenko" wrote:

Redemption returns PR_EMAIL_ADDRESS property from the corresponding
IMailuser object

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
Here is what I learned today from an MS employee on AD's Mail,
ProxyAddresses
and LegacyExchangeDN attributes:

"Normally, the AD Mail attribute will match up with the Primary SMTP
Address
that is viewed under the ProxyAddresses attribute. Exchange does not
use
the
Mail field, though, so I cannot guarantee it will always match.

As far as the ProxyAddresses attribute goes, if you look at the
entries,
you
will see that one of the SMTP entries will be capitalized.

i.e. as follows

SMTP:
smtp:
smtp:

The address that shows SMTP in all caps is the primary (reply-to)
address.
All other secondary addresses will have smtp listed in lowercase.

The LegacyExchangeDN normally should not match up to any current e-mail
address entries. The format of the legacyExchangeDN is an x500 format.
If
you have done a cross-organization mailbox move, the OLD
legacyExchangeDN
should show up as an X500 entry to preserve the ability to reply to old
messages."


(Dimitry, how does Redemption get RDOAddressEntry.Address, which
appears
the
same as legacyExchangeDN?)


"Dmitry Streblechenko" wrote:

legacyExchangeDN is p robably teh way to go.
AFAIK legacyExchangeDN is what Exchange itself uses to map a mailbox
to
an
AD user.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Tadwick" wrote in message
...
This is related to a question that we corresponded on last week.
The
user's
mailbox contains a number of useful AD properties like :

msExchRecipientDisplayType (eg ConferenceRoomMailbox)
msExchRecipientTypeDetails (eg RoomMailbox)
msExchResourceCapacity (integer indicating how many people the room
holds)

I can use .Net's DirectoryServices classes to get these properties
but
I
need some way to relate the GAL entry to the AD directory entry.
Using
ADSIEdit, it appears that the AD directory entry "legacyExchangeDN"
is
equivalent to the Address property of an AddressEntry or Recipient
object;
However, I'm not sure how reliable this mapping is and I have only
checked
on
an Exchange 2007 (where the mailboxes were created and not migrated
from
an
earlier Exchange server).

"Eric Legault [MVP - Outlook]" wrote:

Can you tell me more about how a user's mailbox fits into your
solution,
as
well why you need to associate a recipient with an AD property?
This
will
better allow me to validate your approach.

--
Eric Legault - Outlook MVP, MCDBA, MCTS (SharePoint programming,
etc.)
Try Picture Attachments Wizard for Outlook:
http://www.collaborativeinnovations.ca
Blog: http://blogs.officezealot.com/legault/


"Tadwick" wrote:

I have an app that runs in Outlook and allows the user to
retrieve
recipients
via the GAL. (I'm using Redemption to do this.) So far I have
been
using
the EntryID as a unique identifier for a mailbox; however, I
gather
this
property is not static so I'm wondering how best to map a GAL
recipient
to an
AD property like a GUID.

Any assistance with this would be appreciated.


Thanks, Tad