On 8/14/2006 10:57, Jeff Kiesel wrote:
> Everybody talks 
> about the problem but the people who actually have control over OOO 
> (ie, the MTA vendors whose MTAs generate the OOO in the first place) 
> do nothing to help solve it.

An OOO may be generated by the MTA, but most of the problematic OOO messages
that we see are sent by the recipient's MUA. Before he left on vacation, Joe
User created a filter rule in his email client which sends his vacation
auto-reply message to the 'From:' address on every message he receives,
regardless of envelope-sender address on the message, or the number of vacation
auto-reply message that might have been sent to a given address in the last
hour, day, or week. And since his email client is configured to check for new
mail every minute, and he is subscribed to several active lists, and his
subscription is set to MAIL on every one of those lists, his unattended
workstation now becomes a source of OOO spam.

-- 
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
[log in to unmask]