We'd like to update the coreosbot@fp.o email forward to point to coreos-infra@lists.fp.o. I've updated coreosbot's email address in accounts.fp.o, but it seems emails are still being forwarded to the previous address.
coreosbot has not signed the CLA (it's a bot) so it's possible that the forward isn't handled in the usual way; it may have originally been set up as special-case configuration.
When possible.
Metadata Update from @pingou: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @humaton: - Issue assigned to humaton
Hi, I was pointed to ansible regarding adding new aliases. There is a fasjson role with the aliases definition file. Is adding something like:
coreosbot: coreos-infra@lists.fedoraproject.org
the correct solution to this problem? Or should the alias be handled in some other way? cc @pingou
There is an existing forward that should be updated.
It seems like it is already doing this:
bastion01% grep coreosbot /etc/aliases coreosbot: coreos-infra@lists.fedoraproject.org
Perhaps it just hadn't updated yet?
I just tried the alias again, and it's still going to the old address. I updated the email in accounts.fp.o on Friday, FWIW.
And this is the problem:
-rw-------. 1 root root 2726468 Mar 29 19:02 /etc/aliases -rw-r--r--. 1 root root 2400256 Mar 24 16:00 /etc/aliases.db
it's not running newaliases after fasjson runs to update them. ;)
I have run newaliases, so the issue should be fixed now?
@humaton can you adjust the script to run newliases after updating? There's also a problem with groups that have no managers.
Yup, looks like it's fixed, thanks!
Let me close this one and open a new one for improvements to the script. :)
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.