|
|
Hello,
it should actually be http://server/exchange/alias/inbox.
Best regards,
Henning
"Andrew Brook" <ykoorb@xxxxxxxxxxx> wrote in message
news:uQ5WJ4P$GHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
I have looked at the sample application, it looks to work exactly as I
would have hoped. However, i have not yet managed to get the application to
work with my Exchange Server. I have an inbox setup and I would like to
retrieve the messages within it. When filling in the connection information
it asks for a server, should this be in the format
http://<servername>/exchange or should it just be the servername? Also,
what path should be used to retrieve messages, should it be of the format
http://<servername>/exchange/<username>/inbox ?
Any further help would be appreciated,
Thanks,
Andrew
"Andrew Brook" <ykoorb@xxxxxxxxxxx> wrote in message
news:eKNRSxD$GHA.4740@xxxxxxxxxxxxxxxxxxxxxxx
Thanks very much for the response.
I will take a look at the links and also the class library.
ta,
Andrew
"Henning Krause" <hkrause.no@xxxxxxxxxxxxxxxxx> wrote in message
news:%23DcGWu3%23GHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
Hello Andrew,
the SDK is a good starting point.
Additionally, I have several articles on my website (www.infinitec.de)
and a class library which wraps around the messy WebDAV calls... It's
free and comes with full source.
See www.infinitec.de/libraries/exchange/default.aspx">http://www.infinitec.de/libraries/exchange/default.aspx for more
Best regards,
Henning Krause
"Andrew Brook" <ykoorb@xxxxxxxxxxx> wrote in message
news:uJfQF7d%23GHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
Hi Everyone,
I've just started looking into developing .NET 2.0 applications that
communicate with Exchange Server 2003. I've already downloaded the SDK
documentation which does contain various examples. I don't understand a
great deal of it at the moment though. Can anyone suggest some good
learning resources? Not necessarily including code (although this would
be helpful). Good resources concerning the Exchange Server fundamentals
would also be useful.
Thanks
AB
|
|