getting at outlook inboxes programmaticall y

[Mike P]

I am trying to get at different users inboxes programmaticall y (see code
below). It works fine, except for the fact that the logon line seems to
always logon to my local account rather than logging on to other
accounts on the network. Anybody know how to logon to other people's
accounts using this method?

//Create Outlook application
Outlook.Applica tion oApp = new Outlook.Applica tion();

//Get MAPI namespace
Outlook.NameSpa ce oNS = oApp.GetNamespa ce("mapi");

oNS.Logon("user ", "password", false, true);

//Get Messages collection of Inbox
Outlook.MAPIFol der oInbox =
oNS.GetDefaultF older(Outlook.O lDefaultFolders .olFolderInbox) ;

Outlook.Items oItems = oInbox.Items;

int intTotalNumberO fItemsInInbox = oItems.Count;

//Get unread e-mail messages
oItems = oItems.Restrict ("[Unread] = true");
int intTotalUnread = oItems.Count;


*** Sent via Developersdex http://www.developersdex.com ***

[Alexey Smirnov]

On Feb 19, 10:58 am, Mike P <mike.p...@gmai l.comwrote:

I am trying to get at different users inboxes programmaticall y (see code
below). It works fine, except for the fact that the logon line seems to
always logon to my local account rather than logging on to other
accounts on the network. Anybody know how to logon to other people's
accounts using this method?

//Create Outlook application
Outlook.Applica tion oApp = new Outlook.Applica tion();

//Get MAPI namespace
Outlook.NameSpa ce oNS = oApp.GetNamespa ce("mapi");

oNS.Logon("user ", "password", false, true);

//Get Messages collection of Inbox
Outlook.MAPIFol der oInbox =
oNS.GetDefaultF older(Outlook.O lDefaultFolders .olFolderInbox) ;

Outlook.Items oItems = oInbox.Items;

int intTotalNumberO fItemsInInbox = oItems.Count;

//Get unread e-mail messages
oItems = oItems.Restrict ("[Unread] = true");
int intTotalUnread = oItems.Count;

*** Sent via Developersdexht tp://www.developersd ex.com***

<identity impersonate="tr ue"/>

?

[Mike P]

Identity impersonate could be used to hard code a single user's login
details, but I want to be able to have a situation where the user of the
page can select a user from a dropdown and be able to access their
emails.

*** Sent via Developersdex http://www.developersdex.com ***

[Mark Rae]

"Mike P" <mi*******@gmai l.comwrote in message
news:eT******** ******@TK2MSFTN GP04.phx.gbl...

//Create Outlook application
Outlook.Applica tion oApp = new Outlook.Applica tion();

http://support.microsoft.com/default...US;q257757#kb2

Read the "MORE INFORMATION" section, specifically the paragraph in bold...

There's a very strong possibility that this won't work at all in a
production environment...

[Alexey Smirnov]

On Feb 19, 2:42 pm, Mike P <mike.p...@gmai l.comwrote:

Identity impersonate could be used to hard code a single user's login
details, but I want to be able to have a situation where the user of the
page can select a user from a dropdown and be able to access their
emails.

*** Sent via Developersdexht tp://www.developersd ex.com***

Well, I've quickly checked the MSDN and now I'm not sure if you follow
the right way.

As I understand now, Outlook.Applica tion is for automation with local
Outlook and I'm affraid with the current Outlook session.

For tasks like you wanted to do there is another way using Microsoft
Collaboration Data Objects (CDO) for Exchange 2000 Library.

Please check the following MSDN article
http://support.microsoft.com/?kbid=310206

you will need to know path to your Exchange, username and password

[Mark Rae]

"Alexey Smirnov" <al************ @gmail.comwrote in message
news:11******** **************@ t69g2000cwt.goo glegroups.com.. .

Well, I've quickly checked the MSDN and now I'm not sure if you follow
the right way.

The OP most definitely doesn't...

As I understand now, Outlook.Applica tion is for automation with local
Outlook and I'm affraid with the current Outlook session.

Absolutely correct - simply not designed for server-side automation at
all...

For tasks like you wanted to do there is another way using Microsoft
Collaboration Data Objects (CDO) for Exchange 2000 Library.

And for later versions of Exchange too...

[Mike P]

If I can't do what I am trying to do using the Outlook object model, do
you have any useful links with regard to doing this using Microsoft
Collaboration Data Objects (CDO) for Exchange 2000 Library, which I am
totally unfamiliar with.

*** Sent via Developersdex http://www.developersdex.com ***

[Mark Rae]

"Mike P" <mi*******@gmai l.comwrote in message
news:OH******** *****@TK2MSFTNG P04.phx.gbl...

If I can't do what I am trying to do using the Outlook object model, do
you have any useful links with regard to doing this using Microsoft
Collaboration Data Objects (CDO) for Exchange 2000 Library, which I am
totally unfamiliar with.

This should get you started:
http://msdn2.microsoft.com/en-us/library/ms986138.aspx

Although it relates to Exchange 2003, it will be very similar for Exchange
2000...

[Mike P]

Mark,

I've just found out the version being used is 5.5...any links for this
version, or is it likely to be similar to 2003?
Thanks,

Mike
*** Sent via Developersdex http://www.developersdex.com ***

[Mark Rae]

"Mike P" <mi*******@gmai l.comwrote in message
news:ej******** *****@TK2MSFTNG P06.phx.gbl...

I've just found out the version being used is 5.5...

Wow! That's fairly old now...

any links for this version,

I guess the place to start would be here:
http://msdn.microsoft.com/library/de...vr_e55_sdk.asp
However, it's not exactly brimming with code samples...

or is it likely to be similar to 2003?

Not at all - the problem that you're going to come up against is that
access to Exchange 5.5 mailboxes is through CDO 1.21, and that isn't
supported in .NET, at least, not natively... I recall doing some VB6
programming against 5.5 about six years ago, but unfortunately can't locate
the code any more - I'm not even sure I still have it, not that it would
have helped you a great deal...

The link below suggests using COM InterOp - that *may* work...
http://www.thescripts.com/forum/thread300002.html