Hi, > > I'm afraid this broke a number of aliases, in particular > > www-d...@savannah.gnu.org and invalid.nore...@savannah.gnu.org which, > > if they don't receive mail, need to be valid senders. > > > > Check /com/mailer/aliases. > > > > Mails were bounced because of this. > > Please revert this change! > > Ah, sorry about that. I've copied the relevant info from > /com/mailer/aliases: >
> savannah-help-public: savannah-hackers@gnu.org ^^^ That one needs to stay at fencepost! :) > # - Savane's automated e-mails > INVALID.NOREPLY: :blackhole: > # - CVS rsync'd repositories > amrsync: :blackhole: > coreutilsrsync: :blockhole: > gccrsync: :blackhole: > libcrsync: :blackhole: > gawkrsync: :blackhole: > www-data: :blackhole: > > and added them to the aliases on monty python. Now, the downside of this > is that you can no longer add entries to this file. If you want to be > able to edit it, we could set up a cron job that rsyncs it off a place > on savannah somewhere, if you like. That would be nice, yes. How about sv.gnu.org:/root/00_aliases/aliases ? -- Sylvain
