Most importantly, here, is the fact that OOO can cause looping.  Not
necessarily by the OOO itself with the current version of Exchange, but most
likely by some type of rule the User has set up.  About 4 years ago, at a
company in Richmond, VA, I was involved in a major OOO loop.  Filled up the
data drive and shutdown the services.  This was when Exchange OOO every
message, even if it had already sent an OOO to that User.

Geoff.......


-----Original Message-----
From: Chris Scharff [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, July 31, 2002 10:12 PM
To: Exchange Discussions
Subject: RE: OOF Messages to the Internet


I think I described a scenario in which this could happen in another post in
this thread. The threat risk is low, but not 0. One really could
purposefully set up a mail loop with an OOO response if they had the notion.

-----Original Message-----
From: Durkee, Peter
To: Exchange Discussions
Sent: 7/31/2002 6:30 PM
Subject: RE: OOF Messages to the Internet

...but they're friendly lawyers, really. 

Seriously though, we do allow OOFs to the net, by friendly lawyer request,
and if you really can get it to loop I'd very much like to know about it.

-Peter

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to