[BALUG-Admin] Update on the 23 balug-announce subscribers

[Rick Moen]

I wrote:

> I'll probably just quietly remove any similar-outcome subscribers, and 
> report back in a few days about any remaining in "B" state, in the
> roster.

The four days (or whatever it is) of the traditional MTA delivery
timeout period have new elapsed, so today brought in this crop:

amcgee@virtualidentity.org: retry timeout exceeded
btimberl@student.santarosa.edu: retry timeout exceeded
cmsclaud@arches.uga.edu: retry timeout exceeded
danlyke@chattanooga.net: retry timeout exceeded
dlym@mail.sfpcug.org: retry timeout exceeded
harpo@thebackrow.net: retry timeout exceeded
jason@jcorcoran.net: retry timeout exceeded
jsmith4@student.santarosa.edu: retry time not reached for any host after a long failure period
jtbolton@digizen.net: retry timeout exceeded
kevinchi@tp.silkera.net:  retry timeout exceeded
lpennisi@student.santarosa.edu: retry time not reached for any host after a long failure period
luvisi@andru.sonoma.edu: retry timeout exceeded
mditter@student.santarosa.edu: retry time not reached for any host after a long failure period
mhigashi@hooked.net: retry timeout exceeded
ngunther@ricochet.net: retry timeout exceeded
rhernand@student.santarosa.edu: retry time not reached for any host after a long failure period
star@starshine.org: retry timeout exceeded
sugo@pescaralug.org: retry timeout exceeded
theeba@cultureisaweapon.org: Relay access denied: retry timeout exceeded
travis+ml-balug-announce@subspacefield.org: retry time not reached for any host after a long failure period
travis+ml-balug-talk@subspacefield.org: retry timeout exceeded
vdow@unex.berkeley.edu: retry timeout exceeded

I'd already removed theeba@cultureisaweapon.org, so (just now) 
removed the other 21.

Checking the remaining subscriber roster on balug-announce, there are
now 589 members, and _zero_ of those are in "B" state on account of
excess bouncing.  Therefore, the good news is that all of those problem
subscribers were genuine cases of no-longer-deliverable addresses, and
nobody at all (among subscribers' SMTP providers) is blacklisting the 
BALUG IP address -- despite remaining DNSBL problems.


As of today, using https://multirbl.valli.org/ and running test "DNSBL
lookups" on balug.org IPv4 address, we are still getting 6 blacklist
positives:

b.barracudacentral.org (Barracuda Reputation Block List)
bb.barracudacentral.org (Barracuda Reputation Block List for SpamAssassin)
fulldom.rfc-clueless.org (RFC-Clueless (RFC²) Metalist RBL)
postmaster.rfc-clueless.org (RFC-Clueless (RFC²) postmaster RBL)
all.s5h.net (s5h.net RBL)
spam.dnsbl.sorbs.net (SORBS Spamhost (any time))

Effectively, that is four (ignoring redundancies).


Michael, after your gentle reminder, I made sure those four had entries
on https://www.balug.org/wiki/doku.php?id=balug:balug_todo_list .