[BBLISA] Last night's IPv6 talk

[Internaut at Large]

Greetings,

On Tue, 2010-05-18 at 11:00 -0400, Sean Lutner wrote:
> On May 18, 2010, at 10:25 AM, Internaut at Large wrote:
> 
> > Greetings,
> > 
> > On Mon, 2010-05-17 at 23:55 -0400, Edward Ned Harvey wrote:
> >>> From: dkap at haven.org [mailto:dkap at haven.org] On Behalf Of Internaut at
> >>> Large
> >>> 
> >>> I can _barely_ get Exchange to talk to my mac, 
> >> 
> >> EWS.
> >> 
> >> Sorry for being terse.  I did indicate I'm not interested in having an
> >> argument about which mail client is "best."
> >> 
> >> If you're using mac & exchange, use EWS.
> > 
> > That's what I mean by barely.  Every other system, including things like
> > google, can talk to the standard mac mail app.  The fact that I have to
> > put a specific, other piece of software, to manage my email, differently
> > than all the other email I have ... that is not "Cross Platform
> > compatible" by any stretch of the imagination.  I won't even mention
> > that it's a closed app, written by the same company that puts out the
> > "cross platform" server you are touting, to begin with.  That doesn't
> > read "cross platform" to me, by any stretch of the imagination.
> 
> I've used Mac Mail, iCalendar and AddressBook against an Exchange installation more than once and the only issue I had was with all day calendar appointments in iCal. If the folks who administer your Exchange installation aren't clued enough to open OWA access, IMAP, POP and SMTP then you have bad admins, not a bad system. If you do have the access you need in place and still can't access Exchange with Mac Mail, you're doing it wrong. Mac Mail 3, when used as a client to Exchange 2007 will work seamlessly and does all the integration with the other apps. 

Alas, they are "Microsoft" administrators, and claim to follow the
"Microsoft recommended Security recommendations" and do not open OWA
POPs, IMAPs and SMTPS/TLS.  I wouldn't ask them to open POP, or IMAP,
because, well, passwords in the clear is never secure.  This means that,
the only protocol available for connection is MAPI.  (Or CDO, or
whatever Microsoft is calling it now.)
 
> > And I have to run several different versions of it for the different
> > Exchange versions, EWS 2008 only works with Exchange 2007SP1 Rollup 4,
> > or later ... not anything earlier, and webDAV is not activated on the
> > servers, because it is a GAPING security hole, and a whole bunch of SANS
> > bugs have been filed over Exchange and webDAV.
> > 
> > -dkap wondering if he is even speaking the same language.