Auto-Delete is a function of:
 
1) your list's definitions (assuming a current level of LISTSERV)
2) the particular MAILER involved at the destination site (not
   "intermediate" like I incorrectly said before (M.K.))
3) the particular versions of SMTP involved (if any)
 
Even if that is all working as designed (WAD?), that does not inhibit
the delivery of "bounce" messages to the ERRORS= kw operands.  Why?
Auto-Delete was not meant to _suppress_ the receipt of the bounce
messages, just to take action on ones that conform to its algorithm.
Thus, though it may prevent FUTURE distribution of new mail to
non-existent userids, it does NOTHING to inhibit the receipt of
in-progress delivery attempts and their possible bounces.
 
So if 10 messages to a particular "broken" userid are in-progress of
being delivered via the LISTSERV distribute algorithm, and LISTSERV
Auto-Delete acts upon the first bounces, you'll still get that bounce
plus 9 more until the delivery queue "drains" (assuming a permanent
"broken" userid).
 
--  co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
[log in to unmask] "Let them get their own mailing list"  +1 814 863 1843
31 Shields Bldg. -- Penn State Univ -- University Park, PA 16802-1202 USA