in message
...
Just to be pedantic... Exchange *is* a POP3/IMAP4 server.
Then any POP3-enabled e-mail client could connect to Exchange.
Obviously that is not true. Other than Outlook with its build
Exchange protocol support, what other *POP* e-mail client can connect
to Exchange? Not even Outlook can connect to Exchange using POP3.
You must specify the account type is Exchange. Exchange uses its own
propriety command protocol, and that isn't POP3's command set. You
can add a POP3 gateway server that will run *with* Exchange to provide
that mode of access to your mailbox, but that isn't Exchange itself.
http://technet.microsoft.com/en-us/library/bb124934.aspx
Note that you have to *enable* the POP3 gateway. Well, if you have to
enable POP3 support then that means Exchange itself does not use the
POP3 command set. If enabling the POP3 gateway gives you POP3 access,
and if Exchange were a POP3 server, then disabling that POP3 gateway
would mean no Outlook users could connect to Exchange using POP3.
Well, Outlook users *do* connect to Exchange and without ever using
POP3. Exchange itself is *not* a POP3 server.
The OE user cannot connect to Exchange because OE does not support the
command set required to communicate to the Exchange server. If a POP3
gateway has been enabled for use with the Exchange server then the OE
user can get at their Exchange mailbox but they do so through the POP3
gateway, not by OE connecting to Exchange. If a gateway (aka
connector) is added or enabled in Exchange then you get support for
that protocol. Just because the connectors are included in an install
of Exchange doesn't make them part of exchange. Adding Paint into
Windows didn't make Windows itself a graphics editor.
Where do you see in the RFCs for POP3 the discussion of the commands
used for calendaring, shared/public folders, scheduling, global
address books, or all the other collaboration functions available
through Exchange? Just what POP3 command is Outlook going to send
Exchange to send a meeting request with voting buttons, even for
plain-text formatted e-mails?
Yeah, right, Exchange is a POP3 server, uh huh. Just when has any
author of an e-mail program had to get a protocol development kit
(
http://msdn2.microsoft.com/en-us/library/ms986138.aspx) to write code
to support the long-established and public commands available for Post
Office Protocol public standard?
Microsoft's Exchange is a mail server that uses a proprietary RPC
protocol of which only part of it is documented (only the API is
documented). You can add connectors or gateways that themselves
support other protocols but Exchange itself is not a POP3 or IMAP4
server. I only mentioned Exchange. I did not go through all the
connectors that can be used with it. Hotmail is an HTTP account (uses
HTTP as the communications protocol but WebDAV as the scripting
language to send the command set). I'm sure there are services that
will provide POP3 access to the Hotmail HTTP/WebDAV accounts but that
doesn't make Hotmail itself a POP3 service.
So it still comes back to my statement "Outlook Express will not work
with Exchange, so you must have an POP3/SMTP account." Okay, if you
have a POP3 gateway enabled to access your Exchange mailbox then you
can use a POP3 client to get to your mailbox, but you STILL need a
POP3 capable server to communicate with your POP3 client, so you still
need a "POP3 account".
