Thanks, Pete (once I disentangled the message from the html code). I had suspected this might be the case. But it wasn't clear to me why the problem had only arisen in May. Now that I think about it, though, I imagine that's when the subscriber started the autoforwarding. And of course since the nonexistent forwarding address doesn't match the one doing the forwarding, LISTSERV is helpless to do anything about it. I would think it might be a good idea for LISTSERV auto-delete to send an owner a warning message when an address goes over the limit (4 days or 100 bounces) and can't be deleted. Possible? -- rh On Tue, 12 Jun 2001 08:54:46 -0400, Pete Weiss <[log in to unmask]> wrote: ><html> >Russ:<br><br> >Your subscriber<br><br> >[log in to unmask] >Graham Alsop<br><br> >is auto-forwarding<br><br> >220 mithras.lgu.ac.uk ESMTP Sendmail 8.9.1/8.9.1; Tue, 12 Jun 2001 >13:51:31 +0100 (BST)<br> >expn alsop<br> >250 <alsop@venus><br><br> >Pete<br><br>