Re: Recent Spam problem
On 2017-08-13, J. Clarke wrote: > In article , > skybuck2...@hotmail.com says... >> >> I see two solutions: > It would be really nice if someone could convince radical Islam that > spammers are offensive to Mohammed. After a few of them got hunted down > and blown up, the rest might take the hint. It would be really nice if someone could convice people to stopped replying to spam posted from googlegroups. That way people who've taken the common-sense approach and plonked all postings from google groups wouldn't have to see them. -- Grant -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
In article , skybuck2...@hotmail.com says... > > I see two solutions: > > 1. We build new architecture or adept current one so it's more like a > blockchain, have to calculate some hash before being able to post and upload > and such. > > or > > 2. We counter-attack by installing a special tool, so we all denial of > service attack the source of the message, I am not sure if the source is > genuine information, what you make of it: > > NNTP-Posting-Host: 39.52.70.224 > > > Now the first solution would require a lot of work. > > The second solution would be easy to do. > > My question to you is: > > What solution do you pick of any ? =D It would be really nice if someone could convince radical Islam that spammers are offensive to Mohammed. After a few of them got hunted down and blown up, the rest might take the hint. -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
Am Dienstag, 25. Juli 2017 07:13:51 UTC+2 schrieb Rustom Mody:
> Of late there has been an explosion of spam
> Thought it was only a google-groups (USENET?) issue and would be barred from
> the mailing list.
>
> But then find its there in the mailing list archives as well
> Typical example:
> https://mail.python.org/pipermail/python-list/2017-July/724085.html
>
> What gives??
>
> On a different note this problem seems to be peculiar to comp.lang.python
> via google-groups and is absent on ½ dozen other google groups I see.
>
> Since spammers are unlikely to be choosy about whom they spam:
> Tentative conclusion: Something about the USENET-ML gateway is more leaky
> out here than elsewhere
What i do is to "install" the bookmarklet "Jquerify" from
https://mreidsma.github.io/bookmarklets/jquerify.html, open the developer tools
(i use Google Chrome), go to the console and paste the following javascript:
$('tr > td > div > div > div > div > div > div > div:contains("Case Solution"),
div:contains("Test Banks")').closest("tr").hide(); $('tr > td > div > div > div
> div > div > div > a').each(function(){if($(this).text().length > 100)
$(this).closest("tr").hide()});
This hides all the posts from "Case Solution" and "Test Banks" and all posts
with a subject length > 100. Rerun the code to hide more, not elegant but
helpful (at least for me :) )
best regards,
Gerd
--
https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
Yes, it's more "leaky," though that's not quite the term I'd use. Instead, I'd say there are fewer checks. On the mailing list side of things, you have all the Postfix bells and whistles, which stop a ton of crap, much of it before the message is officially entered into the mail.python.org system. Behind that is a SpamBayes instance to pick up any loose ends. The Usenet gateway feeds into the system behind everything except the SpamBayes instance. It gets only sporadic attention from me. If I'm not paying attention, stuff which starts to "leak" through doesn't get trained as spam so it can help minimize the chances that later versions of the same crap get through. One thing which never got produced was an easy way for a list moderator to say, "Hey, this got through and it's spam." Sorting through "unsure" messages and retraining automatically using some Mailman/SpamBayes conduit would be a nice addition to the overall system. If you wanted to write software, that's where I'd focus my efforts. Skip -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On Tue, 25 Jul 2017 21:44:22 +, Grant Edwards wrote: > On 2017-07-25, Wildman via Python-list wrote: > >> The posts are being made through Google Groups. Forwarding >> the posts with headers to groups-ab...@google.com might help. > > I never has in the past. I (and many others) have for years and years > been plonking all posts made through Google Groups. Trust me, you'll > not miss out on anything worthwile. :) > >> I have sent a couple but if everyone here did it maybe Google will >> pay attention and do something. > > They won't. > > Just configure your .score file (or bogofilter or spamassassin or > whatever) to throw out all posts that have a Message-ID: header field > that ends in 'googlegroups.com'. That, grashopper, is the path to > serenity. In the past I never used a 'kill file' so I didn't consider it. However, I took your advice and created the score file and I will say the path to serenity is sweet. Thank you. -- GNU/Linux user #557453 "SERENITY NOW! SERENITY NOW!" -Frank Costanza -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
breamore...@gmail.com wrote: Hence why I asked a couple of weeks back why we don't just bin the existing group and start afresh with a new, properly moderated group. Someone would need to volunteer to be the moderator. Also, moderation is something of a consenting-adults thing on usenet. It's not hard for a sufficently knowledgeable person to bypass the moderation. (I'm told there's a security-related usenet group that takes advantage of this. It's a moderated group with no moderator; if you know enough to fake the approval, you're considered entitled to post. :-) -- Greg -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On Wednesday, July 26, 2017 at 8:29:07 AM UTC+1, Tim Golden wrote: > On 25/07/2017 06:13, Rustom Mody wrote: > > Of late there has been an explosion of spam > > Thought it was only a google-groups (USENET?) issue and would be barred > > from the mailing list. > > > > But then find its there in the mailing list archives as well > > Typical example: > > https://mail.python.org/pipermail/python-list/2017-July/724085.html > > > > What gives?? > > I almost never look at the GG mirror (or Usenet) so it wasn't until the > post which started this thread that I realised just how much spam is > being thrown at the newsgroup. > Hence why I asked a couple of weeks back why we don't just bin the existing group and start afresh with a new, properly moderated group. I suggest a really innovative name like python-users :) Kindest regards. Mark Lawrence. -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On 25/07/2017 06:13, Rustom Mody wrote: Of late there has been an explosion of spam Thought it was only a google-groups (USENET?) issue and would be barred from the mailing list. But then find its there in the mailing list archives as well Typical example: https://mail.python.org/pipermail/python-list/2017-July/724085.html What gives?? Well, just for clarification: the spam measures on the list are at least partly manual. In this case, the spammer started to use a different address from the one we were trapping so it took until one of us (me, in this case) spotted the incoming spam before we were able to block it. I almost never look at the GG mirror (or Usenet) so it wasn't until the post which started this thread that I realised just how much spam is being thrown at the newsgroup. In case it wasn't clear to anyone: GG is actually a gateway to comp.lang.python which presents itself as a mailing list, while gmane (while it's still running) is a gateway to the python-list which presents itself as a newsgroup. TJG -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On 2017-07-25 10:03, alister wrote: On Tue, 25 Jul 2017 17:29:56 +1000, Chris Angelico wrote: On Tue, Jul 25, 2017 at 4:50 PM, wrote: I see two solutions: 1. We build new architecture or adept current one so it's more like a blockchain, have to calculate some hash before being able to post and upload and such. 2. We counter-attack by installing a special tool, so we all denial of service attack the source of the message, I am not sure if the source is genuine information, what you make of it: There are bad people in the world. I know! Let's all go and drop nuclear bombs on them. That'll fix the problem! OR... you could try just filtering it all out, and not stooping to their level. i say nuke em/ otherwise my /dev/null is going to need expanding ;-) I just got a new nulldev from Data General about a week back: username@hostname$ ll /dev/null crw-rw-rw- 1 root root 1, 3 Jul 16 15:22 /dev/null username@hostname$ Its performance is awesome, and it comes with a powerful GUI for configuring and customizing. -- Michael F. Stemper Indians scattered on dawn's highway bleeding; Ghosts crowd the young child's fragile eggshell mind. -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On 2017-07-25, Wildman via Python-list wrote: > The posts are being made through Google Groups. Forwarding > the posts with headers to groups-ab...@google.com might help. I never has in the past. I (and many others) have for years and years been plonking all posts made through Google Groups. Trust me, you'll not miss out on anything worthwile. :) > I have sent a couple but if everyone here did it maybe Google will > pay attention and do something. They won't. Just configure your .score file (or bogofilter or spamassassin or whatever) to throw out all posts that have a Message-ID: header field that ends in 'googlegroups.com'. That, grashopper, is the path to serenity. -- Grant Edwards grant.b.edwardsYow! I like your SNOOPY at POSTER!! gmail.com -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On Mon, 24 Jul 2017 23:01:43 -0700, Paul Rubin wrote: > Rustom Mody writes: >> Since spammers are unlikely to be choosy about whom they spam: >> Tentative conclusion: Something about the USENET-ML gateway is more leaky >> out here than elsewhere > > It could be a sort-of DOS attack by some disgruntled idiot. I wonder if > the email address in those spam posts actually works. Then there's the > weird Italian rants. No idea about those. The posts are being made through Google Groups. Forwarding the posts with headers to groups-ab...@google.com might help. I have sent a couple but if everyone here did it maybe Google will pay attention and do something. The same goes for our Italian "friend". -- GNU/Linux user #557453 The cow died so I don't need your bull! -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On Tue, 25 Jul 2017 17:29:56 +1000, Chris Angelico wrote: > On Tue, Jul 25, 2017 at 4:50 PM, wrote: >> I see two solutions: >> >> 1. We build new architecture or adept current one so it's more like a >> blockchain, have to calculate some hash before being able to post and >> upload and such. >> >> or >> >> 2. We counter-attack by installing a special tool, so we all denial of >> service attack the source of the message, I am not sure if the source >> is genuine information, what you make of it: >> >> NNTP-Posting-Host: 39.52.70.224 >> >> >> Now the first solution would require a lot of work. >> >> The second solution would be easy to do. >> >> My question to you is: >> >> What solution do you pick of any ? =D > > There are bad people in the world. I know! Let's all go and drop nuclear > bombs on them. That'll fix the problem! > > OR... you could try just filtering it all out, and not stooping to their > level. > > ChrisA i say nuke em/ otherwise my /dev/null is going to need expanding ;-) -- "To YOU I'm an atheist; to God, I'm the Loyal Opposition." -- Woody Allen -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
On Tue, Jul 25, 2017 at 4:50 PM, wrote: > I see two solutions: > > 1. We build new architecture or adept current one so it's more like a > blockchain, have to calculate some hash before being able to post and upload > and such. > > or > > 2. We counter-attack by installing a special tool, so we all denial of > service attack the source of the message, I am not sure if the source is > genuine information, what you make of it: > > NNTP-Posting-Host: 39.52.70.224 > > > Now the first solution would require a lot of work. > > The second solution would be easy to do. > > My question to you is: > > What solution do you pick of any ? =D There are bad people in the world. I know! Let's all go and drop nuclear bombs on them. That'll fix the problem! OR... you could try just filtering it all out, and not stooping to their level. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
I see two solutions: 1. We build new architecture or adept current one so it's more like a blockchain, have to calculate some hash before being able to post and upload and such. or 2. We counter-attack by installing a special tool, so we all denial of service attack the source of the message, I am not sure if the source is genuine information, what you make of it: NNTP-Posting-Host: 39.52.70.224 Now the first solution would require a lot of work. The second solution would be easy to do. My question to you is: What solution do you pick of any ? =D -- https://mail.python.org/mailman/listinfo/python-list
Re: Recent Spam problem
Rustom Mody writes: > Since spammers are unlikely to be choosy about whom they spam: > Tentative conclusion: Something about the USENET-ML gateway is more leaky > out here than elsewhere It could be a sort-of DOS attack by some disgruntled idiot. I wonder if the email address in those spam posts actually works. Then there's the weird Italian rants. No idea about those. -- https://mail.python.org/mailman/listinfo/python-list
Recent Spam problem
Of late there has been an explosion of spam Thought it was only a google-groups (USENET?) issue and would be barred from the mailing list. But then find its there in the mailing list archives as well Typical example: https://mail.python.org/pipermail/python-list/2017-July/724085.html What gives?? On a different note this problem seems to be peculiar to comp.lang.python via google-groups and is absent on ½ dozen other google groups I see. Since spammers are unlikely to be choosy about whom they spam: Tentative conclusion: Something about the USENET-ML gateway is more leaky out here than elsewhere -- https://mail.python.org/mailman/listinfo/python-list
