The original GitBox notifications go to the notification@teaclave for archive: http://mail-archives.apache.org/mod_mbox/teaclave-notifications/202001.mbox/browser.
Right now, we are trying to setup GitHub notifications forwarding to dev@teaclave. The only thing left is to setup the list to accept notification from `[email protected]`. I have submitted the ticket but no one take action yet. Let me ping the ticket again. Thanks. On Wed, Jan 15, 2020 at 8:09 AM Matt Sicker <[email protected]> wrote: > > Ok yeah, I'm definitely seeing duplicate messages. It seems like Infra > enabled the notifications through a different mechanism. > > On Wed, 15 Jan 2020 at 10:05, Matt Sicker <[email protected]> wrote: > > > > I'm also noticing that some of the GitHub notifications being filtered > > by the list are already being sent from another address now. We can > > probably remove the first notification setup now. > > > > On Wed, 15 Jan 2020 at 10:02, Matt Sicker <[email protected]> wrote: > > > > > > Still getting flooded with moderation messages for filtered messages. > > > > > > On Sun, 12 Jan 2020 at 18:53, Mingshen Sun <[email protected]> wrote: > > > > > > > > Just give you guys an update on this. I have submitted the ticket but > > > > still haven't been setup up. Hopefully, this will resolve this week. > > > > Thanks. > > > > > > > > - https://issues.apache.org/jira/projects/INFRA/issues/INFRA-19621 > > > > > > > > On Wed, Jan 8, 2020 at 11:43 AM Mingshen Sun <[email protected]> wrote: > > > > > > > > > > Sure, I have submitted ticket to the INFRA team. Will update this > > > > > email when it's done. Thanks. > > > > > > > > > > On Wed, Jan 8, 2020 at 11:04 AM Matt Sicker <[email protected]> wrote: > > > > > > > > > > > > I'm not really sure how that works, so I'd go the infra route for > > > > > > now. > > > > > > They might already have a service we can use for this. > > > > > > > > > > > > On Wed, 8 Jan 2020 at 12:12, Mingshen Sun <[email protected]> wrote: > > > > > > > > > > > > > > Thanks. I have notice this issue. One extra step is to put ` > > > > > > > [email protected]` into the dev list's whitelist. Should I > > > > > > > contact > > > > > > > INFRA team or our moderators can get it done? > > > > > > > > > > > > > > On Wed, Jan 8, 2020 at 10:06 AM Matt Sicker <[email protected]> > > > > > > > wrote: > > > > > > > > > > > > > > > Seems that some sort of archival service isn't actually > > > > > > > > subscribed to > > > > > > > > the mailing list which is causing every notification to be > > > > > > > > blocked. An > > > > > > > > INFRA ticket could be helpful in configuring notification lists > > > > > > > > here. > > > > > > > > > > > > > > > > -- > > > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Matt Sicker <[email protected]> > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > -- > > > Matt Sicker <[email protected]> > > > > > > > > -- > > Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
