Bug 674278 – Proctors: Request for 7 day mailing list ban for [e-mail]

• Status: RESOLVED FIXED
• Product: Gentoo Infrastructure

[Description Richard Freeman 2019-01-01 20:28:26 UTC]

[e-mail] was issued a warning by proctors, which was ignored.  Requesting a 7-day ban from all Gentoo mailing lists, in particular gentoo-user.

After the end of the ban if there are repeats of this on the same topic in the medium term this will be escalated to a 30 day ban and referred to Comrel.


Copy of warning email for records:

Date: Fri, 28 Dec 2018 13:19:01 -0500
References: <[e-mail]>
In-Reply-To: <[e-mail]>
Message-ID: <[e-mail]>
Subject: Re: [gentoo-user] Why is no one discussing this anymore?
From: Rich Freeman <[e-mail]>
To: [e-mail]
Cc: [e-mail]
Content-Type: text/plain; charset="UTF-8"

On Thu, Dec 27, 2018 at 3:32 PM <[e-mail]> wrote:
>
> Why is no one discussing this anymore.
>

This is off-topic for the gentoo-users mailing list.  Please refrain
from any additional posts to any Gentoo lists on this topic (we do not
generally hold or discuss Linux copyrights), and from copying any
Gentoo list on any broadly-crossposted message, in accordance with the
principle of using the correct forum for your post.

Further posts not in accordance with this warning will result in a ban
from Gentoo communications media.

-- 
Rich

[Comment 1 Alec Warner (RETIRED) 2019-01-01 20:54:02 UTC]

(In reply to Richard Freeman from comment #0)
> [e-mail] was issued a warning by proctors, which was ignored.
> Requesting a 7-day ban from all Gentoo mailing lists, in particular
> gentoo-user.
> 
> After the end of the ban if there are repeats of this on the same topic in
> the medium term this will be escalated to a 30 day ban and referred to
> Comrel.
> 
> 
> Copy of warning email for records:
> 
> Date: Fri, 28 Dec 2018 13:19:01 -0500
> References: <[e-mail]>
> In-Reply-To: <[e-mail]>
> Message-ID:
> <[e-mail]>
> Subject: Re: [gentoo-user] Why is no one discussing this anymore?
> From: Rich Freeman <[e-mail]>
> To: [e-mail]
> Cc: [e-mail]
> Content-Type: text/plain; charset="UTF-8"
> 
> On Thu, Dec 27, 2018 at 3:32 PM <[e-mail]> wrote:
> >
> > Why is no one discussing this anymore.
> >
> 
> This is off-topic for the gentoo-users mailing list.  Please refrain
> from any additional posts to any Gentoo lists on this topic (we do not
> generally hold or discuss Linux copyrights), and from copying any
> Gentoo list on any broadly-crossposted message, in accordance with the
> principle of using the correct forum for your post.
> 
> Further posts not in accordance with this warning will result in a ban
> from Gentoo communications media.
> 
> -- 
> Rich

Done for -user, I don't have documentation handy for *all* lists.

-A

[Comment 2 Richard Freeman 2019-01-08 14:24:07 UTC]

So, this was intended as a 7-day ban, but these were widely cross-posted emails.  Is there any way to tell from logs whether we're still getting rejected list posts from this email address on these threads?  While the intent is for the ban to not be permanent if we're still getting flooded with cross-posts it doesn't make sense to lift the ban and then re-apply it after spamming everybody.

There isn't much on the other list archives that I've checked for other distros, but that could just be the result of bans.  Plus those archives don't all show headers anyway so it is hard to tell from those if they are cross-posted.

[Comment 3 Alec Warner (RETIRED) 2019-01-08 14:48:07 UTC]

(In reply to Richard Freeman from comment #2)
> So, this was intended as a 7-day ban, but these were widely cross-posted
> emails.  Is there any way to tell from logs whether we're still getting
> rejected list posts from this email address on these threads?  While the
> intent is for the ban to not be permanent if we're still getting flooded
> with cross-posts it doesn't make sense to lift the ban and then re-apply it
> after spamming everybody.
> 
> There isn't much on the other list archives that I've checked for other
> distros, but that could just be the result of bans.  Plus those archives
> don't all show headers anyway so it is hard to tell from those if they are
> cross-posted.


This person continues to (attempt) to cross-post.

Jan  6 03:06:11 pigeon postfix/cleanup[25382]: 885E1E0B35: info: header From: [e-mail] from cock.li[2a06:1700:0:b::c0cc]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  6 03:06:11 pigeon postfix/cleanup[25382]: 885E1E0B35: info: header To: [e-mail], [e-mail],? [e-mail], [e-mail] from cock.li[2a06:1700:0:b::c0cc]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  6 03:06:11 pigeon postfix/cleanup[25382]: 885E1E0B35: info: header Cc: [e-mail], [e-mail], [e-mail],? [e-mail], [e-mail] from cock.li[2a06:1700:0:b::c0cc]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  6 03:06:11 pigeon postfix/cleanup[25382]: 885E1E0B35: info: header Subject: (Audio/Video) Linux and GPLv2 license rescission. (previous was? removed by liveleak) from cock.li[2a06:1700:0:b::c0cc]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>

Jan  3 05:33:01 pigeon postfix/cleanup[23975]: 1A9F7E09BF: info: header From: [e-mail] from cock.li[185.100.85.212]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  3 05:33:01 pigeon postfix/cleanup[23975]: 1A9F7E09BF: info: header To: [e-mail], [e-mail],? [e-mail], [e-mail] from cock.li[185.100.85.212]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  3 05:33:01 pigeon postfix/cleanup[23975]: 1A9F7E09BF: info: header Cc: [e-mail], [e-mail], [e-mail] from cock.li[185.100.85.212]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>
Jan  3 05:33:01 pigeon postfix/cleanup[23975]: 1A9F7E09BF: info: header Subject: knifeshack (Linux Property rights) from cock.li[185.100.85.212]; from=<[e-mail]> to=<[e-mail]> proto=ESMTP helo=<cock.li>

The most recent attempt was Jan 8.

-A

[Comment 4 Richard Freeman 2019-01-08 17:32:15 UTC]

Comrel - as both the warning and ban were disregarded and there seems to be little interest in participating as a contributing member of the community, Proctors would like to escalate this for a permanent ban.  For the moment we'll request that infra leaves the ban in place until there is a decision, as otherwise we'll just get more cross-posting and we'll just end up doing another ban.

In general we prefer that proctors bugs remain open (we deal with issues that are already public).  If this will create an issue we can submit a new bug for comrel to work with.  

All decisions to-date have been communicated to the email in the subject.  They are not CC'ed as they do not have a bugzilla account.  This request for escalation has not been communicated - if you wish for us to do so let me know.

[Comment 5 Mikle Kolyada (RETIRED) 2019-01-10 16:52:19 UTC]

ComRel has voted on the issue and permanent ban was agreed upon. 
I can confirm that the user is banned, so nothing should be done by infra.