From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from majordomo by infradead.org with local (Exim 3.20 #2) id 14SJet-00022L-00 for mtd-list@infradead.org; Mon, 12 Feb 2001 14:08:51 +0000 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237] helo=passion.cambridge.redhat.com) by infradead.org with esmtp (Exim 3.20 #2) id 14SJes-00022E-00 for mtd@infradead.org; Mon, 12 Feb 2001 14:08:50 +0000 Received: from dwmw2 (helo=redhat.com) by passion.cambridge.redhat.com with local-esmtp (Exim 3.16 #2) id 14SJep-000825-00 for mtd@infradead.org; Mon, 12 Feb 2001 14:08:47 +0000 From: David Woodhouse To: mtd@infradead.org Subject: List admin stuff. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Feb 2001 14:08:47 +0000 Message-ID: <30880.981986927@redhat.com> Sender: owner-mtd@infradead.org List-ID: I'm getting bored of dealing with bounces and mail getting stuck on the outgoing queue. Until now, I've been making a valiant effort to notify people - generally via their postmaster - when their mail has been bouncing for any length of time. I will now just unsubscribe them. (Starting with r.siagri@eurotech.it if relay.eurotech.it refuses to relay this mail). I will also be far quicker to unsubscribe people whose domain has only a single MX (or A) record - I may not even wait for mail to bounce. If you care - get an account on a real mail system and subscribe from there. You'll note I tend to avoid using my company email address in public fora for partly that reason. I'm not ruling out the possibility that the mail exploder will be doing ECN in a few weeks' time, either. But it's unlikely. -- dwmw2 To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org