The way it breaks down is this. Exchange has it's own MTA serivces built in.
Exchange can support IMAP, MAPI, SMTP, POP3, CCMAIL...etc. If you setup
Exchange to work with Outlook using the Microsoft Exchange Server protocol,
then you are using MAPI and any and all work done between the two (the server
and the client) is passed using that protocol. However, when it come time for
the Exchange box to send or receive mail to the outside world (the rest of the
internet) it uses the SMTP protocol. You can see if the Exchange box is running
SMTP and POP3 by telneting into the specific ports (110 & 25). If the Exchange
box has the services enabled, you will see the following messages:
+OK Microsoft Exchange POP3 server version 5.5.2650.23 ready
220 mailbox.foo.net ESMTP Server (Microsoft Exchange Internet Mail Service
.5.2650.21) ready


"Zaleski, Matthew (M.E.)" wrote:

> > -----Original Message-----
> > From: Denis Havlik [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, August 01, 2000 12:57 PM
> > To: Zaleski, Matthew (M.E.)
> > Subject: RE: [expert] I'll be back
> >
> >
> > :~>My understanding is that IMAP4 is a DL ownly protocol.  I need SMTP
> > :~>available if I want to send out from that Exchange server.
> >  Is that correct?
> >
> > Yes. But, how on earth are these look-out clients sending
> > their messages
> > if no SMTP server is around?  (i know nothing about windoze
> > world, sorry)
> >
>
> I wish I knew less about the Windoze world.  It appears, although I have not
> done any indepth research yet, that when Outlook is configured to talk to an
> Exchange server, they use a private protocol that is not SMTP, POP3 or
> IMAP4.  Exchange IS capable of all of those protocols, but appears to
> support another proprietary one for an intergrated solution.  The way our
> Outlook clients are configured, I can do calendar type activities, like
> schedule meetings and meeting rooms and know immediately the availability of
> people and resources.  It works reasonably well.  I just wish it would work
> directly from Linux so that I didn't need to run VMWare or Win4Lin.
>
> Matt

Reply via email to