Re: Accessing an email account programmatically

From: Sanjay Tibrewal (stibrewal_killspam_at_earthlink.net)
Date: 04/13/04 

Date: Tue, 13 Apr 2004 13:43:05 -0700

Chris - Thanks for the details. The only reason I thought of POP was that I
don't want to have to bug the sysadmin everytime I want to change the script
in event sink as you described earlier. I would imagine you could tie down
POP access to a specific IP address to minize security issues. But that's
just one thought. I don't HAVE to use POP. Basically anything that is simple
to implement with the least number of knocks on the exchange admin's door
going forward.

Would you know of examples using DAV and/or POP or other protocols to access
email from Exchange? Another 3 letter acronym that popped into my head is
CDO. I understand it's a layer on top of MAPI and would also enable easy
access to emails. Any thoughts on that?

Thanks a bunch.
Sanjay.

"Chris Ahlers [MSFT]" <ChrisAhl@Online.Microsoft.Com> wrote in message
news:ezmpKyYIEHA.3444@TK2MSFTNGP11.phx.gbl...
> Of course this can be done. Just have the admin do the following:
> Open "Active Directory Users and Computers"
> Click on the "View" file menu and select "Advanced Features"
> Next, right click on the user account for the Exchange Mailbox that you
want
> programmatic access to and select "Properties"
> Click on the "Exchange Advanced" tab and then click on the "Exchange
Rights"
> button
> Now just give the appropriate user account "Full Mailbox Access" and you
> should be able to log into the mailbox using whatever protocol you like.
>
> You could also do the same thing as above by logging into the mailbox via
> Outlook and then setting up Delegate permissions the appropriate user
> account on the Inbox.
>
> The biggest danger I see with this way of accessing the mailbox is that if
> the user account used for programmatic access is compromised the mailbox
can
> be accessed remotely and all the information can be accessed.
Furthermore,
> how are you going to know if this account has been compromised?
>
> Is there a reason why you want to use POP? You could always use DAV which
> would allow you to execute a SEARCH request to find the necessary emails
and
> DAV is enabled by default since it is needed to make OWA (Outlook Web
> Access) work.
>
> --Chris
>
>
============================================================================
> ====
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm.
> Please do not send e-mail directly to this alias. This alias is for
> newsgroup purposes only.
>
============================================================================
> ====
>
> "Sanjay Tibrewal" <stibrewal_killspam@earthlink.net> wrote in message
> news:%235qT$FYIEHA.364@TK2MSFTNGP11.phx.gbl...
> > How about opening a simple POP3 connection to the mailbox(s)? Any
thoughts
> > on that? I take it there is bunch of software out there that will help
me
> > access the account using POP3 if I can enable that on Exchange which I
> > believe should be possible.
> >
> > Thanks,
> > Sanjay.
> >
> > "Chris Ahlers [MSFT]" <ChrisAhl@Online.Microsoft.Com> wrote in message
> > news:#1CI39XIEHA.1944@TK2MSFTNGP11.phx.gbl...
> > > I can't provide you with any whitepapers that discuss this topic, but
I
> > can
> > > provide you with an alternate solution.
> > >
> > > Exchange supports "Event Sinks" which can be used to develop messaging
> > > applications. An Event Sink can be thought of as a true server side
> rule.
> > > The good thing about this is that the Exchange Admin can keep the
Event
> > Sink
> > > under lock and key and there is no need to have a shared account with
> > > permission to access the appropriate mailbox(es). You could put most,
> if
> > > not all, your biz logic directly into the Event Sink and it will run
as
> > part
> > > of Exchange.
> > >
> > > I have included some links to the Exchange SDKs which contain a lot of
> > > information about Event Sinks
> > >
http://www.microsoft.com/exchange/techinfo/development/2000/default.asp
> > > http://www.microsoft.com/exchange/techinfo/development/2003.asp
> > >
> > > --Chris
> > >
> > >
> >
>
============================================================================
> > > ====
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > Use of any included script samples are subject to the terms specified
at
> > > http://www.microsoft.com/info/cpyright.htm.
> > > Please do not send e-mail directly to this alias. This alias is for
> > > newsgroup purposes only.
> > >
> >
>
============================================================================
> > > ====
> > >
> > > "Sanjay Tibrewal" <stibrewal_killspam@earthlink.net> wrote in message
> > > news:%23Z7greXIEHA.3476@TK2MSFTNGP11.phx.gbl...
> > > > Hello,
> > > >
> > > > We have Exchange 2K (moving soon to 2003) that serves all our
users -
> > > about
> > > > 1500. I need to access a particular email account programmatically
for
> > one
> > > > of my applications so that I can get emails and respond based on
> certain
> > > biz
> > > > logic. Understandably the Excahnge admin is hesistant in letting me
do
> > > > anything "fancy".
> > > >
> > > > What options do I have to be able to access one or more email
accounts
> > > > programmatically and what if any are risks associated with each of
> those
> > > > methods. Any pointers to whitepapers discussing these would also be
> > > helpful.
> > > >
> > > > TIA,
> > > > Sanjay.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Loading