I did not see the problem reports, but I did submit several netwide
delete jobs - breaking the 3200 inactive and/or mail abusing vax ids that
were locked out this week into many small ( <250 ids ) delete jobs and
submitting them ( marked for off-hours ) over several nights.
 
If only the message " User unable to receive new mail" on returned mail
would cause automatic unsub or option change to nomail instead of
appearing to trigger retries ....
 
 
( I was surprised to see that after more than a week of bouncing 10-15 messages
  per day per list for some ids, I was only able to document ONE list owner
  who took action - apparently most feel this message indicates a temporary
  problem that does not require intervention.  Perhaps an alternate message
  needs to be defined = "this id has lost e-mail access" or "this id locked"
  that listserv could treat the same as a 'user unknown or invalid'.  The
  VAX logic of 'locking' a users incoming mailbox while still allowing the
  user to send mail ( including subscription requests ) makes no sense to me. )
 
   - mike
.sp;.fo off
Copy:  system@albnyvms