On Mon, Mar 01, 2004 at 07:21:43PM +0100, Benno Goedhart wrote: > > Same thing here. This is actually the second time this has happened in > one week. This morning all messages came in though. > > Aren't there plans to announce such things. Planned outages could be posted to a web site as could status. For troubles, announce via - ???? - Mail takes 12 hours when things are congested/ broken so mail is not a good tool. ;-) Since this is a global list and recent troubles have involved localish network routing troubles there may not be a general solution to this. On a busy list like this it might be possible for an end user to tabulate messages per unit time and compare against history to see latency. But what actions are possible when a problem is found? In my limited experience when things go sideways on mail exploders it takes a while for the bits to settle no matter how quickly the admin folks are notified. The default FC1 queue timer is (QUEUE=1h) so if a message is undelivered on the first try it will retry in an hour. Monster exploders like this list server may have the timer set larger. My guess is that it is set to (QUEUE=3h) on the boxes that service this list. -- T o m M i t c h e l l /dev/null the ultimate in secure storage. mitch48-at-sbcglobal-dot-net
