<?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: Quick Mailserver Update</title>
	<atom:link href="http://www.deltanova.co.uk/563/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deltanova.co.uk/563/</link>
	<description>Creative thoughts from a corrupted mind.</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:10:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Quantum</title>
		<link>http://www.deltanova.co.uk/563/comment-page-1/#comment-87439</link>
		<dc:creator>Quantum</dc:creator>
		<pubDate>Wed, 10 Jun 2009 21:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.deltanova.co.uk/?p=563#comment-87439</guid>
		<description>Success. I think at long last I have implemented the last component of my mailserver. The antivirus scanning and spam filtering has possibly been the most difficult bit of the entire project. Whilst the rest of the setup was quite lengthy and involved alot of options there was a wealth of documetation tom refer to. The last stage involved some non-standard packages combined in a non-standard way. The available documentation and examples of exisiting setups was next to impossible to find. In the end I resorted to reading the documentaion for the individual packages, not an easy task to read 40 pages of vague techniucal explanations which assumed you already fully understood what you were attempting to configure.

All that is left to do now is test, tweak a little bit more, train up the spam filter &amp; make sure the log files are reporting things as they should. Documenting this last stage of the project should be alot easier, the integration into the established setup is probably no more than 10 lines of code across a few config files. The setup I am using was decided upon from the outset to be used by a single user,as a home system  or for a small low traffic user group. I feel it has met it&#039;s goals very well. 

There are some areas which can be built upon. The current setup uses system user accounts. It should be possible to expand to support virtual users. The integration of dspam can be done in a different way and should allow the mailserver to scale better. 

Time for me to have a break before I get back to the documentation. Hopefully more posts will follow soon regarding the implementation.</description>
		<content:encoded><![CDATA[<p>Success. I think at long last I have implemented the last component of my mailserver. The antivirus scanning and spam filtering has possibly been the most difficult bit of the entire project. Whilst the rest of the setup was quite lengthy and involved alot of options there was a wealth of documetation tom refer to. The last stage involved some non-standard packages combined in a non-standard way. The available documentation and examples of exisiting setups was next to impossible to find. In the end I resorted to reading the documentaion for the individual packages, not an easy task to read 40 pages of vague techniucal explanations which assumed you already fully understood what you were attempting to configure.</p>
<p>All that is left to do now is test, tweak a little bit more, train up the spam filter &#038; make sure the log files are reporting things as they should. Documenting this last stage of the project should be alot easier, the integration into the established setup is probably no more than 10 lines of code across a few config files. The setup I am using was decided upon from the outset to be used by a single user,as a home system  or for a small low traffic user group. I feel it has met it&#8217;s goals very well. </p>
<p>There are some areas which can be built upon. The current setup uses system user accounts. It should be possible to expand to support virtual users. The integration of dspam can be done in a different way and should allow the mailserver to scale better. </p>
<p>Time for me to have a break before I get back to the documentation. Hopefully more posts will follow soon regarding the implementation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

