> Is there something wrong with the server for amanda-users? I finally
> got around to changing my subscription from an old address to my
> current one today and am very dismayed at what I'm seeing from this
> list. My old address is receiving amanda-users messages more than
> an hour sooner than my current address! I was going to un$ubscribe
> the old address but this is rediculous. Is this list so huge that it
> takes more than 1 hour to run a single message through it? Or is the
> server or it's network connection just way too overloaded?
>
> Yes, I can provide Received: headers to verify all this if you'd like.
> Further, my old address is forwarding to my current one, so I'm receiving
> both copies in the same mailbox, disproving any possibility that the
> problem might be an overload on this end. Is there anything that can
> be done?
There's a slew of people on the list that are causing name server
timeouts or have really slow connections resuling in it taking a long
time for everyone on the list to be gotten to. I'm currently flushing
those people out and have a few other configuration changes I'm planning
that will likely streamline the process.
I do not keep a close eye on the lists except for possible major issues
and unsubscribe/subscribe problems, so this sort of cleanup doesn't happen
that often.
In the past, the amanda lists went through UUNET's mail relays which
did delivery in parallel, but when I switched providers recently, it went
back to serial delivery which is why this is a relatively new problem.
At some point (I keep saying this but never get around to executing),
the amanda lists will move to sourceforge with the rest of the project,
which theoretically has delivery more optimized for large lists.
-Todd
