let me paste here (for others) my initial reply :

the virtusertable is dynamically created from fasjson.fedoraproject.org and clearly someone did something "interesting" : As group members should be normally real accounts, the idea for sig-<name>@centosproject.org was to have all group members added in that alias ...

But then someone (don't know who, but clearly from your SIG), created hyperscalebot, but giving as email address the name of the group alias, which then itself was added too, so you see the loop ?

Just update that bot account email address so something else than the group alias and it will all be back to normal

So you have a workaround for the moment (updating in FAS for hyperscalebot) but it's clearly a corner case that we never thought about when writing the script querying fasjson. So a little bit for work to implement an extra check and it should all be back in action

Ah, that was probably my fault. hyperscalebot is the bot account we use for automated builds on CBS (e.g. for the systemd daily CI). I had set the email to the alias when we created it, and that worked fine for a while, but something must have changed recently.

I've updated its email to another address for now, thanks!

[backlog refinement]
We should put an extra check to prevent this from happening in the future.

[backlog refinement]
This ticket is easy to fix and good candidate for first CentOS infra ticket.

[backlog refinement]
Looking for assignee for this ticket.

issue was fixed already some time ago but just waiting for additional check for the script rendering the postfix virtusertable.
It's now pushed so closing