<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DevSyS Community &#187; Develop</title>
	<atom:link href="http://www.techfusion.it/category/develop/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techfusion.it</link>
	<description>..:: Natural LifeCycle Brainstorming ::..</description>
	<lastBuildDate>Wed, 18 Jan 2012 11:04:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>[QMAIL] qmail-scanner-queue.pl return-path anonymizer</title>
		<link>http://www.techfusion.it/2007/12/20/qmail-scanner-qmail-scanner-queuepl-return-path-anonymizer/</link>
		<comments>http://www.techfusion.it/2007/12/20/qmail-scanner-qmail-scanner-queuepl-return-path-anonymizer/#comments</comments>
		<pubDate>Thu, 20 Dec 2007 15:02:36 +0000</pubDate>
		<dc:creator>Parantido</dc:creator>
				<category><![CDATA[Develop]]></category>
		<category><![CDATA[Sys Admin]]></category>

		<guid isPermaLink="false">http://blog.techfusion.it/2007/12/20/qmail-scanner-qmail-scanner-queuepl-return-path-anonymizer/</guid>
		<description><![CDATA[The following patch is able to anonymize the entire mails routing path. Reason about this feature is the following: Customers privacy preservation Nullify RBL (Source Path) SpamCheck for RBListed ISP connection (fastweb.net, tim.it, etc etc). In the diff patch attached file you can find some commented code block. You can store an original email copy, [...]]]></description>
		<wfw:commentRss>http://www.techfusion.it/2007/12/20/qmail-scanner-qmail-scanner-queuepl-return-path-anonymizer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[PERL] &#8220;How to&#8221; Develop a Dynamic Plugin Engine</title>
		<link>http://www.techfusion.it/2007/12/18/perl-how-to-develop-a-dynamic-plugin-engine/</link>
		<comments>http://www.techfusion.it/2007/12/18/perl-how-to-develop-a-dynamic-plugin-engine/#comments</comments>
		<pubDate>Tue, 18 Dec 2007 10:08:53 +0000</pubDate>
		<dc:creator>Parantido</dc:creator>
				<category><![CDATA[Develop]]></category>

		<guid isPermaLink="false">http://blog.techfusion.it/2007/12/18/perl-how-to-develop-a-dynamic-plugin-engine/</guid>
		<description><![CDATA[:: INTRODUCTION The main problem in my projects was a dynamically features extension through new implementations and new technology fully-fit across the time (software maintenance). For this problem i&#8217;m looking for a method to develop a core engine and to develop features through hooked attached plugins. I decided to write this tutorial to share my [...]]]></description>
		<wfw:commentRss>http://www.techfusion.it/2007/12/18/perl-how-to-develop-a-dynamic-plugin-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

