[6384] in Release_7.7_team
Should we update the Pine and Evolution wrappers for Athena 9?
daemon@ATHENA.MIT.EDU (Jonathan D Reed)
Fri Jul 10 18:30:47 2009
From: Jonathan D Reed <jdreed@MIT.EDU>
To: "release-team@mit.edu" <release-team@mit.edu>
Date: Fri, 10 Jul 2009 18:30:31 -0400
Message-ID: <1247265033.acDcfbA4.25377FA21D29C521B794EA2CF2B8CFE1AF5E501CA8C731E52@w92expo3.exchange.mit.edu>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-Spam-Flag: NO
X-Spam-Score: 0.00
Content-Transfer-Encoding: 8bit
As of today, Exchange users now have Hesiod Pobox records that point to "imap.exchange.mit.edu". This means that instead of failing with Hesiod errors, Evolution and Pine on Athena 9 will sit there and try to connect to imap.exchange.mit.edu on port 143, and fail. While Exchange users should not be attempting to use these clients, some probably will. I know we're not supposed to release patch releases for Athena 9 anymore, but is it worth putting one out that updates the Pine and Evolution wrappers to check for Exchange Hesiod information and say "You cannot use Pine or Evolution on Athena 9. Please find a Debathena machine or visit http://owa.mit.edu"?
Or should we not bother and just accelerate our Debathena deployment schedule?
-Jon
