Re: master's mail backlog and upgrade time
Ian Jackson <email@example.com> writes:
> Six days ago I discovered that one of the Debian system
> administrators had made a deliberate and highly unusual
> configuration change which predictably broke mail from or via master
Err, no. Mail was _already_ bouncing, but after reaching the retry
maximum. The change did not change the end result, only when it
> No-one had contacted me, or anyone else affected.
The change was made roughly less than 24 hours before your first post
to debian-devel. There wasn't actually all that much time to contact
> but in any case immediately I found out about the situation I
> arranged matters so that master should no longer have any difficulty
> talking to chiark.
Err, no you haven't. In
on Sat, 19 Nov 2005 15:39:36 +0000, you've asked chiark users to
individually change their config to ensure chiark won't DoS master.
Until it's confirmed that all those users have done so, it's not fair
to say master will not have any difficulty talking to chiark.
And this still relies on per-user config rather than being a global
change. Which means the next time a chiark user gets a debian.org
account but neglects to perform the necessary incantation, master will
once again be DoSed by chiark.
> I also immediately notified debian-admin of these facts and have not had:
Err, no you didn't. You mailed debian-devel, and THREE DAYS LATER
mailed debian-admin. That is not immediate.
> * Correction of the broken configuration on master
troup@master:~$ grep chiark /etc/exim4/exim4.conf
And it's been like that for several days.
> * An apology for the lack of communication or a promise to do better
Speaking of doing better, could you please actually fix chiark?
Because it's STILL firewalling master....
> This situation is intolerable and must be rectified forthwith.
With all due respect, your attitude is intolerable and should be
> If the Debian system administrators are too busy to deal with this
> then I would be happy to help.