Hi,
I fully agree with Adrien, because the mails land in different IMAP
folders. This behaviour is also not different to JIRA, If I am watching
an issue or opened/assigned it to me, i get direct mails!
If I am actively working/watching on a PR or issue, i get the mail
adressed directly to my main mail adress and they land in the inbox.
Notifications about all issues of Lucene/Solr are filtered with Sieve
and land in the Lucene-issues and Solr-issues folders. This folder is
only checked quickly ("diagonally"), while mails adressed to me dircetly
get higher importance as they land in INBOX.
Theres also no way to prevent the duplicates if sent by different
systems with different message-ids. My mail filtering only removes
duplicates with same message ID (like mails going to multiple lists and
CCed to myself; Dovecot has support to remove them from beginning).
Uwe
Am 11.07.2022 um 11:17 schrieb Adrien Grand:
Hey Mike,
I'm only subscribed to issues/PRs I'm participating in on GitHub,
which I've found useful since I can filter these and be more reactive
on them, while still having access to the entire stream of activity
via issues@l.a.o.
On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless
<luc...@mikemccandless.com> wrote:
Hi Team,
Mike Sokolov mentioned this recently, making me realize it was not
just me getting double-emails on comments on GitHub PRs/issues :)
I think it happens because we are subscribed to notifications on
Apache org repositories, so we get an email notification from
GitHub (as an HTML email). But then Apache mirrors these repos to
its own Git instance, and that also sends notification emails (as
plain text).
Does anyone else see these duplicates because Mike S and I? How
do you avoid / fix it :) Which one should we unsubscribe from?
Mike McCandless
http://blog.mikemccandless.com
--
Adrien
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de
