<?xml version="1.0" encoding="utf-8" ?>
<?xml-stylesheet type="text/xsl" href="RSS_xslt_style.asp" version="1.0" ?>
<rss version="2.0" xmlns:WebWizForums="http://syndication.webwiz.co.uk/rss_namespace/">
 <channel>
  <title>Spam Filter ISP Forums : How to allow IP range?</title>
  <link>https://www.logsat.com/spamfilter/forums/</link>
  <description><![CDATA[This is an XML content feed of; Spam Filter ISP Forums : Spam Filter ISP Support : How to allow IP range?]]></description>
  <pubDate>Fri, 06 Mar 2026 15:25:22 +0000</pubDate>
  <lastBuildDate>Mon, 09 Jun 2003 12:52:00 +0000</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Web Wiz Forums 11.04</generator>
  <ttl>360</ttl>
  <WebWizForums:feedURL>https://www.logsat.com/spamfilter/forums/RSS_post_feed.asp?TID=820</WebWizForums:feedURL>
  <image>
   <title><![CDATA[Spam Filter ISP Forums]]></title>
   <url>https://www.logsat.com/spamfilter/forums/forum_images/web_wiz_forums.png</url>
   <link>https://www.logsat.com/spamfilter/forums/</link>
  </image>
  <item>
   <title><![CDATA[How to allow IP range? : George i am not trying to block...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=848&amp;title=how-to-allow-ip-range#848</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=2">Guests</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 09 June 2003 at 12:52pm<br /><br />George i am not trying to block IP ranges, I am looking at a way to&nbsp;allow certain IP ranges to bypass filtering.&nbsp; Right now it appears the only way is to manually enter all the IP's in thet IP range.]]>
   </description>
   <pubDate>Mon, 09 Jun 2003 12:52:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=848&amp;title=how-to-allow-ip-range#848</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : Hmmm,I guess I&amp;#039;m lucky since...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=834&amp;title=how-to-allow-ip-range#834</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=2">Guests</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 07 June 2003 at 1:37am<br /><br /><P>Hmmm,<BR>I guess I'm lucky since I have had my upstream provider block IP address's when needed&nbsp;and ports 135,137 ,139 and 445. I guess it depends on who you know. ;)</P>]]>
   </description>
   <pubDate>Sat, 07 Jun 2003 01:37:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=834&amp;title=how-to-allow-ip-range#834</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : Geroge, Most, if not all backbone...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=833&amp;title=how-to-allow-ip-range#833</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=22">Desperado</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 07 June 2003 at 1:14am<br /><br /><P>Geroge,</P><P>Most, if not all backbone providers have a policy that won't allow them to block SOURCE addresses, only DESTINATION address.&nbsp; This is to prevent possible liability suits.&nbsp; This is even true in the case of a DOS attack.&nbsp; The provider will prevent ANY traffic to the IP or IP's on YOUR network.&nbsp; They also tend to schedule a "release" ot the block.&nbsp; I know of no providers that will actualy block an IP just for port 25.&nbsp; It would be to "costly" for them due to the large number of customers.&nbsp; I think your first choice of putting a block in HIS router is the corect answer and if the address is actually being spoofed, the block may not work anyway.&nbsp; We try to keem ACL's at a minimum on all our routers due to the high overhead.&nbsp; Prefix lists are somewhat easier to manage but still, I thin the block should be at the SMTP server itself.</P><P>The only other answer it to hunt down and seriously wound any and all Spammers and hackers.&nbsp; I get tired of fighting jerks all the time.&nbsp; Thats another discussion.</P><P>Dan S.</P>]]>
   </description>
   <pubDate>Sat, 07 Jun 2003 01:14:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=833&amp;title=how-to-allow-ip-range#833</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : This is something that could be...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=832&amp;title=how-to-allow-ip-range#832</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=2">Guests</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 07 June 2003 at 12:38am<br /><br />This is something that could be done at the router with the access control list. You would have better control. The only drawback is any messages that come from the blocked IP's would not be quarantined since the connection would not be allowed past the router. If you don't have access to the router you would have the have your provider do it for you.]]>
   </description>
   <pubDate>Sat, 07 Jun 2003 00:38:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=832&amp;title=how-to-allow-ip-range#832</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : The domain/IP whitelist is treated...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=828&amp;title=how-to-allow-ip-range#828</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 06 June 2003 at 5:00pm<br /><br /><P>The domain/IP whitelist is treated as a string, so only string-type wildcards are allowed. It is not possible to enter IP ranges. This was by design, as it's rather unusual having to allow specific IPs but not adjacent ones in the same subnet, and designing the functionality as we did optimized our lookups a little bit.</P><P>Roberto F.<BR>LogSat Software</P>]]>
   </description>
   <pubDate>Fri, 06 Jun 2003 17:00:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=828&amp;title=how-to-allow-ip-range#828</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : But I only want a specific range...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=827&amp;title=how-to-allow-ip-range#827</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=2">Guests</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 06 June 2003 at 3:57pm<br /><br /><P>But I only want a specific range of addressing.</P><P>for instance how would I enter a range like xxx.yyy.13.121 to xxx.yyy.13.126?</P><P>&nbsp;</P>]]>
   </description>
   <pubDate>Fri, 06 Jun 2003 15:57:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=827&amp;title=how-to-allow-ip-range#827</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : Alan, A simple DOS-like wildcard...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=822&amp;title=how-to-allow-ip-range#822</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=8">LogSat</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 06 June 2003 at 1:03pm<br /><br /><P>Alan,</P><P>A simple DOS-like wildcard entry will do the job. For ex. to exclude the Class C 1.2.3.1-1.2.3.255 just add:</P><P>1.2.3.*</P><P>so&nbsp;any IP starting with 1.2.3. will trigger a match.</P><P>Roberto Franceschetti<BR>LogSat Software</P>]]>
   </description>
   <pubDate>Fri, 06 Jun 2003 13:03:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=822&amp;title=how-to-allow-ip-range#822</guid>
  </item> 
  <item>
   <title><![CDATA[How to allow IP range? : What format does an IP range or...]]></title>
   <link>https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=820&amp;title=how-to-allow-ip-range#820</link>
   <description>
    <![CDATA[<strong>Author:</strong> <a href="https://www.logsat.com/spamfilter/forums/member_profile.asp?PF=2">Guests</a><br /><strong>Subject:</strong> 820<br /><strong>Posted:</strong> 06 June 2003 at 12:54pm<br /><br /><P>What format does an IP range or subnet need to take in the Excluded IP whitelist?</P><P>I want to included Excluded Domains for certain domains we want unfiltered, but often these domain names are spoofed by spammers, so I would like to exclude them by IP address range instead.</P>]]>
   </description>
   <pubDate>Fri, 06 Jun 2003 12:54:00 +0000</pubDate>
   <guid isPermaLink="true">https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=820&amp;PID=820&amp;title=how-to-allow-ip-range#820</guid>
  </item> 
 </channel>
</rss>