I've run into this. In bulk. It was painful actually - a couple of Exchange versions ago the OOO message went from this: "Out Of Office" ...to this... "Out of Office" Since our workflow was based on 'Subject' = "Out Of Office" we suddenly had stuff breaking and ended up with 1000+ new incidents due to an email loop, etc. The way to deal with this was to a) convert everything in the subject to uppercase and then look for "OUT OF OFFICE" (lowercase would have worked too of course) and also to inject a 5-minute pause on emails sent from newly created incidents. That last bit allowed us to stop any vicious loops. William Rentfrow Principal Consultant, StrataCom Inc. [email protected] Corporate Website, www.stratacominc.com <http://www.stratacominc.com/> Blog, www.williamrentfrow.com <http://www.williamrentfrow.com/> 715-410-8156 C
________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Boyd, Rebecca E. Sent: Wednesday, October 27, 2010 7:27 AM To: [email protected] Subject: Out of Office Messages ** Good Morning! We've configured our system to allow incoming e-mails to update incidents. We'd like the process to ignore Out-of-Office messages based on information contained in the e-mail header. However, when I look at incoming messages in the AR System Email Messages form, I don't see complete header information like I do when I view header information in my local Exchange client. Is there another form where I can find this information? Or some way to configure Remedy to capture it? ITSM 7.5.01, ARS 7.5.00 Thanks, Rebecca Rebecca Boyd Application Administrator Information Systems 336.758.5671 _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
<<image001.jpg>>
