Re: Brittle communication channels

Quoting Ivan Sergio Borgonovo ([email protected]):

> mmm coincidentally I received from the list some old posts just today if 
> this help to diagnose any problem.

As mentioned separately, I deliberately induced Mailman to re-process
some postings starting June 3rd, 2016, that it had sidetracked into a
queue in Python 'pickled' data-storage format, in directory
MAILMAN_HOME/qfiles/shunt .  Thereupon, it delivered those held
('shunted') messages to all current subscribers.


There was a subscriber on (as it turns out) both svlug@ (this mailing
list) and svlug-announce@ , whose name Mailman choked on starting around
June 3rd.  Accordingly, Mailman either (1) ceased sending any mail at
all, or (2) sent mail iteratively through the subscriber list until it
reached that subscriber, then quit and quarantined the message.

I'm not certain offhand, but suspect it was option #2 -- delivery to
_some_ subscribers (those before the gentleman in question) but not
those after.  

I'm therefore guessing that only _some_ svlug-announce@ subscribers
received the July meeting announcement.  (I did, for example, though I
received no svlug@ mail during that time period.)