DSNs arrived overnight on some of my test messages from
rick(a)linuxmafia.com to the 24 balug-announce subscribers for whom
delivery recently got disabled (over high bounce scores).
vdow(a)unex.berkeley.edu: Delivery attempts will continue
star(a)starshine.org: Delivery attempts will continue
luvisi(a)andru.sonoma.edu: Delivery attempts will continue
jtbolton(a)digizen.net: Delivery attempts will continue
cmsclaud(a)arches.uga.edu: Delivery attempts will continue
amcgee(a)virtualidentity.org: Delivery attempts will continue
harpo(a)thebackrow.net: Delivery attempts will continue
danlyke(a)chattanooga.net: Delivery attempts will continue
jason(a)jcorcoran.net: Delivery attempts will continue
kevinchi(a)tp.silkera.net: Delivery attempts will continue
sugo(a)pescaralug.org: Delivery attempts will continue
theeba(a)cultureisaweapon.org: 454 4.7.1 Relay access denied
mhigashi(a)hooked.net: Delivery attempts will continue
mark(a)gidgetkitchen.org: Delivery attempts will continue
travis+ml-balug-talk(a)subspacefield.org: Delivery attempts will continue
ngunther(a)ricochet.net: Delivery attempts will continue
mditter(a)student.santarosa.edu: Delivery attempts will continue
dlym(a)pop.vox.secureserver.net (generated from dlym(a)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(a)cultureisaweapon.org" is
definitely undeliverable, so I just now removed it from the roster (to
clean things up just that little bit more).