Re: [Exim] OT - Why you should not put Exchange on the Inter…

Top Page

Reply to this message
Author: Richard Welty
Date:  
To: exim-users
Subject: Re: [Exim] OT - Why you should not put Exchange on the Internet.
On Thu, 22 Jan 2004 20:23:00 -0500 (EST) Richard Welty <rwelty@???> wrote:

> this seems awfully offtopic, but i'll chip in anyway.


> On Thu, 22 Jan 2004 18:49:54 -0600 Phil Brutsche <phil@???> wrote:
> > I can verify that to be the truth (we're about to contaminate our office
> > with Exchange 2003).


> > Outlook, when used as an Exchange client, needs to communicate with the
> > Exchange server on TCP port 135 - the infamous Windows RPC port. Not
> > all traffic is on port 135, however - it also negotiates alternate port
> > numbers.


> this is true if you use MAPI. Outlook can (or used to be able to) use ordinary
> pop3 and imap w/o going into these modes, and Exchange used to be able to
> talk pop3 and imap ok. it's been a few years since i fought with this stuff,
> though.


ack. i also need to add that it's reasonable to allow remote users to use
MAPI if you install any one of a number of effective IPSec VPN appliances
and clients. i should know, i used to work for such a vendor.

richard
   (offtopic? who, me?)
--
Richard Welty                                         rwelty@???
Averill Park Networking                                         518-573-7592
    Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security