> GetRecipientTable is only a client-side call which fully relies/build
> data based on information returned by GetEmbeddedMessage or OpenMessage
> etc. (depending on the context). The information these calls return are
> described as part of MS-OXCDATA specifications for RecipientRow
> structure (2.10.3.2 RecipientRow).
The fun part with that document is that it uses terms that don't
match the PR_ or PidTag nomenclature...
> If the information you are looking for is not available/returned by
> GetRecipientTable (or available in OpenEmbeddedMessage at "network
> trace" level), the best I can suggest would be to call ResolveNames
> function and specify the set of properties you're looking for.
Am I correct that ResolveNames uses the address book on the server,
i.e. it would work only for employees of my company, not for
external parties?
> For example, mapitest returns the following information for
> OpenEmbeddedMessage test:
>
> [*] OXCMSG-OPEN-EMBEDDED-MESSAGE
> [TEST] OXCMSG-OPEN-EMBEDDED-MESSAGE
I am getting pretty much the same when I run this test. However,
when I use my application on the embedded "sent-item" messages
that I receive from other people, PR_7BIT_DISPLAY_NAME is empty
as well.
Now I tried a mapidump_SRowSet on the set returned by
GetRecipientTable. The result is attached below. There are no
names anywhere except coded into the PR_RECIPIENT_ENTRYID.
The example here includes two cases:
(1) jason is an external contact and we see his name and email
address in PR_RECIPIENT_ENTRYID pretty much in the same way
as it appears on the OWA GUI.
(2) the second one is myself and Exchange apparently replaced
whatever was sent by the sender with this LDAP string in
PR_RECIPIENT_ENTRYID.
I have not found any information how this entry ID field is
coded. Do you know anything about it? Do you think it makes
sense to scan through this data to extract a display name?
And is there a way to request the server to translate the
whole LDAP string into first name, last name, etc? The last
/cn part is my user name. I suppose I can use this as a
parameter to ResolveNames. But how do I know that these
LDAP strings are always structured as in this example, i.e.
with the user name in the last /cn tag?
thanks for your help
dirk
------------------------------------------
* PR_RECIPIENTS_FLAGS: 1
* PR_RECIPIENT_ENTRYID
[0000] 00 00 00 00 81 2B 1F A4 BE A3 10 19 9D 6E 00 DD .....+.. .....n..
[0010] 01 0F 54 02 00 00 01 80 4A 00 61 00 73 00 6F 00 ..T..... J.a.s.o.
[0020] 6E 00 20 00 ?? 00 ?? 00 ?? 00 ?? 00 20 00 28 00 n. .?.?. ?.?. .(.
[0030] 45 00 2D 00 6D 00 61 00 69 00 6C 00 29 00 00 00 E.-.m.a. i.l.)...
[0040] 53 00 4D 00 54 00 50 00 00 00 6A 00 61 00 73 00 S.M.T.P. ..j.a.s.
[0050] 6F 00 6E 00 ?? 00 ?? 00 ?? 00 ?? 00 40 00 ?? 00 o.n.?.?. ?...@.?.
[0060] ?? 00 ?? 00 ?? 00 ?? 00 ?? 00 ?? 00 ?? 00 ?? 00 ?.?.?.?. ?.?.?.?.
[0070] 2E 00 63 00 6F 00 6D 00 2E 00 68 00 6B 00 00 00 ..c.o.m. ..h.k...
* PR_SMTP_ADDRESS_UNICODE: jason?...@????????.com.hk
* PR_DISPLAY_TYPE: 0
* PR_OBJECT_TYPE: 6
* PR_RECIPIENT_TYPE: 1
* PR_INTERNET_CPID: 1252
* PR_RECIPIENTS_FLAGS: 1
* PR_RECIPIENT_ENTRYID
[0000] 00 00 00 00 DC A7 40 C8 C0 42 10 1A B4 B9 08 00 ......@. .B......
[0010] 2B 2F E1 82 01 00 00 00 00 00 00 00 2F 6F 3D ?? +/...... ..../o=?
[0020] ?? ?? ?? ?? ?? ?? 2F 6F 75 3D 45 78 63 68 61 6E ??????/o u=E?chan
[0030] 67 65 20 41 64 6D 69 6E 69 73 74 72 61 74 69 76 ge Admin istrativ
[0040] 65 20 47 72 6F 75 70 20 28 ?? ?? ?? ?? ?? ?? ?? e Group (???????
[0050] ?? ?? ?? ?? ?? ?? ?? ?? 29 2F 63 6E 3D 52 65 63 ???????? )/cn=Rec
[0060] 69 70 69 65 6E 74 73 2F 63 6E 3D 48 ?? ?? ?? ?? ipients/ cn=H????
[0070] ?? ?? 44 00 ??D.
* PR_SMTP_ADDRESS_UNICODE: dh???...@??????????.com
* PR_DISPLAY_TYPE: 0
* PR_OBJECT_TYPE: 6
* 0?39050003: 1073741824
* PR_RECIPIENT_TYPE: 1
* PR_INTERNET_CPID: 1252
--
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
