<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Greylisting Spams with Postfix + Gld</title>
	<atom:link href="http://hostingfu.com/article/greylisting-spams-with-postfix-gld/feed" rel="self" type="application/rss+xml" />
	<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld</link>
	<description>Web Hosting Blog by a Software Developer</description>
	<lastBuildDate>Fri, 02 Jul 2010 10:59:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: kali</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-1732</link>
		<dc:creator>kali</dc:creator>
		<pubDate>Fri, 02 Jul 2010 10:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-1732</guid>
		<description>Why not? GLD just does SQL queries, it doesn&#039;t care the engine underneath. The problem with memory tables is not because of any &quot;non supported&quot; feature, but instead because the table growth in memory could reach the mysql limits, or even worse: the system limit.

I use GLD with InnoDB tables and it works like a charm.</description>
		<content:encoded><![CDATA[<p>Why not? GLD just does SQL queries, it doesn&#8217;t care the engine underneath. The problem with memory tables is not because of any &#8220;non supported&#8221; feature, but instead because the table growth in memory could reach the mysql limits, or even worse: the system limit.</p>
<p>I use GLD with InnoDB tables and it works like a charm.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apollonio</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-1681</link>
		<dc:creator>Apollonio</dc:creator>
		<pubDate>Tue, 08 Jun 2010 08:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-1681</guid>
		<description>About InnoDB,
GLD supports it natively?
I can change MyISAM to InnoDB tables and to expect GLD works again without any other changes in software?

Thanks a lot
Regards</description>
		<content:encoded><![CDATA[<p>About InnoDB,<br />
GLD supports it natively?<br />
I can change MyISAM to InnoDB tables and to expect GLD works again without any other changes in software?</p>
<p>Thanks a lot<br />
Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kali</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-1510</link>
		<dc:creator>kali</dc:creator>
		<pubDate>Tue, 23 Feb 2010 05:23:24 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-1510</guid>
		<description>@Sune et al:

The memory tables suggestion is quite old but still I&#039;m writing this to suggest others not doing memory tables. Why? In my company we are using a simple gld daemon and we handle lots of emails, hence the database is growing up like crazy even with the standard expiration dates. This means my table is right now around 1.5G big, which if stored in memory would make my machine just die. I would suggest using InnoDB instead.

Also, even though I can&#039;t recall now how, you can also make postfix soft-failing if the gld daemon is not running or can&#039;t perform the check within a reasonable period of time, thus avoiding your email service to get down because of an external process to postfix itself. It will of course allow some spam leaks, but like scotty said, it is always better to have little spam rather than loosing ham emails.</description>
		<content:encoded><![CDATA[<p>@Sune et al:</p>
<p>The memory tables suggestion is quite old but still I&#8217;m writing this to suggest others not doing memory tables. Why? In my company we are using a simple gld daemon and we handle lots of emails, hence the database is growing up like crazy even with the standard expiration dates. This means my table is right now around 1.5G big, which if stored in memory would make my machine just die. I would suggest using InnoDB instead.</p>
<p>Also, even though I can&#8217;t recall now how, you can also make postfix soft-failing if the gld daemon is not running or can&#8217;t perform the check within a reasonable period of time, thus avoiding your email service to get down because of an external process to postfix itself. It will of course allow some spam leaks, but like scotty said, it is always better to have little spam rather than loosing ham emails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhijeet Pathak</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-1447</link>
		<dc:creator>Abhijeet Pathak</dc:creator>
		<pubDate>Sun, 31 Jan 2010 10:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-1447</guid>
		<description>@Crzynewbaby Try https://members.nearlyfreespeech.net/ host. VERY cheap for normal sites and professional too.</description>
		<content:encoded><![CDATA[<p>@Crzynewbaby Try <a href="https://members.nearlyfreespeech.net/" rel="nofollow">https://members.nearlyfreespeech.net/</a> host. VERY cheap for normal sites and professional too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crzynewbaby</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-153</link>
		<dc:creator>Crzynewbaby</dc:creator>
		<pubDate>Tue, 14 Jul 2009 23:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-153</guid>
		<description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I have 3 domains/sites hosted on my hosting plan on Bluehost.
Sites are small (~100 visitors/day), no forums ect...&lt;/p&gt;
&lt;p&gt;After a two weeks there will be expiration date and I&#039;m thinking about migrating to other hosting company.
Bluehost is OK until you saw his uptime and it is terrible for me about speed!
They&#039;re veeeery slow!
(I&#039;m from Germany, EU)&lt;/p&gt;
&lt;p&gt;So, recently I found a Host1Plus.com
Any experience with this hoster, anyone?
It looks like much faster and have more servers in variuos world countries.
And at this moment they offer 15%  discount with coupon code - FORUMS&lt;/p&gt;
&lt;p&gt;Should I go there? &lt;/p&gt;
&lt;p&gt;Any opinions will be appreciated. Please share your thoughts.&lt;/p&gt;
&lt;p&gt;Thank You and sorry for my english...&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I have 3 domains/sites hosted on my hosting plan on Bluehost.<br />
Sites are small (~100 visitors/day), no forums ect&#8230;</p>
<p>After a two weeks there will be expiration date and I&#8217;m thinking about migrating to other hosting company.<br />
Bluehost is OK until you saw his uptime and it is terrible for me about speed!<br />
They&#8217;re veeeery slow!<br />
(I&#8217;m from Germany, EU)</p>
<p>So, recently I found a Host1Plus.com<br />
Any experience with this hoster, anyone?<br />
It looks like much faster and have more servers in variuos world countries.<br />
And at this moment they offer 15%  discount with coupon code &#8211; FORUMS</p>
<p>Should I go there? </p>
<p>Any opinions will be appreciated. Please share your thoughts.</p>
<p>Thank You and sorry for my english&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alibabiusta</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-152</link>
		<dc:creator>Alibabiusta</dc:creator>
		<pubDate>Tue, 14 Jul 2009 10:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-152</guid>
		<description>&lt;p&gt;Hello&lt;/p&gt;
&lt;p&gt;I need to know more information about this three hosting companies
Host1Plus
GoDaddy
1&amp;1 Hosting&lt;/p&gt;
&lt;p&gt;I need just your opinions (not your friends or info from other forums)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hello</p>
<p>I need to know more information about this three hosting companies<br />
Host1Plus<br />
GoDaddy<br />
1&amp;1 Hosting</p>
<p>I need just your opinions (not your friends or info from other forums)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland Haeder</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-#comment-150</link>
		<dc:creator>Roland Haeder</dc:creator>
		<pubDate>Sun, 02 Nov 2008 21:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-150</guid>
		<description>&lt;p&gt;Nice idea, even when my reply takes so long. ;-) That would result in fastest graylist-handling. And turning MyISAM/InnoDB to memory isn&#039;t that hard. Sorry for maybe broken english. ;)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Nice idea, even when my reply takes so long. ;-) That would result in fastest graylist-handling. And turning MyISAM/InnoDB to memory isn&#8217;t that hard. Sorry for maybe broken english. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sune Beck</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-151</link>
		<dc:creator>Sune Beck</dc:creator>
		<pubDate>Tue, 10 Jun 2008 17:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-151</guid>
		<description>&lt;p&gt;Why not use the &quot;memory&quot; MySQL table scheme, where rows are stored in memory altogether? This will cause data to be lost if the mysql server is restarted, but isn&#039;t that OK for greylisting?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Why not use the &#8220;memory&#8221; MySQL table scheme, where rows are stored in memory altogether? This will cause data to be lost if the mysql server is restarted, but isn&#8217;t that OK for greylisting?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland Haeder</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-#comment-146</link>
		<dc:creator>Roland Haeder</dc:creator>
		<pubDate>Tue, 06 May 2008 11:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-146</guid>
		<description>&lt;p&gt;Hmmm, my gld version does also support the c/C and k/K option he mentioning. Maybe you had an outdated version? I have 1.7 here.&lt;/p&gt;
&lt;p&gt;Anyway. I have rewritten you shell script to PHP. Maybe some people doesn&#039;t have shell access. I have also rewritten the WHERE statements to let the database provide the unix timestamp and not the script.&lt;/p&gt;
&lt;p&gt;Here are the links:&lt;br /&gt;
http://www.mxchange.org/downloads/greylist-expire.phps&lt;br /&gt;
http://www.mxchange.org/downloads/greylist-expire.zip&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hmmm, my gld version does also support the c/C and k/K option he mentioning. Maybe you had an outdated version? I have 1.7 here.</p>
<p>Anyway. I have rewritten you shell script to PHP. Maybe some people doesn&#8217;t have shell access. I have also rewritten the WHERE statements to let the database provide the unix timestamp and not the script.</p>
<p>Here are the links:<br />
<a href="http://www.mxchange.org/downloads/greylist-expire.phps" rel="nofollow">http://www.mxchange.org/downloads/greylist-expire.phps</a><br />
<a href="http://www.mxchange.org/downloads/greylist-expire.zip" rel="nofollow">http://www.mxchange.org/downloads/greylist-expire.zip</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garrett honeycutt</title>
		<link>http://hostingfu.com/article/greylisting-spams-with-postfix-gld/comment-page-1#comment-149</link>
		<dc:creator>garrett honeycutt</dc:creator>
		<pubDate>Tue, 03 Jul 2007 00:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=43#comment-149</guid>
		<description>&lt;p&gt;GLD uses MyISAM tables by default, which under any kind of load will cause your service to hang and load on your mail servers to jump up. This happens because MyISAM locks the entire table during an insert. You should change the storage type in /usr/share/gld/sql/tables.mysql to InnoDB. InnoDB uses row level locking and will not cause your selects to block while inserts are happening. InnoDB can be memory intensive, so take the time to tune MySQL.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>GLD uses MyISAM tables by default, which under any kind of load will cause your service to hang and load on your mail servers to jump up. This happens because MyISAM locks the entire table during an insert. You should change the storage type in /usr/share/gld/sql/tables.mysql to InnoDB. InnoDB uses row level locking and will not cause your selects to block while inserts are happening. InnoDB can be memory intensive, so take the time to tune MySQL.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
