#12296 Messages sent to devel-announce are no longer being forwarded to devel
Closed: Fixed with Explanation 18 days ago by zlopez. Opened 19 days ago by gui1ty.

This seems to have started a while ago. I discussed it with @zbyszek on Matrix last Friday.

The first message I noticed was a change proposal. I only indirectly became aware of it. It seems re-subscribing devel to devel-announce did not have the desired effect.

I noticed another message later that day - the announcement of the release watch party. Someone replied to it. I'm assuming that person is subscribed to both lists.

Today, while scanning my Matrix backlog, I notice @amoloney mentioning the elections open has been sent to devel-announce. Again, this has not been forwarded to devel as expected.

This is kind of urgent, since people paying more attention to their mailbox than to other channels are going to miss important information.


On a closer look, it seems none of the recent change proposal announcements mentioned on the landing page has made it to the devel list.

The latest change proposal announcements that I have received directly in my mailbox is F42 Change Proposal: Ansible 11 (Self-Contained) from 24 September 2024.

I recently resubscribed the devel to devel-announce list again as I couldn't find any reason for the message to not be forwarded. The devel was correctly subscribed to devel-annouce and there wasn't any error in logs regarding the mails unforwarded in the past. I also noticed that the older e-mails were always sent to both devel-announce and devel. So it's possible that this didn't work for longer time.

So is there a new e-mail that wasn't forwarded?

EDIT: I can see that there is a fresh e-mail about F41 elections sent yesterday. It seems that the resubscribing of devel list to devel-announce didn't work. So this needs to be investigated.

In the meantime I can only recommend to always sent the e-mail to both.

Metadata Update from @zlopez:
- Issue assigned to zlopez
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation

19 days ago

So is there a new e-mail that wasn't forwarded?

Yes, there is. The aforementioned elections announcement. But also the Xfce 4.20 change proposal from yesterday.

Both messages post-date your re-subscription of devel to devel-announce.

The reason is the mitigations we set on all lists. ;)

Before the post would come from the person making the post and they were subscribed to devel list so it posted.

Now it's coming from:

devel-announce@lists.fedoraproject.org

which is not subscribed to devel, so it rejects it.

So, I guess we just subscribe that? (and set it to 'nomail' so it doesn't send devel list posts to devel-announce. ;)

This same thing might be affected test-announce/test too?

Thanks for the clarification @kevin I didn't put together this and the DMARC changes we did.

I will subscribe the devel-announce to devel as nomail. Will do the same for test-announce and test.

So I subscribed devel-announce to devel and disabled the deliveries. I noticed that this is already done for test/test-announce.

So I'm closing this as fixed. If the issue will be still there we will reopen the ticket.

Metadata Update from @zlopez:
- Issue untagged with: Needs investigation
- Issue tagged with: high-gain, low-trouble, ops

18 days ago

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

18 days ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog