I'm sure I'm one of the guilty party. Exchange 2003 had a registry hack that was supposed to minimize occurrences of OOO's going to mailing lists, but I believe that has gone away with 2007.
Exchange 2007 does support separating the handling of OOO's between internal and external senders, but I turn both on. I need people outside of my organization (vendors, members of the public, etc.) to know I'm OOO just as much as I need people within my organization to know it. John Hornbuckle MIS Department Taylor County School District www.taylor.k12.fl.us -----Original Message----- From: Edward B. DREGER [mailto:[email protected]] Sent: Monday, December 29, 2008 1:03 PM To: NT System Admin Issues Subject: Aaaiiiyyyeeeeee!!! OOO notices! (OT) I normally get a few OOOs in response to a post... but _thirteen_ just now?! Hint: If a message is addressed to a list (not to oneself), from a list server, et cetera, an OOO response might not be appropriate. And telling random people that you'll be out of state for two months is unwise from a security perspective. Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: [email protected] -*- [email protected] -*- [email protected] Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
