On Thu, Dec 29, 2011 at 2:52 PM, Micheal Espinola Jr <[email protected]> wrote: >> Because they’re Microsoft? > > I love to think that too, but I there has *got* to be a very specific reason > for them to have simply changed this functionality. I suspect something in > inherently programmatically flawed here.
There doesn't have to be a "change" made if it was broken from the start. I expect it prolly went something like this: Internally, Exchange is based on X.400 more than Internet email. The guy who wrote the code for the out-of-office auto-responder was thus able to be mostly ignorant of Internet mail standards. The code does things the X.400 way and ignores any Internet info that might be present. It could be fixed, of course -- every message gatewayed into Exchange from the Internet preserves all the needed headers and properties. But that would require assigning developer resources to the issue. Microsoft isn't going to do that unless they see an ROI. I expect they don't see an ROI in following Internet email standards here. This is all just guess-work, of course, but it's all I have to go on. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
