G
Guest
I'm hoping there's an elegant solution to this problem.
I have a 1.1 desktop application with a custom security table that
authenticates and authorizes users based on Windows login. Recently I found
the need to be able to send these users an email at certain points, and the
assumption I was making originally was that the exchange name was the same as
the windows name. Unfortunately, that assumption has proven false for a
small group of users who have been around for a long time. These users, who
were here when logins were restricted to eight characters, have exchange
names longer than their windows login. For example, Bill Leiderhosen might
have an exchange name of bleiderhosen but a windows name of bleiderh. When I
specify a MailMessage.To value of "bleiderhosen", the email is sent
successfully. When I just specify bleiderh, though, it doesn't.
One commonality, though, that I've picked up on is that the first eight
characters of both the windows login and the exchange name are the same.
What I was hoping would happen is that I could just pass in the partial
exchange name (the first eight characters), and Exchange would resolve the
name correctly and send the email. What I'm seeing, though, is that this
doesn't happen.
Short of adding a separate field in the table for email address or creating
a component to query active directory using LDAP, is there a more elegant way
to use a wild card in the name, or is there a built-in framework method to
resolve the name before sending it?
Please advise.
Thanks very much,
TheManFromSql
I have a 1.1 desktop application with a custom security table that
authenticates and authorizes users based on Windows login. Recently I found
the need to be able to send these users an email at certain points, and the
assumption I was making originally was that the exchange name was the same as
the windows name. Unfortunately, that assumption has proven false for a
small group of users who have been around for a long time. These users, who
were here when logins were restricted to eight characters, have exchange
names longer than their windows login. For example, Bill Leiderhosen might
have an exchange name of bleiderhosen but a windows name of bleiderh. When I
specify a MailMessage.To value of "bleiderhosen", the email is sent
successfully. When I just specify bleiderh, though, it doesn't.
One commonality, though, that I've picked up on is that the first eight
characters of both the windows login and the exchange name are the same.
What I was hoping would happen is that I could just pass in the partial
exchange name (the first eight characters), and Exchange would resolve the
name correctly and send the email. What I'm seeing, though, is that this
doesn't happen.
Short of adding a separate field in the table for email address or creating
a component to query active directory using LDAP, is there a more elegant way
to use a wild card in the name, or is there a built-in framework method to
resolve the name before sending it?
Please advise.
Thanks very much,
TheManFromSql