trijug.org problems (was Re: TriJUG meetings moving to Red Hat: 1801 Varsity Drive Raleigh NC)

Stuff started going on behind the scenes at 12:30 this morning, but the 
catch-22, as you know, is that our ISP is also after us to limit our 
outbound email traffic. I'm not pointing this out to trigger a 
discussion -  as you and I were going over this just a few days ago, we 
appreciate the goofy aspect of the ISP offering GNU/Mailman but 
punishing us for nearly trivial usage, etc - but instead I'm mentioning 
this to explain why I and others didn't "reply-all" earlier. The hope 
was that Resin would be restarted and I'd put a parenthetical into the 
usual Monday-before meeting reminder. As it is, I figure we've blown the 
lid off the traffic limit, so one more explanation times 400 msgs can't 
do much more damage. I began searching for an alternative provider for 
the email lists last week, but wish now I'd pressed harder.

One has to wonder how Resin could be on its back for way over 12 hours 
without one of the other users of the system hosting trijug.org yelling 
about it by now.

(Running to an appointment now: back on this and other subjects in a few 
hours)

-Pete