[BALUG-Admin] 27 balug-announce subscribers newly in "B" status

Wed Aug 24 08:29:50 UTC 2022

Here we have listed 27 subscribed addresses on balug-announce that 
on Sunday got delivery disabled, all at once, on account of too high a
bounce score.  Of those, three were special cases, resolved as follows:

1.  glub-balug-talk@gmane.org     (service moved to m.gmane-mx.org; see
https://lars.ingebrigtsen.no/2020/01/15/news-gmane-org-is-now-news-gmane-io/):
removed old subscription, sent invite to glub-balug-talk@m.gmane-mx.org

2. grep@oriole.sbay.org   (gone; DNS doesn't resolve any more): removed

3. lobal@cds1.net:  non-delivery notice says: "550 sorry, no mailbox here
by that name": removed

4. Doug Lym <dlym@pop.vox.secureserver.net> a longtime friend of mine,
is subscribed as "dlym@mail.sfpcug.org", which FQDN is a CNAME
resolving to pop.vox.secureserver.net .  I sent from rick@linuxmafia.com
to his mail.sfpcug.org the following form message, which appears to have
SMTP 250 delivered (in any event, did not generate DSN):

From: Rick Moen <rick@linuxmafia.com>
To: [recipient]
Subject: Checking your BALUG subscription address's deliverability

Greetings.  Your address is subscribed to announcements mailing list 
balug-announce@lists.balug.org, but lately has been undeliverable,
so this is a test message to verify you're still reachable.
Apologies for any intrusion.  This is the best way I could think
of to check.

-- Rick Moen
   Bay Area Linux User Group listadmin

5 through 27:  Likewise, I sent the same form mail to the remaining 23
subscribers, listed below with fullnames where known:

Art McGee <amcgee@virtualidentity.org>
btimberl@student.santarosa.edu
cmsclaud@arches.uga.edu
Dan Lyke <danlyke@chattanooga.net>
Will Lowe <harpo@thebackrow.net>
Jason Corcoran <jason@jcorcoran.net>
jsmith4@student.santarosa.edu
jtbolton@digizen.net
kevinchi@tp.silkera.net
Laurie Pennisi <lpennisi@student.santarosa.edu>
Andru Luvisi <luvisi@andru.sonoma.edu>
Mark Terranova <mark@gidgetkitchen.org>
mditter@student.santarosa.edu
Mike Higashi <mhigashi@hooked.net>
Neil J. Gunther <ngunther@ricochet.net>
rhernand@student.santarosa.edu
shart@blacklight.net
Heather Stern <star@starshine.org>
sugo@pescaralug.org
theeba@cultureisaweapon.org
Travis Hassloch <travis+ml-balug-announce@subspacefield.org>
Travis Hassloch <travis+ml-balug-talk@subspacefield.org>
vdow@unex.berkeley.edu

As with my mail to Doug Lym, all of my test mails to those
appear to have gone through.

Michael P., AFAIK, only you have the MTA/MLM log file access on the BALUG
host necessary to determine why these subscribers' mail is generating
bounce scores.  Therefore, I am ending my investigation with the
problem left open, unless someone can think of another route forward.

That leaves subscribers 4-27 (above) in "B" status, delivery disabled
owing to high bounce scores, and likely eventually to get unsubscribed.

----- Forwarded message from mailman@lists.balug.org -----

Date: Sun, 21 Aug 2022 00:38:48 +0000
From: mailman@lists.balug.org
To: balug-announce-owner@lists.balug.org
Subject: Bounce action notification
X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00,MAILING_LIST_MULTI,
	NO_REAL_NAME,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham version=3.3.1

This is a Mailman mailing list bounce action notice:

    List:       BALUG-Announce
    Member:     sugo@pescaralug.org
    Action:     Subscription disabled.
    Reason:     Excessive or fatal bounces.

The triggering bounce notice is attached below.

Questions? Contact the Mailman site administrator at
mailman@lists.balug.org.

Received: from Debian-exim by balug-sf-lug-v2.balug.org with local (Exim 4.92)
	id 1oPYuV-0007SV-Hf
	for balug-announce-bounces@lists.balug.org; Sun, 21 Aug 2022 00:33:51 +0000
X-Failed-Recipients: amcgee@virtualidentity.org,
  ngunther@ricochet.net,
  mark@gidgetkitchen.org,
  grep@oriole.sbay.org,
  star@starshine.org,
  kevinchi@tp.silkera.net,
  jtbolton@digizen.net,
  travis+ml-balug-announce@subspacefield.org,
  travis+ml-balug-talk@subspacefield.org,
  glub-balug-talk@gmane.org,
  jason@jcorcoran.net,
  shart@blacklight.net,
  sugo@pescaralug.org,
  lobal@cds1.net,
  dlym@pop.vox.secureserver.net,
  danlyke@chattanooga.net,
  theeba@cultureisaweapon.org,
  harpo@thebackrow.net,
  mhigashi@hooked.net
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@balug.org>
To: balug-announce-bounces@lists.balug.org
Content-Type: multipart/report; report-type=delivery-status; boundary=1661042031-eximdsn-619765593
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1oPYuV-0007SV-Hf@balug-sf-lug-v2.balug.org>
Date: Sun, 21 Aug 2022 00:33:51 +0000

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  amcgee@virtualidentity.org
    retry timeout exceeded
  ngunther@ricochet.net
    retry timeout exceeded
  mark@gidgetkitchen.org
    retry timeout exceeded
  grep@oriole.sbay.org
    retry timeout exceeded
  star@starshine.org
    retry timeout exceeded
  kevinchi@tp.silkera.net
    retry timeout exceeded
  jtbolton@digizen.net
    retry timeout exceeded
  travis+ml-balug-announce@subspacefield.org
    host c.mx.subspacefield.org [64.156.192.217]
    retry timeout exceeded
  travis+ml-balug-talk@subspacefield.org
    host c.mx.subspacefield.org [64.156.192.217]
    retry timeout exceeded
  glub-balug-talk@gmane.org
    retry timeout exceeded
  jason@jcorcoran.net
    host jcorcoran.net [34.102.136.180]
    retry timeout exceeded
  shart@blacklight.net
    host mail.blacklight.net [35.163.141.36]
    SMTP error from remote mail server after initial connection:
    451 http://www.barracudanetworks.com/reputation/?pr=1&ip=96.86.170.229:
    retry timeout exceeded
  sugo@pescaralug.org
    retry timeout exceeded
  lobal@cds1.net
    host mail.cds1.net [74.208.12.112]
    retry timeout exceeded
  dlym@pop.vox.secureserver.net
    (generated from dlym@mail.sfpcug.org)
    retry timeout exceeded
  danlyke@chattanooga.net
    retry timeout exceeded
  theeba@cultureisaweapon.org
    host cultureisaweapon.org [183.181.85.9]
    SMTP error from remote mail server after RCPT TO:<theeba@cultureisaweapon.org>:
    454 4.7.1 <theeba@cultureisaweapon.org>: Relay access denied:
    retry timeout exceeded
  harpo@thebackrow.net
    retry timeout exceeded
  mhigashi@hooked.net
    retry timeout exceeded

Reporting-MTA: dns; balug-sf-lug-v2.balug.org

Action: failed
Final-Recipient: rfc822;mhigashi@hooked.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;harpo@thebackrow.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;theeba@cultureisaweapon.org
Status: 5.0.0
Remote-MTA: dns; cultureisaweapon.org
Diagnostic-Code: smtp; 454 4.7.1 <theeba@cultureisaweapon.org>: Relay access denied: retry timeout exceeded

Action: failed
Final-Recipient: rfc822;danlyke@chattanooga.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;dlym@pop.vox.secureserver.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;lobal@cds1.net
Status: 5.0.0
Remote-MTA: dns; mail.cds1.net

Action: failed
Final-Recipient: rfc822;sugo@pescaralug.org
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;shart@blacklight.net
Status: 5.0.0
Remote-MTA: dns; mail.blacklight.net
Diagnostic-Code: smtp; 451 http://www.barracudanetworks.com/reputation/?pr=1&ip=96.86.170.229: retry timeout exceeded

Action: failed
Final-Recipient: rfc822;jason@jcorcoran.net
Status: 5.0.0
Remote-MTA: dns; jcorcoran.net

Action: failed
Final-Recipient: rfc822;glub-balug-talk@gmane.org
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;travis+ml-balug-talk@subspacefield.org
Status: 5.0.0
Remote-MTA: dns; c.mx.subspacefield.org

Action: failed
Final-Recipient: rfc822;travis+ml-balug-announce@subspacefield.org
Status: 5.0.0
Remote-MTA: dns; c.mx.subspacefield.org

Action: failed
Final-Recipient: rfc822;jtbolton@digizen.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;kevinchi@tp.silkera.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;star@starshine.org
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;grep@oriole.sbay.org
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;mark@gidgetkitchen.org
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;ngunther@ricochet.net
Status: 5.0.0

Action: failed
Final-Recipient: rfc822;amcgee@virtualidentity.org
Status: 5.0.0

Return-path: <balug-announce-bounces@lists.balug.org>
Received: from localhost ([127.0.0.1] helo=balug.org)
	by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92)
	(envelope-from <balug-announce-bounces@lists.balug.org>)
	id 1oO5xs-00055p-Aa; Tue, 16 Aug 2022 23:27:16 +0000
Received: from shell1.rawbw.com ([198.144.192.42])
 by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92)
 (envelope-from <Michael.Paoli@cal.berkeley.edu>) id 1oO5xq-00055f-DK
 for balug-announce@lists.balug.org; Tue, 16 Aug 2022 23:27:14 +0000
Received: from mail1.rawbw.com (mail1.rawbw.com [198.144.192.43])
 by shell1.rawbw.com (8.15.1/8.15.1) with ESMTP id 27GNRBvD052143;
 Tue, 16 Aug 2022 16:27:11 -0700 (PDT)
 (envelope-from Michael.Paoli@cal.berkeley.edu)
Received: from h199-255-45-4.hgst.com (h199-255-45-4.hgst.com
 [199.255.45.4]) by webmail.rawbw.com (Horde Framework) with HTTP; Tue, 16
 Aug 2022 16:27:11 -0700
Message-ID: <20220816162711.87896zn2932vipcs@webmail.rawbw.com>
Date: Tue, 16 Aug 2022 16:27:11 -0700
From: "Michael Paoli" <Michael.Paoli@cal.berkeley.edu>
To: BALUG-Announce <balug-announce@lists.balug.org>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.2.1-RC1)
Received-SPF: none client-ip=198.144.192.42;
 envelope-from=Michael.Paoli@cal.berkeley.edu; helo=shell1.rawbw.com
Subject: [BALUG-Announce] BALUG - no meeting today!
X-BeenThere: balug-announce@lists.balug.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Announcements for and by BALUG <balug-announce.lists.balug.org>
List-Unsubscribe: <https://lists.balug.org/cgi-bin/mailman/options/balug-announce>, 
 <mailto:balug-announce-request@lists.balug.org?subject=unsubscribe>
List-Archive: <https://lists.balug.org/pipermail/balug-announce/>
List-Post: <mailto:balug-announce@lists.balug.org>
List-Help: <mailto:balug-announce-request@lists.balug.org?subject=help>
List-Subscribe: <https://lists.balug.org/cgi-bin/mailman/listinfo/balug-announce>, 
 <mailto:balug-announce-request@lists.balug.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="Yes"
Errors-To: balug-announce-bounces@lists.balug.org
Sender: "BALUG-Announce" <balug-announce-bounces@lists.balug.org>

BALUG - no meeting today!

Sorry, no meeting today.
Watch this list and/or check the web site for updates.
https://www.balug.org/#Meetings-upcoming

_______________________________________________
BALUG-Announce mailing list
BALUG-Announce@lists.balug.org
https://lists.balug.org/cgi-bin/mailman/listinfo/balug-announce

----- End forwarded message -----
----- Forwarded message from mailman@lists.balug.org -----

Date: Sat, 20 Aug 2022 23:53:47 +0000
From: mailman@lists.balug.org
To: balug-announce-owner@lists.balug.org
Subject: Bounce action notification
X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00,MAILING_LIST_MULTI,
	NO_REAL_NAME,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham version=3.3.1