<?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; Filters</title>
	<atom:link href="http://postfixmail.com/blog/index.php/category/filters/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>Bot Connection Attempts to Postfix</title>
		<link>http://postfixmail.com/blog/index.php/bot-connection-attempts-to-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/bot-connection-attempts-to-postfix/#comments</comments>
		<pubDate>Mon, 21 Feb 2011 18:18:13 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[anvil]]></category>
		<category><![CDATA[logs]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=1014</guid>
		<description><![CDATA[There are obviously many different kinds of bots that systematically search the Internet for vulnerabilities.  At times you may see bot connection attempts to your Postfix mail server in the logs.  Here is an example of what that may look like. As you examine the logs (/var/log/maillog centOS) you see that the smtpd daemon receives [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/bot-connection-attempts-to-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Policy Banks with Amavis</title>
		<link>http://postfixmail.com/blog/index.php/policy-banks-with-amavis/</link>
		<comments>http://postfixmail.com/blog/index.php/policy-banks-with-amavis/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 12:06:22 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[amavisd-new]]></category>
		<category><![CDATA[policy banks]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[Postfix filtering]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=907</guid>
		<description><![CDATA[Amavisd-new provides Policy Banks that allow you to manage messages based on the client or sender.  For example if you wanted senders to be able to send to email lists without using the server resources for scanning with Spamassassin and ClamAv for these outgoing messages you could create a Policy Bank Solution: Specify Clients Who [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/policy-banks-with-amavis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Vacation Message for Postfix</title>
		<link>http://postfixmail.com/blog/index.php/vacation-message-for-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/vacation-message-for-postfix/#comments</comments>
		<pubDate>Sat, 28 Mar 2009 15:04:46 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[Postfix vacation message]]></category>
		<category><![CDATA[vacation message]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=455</guid>
		<description><![CDATA[The vacation program is not built specifically for Postfix.  So you will need to set it up separately from Postfix and then integrate it. The vacation feature allows you to configure a message that will be returned to the sender when you are out of the office.  If you are using a CentOS version you [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/vacation-message-for-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Header Checks: Examples of What Not to Do</title>
		<link>http://postfixmail.com/blog/index.php/header-checks-examples-of-what-not-to-do/</link>
		<comments>http://postfixmail.com/blog/index.php/header-checks-examples-of-what-not-to-do/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 12:26:22 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[header checks]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[postfix spam]]></category>
		<category><![CDATA[Postfix Training]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=305</guid>
		<description><![CDATA[Listed here are a number of header checks that do work but they are ineffective for the most part.  Here is the problem.  When you look at these examples they have a Subject that you are searching for.  As a result you will be writing header checks until the day you die, not good.    My [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/header-checks-examples-of-what-not-to-do/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>Built in Content Filters for Postfix</title>
		<link>http://postfixmail.com/blog/index.php/built-in-content-filters-for-postfix/</link>
		<comments>http://postfixmail.com/blog/index.php/built-in-content-filters-for-postfix/#comments</comments>
		<pubDate>Sat, 08 Nov 2008 15:18:51 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Filters]]></category>
		<category><![CDATA[header checks]]></category>
		<category><![CDATA[postfix header]]></category>
		<category><![CDATA[Postfix Training]]></category>

		<guid isPermaLink="false">http://postfixmail.com/blog/?p=293</guid>
		<description><![CDATA[One way to implement content filtering is to use regular expressions in your header, mime_header, nested_header and  body checks.  This should be simple matches to regular expressions.  The goal with this example is to eliminate non-English characters, since we cannot read them anyway.  This will drop all non-English mail. header_checks = pcre:/etc/postfix/header_checks mime_header_checks = pcre:/etc/postfix/mime_header_checks [...]]]></description>
		<wfw:commentRss>http://postfixmail.com/blog/index.php/built-in-content-filters-for-postfix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

