Re: Is anyone else getting four emails for every closed ticket ?

Bernard Quatermass via Exim-dev <[email protected]> Thu, 5 Mar 2026 14:59:46 +0000

Newsgroups	gmane.mail.exim.devel
Message-ID	<[email protected]>

On 05/03/2026 14:25, Andrew C Aitchison via Exim-dev wrote:
> 
> I am now getting *four* emails each time Jeremy closes a ticket
> - and not just ones to which I subscribed or participated.
> 
> That is two each from
>      [email protected]
>      List-ID: exim/exim <exim.exim.code.exim.org>
> and
>      [email protected]
>      List-Id: Exim MTA  development list <exim-dev.lists.exim.org>
> 
> For each list there is one email with the message from the closer
> and another from a bot to say that the bug was closed.
> 
> I see that I was listed on
>    https://code.exim.org/exim/exim/watchers
> and will see whether disabling that that halves the number of emails.
> 
> Since the new bug system can send emails whenever a bug is updated,
> do we wish to rethink also sending them to/through
>      [email protected]
> ?
> 

This is expected behaviour with the current configuration.

There are two factors involved here.

The first is that the closing of a ticket is a distinct event from any final comment.
This results in a pair of emails. There is no mechanism to change this, though there
are a couple of forgejo tickets related to improving granularity of notifications,
notably https://codeberg.org/forgejo/forgejo/issues/7461

The other factor is that to continue any utility with the exim-dev mailing list we
have an "exim-dev-list" pseudo-user subscribe to the project in forgejo such that
it receives all project notification emails and relays them into the list.
This result in all current exim-dev list members continuing to receive ticket
updates without creating accounts on code.exim.org.

It might be argued that the more appropriate approach would be to retire exim-dev
list entirely and rely on direct notifications to accounts on code.exim.org but
this would constitute an even larger change in behaviour than any of the recent
upgrades and require additional discussion.

-- 
Bernard Quatermass

OpenPGP_signature.asc (application/pgp-signature, 665 B)