Problems with CDO based ASP code
Hi All,
This is my very first post to this forum, and my first post on MS
Exchange and CDO, so please bear with me.
At the place I work, I've been asked to try and debug an ASP that offers
users the ability to change their details without having to bother
administration. It uses CDO to access an MS Exchange Server (version 5.5, I
think).
There are two issues that I've noticed:
1. It turns out that there are multiple users sharing the same alias, though
they are situated in different login domains. I proved this to one of the
people administering the Global Address List on the Exchange server which
the application extracts data from. When one of these users tries to use
the application, it falls over at the Session objects logon method. Is
there any other way of establishing uniqueness in this application, or in
Exchange without having to change user logins/aliases? Must user logins be
changed so that uniqueness is established? I would prefer a straightforward
solution since I'm not one of the people responsible for administering the
Exchange server.
2. It is possible to edit the details of other users in the same domain as
yourself. This is definitely not functioning correctly. Everything is fine
if you try to edit the details of a user in a domain different to your own
(i.e. changes are denied). What must I do in order to correct this problem?
Any further information would be greatly appreciated.
Regards,
Balance..
|