On June 5, 2018 1:22:54 AM UTC, Mark Sapiro wrote:
>On 06/04/2018 05:48 PM, Mark Sapiro wrote:
>> I have applied the attached patch to a couple of installations. We'll
>> see if it helps.
>
>
>I have made this a feature contingent on setting
>
>mm_cfg.BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE = Yes
>
Th
On 06/04/2018 06:40 PM, Adam Goldberg wrote:
> Mark - did you consider generalizing the patch a little bit (so it works with
> Spamhaus, but also with other RBLs)? Spamhaus is one RBL provider, but there
> are a bunch (and most of them work the same way).
Yes, I know, but I wanted something si
On 06/04/2018 05:48 PM, Mark Sapiro wrote:
> I have applied the attached patch to a couple of installations. We'll
> see if it helps.
I have made this a feature contingent on setting
mm_cfg.BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE = Yes
and committed it for the next release.
--
Mark Sapiro
On 06/04/2018 03:27 PM, Jim Popovitch via Mailman-Users wrote:
>
> BTW, most of those IPs are listed in the XBL (https://www.spamhaus.org/
> xbl/). I think I'll work on a patch to block signups from IPs in the
> XBL and domains in the DBL (https://www.spamhaus.org/dbl/)
I just checked against s
My own production server started getting these a few hours ago. I am
currently banning '^support[@+].*' and '^info[@+].*'
These are addresses I've banned within the last 2 hours:
i...@bitbroker.co.uk
i...@btcsolutions.ca
support+aal...@bitflyer.com
support+adqyy...@coindirect.com
support+aog...@c
I can add a few more:
glacierponi+ (etc.)
hanakage777+
icecreamkatana+
nasamok2+
oddjuice11+
and all of these (plus one that probably wouldn't make it past a spam
filter):
i...@bitbroker.co.uk
i...@btcsolutions.ca
oddju...@yahoo.com
s7g...@yahoo.com
supp...@cryptopay.me
> -- Forwar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2018-06-04 at 18:10 -0400, Jim Popovitch wrote:
> On Mon, 2018-06-04 at 14:48 -0700, Russell Clemings wrote:
> > They seem to be changing their tactics pretty much regularly now.
> > Just
> > tailing the subscribe log I see all of these:
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2018-06-04 at 14:48 -0700, Russell Clemings wrote:
> They seem to be changing their tactics pretty much regularly now.
> Just
> tailing the subscribe log I see all of these:
>
> Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
>
They seem to be changing their tactics pretty much regularly now. Just
tailing the subscribe log I see all of these:
Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
supp...@quickbitcoin.co.uk> 159.203.88.55
Jun 04 21:30:06 2018 (17063) LISTNAME1: pending Steve Asher <
supp...@bitcoi
Global remove is easy. The bin/remove_members application as a --fromall option
So something like this:
/bin/remove_members --fromall idtoremove@their.domain
Gretchen Beck
Carnegie Mellon
From: Mailman-Users on
behalf of Parker, Michael D.
Sent: Monday, Ju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 2018-06-04 at 18:47 +, Parker, Michael D. wrote:
> I have mailman 2.x and am specifically interested in knowing how to
> do the following two tasks:
>
>
> 1. List all users with all their mailing lists
list_members -h
>
> 2.
I have mailman 2.x and am specifically interested in knowing how to do the
following two tasks:
1. List all users with all their mailing lists
2. Globally remove a user from all mailing lists
Thanks.
* * *
Michael D. Parker - provisional CISSP
General Atomics - Electro
Thank you friend,
With this, I can configure Fail2Ban to stop the attack.
Block the IP on which you tried to log in without success for more than
three consecutive times.
Regards,
Henrique Fagundes
supo...@aprendendolinux.com
Skype: magnata-br-rj
Linux User: 475399
https://www.aprendendolinu
Mark Dale writes:
> D'oh. My apologies. The error was not from the trailing '$' but
> from not having the quotes in place originally. All is now well
> (with the above).
No big deal; on the contrary, we really appreciate your report
confirming that the regex works as expected for you, after
14 matches
Mail list logo
