Hi.
Le jeu. 10 août 2023 à 15:41, Mark Thomas a écrit :
>
> Got them.
>
> The idiot concerned has won themselves a lifetime subscription to the
> deny list for commons-dev and the handful of other ASF lists they are
> subscribed to.
>
> Sorry it took a while to sort this out.
Was it a mistake
I had my pitchfork ready, but I suppose a ban is more civil.
Thanks!
On Thu, Aug 10, 2023 at 9:41 AM Mark Thomas wrote:
> Got them.
>
> The idiot concerned has won themselves a lifetime subscription to the
> deny list for commons-dev and the handful of other ASF lists they are
> subscribed to.
Thank you Mark!
Gary
On Thu, Aug 10, 2023, 9:41 AM Mark Thomas wrote:
> Got them.
>
> The idiot concerned has won themselves a lifetime subscription to the
> deny list for commons-dev and the handful of other ASF lists they are
> subscribed to.
>
> Sorry it took a while to sort this out.
>
>
Got them.
The idiot concerned has won themselves a lifetime subscription to the
deny list for commons-dev and the handful of other ASF lists they are
subscribed to.
Sorry it took a while to sort this out.
Some of you won't yet have received the test message yet due to my mail
server being
Hi all,
In an effort to trace the idiot that set up whatever process is
triggering these messages directly to anyone who posts to the dev list I
will be sending out some test messages later today. Each subscriber to
this list should only receive one test message. Apologies in advance for
the
Le lun. 7 août 2023 à 16:38, Gilles Sadowski a écrit :
>
> Le lun. 7 août 2023 à 10:46, Mark Thomas a écrit :
> >
> > Got the error message. To help me play hunt the subscriber, can anyone
> > provide information on when this behaviour started?
>
> I got one on Saturday at 11:17, in a thread
Le lun. 7 août 2023 à 10:46, Mark Thomas a écrit :
>
> Got the error message. To help me play hunt the subscriber, can anyone
> provide information on when this behaviour started?
I got one on Saturday at 11:17, in a thread with
[commons-math] Three Concerns
as subject line. Content was:
At least 2 days ago on a thread called "[commons-lang] Comments on new
FunctionUtils / nested lambda feature"
Gary
On Mon, Aug 7, 2023, 4:47 AM Mark Thomas wrote:
> Got the error message. To help me play hunt the subscriber, can anyone
> provide information on when this behaviour started?
>
>
Got the error message. To help me play hunt the subscriber, can anyone
provide information on when this behaviour started?
Thanks,
Mark
On 07/08/2023 09:44, Mark Thomas wrote:
".invalid" is something that the ASF adds to addresses.
See
".invalid" is something that the ASF adds to addresses.
See https://infra.apache.org/blog/dmarc_filtering_on_lists_that.html
Hopefully I'll get a similar error message from gitlab in response to
this. I'll see if I can track down which mailing list subscriber is
triggering it.
Mark
On
Ah, right, you're post here... I'm guessing that address is no longer valid
or is one of those ".invalid" addresses services like Proton Mail uses...
Gary
On Sun, Aug 6, 2023, 10:04 AM Gary Gregory wrote:
> I commons dev mailing list gets those.
>
> Gary
>
> On Sun, Aug 6, 2023, 9:29 AM Daniel
I commons dev mailing list gets those.
Gary
On Sun, Aug 6, 2023, 9:29 AM Daniel Watson wrote:
> Does anyone else get gitlab error messages in response to emails sent to
> this list (coming from supp...@cons3rt.com) ? The messages have no
> information as to the cause or resolution. Can't find
Does anyone else get gitlab error messages in response to emails sent to
this list (coming from supp...@cons3rt.com) ? The messages have no
information as to the cause or resolution. Can't find any documentation
about it on mailing list page.
13 matches
Mail list logo
