<?xml version="1.0" encoding="UTF-8" ?>

<rss version="2.0"
  xmlns:ent="http://www.purl.org/NET/ENT/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
  <title>Open Reputation System for Email</title>
  <link>http://ors.blogs4change.org/blog</link>
  <description></description>
  <language>en-us</language>
  <lastBuildDate>Fri, 10 Sep 2010 18:59:32 +1200</lastBuildDate>
  <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
  <generator>Blogware</generator>
  
  <item>
    <dc:creator>April Lorenzen (Outbound Index)</dc:creator>
    <title>Cheap Rides for Internet Abusers &amp; Related Data Points for Email Reputation</title>
    <link>http://ors.blogs4change.org/blog/_archives/2006/2/4/1742908.html</link>
    <guid>http://ors.blogs4change.org/blog/_archives/2006/2/4/1742908.html</guid>
    <pubDate>Sun, 05 Feb 2006 12:02:17 +1300</pubDate>
    <description>&quot;One of the measures of interest is the size of the &quot;free license to abuse&quot; window. Is the window between detectable illicit action and termination long enough to get off a profitable phishing or spamming run? Is the initial screening process left so open that numerous such incidents are going to keep occuring? Ok, so noted in the service provider&#39;s &lt;B&gt;Vetting Effectiveness Profile&lt;/B&gt;.&quot;</description>
    
    <category domain="http://ors.blogs4change.org/blog">Main Page</category>
    
    <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
    
    
    <ent:cloud ent:href="">
    
    <ent:topic ent:id="whitelist" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=whitelist">whitelist</ent:topic>
    
    <ent:topic ent:id="reputation" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=reputation">reputation</ent:topic>
    
    <ent:topic ent:id="nameserver" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=nameserver">nameserver</ent:topic>
    
    <ent:topic ent:id="email" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=email">email</ent:topic>
    
    <ent:topic ent:id="blacklist" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=blacklist">blacklist</ent:topic>
    
    <ent:topic ent:id="antispam" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=antispam">antispam</ent:topic>
    
    <ent:topic ent:id="accreditation" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=accreditation">accreditation</ent:topic>
    
    </ent:cloud>
    
    
    
  </item>
  
  <item>
    <dc:creator>April Lorenzen</dc:creator>
    <title>DCC Reputation</title>
    <link>http://ors.blogs4change.org/blog/_archives/2005/11/9/1362290.html</link>
    <guid>http://ors.blogs4change.org/blog/_archives/2005/11/9/1362290.html</guid>
    <pubDate>Wed, 09 Nov 2005 08:21:30 +1300</pubDate>
    <description>DCC offers an IP based reputation score given as the percentage of
&quot;bulk&quot; mail seen from that IP. The IP reputation scoring is only
available on the proprietary commercial version of DCC, according to&lt;a href=&quot;http://www.rhyolite.com/anti-spam/dcc/reputations.html&quot;&gt; http://www.rhyolite.com/anti-spam/dcc/reputations.html&lt;/a&gt;&lt;br&gt;</description>
    
    <category domain="http://ors.blogs4change.org/blog">Main Page</category>
    
    <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
    
    
    <ent:cloud ent:href="">
    
    <ent:topic ent:id="collector" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=collector">collector</ent:topic>
    
    </ent:cloud>
    
    
    
  </item>
  
  <item>
    <dc:creator>April Lorenzen (Outbound Index)</dc:creator>
    <title>Phishing Site Take Down Research Project</title>
    <link>http://ors.blogs4change.org/blog/_archives/2005/9/17/1233657.html</link>
    <guid>http://ors.blogs4change.org/blog/_archives/2005/9/17/1233657.html</guid>
    <pubDate>Sat, 17 Sep 2005 12:30:32 +1200</pubDate>
    <description>The following is presented to encourage comments and discussion about a
short research project designed to illumiate the existing state ...</description>
    
    <category domain="http://ors.blogs4change.org/blog">Main Page</category>
    
    <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
    
    
    
    
  </item>
  
  <item>
    <dc:creator>April Lorenzen (Outbound Index)</dc:creator>
    <title>Industry Classification Index for Email Sources</title>
    <link>http://ors.blogs4change.org/blog/_archives/2005/8/8/1115296.html</link>
    <guid>http://ors.blogs4change.org/blog/_archives/2005/8/8/1115296.html</guid>
    <pubDate>Mon, 08 Aug 2005 03:40:49 +1200</pubDate>
    <description>&lt;I&gt;Excerpt&lt;/I&gt;
&lt;P&gt;&lt;P&gt;
Classification may be the work of Reputation Collectors, or of Reputation Aggregators, or perhaps ideally an open system that can handle a &quot;source&quot; record. Source is who put this record in, who thinks the classification is X. 
&lt;P&gt;
You can then choose which source(s) you will use/trust. You could selectively drop (ignore) sources you find you don&#39;t want to trust. You could set up your own interpretation / voting:
&lt;P&gt;
 - Source &quot;ReSpam&quot; says this sender is a school
&lt;P&gt;
 - Source &quot;Montgomery Report&quot; says this sender allows anonymous webmail signups and has no outbound rate limiting.
&lt;P&gt;
I am not suggestion that this classification system become a reputation system unto itself, with evidence files or an unlimited number of data points. Rather that it stick to a narrowly defined area of &quot;classifications useful in differentiating characteristics of email sources.&quot; Other reputation collectors could reference the ID or classification numbers in this system if they wished to, and attach other data points within their own databases.</description>
    
    <category domain="http://ors.blogs4change.org/blog">Main Page</category>
    
    <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
    
    <category domain="http://ors.blogs4change.org/blog/Aggregators">Aggregators</category>
    
    
    <ent:cloud ent:href="">
    
    <ent:topic ent:id="aggregator" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=aggregator">aggregator</ent:topic>
    
    <ent:topic ent:id="classification" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=classification">classification</ent:topic>
    
    <ent:topic ent:id="collector" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=collector">collector</ent:topic>
    
    <ent:topic ent:id="SIC" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=SIC">SIC</ent:topic>
    
    <ent:topic ent:id="industry" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=industry">industry</ent:topic>
    
    <ent:topic ent:id="spam" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=spam">spam</ent:topic>
    
    <ent:topic ent:id="services" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=services">services</ent:topic>
    
    <ent:topic ent:id="repuation" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=repuation">repuation</ent:topic>
    
    <ent:topic ent:id="email" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=email">email</ent:topic>
    
    <ent:topic ent:id="antispam" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=antispam">antispam</ent:topic>
    
    </ent:cloud>
    
    
    
  </item>
  
  <item>
    <dc:creator>April Lorenzen</dc:creator>
    <title>Reactive vs Predictive Email Reputation Collectors</title>
    <link>http://ors.blogs4change.org/blog/_archives/2005/8/1/1094522.html</link>
    <guid>http://ors.blogs4change.org/blog/_archives/2005/8/1/1094522.html</guid>
    <pubDate>Mon, 01 Aug 2005 07:00:18 +1200</pubDate>
    <description>My favored predictive collectors focus on factors that can be measured before the message is accepted, even before the first spam from a new run is accepted. I also like predictive collectors that focus on positive or &quot;good&quot; characteristics rather than characteristics of &quot;bad&quot; senders.</description>
    
    <category domain="http://ors.blogs4change.org/blog">Main Page</category>
    
    <category domain="http://ors.blogs4change.org/blog/ReputationCollectors">Reputation Collectors</category>
    
    
    <ent:cloud ent:href="">
    
    <ent:topic ent:id="spam" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=spam">spam</ent:topic>
    
    <ent:topic ent:id="services" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=services">services</ent:topic>
    
    <ent:topic ent:id="repuation" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=repuation">repuation</ent:topic>
    
    <ent:topic ent:id="email" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=email">email</ent:topic>
    
    <ent:topic ent:id="antispam" ent:href="http://ors.blogs4change.org/blog/cmd=search_keyword/k=antispam">antispam</ent:topic>
    
    </ent:cloud>
    
    
    
  </item>
  
</channel>
</rss>
