From owner-freebsd-current Mon Oct 11 21:34:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat203.183.mpoweredpc.net [142.177.203.183]) by hub.freebsd.org (Postfix) with ESMTP id 241061518F; Mon, 11 Oct 1999 21:34:45 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id BAA88716; Tue, 12 Oct 1999 01:34:44 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 12 Oct 1999 01:34:44 -0300 (ADT) From: The Hermit Hacker To: "Jonathan M. Bresler" Cc: nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: People getting automatically unsub'ed from -arch In-Reply-To: <19991011174430.2B133153CB@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Oct 1999, Jonathan M. Bresler wrote: > when the MTA gives up trying to deliver the mail, i call it > bounced. so a 500 series error from the other MTA means the email has > bounced. Have you considered using bouncefilter for this? I'm using it for the PostgreSQL mailnig lists, and find its really cut down on my requirement to intervene on 'dead addresses'... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message