<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.ryansimpkins.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>RyanSimpkins.com - </title>
 <link>http://www.ryansimpkins.com</link>
 <description></description>
 <language>en</language>
<item>
 <title>Regional SPAM Blocking in Postfix</title>
 <link>http://www.ryansimpkins.com/?q=node/17</link>
 <description>&lt;p&gt;There have been a couple of requests for the cidr file I&#039;m using to block spam in postfix. This only works if you know you&#039;ll likley never recieve mail from outside the US (or you don&#039;t want to). Further, it only works for fairly low traffic mail servers. If you really want to use it for a high traffic site, change the 451s to REJECTs. If you have a lot of users or recieve mail from outside the US often you won&#039;t want to use this approach. Use the personal_cidr file to keep a list of your personal blocks, or to OK clients.&lt;/p&gt;
&lt;/br&gt;
&lt;p&gt;This is the real file I use, so it will be updated over time. You could wget it in a cron every 2-3 months for example. If you have any updates to it - please send them along. Also, this list may be out of date. Any corrections/removals would be very welcome.&lt;/p&gt;
&lt;/br&gt;
&lt;p&gt;&lt;a href=&quot;http://ryansimpkins.com/cidr&quot;&gt;http://ryansimpkins.com/regional_cidr&lt;/a&gt;&lt;/p&gt;
&lt;/br&gt;
&lt;p&gt;In main.cf, add this (I also do these RBLs which really help):
&lt;pre&gt;
smtpd_client_restrictions =
    cidr:/etc/postfix/personal_cidr,
    cidr:/etc/postfix/regional_cidr,
    reject_rbl_client zen.spamhaus.org,
    reject_rbl_client bl.spamcop.net,
    reject_rbl_client dnsbl.njabl.org
&lt;/pre&gt;
&lt;/br&gt;
&lt;p&gt;Don&#039;t forget to run postmap &amp; restart.&lt;/p&gt;
&lt;pre&gt;
postmap /etc/postfix/personal_cidr
postmap /etc/postfix/regional_cidr
/etc/init.d/postfix restart
&lt;/pre&gt;
&lt;p&gt;Incidently, I had to unblock a server in Euorpe last night. Since I sent 451&#039;s back instead of REJECTs, adding the MX to my whitelist was all that I had to do. The mail came through a few minutes later.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.ryansimpkins.com/?q=node/17&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 09 Jul 2009 13:07:50 -0600</pubDate>
 <dc:creator>Ryan Simpkins</dc:creator>
 <guid isPermaLink="false">17 at http://www.ryansimpkins.com</guid>
</item>
<item>
 <title>New Server</title>
 <link>http://www.ryansimpkins.com/?q=node/16</link>
 <description>A new server has been provisioned for ryansimpkins.com. Main upgrades include a better storage array, lower bandwidth costs, and faster gear. Things have been changing rapidly on the backend over the last six months. To keep up with the latest on what I am doing, you might follow me better over at my &lt;a href=&quot;http://www.linkedin.com/in/ryansimpkins&quot; target=&quot;_blank&quot; title=&quot;LinkedIn - Ryan Simpkins&quot;&gt;LinkedIn&lt;/a&gt; profile.</description>
 <pubDate>Wed, 08 Jul 2009 16:13:57 -0600</pubDate>
 <dc:creator>Ryan Simpkins</dc:creator>
 <guid isPermaLink="false">16 at http://www.ryansimpkins.com</guid>
</item>
<item>
 <title>Welcome to RyanSimpkins.com</title>
 <link>http://www.ryansimpkins.com/?q=node/15</link>
 <description>&lt;p&gt;Welcome to ryansimpkins.com. Ryan Simpkins is a Linux computer expert located in Utah. Ryan has been professionally administrering Linux systems for ten years. &lt;i&gt;If you are currently  experiencing a Linux related emergency and need a sys admin NOW - you can call him 24/7/365.&lt;/i&gt;&lt;/p&gt;
&lt;br&gt;
&lt;p&gt;Ryan does not update this main site often. Behind the scenes, however, there are constant changes occuring. Feel free to contact him via e-mail, phone, or IRC chat. He is more than happy to answer any questions at all.&lt;/p&gt;</description>
 <pubDate>Sun, 31 Dec 2006 10:37:50 -0700</pubDate>
 <dc:creator>Ryan Simpkins</dc:creator>
 <guid isPermaLink="false">15 at http://www.ryansimpkins.com</guid>
</item>
<item>
 <title>Quick Topic: DNS Root</title>
 <link>http://www.ryansimpkins.com/?q=node/5</link>
 <description>&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Have you ever performed a &#039;whois&#039; on a domain name to see what name servers are authoritative for it? Did you know that this information is not the information that is used when your domain name is actually resolved to an IP address? The authoritative name servers for a domain are actually stored in the Internet&#039;s DNS root servers. The data you receive from performing a whois on a domain is for convenience only, and may not always be accurate. In this article we will examine the roll of the DNS root servers, and the basics of domain resolution.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.ryansimpkins.com/?q=node/5&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <category domain="http://www.ryansimpkins.com/?q=articles">Articles</category>
 <pubDate>Tue, 09 May 2006 19:52:06 -0600</pubDate>
 <dc:creator>Ryan Simpkins</dc:creator>
 <guid isPermaLink="false">5 at http://www.ryansimpkins.com</guid>
</item>
</channel>
</rss>
