You know what, this is only a concern when they are internal. I just flipped the dns so internal webmail directly connects. That should be the end of that.
From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Thursday, May 29, 2014 8:35 AM To: [email protected] Subject: [Exchange] RE: OWA notifications via reverse proxy. ARR is on the box, but just using a straight URL rewrite. Sorry for the delay. Was out yesterday. From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, May 27, 2014 5:30 PM To: [email protected] Subject: [Exchange] RE: OWA notifications via reverse proxy. Are you using ARR, WAP, or straight URL rewrite? From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Tuesday, May 27, 2014 10:16 AM To: [email protected] Subject: [Exchange] OWA notifications via reverse proxy. Publishing my OWA 2010 SP3 RU 5 via a 2012 URL rewrite. No fancy rules on the URL rewrite just straight up publishing of a few fqdn's. I switched from an ISA server to 2012 URL rewrite. Notifications were working prior the changeover. It is the dreaded little bell that says 'Notifications couldn't be retrieved'. Google mentions the issue but supposedly fixed in RU 5. Not finding many clues there.
