Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Speaking of mail etc

As a rule, the Exchange client should not be used outside of the "Local"  
network.  We always recommend alternative access mechanisms (POP/IMAP/OWA*)  
for external client access to the Exchange Server or, if feasible, VPN access
to utilize the full Exchange client.

* IMHO - OWA should always be protected using something along the lines of
Whale e-Gap to protect against IIS/Exchage vulnerabilities.

On 26 Jul 2003 at 19:47 -0400 Johannes Ullrich was heard to utter:

JU> Interestingly, Microsoft suggested in its latest advisory, not to use
JU> Windows RPC (port 135) over the
JU> "open network". However, Exchange requires this port to work properly
JU> with Outlook. So one may wonder if Exchange is supposed to be used
JU> across a public network.

This message has been scanned for viruses and
dangerous content by MailScanner/Sophos on and is believed to be clean.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /