<?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; Troubleshooting</title>
	<atom:link href="http://postfixmail.com/blog/index.php/category/troubleshooting/feed/" rel="self" type="application/rss+xml" />
	<link>http://postfixmail.com/blog</link>
	<description>Postfix Mail Server Training and Consulting</description>
	<lastBuildDate>Fri, 09 Dec 2011 17:11:03 +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>Emergency: Cleaning the Active Queue</title>
		<link>http://postfixmail.com/blog/index.php/emergency-cleaning-the-active-queue/</link>
		<comments>http://postfixmail.com/blog/index.php/emergency-cleaning-the-active-queue/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 03:19:33 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[postfix queue]]></category>
		<category><![CDATA[sctive queue]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=903</guid>
		<description><![CDATA[What do you do when you massive overload of unwanted mail that is coming to your server?  Recently I saw a Postfix Mail server that had gone down some months ago but had 10s of thousands of email ready to  be sent.  When it was repaired it began sending tons of old mail&#8230;.mail that was [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/emergency-cleaning-the-active-queue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Troubleshooting Amavisd</title>
		<link>http://postfixmail.com/blog/index.php/troubleshooting-amavisd/</link>
		<comments>http://postfixmail.com/blog/index.php/troubleshooting-amavisd/#comments</comments>
		<pubDate>Wed, 13 May 2009 11:18:56 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[amavisd]]></category>
		<category><![CDATA[amavisd-new]]></category>
		<category><![CDATA[Poaatfix troubleshooting]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=665</guid>
		<description><![CDATA[Recently my mail server just stopped.  No indication of problems just no mail delivered.  So what do you do in this situation?  Since I have set up so I receive an email summary of mail each day, when that does not come, it tells me I have trouble. 1. Check the Logs This seems so [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/troubleshooting-amavisd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Amavisd: Fixing Broken Perl Modules</title>
		<link>http://postfixmail.com/blog/index.php/amavisd-fixing-broken-perl-modules/</link>
		<comments>http://postfixmail.com/blog/index.php/amavisd-fixing-broken-perl-modules/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 13:11:05 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[amavisd-new]]></category>
		<category><![CDATA[perl modules]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=453</guid>
		<description><![CDATA[Recently, working on amavisd-new and restarting it broke several perl modules that are required.  The results of this was that the mail server quit sending mail because it could not process mail due to the broken modules.  Here is the log file info that helped me locate the problem. Mar 20 03:23:33 ns postfix/smtp[20284]: 992BB207DE0: [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/amavisd-fixing-broken-perl-modules/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>Using dig to check MX Records</title>
		<link>http://postfixmail.com/blog/index.php/using-dig-to-check-mx-records/</link>
		<comments>http://postfixmail.com/blog/index.php/using-dig-to-check-mx-records/#comments</comments>
		<pubDate>Tue, 07 Oct 2008 08:40:29 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[dig]]></category>
		<category><![CDATA[mx records]]></category>
		<category><![CDATA[postfix]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=228</guid>
		<description><![CDATA[It is important to verify that MX records can be seen.  To check use the dig command with the -t option which will allow you to do an MX lookup.  This example shows the MX records for the myexample.com domain which is using the ns.example.org server as the mail server. dig -t MX myexample.com ; [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/using-dig-to-check-mx-records/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postfix Troublehooting Errors</title>
		<link>http://postfixmail.com/blog/index.php/postfix-troublehooting-errors/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-troublehooting-errors/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 12:11:45 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[postfix errors]]></category>
		<category><![CDATA[postfix scripts]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=205</guid>
		<description><![CDATA[One of the best ways to begin troubleshooting is to check your logs.  Here is a script that you can create that provides a timestamp of the current problems and then will email you that data to a a chosen email account. #!/bin/sh # Check Logs, Mail Output with Timestamp TIMESTAMP=`date +%Y%m%d_%H%M%S`; echo $TIMESTAMP egrep  [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-troublehooting-errors/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Postfix: Cannot Receive Mail</title>
		<link>http://postfixmail.com/blog/index.php/postfix-cannot-receive-mail/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-cannot-receive-mail/#comments</comments>
		<pubDate>Thu, 18 Sep 2008 12:15:18 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Postfix Mail Server Trainging]]></category>
		<category><![CDATA[Postfix Training]]></category>
		<category><![CDATA[Postfix troubleshooting]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=147</guid>
		<description><![CDATA[Problem: Cannot Receive Mail In this example the user can send mail and it all works correctly but the user is not able to receive any mail. However, viewing the /var/log/ Sep 17 13:25:50 ns postfix/smtpd[17971]: &#62; rn-out-0910.google.com[64.233.170.190]: 250 2.0.0 Ok: queued as 4A454207D8D Sep 17 13:25:50 ns postfix/virtual[17976]: 4A454207D8D: to=&#60;tsmith@example.com&#62;, relay=virtual, delay=1.8, delays=1.8/0/0/0.01, dsn=4.2.0, [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-cannot-receive-mail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postfix Logs</title>
		<link>http://postfixmail.com/blog/index.php/postfix-logs/</link>
		<comments>http://postfixmail.com/blog/index.php/postfix-logs/#comments</comments>
		<pubDate>Sun, 14 Sep 2008 14:54:19 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix Logs]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=43</guid>
		<description><![CDATA[Checking Logs The file /etc/syslog.conf contains a line that is used to copy all mail by syslogd (CentOS). Note that Suse uses syslog-ng and so that config file is found at /etc/syslog-ng/syslog-ng.conf (see below). Here is that line(CentOS): # Log all the mail messages in one place. mail.* -/var/log/maillog So the location of the maillog [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/postfix-logs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

