<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>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)</div><div><br></div><div>The loss of excluding an enthusiastic Sudo person because of an overbroad ban is disproportionately high for a place emphasizing openness and inclusion.</div><div>I say: Take down the wall!</div><div><br>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.</div><div><br></div><div><br></div><div>My 2 bitcoins.</div><div>(2 is worth a lot these days on the bitcoin market, isn't it?)</div><div><br>sent from <a href="http://eddan.com">eddan.com</a></div><div><br>On Oct 31, 2013, at 2:38 AM, GtwoG PublicOhOne <<a href="mailto:g2g-public01@att.net">g2g-public01@att.net</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<br>
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 <a href="http://yandex.com">yandex.com</a> addresses is presently 1.0 : 0. <br>
<br>
That's a lousy risk/benefit ratio. So IMHO ban the hell out of
<a href="http://yandex.com">yandex.com</a> and any other domain that shows itself to be a
significant source of spam etc. <br>
<br>
"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. <br>
<br>
-G<br>
<br>
<br>
=====<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 13-10-30-Wed 5:10 PM, Steve Berl
wrote:<br>
</div>
<blockquote cite="mid:CAB4gGnd6sdWnRDNUM0nirE1rNxCXBvXi8F=wQL6sCMjRf1uYyQ@mail.gmail.com" type="cite">
<div dir="ltr">You might not want to ban everyone from <a moz-do-not-send="true" href="http://yandex.com">yandex.com</a>.
It is a huge ISP with many millions of customers from all over
Russia, Ukraine, Belarus, and <span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.727272033691406px;line-height:19.190340042114258px">Kazakhstan.
It would be equivalent to banning everyone from <a moz-do-not-send="true" href="http://yahoo.com">yahoo.com</a>
or similar. </span>
<div>
<span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.727272033691406px;line-height:19.190340042114258px"><br>
</span></div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.727272033691406px;line-height:19.190340042114258px">I'd
suggest a bit more specific filtering.</span></div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.727272033691406px;line-height:19.190340042114258px"><br>
</span></div>
<div><span style="color:rgb(0,0,0);font-family:sans-serif;font-size:12.727272033691406px;line-height:19.190340042114258px">-steve</span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Oct 30, 2013 at 11:03 AM,
Yardena Cohen <span dir="ltr"><<a moz-do-not-send="true" href="mailto:yardenack@gmail.com" target="_blank">yardenack@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Oct 30, 2013 at 9:01 AM, Steve Berl
<<a moz-do-not-send="true" href="mailto:steveberl@gmail.com">steveberl@gmail.com</a>>
wrote:<br>
> The spam From: field says "john re <<a moz-do-not-send="true" href="mailto:giovanni-re@yandex.com">giovanni-re@yandex.com</a>>"<br>
> The real emails seem to come from "giovanni_re" <<a moz-do-not-send="true" href="mailto:john_re@fastmail.us">john_re@fastmail.us</a>><br>
<br>
</div>
The spam emails all came from:<br>
<br>
<a moz-do-not-send="true" href="mailto:giovanni-re@yandex.com">giovanni-re@yandex.com</a><br>
<a moz-do-not-send="true" href="mailto:carefullychipped@yandex.com">carefullychipped@yandex.com</a><br>
<br>
Neither of these had posted to the list before, and both
were banned.<br>
A pattern also became clear after yet another new subscriber
showed<br>
up, named:<br>
<br>
<a moz-do-not-send="true" href="mailto:yardena.cohen@yandex.com">yardena.cohen@yandex.com</a><br>
<br>
Creepy! At that point I just decided to ban everything from<br>
<a moz-do-not-send="true" href="http://yandex.com" target="_blank">yandex.com</a>, which seems to have
stopped the problem. There were no<br>
other subscribers from that domain.<br>
<div class="HOEnZb">
<div class="h5">_______________________________________________<br>
sudo-discuss mailing list<br>
<a moz-do-not-send="true" href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
<a moz-do-not-send="true" href="http://lists.sudoroom.org/listinfo/sudo-discuss" target="_blank">http://lists.sudoroom.org/listinfo/sudo-discuss</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
-steve
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
sudo-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sudoroom.org/listinfo/sudo-discuss">http://lists.sudoroom.org/listinfo/sudo-discuss</a>
</pre>
</blockquote>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>sudo-discuss mailing list</span><br><span><a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a></span><br><span><a href="http://lists.sudoroom.org/listinfo/sudo-discuss">http://lists.sudoroom.org/listinfo/sudo-discuss</a></span><br></div></blockquote></body></html>