I strongly agree with Eddan. It makes no sense to ban a non-negligible
portion of the worlds population because of 2 known bad email addresses.
Why not try just banning those 2 and see how it goes.
Steve
On Thursday, October 31, 2013, Eddan Katz wrote:
I disagree with this risk/benefit analysis below. The
risk of excluding
some Russian programmers (or émigrés) due to this policy is not 0. (Might
want to scan our current membership)
The loss of excluding an enthusiastic Sudo person because of an overbroad
ban is disproportionately high for a place emphasizing openness and
inclusion.
I say: Take down the wall!
As a policy, I think it only makes sense to ban an address after it has
been demonstrated that it has abused its privilege. Until then, I think all
email addresses should be considered innocent until proven guilty.
My 2 bitcoins.
(2 is worth a lot these days on the bitcoin market, isn't it?)
sent from
eddan.com
On Oct 31, 2013, at 2:38 AM, GtwoG PublicOhOne
<g2g-public01@att.net<javascript:_e({}, 'cvml',
'g2g-public01(a)att.net');>>
wrote:
The probability of anyone in Russia, Ukraine, Belarus, or Kazakhstan,
becoming an SR member, asymptotically approaches zero. The probability of
spams, scams, spyware, malware, etc. coming from those locations, is high.
The ratio of spam to real correspondence from
yandex.com addresses is
presently 1.0 : 0.
That's a lousy risk/benefit ratio. So IMHO ban the hell out of yandex.comand any
other domain that shows itself to be a significant source of spam
etc.
"Open" as in "accepting" does not equal "open" as in
"unprotected." We
are not under any obligation to have no collective immune system. Species
without immune defenses don't even last long enough to become footnotes in
archaeology.
-G
=====
On 13-10-30-Wed 5:10 PM, Steve Berl wrote:
You might not want to ban everyone from
yandex.com. It is a huge ISP with
many millions of customers from all over Russia, Ukraine, Belarus, and Kazakhstan.
It would be equivalent to banning everyone from
yahoo.com or similar.
I'd suggest a bit more specific filtering.
-steve
On Wed, Oct 30, 2013 at 11:03 AM, Yardena Cohen
<yardenack@gmail.com<javascript:_e({}, 'cvml',
'yardenack(a)gmail.com');>
wrote:
On Wed, Oct 30, 2013 at 9:01 AM, Steve Berl
<steveberl@gmail.com<javascript:_e({}, 'cvml',
'steveberl(a)gmail.com');>>
wrote:
The spam From: field says "john re
<giovanni-re@yandex.com<javascript:_e({}, 'cvml',
'giovanni-re(a)yandex.com');>
"
The real emails seem to come from "giovanni_re"
<john_re@fastmail.us<javascript:_e({}, 'cvml',
'john_re(a)fastmail.us');>
The spam emails all came from:
giovanni-re(a)yandex.com <javascript:_e({}, 'cvml',
'giovanni-re(a)yandex.com');>
carefullychipped(a)yandex.com <javascript:_e({}, 'cvml',
'carefullychipped(a)yandex.com');>
Neither of these had posted to the list before, and both were banned.
A pattern also became clear after yet another new subscriber showed
up, named:
yardena.cohen(a)yandex.com <javascript:_e({}, 'cvml',
'yardena.cohen(a)yandex.com');>
Creepy! At that point I just decided to ban everything from
yandex.com, which seems to have stopped the problem. There were no
other subscribers from that domain.
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org <javascript:_e({}, 'cvml',
'sudo-discuss(a)lists.sudoroom.org');>
http://lists.sudoroom.org/listinfo/sudo-discuss
--
-steve
_______________________________________________
sudo-discuss mailing listsudo-discuss(a)lists.sudoroom.org <javascript:_e({},
'cvml',
'sudo-discuss@lists.sudoroom.org');>http://lists.sudoroom.org/listinfo/sudo-discuss
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org <javascript:_e({}, 'cvml',
'sudo-discuss(a)lists.sudoroom.org');>
http://lists.sudoroom.org/listinfo/sudo-discuss