This is likely more a infra ticket than releng, but no big deal. We can do this once we are out of freeze.

Shouldn't it be anaconda-devel@lists.fedoraproject.org as the primary address?

Good point Neal. I agree that having the lists twice doesn't look nice.

This is likely more a infra ticket than releng, but no big deal. We can do this once we are out of freeze.

Thanks, I wasn't sure where to file this.

Ping, any progress about this?

Created mailing list: anaconda-devel@lists.fedoraproject.org

You should be admin, and from there you can add whoever else you like.

I don't have the power to make the anaconda-devel-list@redhat.com alias to the new list. For that you will need to file an internal ticket. ;(

If there's anything else we can do here, feel free to re-open or file a new issue.

Hi,

Thanks for creating the mailing list. I manage to solve the internal redirect to this one by

we can take the alias and create a fork - it will point to
fedorapoject and to the ml at the same time. This means that emails will go
to both.

However, when I'm trying to send mail to the anaconda-devel@redhat.com it's always require the administrator approval because

Message has implicit destination

I guess, I have to set the alias somehow on the mailing list settings but I don't know how. I tried to set "Acceptable aliases" but it doesn't seem to be helping. Could you please give me a help hand here?

This is mailman2 right?

Privacy Options >> Recipient filters
Change the Must posts have list named in destination (to, cc) field (or be among the acceptable alias names, specified below)

(either add the lists.fedoraproject.org there or unset the must)

I turned the require_explicit_destination off on the anaconda-devel-list@redhat.com side but still the same issue.

When I sent mail to anaconda-devel-list@redhat.com it is blocked on the anaconda-devel@lists.fedoraproject.org side and requires administrator approval with message: "Message has implicit destination". In other words, nothing has changed.

Honestly, I hate that I'm spamming the list a lot because to this testing :(. Is there a better way to test this?

We finally resolved the old (Red Hat) ML to be transparently disabled. I'm still having issue that when someone will send mail to old ML it's blocked on the new ML (Fedora) side but it's not really blocking.

We have low amount of traffic there so I don't have an issue to manually confirm messages from the old ML and also it could be a bit beneficial so the people would know that they should re-subscribe.

Thanks for all the help!