On Tue, 20 Apr 2021 at 17:22, Matt Sicker <boa...@gmail.com> wrote:
>
> I've tried adding that email to the allow-subscribe list for that
> mailing list. Let's see if the next messages get through without
> moderation now.

As already noted, the Return-Path is different for each email - have a
look at the headers in the email source.

I have raised INFRA-21752 with a potential solution.

> On Tue, 20 Apr 2021 at 10:46, Matt Sicker <boa...@gmail.com> wrote:
> >
> > I've accepted all the moderation requests so far, though I also get
> > CC'd on the same emails, so my inbox is a little messy at the moment
> > to verify that it's going through the mailing list, too. There's
> > already been like 20 alerts found, so good call on the separate
> > mailing list! :)
> >
> > On Tue, 20 Apr 2021 at 10:43, sebb <seb...@gmail.com> wrote:
> > >
> > > On Tue, 20 Apr 2021 at 16:34, Fabian Meumertzheim
> > > <meumertzh...@code-intelligence.com> wrote:
> > > >
> > > > I think that the sender address has been 
> > > > monorail+v2.382749...@chromium.org for
> > > > me since February, so it might be more stable than it looks.
> > >
> > > Yes, but ezmlm uses the envelope sender, i.e. the Return-Path.
> > >
> > > At least the current ones all have the same domain name.
> > >
> > > If this is sufficiently unique it should be possible to filter all
> > > such emails without opening the floodgates.
> > > (the filter just removes the variable part, so normal moderation rules
> > > can be applied)
> > >
> > > > On Tue, Apr 20, 2021, 17:30 Matt Sicker <boa...@gmail.com> wrote:
> > > >
> > > > > Guess we'll have to ask infra then. They probably have a way to filter
> > > > > based on regex or something.
> > > > >
> > > > > On Tue, 20 Apr 2021 at 10:05, sebb <seb...@gmail.com> wrote:
> > > > > >
> > > > > > On Tue, 20 Apr 2021 at 15:53, Matt Sicker <boa...@gmail.com> wrote:
> > > > > >
> > > > > > > Looks like we need to add the bot email as an allowed sender to 
> > > > > > > the
> > > > > list.
> > > > > > >
> > > > > >
> > > > > > Easier said than done, as email appears to use a dynamic address.
> > > > > >
> > > > > >
> > > > > > > Otherwise, I’ve seen the alerts start already
> > > > > > >
> > > > > >
> > > > > >
> > > > > > > On Tue, Apr 20, 2021 at 09:27 Fabian Meumertzheim <
> > > > > > > meumertzh...@code-intelligence.com> wrote:
> > > > > > >
> > > > > > > > The first OSS-Fuzz build passed and some bugs have already been
> > > > > created.
> > > > > > > > Everything looks good from my side, but let me know if you have 
> > > > > > > > any
> > > > > > > > questions.
> > > > > > > >
> > > > > > > > One more thing: Could you perhaps add the following line to the
> > > > > READMEs
> > > > > > > of
> > > > > > > > compress and imaging?
> > > > > > > >
> > > > > > > > [![Fuzzing Status](
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > https://oss-fuzz-build-logs.storage.googleapis.com/badges/apache-commons.svg)](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:apache-commons
> > > > > > > > )
> > > > > > > >
> > > > > > > > This will give you both an indicator of the fuzzer build status 
> > > > > > > > as
> > > > > well
> > > > > > > as
> > > > > > > > a convenient link to the bugs on the OSS-Fuzz issue tracker.
> > > > > > > >
> > > > > > > > On Mon, Apr 19, 2021, 12:16 sebb <seb...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > > On Mon, 19 Apr 2021 at 07:54, Stefan Bodewig 
> > > > > > > > > <bode...@apache.org>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > On 2021-04-18, Stefan Bodewig wrote:
> > > > > > > > > >
> > > > > > > > > > > I've created 
> > > > > > > > > > > https://issues.apache.org/jira/browse/INFRA-21741
> > > > > if
> > > > > > > > you
> > > > > > > > > > > want to lend a hand moderating, you may want to add 
> > > > > > > > > > > yourself
> > > > > to the
> > > > > > > > > > > ticket before the list is created.
> > > > > > > > > >
> > > > > > > > > > The list has been created, so if you want to receive the 
> > > > > > > > > > fuzz
> > > > > reports
> > > > > > > > > > please subscribe to fuzz-testing@commons and one of the 
> > > > > > > > > > intial
> > > > > > > > > > moderators will accept the subscription (if we can 
> > > > > > > > > > recognize the
> > > > > > > email
> > > > > > > > > > address :-).
> > > > > > > > >
> > > > > > > > > Best to ensure that you use an address that is listed in your 
> > > > > > > > > LDAP
> > > > > > > > account.
> > > > > > > > > Visit https://whimsy.apache.org/roster/committer/__self__ to
> > > > > maintain
> > > > > > > > the
> > > > > > > > > list.
> > > > > > > > > Moderators can then use Whimsy to search committers by email
> > > > > address
> > > > > > > > > to find you.
> > > > > > > > >
> > > > > > > > > Also, it looks like the content will appear on lists.a.o 
> > > > > > > > > (requires
> > > > > > > > > login to view):
> > > > > > > > > https://lists.apache.org/list.html?fuzz-test...@commons.apache.org
> > > > > > > > >
> > > > > > > > > There's nothing there at present, so the URL will report an 
> > > > > > > > > error
> > > > > > > > > > Stefan
> > > > > > > > > >
> > > > > > > > > >
> > > > > ---------------------------------------------------------------------
> > > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to