At 15:45 -0400 on 10/05/2007, Ed Finnell wrote about Re: Check out
E-Mail Problem Creates Message Flood - AOL Ne:
Wasn't the original Christmas Worm on VM an OoO attempt?
If I remember correctly it was. User 1 had scheduled a message (I
think it was a large message he wanted to get sent/delivered when the
load on the network was lower by delaying its transmission until the
Weekend) to get sent after he left on vacation as well as setting up
a OoO reply daemon. When the scheduled message finally get sent, the
recipient had a OoO bot of his own on his account. The message got
rejected/reflected back to the original sender along with a separate
OoO reply message (thus there were 2 messages in flight back to the
original sender). These messages each triggered a rejection and OoO
set (thus upping the in-flight count heading to the original
recipient to 4). Each Bounce doubled the number of messages going
back and forth until the system was brought to its knees and an
Administrator had to fix the problem (the next Monday).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
