Jean,
Unfortunately, this is a limitation of Groupwise versions prior to 6.0.  What we've had to do here is to limit or disable the ability of users to set up rules on their side ... at least the ones who use GroupWise.  Your sysadms ought to instruct their users not to set up vacation rules - to sign off any lists they might be subscribed to or to just upgrade their version of GroupWise.  I'd have to say that they were at fault!!  Good luck Jean!

Sincerely,
Chris Barbot


-----Original Message-----
From: Jean Snow [mailto:[log in to unmask]]
Sent: Tuesday, February 12, 2002 1:52 PM
To: [log in to unmask]
Subject: Odd loop


I just got off the phone with the sysadmins at what I'm calling
'unhappyplace.org'.  They were unhappy because they had 80K messages in
their queues for a user, whose vacation program got into an email loop
with Listserv.  We discussed vacation rules they might use (they use
Groupwise, which I'm pleased to say I know nothing about) to prevent this
from happening again.

The reason I'm writing is that I'd have expected listserv to have said
'Unknown command ... try HELP' fifty or so times and then to have served
off the user before much damage was done.

Instead, it said:
8 Feb 2002 06:45:51 -> Rejected:
* Your message is being returned to you unprocessed because no command was
* found in the message body. LISTSERV  expects commands in the body of the
* message, rather than in the message  subject, because some users have no
* control over the contents of the "Subject:" field on outgoing messages.
8 Feb 2002 06:45:51 Sent information mail to [log in to unmask]

The sysadmins say there was text in the body of the message (the usual
vacation stuff).  But maybe they're wrong... that's the only thing I can
think of.  Any other ideas?

Thanks,
Jean Snow