[EAS] email configuration for Gmail?

[Alex Hartman]

The entire mail system is handled by the state of MN system, so i'm
sure there's some very asinine policies in place. Like i said, i know
that if the originating connection is internal (on the 199.17.x.x/16
block) SMTP is disabled. If i do it externally, SMTP/SSL/TLS is
employed for connections back to the servers on campus.

I believe that Google/Android did license ActiveSync like you
mentioned, but there are other implementations in the wild as far as
MAPI support (think third party Android images, evolution mail
program, etc). If there's enough codespace in the Sage ENDECs or not
to handle it, who knows. Probably not.

Native Exchange support should be an item on a lot of this gear. Most
radio/tv stations use Exchange/SBS as well, not to mention most public
stations who rely (like me) on the university network. I understand
the coding nightmare it brings with it, but like it or not, this is a
Microsoft world still.

The best part of this whole adventure is, before 2005, the university
used Unix/BSD. They had 3 mail servers handling all users running on
Sun gear. Barely broke a sweat. Now they spend millions on maintaining
a Microsoft system that makes all the users jump through hoops and
purchase more software. Go figure.

--
Alex Hartman

On Tue, Jun 19, 2012 at 3:26 PM, Cody Wilson
<cwilson at stratusbroadcast.com> wrote:
> Alex -
>
> This sounds like the Hub Transport role Exchange servers are in a DMZ, which is not a bad place for them.  That said, if your IT department has employed stateful firewalls between IP zones, you should still be able to talk to the Hub Transport servers and communicate via SMTP to them.  If they've completely eliminated IP connectivity to the Hub Transport servers except through the Mailbox Store Exchange servers, then unless you can convince a network admin to make an exception for you and allow traffic between your EAS appliance and the Hub Transport servers, or spools up another Hub Transport server that you can have IP access to (which is highly unlikely given the cost of doing so), you're out of luck as far as using your internal mail servers.
>
> Your Android phone likely talks to Exchange over ActiveSync, which is essentially MAPI over HTTP(S).  Google licensed ActiveSync connectivity for Android, as well as deployed ActiveSync servers for Gmail/Google Apps.  That's why you get "free" access to ActiveSync enabled mail servers on your Android phone.  If you're not, then you're constantly routing to the public Internet to access your Exchange account over IMAP/POP3 and SMTP.
>
> -Cody Wilson
> W: 563.388.0095 x260
> cwilson at stratusbroadcast.com
>
> On Tue, Jun 19, 2012 at 3:12 PM, Alex Hartman <goober at goobe.net> wrote:
>>Our university is... well, weird.
>
>>Any mail originating from within the university (IP space) must use
>>the MAPI exchange server/client to talk to the local mail server. Only
>>outbound (destined for out of the domain) is SMTP.
>
>>There is no internal SMTP server, oddly enough.
>
>>The university has...erm... several exchange servers in place to
>>handle the load (60,000 users on the active directory domain for
>>students, another 20,000 for faculty/staff). Not really a lot of
>>users, but since MS bought this campus about 6 years ago, everything
>>has to talk to an MS product. Goofy enough.
>
>>And there has to be a work-around, as my Android phone can talk
>>exchange just fine for free.
>
>>--
>>Alex Hartman
>
>>_______________________________________________
>>This is the EAS Forum Discussion List
>
>>Please invite your friends to join our Forum!
>>http://lists.radiolists.net/mailman/listinfo/eas
>
>>And, remember the main page: http://eas.radiolists.net
>
> _______________________________________________
> This is the EAS Forum Discussion List
>
> Please invite your friends to join our Forum!
> http://lists.radiolists.net/mailman/listinfo/eas
>
> And, remember the main page: http://eas.radiolists.net
>