DSNs arrived overnight on some of my test messages from rick@linuxmafia.com to the 24 balug-announce subscribers for whom delivery recently got disabled (over high bounce scores).
vdow@unex.berkeley.edu: Delivery attempts will continue star@starshine.org: Delivery attempts will continue luvisi@andru.sonoma.edu: Delivery attempts will continue jtbolton@digizen.net: Delivery attempts will continue cmsclaud@arches.uga.edu: Delivery attempts will continue amcgee@virtualidentity.org: Delivery attempts will continue harpo@thebackrow.net: Delivery attempts will continue danlyke@chattanooga.net: Delivery attempts will continue jason@jcorcoran.net: Delivery attempts will continue kevinchi@tp.silkera.net: Delivery attempts will continue sugo@pescaralug.org: Delivery attempts will continue theeba@cultureisaweapon.org: 454 4.7.1 Relay access denied mhigashi@hooked.net: Delivery attempts will continue mark@gidgetkitchen.org: Delivery attempts will continue travis+ml-balug-talk@subspacefield.org: Delivery attempts will continue ngunther@ricochet.net: Delivery attempts will continue mditter@student.santarosa.edu: Delivery attempts will continue dlym@pop.vox.secureserver.net (generated from dlym@mail.sfpcug.org): Delivery attempts will continue
That's 18 of them. I'll wait to hear about the other six. (Of course, those six may have been SMTP 250-delivered immediately, yesterday. I've not checked my outbound logs, to see.)
Those 18 all seem highly likely to be genuinely undeliverable subscription addresses, but I'll wait for the test attempt to time out. Except, of those 18, "theeba@cultureisaweapon.org" is definitely undeliverable, so I just now removed it from the roster (to clean things up just that little bit more).
My test mail from rick@linuxmafia.com to mark@gidgetkitchen.org (Mark Terranova) got permfailed as "unroutable address". Removed from roster.
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.
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 .