Some updated info,

<cfscript> 
username = "test"; 
password = "test"; 
servername = "NTS_4"; 
mailbox = "Office\test"; 
profileInfo = servername & mailbox; 
objExchangeSession = createObject("COM","MAPI.Session"); 
objExchangeSession.Logon(username,password,false,true,0,true,profileInfo
); 
</cfscript>

though still wont work!?






Neil Clark
Team Macromedia
http://www.macromedia.com/go/team

Announcing Macromedia MX!! 
http://www.macromedia.com/software/trial/




-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]] 
Sent: 10 June 2002 17:12
To: CF-Talk
Subject: RE: ColdFusion & Microsoft Exchange Server

> Okay, heres the problem/situation....
> 
> Network Location 1 : ColdFusion Application Server
> 
> Network Location 2 : Microsoft Exchange Server
> 
> Whats the deal with connecting these two together (and I 
> have been to cfcomet, there is nothing ;-). Since they are 
> over a network whats the deal with <cfobject> and connecting 
> to Microsoft Exchange server?
> 
> The goal is to allow multiple users to have web access to 
> their calendar without the Outlook Web Interface.

You can connect via COM to Exchange using the CDO library. There's lots
of
information about CDO on MSDN (http://msdn.microsoft.com/). There's also
a
good book covering CDO from ASP, called "ADSI CDO ASP", from Wrox Press.
CDO
is the interface that the Outlook Web Access application uses, I'm sure.

Unfortunately, I don't know how easy this'll be from CF, since CF does
such
a bad job with COM in general and with MS-specific interfaces like CDO
and
ADSI in particular. I found it extremely difficult to work with ADSI
from
CF, compared with ASP. Also, if you're using CF 5, you can use the
CFIMPERSONATE tag to wrap your CDO calls so that you can impersonate a
specific Exchange user, but there's no equivalent in CF MX, which is
kind of
a bummer. Note that CFIMPERSONATE requires that you run the CF server as
SYSTEM.

> What don't you just VPN the two networks together into a 
> single virtual network, so that you don't have these issues?

While I agree that this would be a good idea if they're not already on
the
same network, this won't solve the programmatic problem of how to get CF
to
talk to Exchange.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444

______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to