<?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>PostfixMail.com &#187; Postfix Mail Server</title>
	<atom:link href="http://postfixmail.com/blog/index.php/tag/postfix-mail-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://postfixmail.com/blog</link>
	<description>Postfix Mail Server Training and Consulting</description>
	<lastBuildDate>Sat, 10 Jul 2010 13:18:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Compiling SASL Packages with Postfix</title>
		<link>http://postfixmail.com/blog/index.php/compiling-sasl-packages-with-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/compiling-sasl-packages-with-postfix/#comments</comments>
		<pubDate>Sat, 24 Oct 2009 10:45:15 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Compile Postfix]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix from source]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[SASL]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=813</guid>
		<description><![CDATA[The environmental variables in CCARGS for instance, provide the options that Postfix needs. AUXLIBS – If you build support for any additional applications you may need to tell the linker where to look for the additional libraries for those programs.  The standard location for system libraries is /usr/lib.  If you want the linker to look [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/compiling-sasl-packages-with-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Do You Use Postfix?</title>
		<link>http://postfixmail.com/blog/index.php/why-do-you-use-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/why-do-you-use-postfix/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 23:26:56 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Postfix Configuration]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[Postfix Server]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=786</guid>
		<description><![CDATA[Recently we asked administrators why they used Postfix Mail Server.  Here are some of the responses: &#8220;Being able to manage users and pretty much all mail aspects from a MySQL table&#8221; &#8220;Security.  Postfix is rock solid and I do not have to worry about the security of the system once it is set up correctly&#8221; [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/why-do-you-use-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postfix: Whitelists and Blacklists</title>
		<link>http://postfixmail.com/blog/index.php/postfix-whitelists-and-blacklists/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-whitelists-and-blacklists/#comments</comments>
		<pubDate>Mon, 11 May 2009 13:47:41 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Spam Control]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Blacklist]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[Postfix whitelist]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=654</guid>
		<description><![CDATA[Whitelists / Blacklists You can set up whitelists and blacklists to modify the settings to make sure certain email addresses never get blocked or always get blocked. Prevent any Spam Checking In order to create a situation where you have no Spam checking you can use the bypass option.  These options are added to amavisd.conf [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-whitelists-and-blacklists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>tcp_wrappers Problems</title>
		<link>http://postfixmail.com/blog/index.php/tcp_wrappers-problems/</link>
		<comments>http://postfixmail.com/blog/index.php/tcp_wrappers-problems/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 12:28:15 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[Postfix Training]]></category>
		<category><![CDATA[tcp_wrappers]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=326</guid>
		<description><![CDATA[Mail Does Not Send A common problem is finding that mail is not sending correctly and that the /var/spool/clientqueue is filling up with files. This directory can actually shut down your server if you do not have a separate directory for /var when this happen. The speed at which this happens is determined by the [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/tcp_wrappers-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dropping X-Mailers in Header Checks</title>
		<link>http://postfixmail.com/blog/index.php/dropping-x-mailers-in-header-checks/</link>
		<comments>http://postfixmail.com/blog/index.php/dropping-x-mailers-in-header-checks/#comments</comments>
		<pubDate>Fri, 14 Nov 2008 14:14:09 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[header checks]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[posttix filters]]></category>
		<category><![CDATA[x-mailers]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=303</guid>
		<description><![CDATA[Header checks with Postfix can be used to deal with unwanted mail before your server wastes time with it.  Created the file /etc/postfix/header_checks and then add this line in your main.cf. header_checks = pcre:/etc/postfix/header_checks The format line for each header check follows this pattern: /^HEADER:.*content_for_review/   ACTION The HEADER that you usually will act on is [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/dropping-x-mailers-in-header-checks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create Users in Cyrus-IMAP</title>
		<link>http://postfixmail.com/blog/index.php/create-users-in-cyrus-imap/</link>
		<comments>http://postfixmail.com/blog/index.php/create-users-in-cyrus-imap/#comments</comments>
		<pubDate>Sat, 01 Nov 2008 23:37:10 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Cyrus-Imap]]></category>
		<category><![CDATA[cyrus-imap users]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[Postfix Training]]></category>
		<category><![CDATA[yrus users]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=279</guid>
		<description><![CDATA[Create Users Create the users on the system. Create users with the false option so they cannot log into the server. This is an added security feature. A. Create the User useradd sue -s /bin/false passwd sue A common mistake is to forget to provide passwords for these users. B. Use saslpasswd2 to create a [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/create-users-in-cyrus-imap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introduction to TLS and SSL</title>
		<link>http://postfixmail.com/blog/index.php/introduction-to-tls-and-ssl/</link>
		<comments>http://postfixmail.com/blog/index.php/introduction-to-tls-and-ssl/#comments</comments>
		<pubDate>Tue, 21 Oct 2008 10:56:38 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Dovecot]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[SSL]]></category>
		<category><![CDATA[TLS]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=260</guid>
		<description><![CDATA[TLS or Transport Layer Security is a protocol that is encrypted and is a close relative of SSL.  Actually TLS has developed from SSL and has backward compatibility.  SSL, Secure Sockets Layer, is a protocol or language that is used to encrypt communication between clients and servers. This type of communication is necessary when transporting [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/introduction-to-tls-and-ssl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing Dovecot on Postfix</title>
		<link>http://postfixmail.com/blog/index.php/testing-dovecot-on-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/testing-dovecot-on-postfix/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 10:42:40 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Dovecot]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=258</guid>
		<description><![CDATA[One thing that you can do is run this command to verify it is listening on the correct port numbers: netstat -aunt This should show that Dovecot is listening on ports 143 and 110 for IMAP and POP3. Check if Dovecot is Listening Another test is to connect to Dovecot using telnet on port 143.  [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/testing-dovecot-on-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tools Needed for Building Postfix</title>
		<link>http://postfixmail.com/blog/index.php/tools-needed-for-building-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/tools-needed-for-building-postfix/#comments</comments>
		<pubDate>Sat, 11 Oct 2008 13:56:48 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Compile Postfix]]></category>
		<category><![CDATA[postfix build]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=243</guid>
		<description><![CDATA[Postfix is built in C so you will be compiling C code.  Usually the options that you want to create for a project are contained in a Makefile.  The make utility creates this Makefile which is used to determine dependencies, any requirements needed or changes you want to create like adding programs or locations of [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/tools-needed-for-building-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AppArmor Templates for Postfix</title>
		<link>http://postfixmail.com/blog/index.php/apparmor-templates-for-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/apparmor-templates-for-postfix/#comments</comments>
		<pubDate>Fri, 10 Oct 2008 01:13:45 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[apparmor]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[postfix security]]></category>
		<category><![CDATA[Ubuntu postfix]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=240</guid>
		<description><![CDATA[Using Pre-Built Templates Add the pre-built templates for Postfix. sudo apt-get install apparmor-profiles This will load many pre-built templates that you can use. cd /usr/share/doc/apparmor-profiles/extras Now copy all of the Postfix related profiles into /etc/apparmor.d/. sudo cp usr.sbin.post* /etc/apparmor.d/ sudo cp usr.lib.post* /etc/apparmor.d/ Restart your the AppArmor daemon. sudo /etc/init.d/apparmor restart Now check the number [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/apparmor-templates-for-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting Postfix with AppArmor</title>
		<link>http://postfixmail.com/blog/index.php/protecting-postfix-with-apparmor/</link>
		<comments>http://postfixmail.com/blog/index.php/protecting-postfix-with-apparmor/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 10:21:08 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[apparmor on postfix]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[postfix Ubuntu]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=237</guid>
		<description><![CDATA[If you are using Postfix on a server that supports AppArmor like Suse, Debian, Ubuntu, etc., you can use AppArmor to protect Postfix.   AppArmor attempts to protect processes on the server or desktop from security threats.  AppArmor enforces limits on what processes can access on the system.  It attempts to restrict processes to those resources [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/protecting-postfix-with-apparmor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postfix Mail Server on OpenVZ: Step 1 &#8211; Create the Host</title>
		<link>http://postfixmail.com/blog/index.php/postfix-mail-server-on-openvz-step-1-create-the-host/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-mail-server-on-openvz-step-1-create-the-host/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 12:42:23 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Virtual Server]]></category>
		<category><![CDATA[openvz]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=223</guid>
		<description><![CDATA[Virtualized Postfix Mail Server This section will show you how to virtualize a mail server with OpenVZ.  There are several advantages to virtualizing your mail server.  One is the ability to backup the entire mail server by either using LVM snapshots, or by creating a compressed tar file.  If nothing else this will give you [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-mail-server-on-openvz-step-1-create-the-host/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Postfix Stress Test with smtp-source and top</title>
		<link>http://postfixmail.com/blog/index.php/postfix-stress-test-with-smtp-source-and-top/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-stress-test-with-smtp-source-and-top/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 15:09:22 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[postfix performance]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=218</guid>
		<description><![CDATA[Testing Load with smtp-source and top In order to evaluate the load on your box you can run smtp-source and combine that with snapshots of top to evaluate the load on the server.  Now open two terminals and in one run the smtp-source command and in the  other snapshots for top. Terminal #1 # time [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-stress-test-with-smtp-source-and-top/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postfix Stress Test</title>
		<link>http://postfixmail.com/blog/index.php/postfix-stress-test/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-stress-test/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 15:06:06 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>
		<category><![CDATA[postfix performance]]></category>
		<category><![CDATA[postfix stress test]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=215</guid>
		<description><![CDATA[One of the questions that you will want to solve is how much mail traffic can your hardware handle.  This is often why people overbuild hardware is that they just are not sure and no one wants to build a mail server and then rebuild in 3 months.  Fortunately, Postfix comes with a couple programs [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-stress-test/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debugging Postfix</title>
		<link>http://postfixmail.com/blog/index.php/debugging-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/debugging-postfix/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 12:13:42 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Compile Postfix]]></category>
		<category><![CDATA[debug postfix]]></category>
		<category><![CDATA[postfix compile]]></category>
		<category><![CDATA[Postfix Mail Server]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=211</guid>
		<description><![CDATA[Using strace to Find Problems The strace command allows you to view the activities of a process.  The first thing you will need to do is locate the process ID that you want to trace. ps aux &#124; grep postfix Here is partiial output of what this command will provide: root      5049  0.0  0.6   5396  [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/debugging-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
