I know why this is done, and we could discuss it until I was blue in the face and got irritated; but long story short - it ain't gonna change in Exchange.
Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Wednesday, December 28, 2011 5:04 PM To: NT System Admin Issues Subject: Re: test On Wed, Dec 28, 2011 at 4:16 PM, Matthew W. Ross <mr...@ephrataschools.org> wrote: > I wish there was a standard for "automatic replies" somewhere in the email > spec. There is. Machine-generated messages should be sent to the envelope sender (SMTP reverse path), not the RFC-822 "From:" sender. If that is done, the auto-responses go to the list server, which can do something reasonable with them, or at least discard them. For some reason, Microsoft Exchange does the Wrong Thing. The Internet mail community has been complaining about this for a decade or so, but apparently MSFT doesn't consider it worth fixing. (There are other mail programs also broken in this way, but Exchange, with its market share, is by far the biggest offender.) > ... so Lyris can easily just filter this stuff to the bit bucket? They never hit Lyris. When a list message hits someone with OoO set, Exchange sends the auto-response directly to the address in the "From:" header, i.e., the person who sent the message. -- 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
