James Rishaw busts through the QRM with...
Something else that needs to be considered is blowing up the list (making smaller, distributed lists). It takes hours sometimes for mail to go through the distribution.
Sometimes, I'll post, and I'll get four, five, six replies before I see my post to the list bounce back this way. It takes hours. :-( Too long for a list where sometimes time-critical information is discussed.
A six hour delay because the list of addressess is too large? That would take tens or hundreds of thousands of addressess, or else some precisely paced queueing logic, or a pathetically overloaded machine. I vote for Tim Ramsey setting things up on his Listserv server, if for no other reason than to just evaluate how well it works. Let's give it a try for a while. -- Phil Howard | eat8this@no1place.com crash340@anyplace.edu suck0it4@lame5ads.net phil | eat20me6@no80ads4.com stop0843@lame4ads.edu blow6me8@anywhere.edu at | ads6suck@spam9mer.edu stop4it8@no1where.edu end2ads1@no3place.com milepost | blow9me5@nowhere1.com no6spam0@lame2ads.edu stop6916@spam0mer.com dot | eat2this@nowhere5.org ads9suck@dumbads5.edu ads0suck@spam3mer.org com | eat34me5@no3where.com stop7598@spammer6.org no4spam9@noplace2.org