From owner-freebsd-security@FreeBSD.ORG Thu Apr 21 13:01:31 2011 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA8451065673 for ; Thu, 21 Apr 2011 13:01:31 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from praag.hoster.bg (praag.hoster.bg [77.77.142.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3AD0F8FC2B for ; Thu, 21 Apr 2011 13:01:31 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by praag.hoster.bg (Postfix) with ESMTP id 8D9E18CAE6 for ; Thu, 21 Apr 2011 15:34:56 +0300 (EEST) Received: from straylight.ringlet.net (unknown [95.111.66.80]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id 01F555C06E for ; Thu, 21 Apr 2011 15:34:47 +0300 (EEST) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id 506764 by straylight.ringlet.net (DragonFly Mail Agent) Thu, 21 Apr 2011 15:34:47 +0300 Date: Thu, 21 Apr 2011 15:34:47 +0300 From: Peter Pentchev To: Paul Blazejowski Message-ID: <20110421123447.GD4543@straylight.ringlet.net> Mail-Followup-To: Paul Blazejowski , Robert Simmons , freebsd-security References: <20110420212354.GB73035@in-addr.com> <20110421042639.GB91477@DataIX.net> <1303360894.3063.1.camel@blaze.homeip.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <1303360894.3063.1.camel@blaze.homeip.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-MailScanner-ID: 01F555C06E.4A261 X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: freebsd-security@freebsd.org X-Spam-Status: No Cc: freebsd-security , Robert Simmons Subject: Re: bad email address X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2011 13:01:31 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 21, 2011 at 12:41:34AM -0400, Paul Blazejowski wrote: > doesn't mailman unsubscribe an email automatically after a couple of > bounces? unless freebsd list is not configured to do so... That's only if the bounce message reaches mailman. In this case, the culprit is a mail bouncing agent (MBA? ;) which addresses the bounce to the original sender (the one from the From header) instead of *any* of the other possible addresses present in mailman-generated messages that would do the right thing. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org peter@packetscale.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I've heard that this sentence is a rumor. --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJNsCRhAAoJEGUe77AlJ98T3SYP/3cgF4CGWd47bxt6MDR4w7BA V8c6gWqi9+HylBdXGdERaGAshgl2IaqSLfJIwx+abCtke3YkGarviCHevG1Wmv5o 1cdCBg5p7xnr0dhIwZDJkK4ZPH9oZqAyGSk1/YCpWge2wU1VuCDJZa08iGk9XPNi Emx8J+nelG2oiDHmfGQ1ebOxaTXZyWG8GaIMGW2YwLllxUpLDj28kyAtBJL0HaKj nX72cgztpaJ8nfXM4XdVHW0Jmb4sqvtdvtBjazjOQhLLnbnjtAOcYeBpVdwtRkiU t7x675EaQbE4iEXOvqgPne4cXiiYGSVtUdK3NRExkASF/mLfKt3TG874oHorxTOe wtySCjVeiJKuqjrqtnQZ+vPVbdk9qvQ9dovADj2XDCFus9bHZsXNQWfNHWIZHUA2 GQnFbRpUmPjToLY0r2iU+fNkYw7hVfylZPIaiXTn+fx3hV/RKcprbWV/rLQa0VAE 4a25IFNRNjnjzh6HYDEFNmZsvAwWlGwBK3rFU8pJiSQfgEZ7D1V1Ihzz19g4qadb 1mS0M8Yf4YLzt8EV0kD7t4v28wXOQHVeE+HfVgQPQH77cwD00Pr9TsdOw1jhf35q jriSaQ8YJxt/UqwEezPxrDV1qCphq1cIb9/vhz4ZhB201mx5l/s0iE5qk/8cRl52 VliSMR7/2236q6UmsOBI =jlhh -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU--