<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Spamd, NAT &amp; Rules [Solved]]]></title><description><![CDATA[<p dir="auto">I've installed spamd. Do I need to install a NAT/Rule to forward traffic on WAN port 25 to the internal mailserver or does the spamd already do this for me by setting the nextMTA?</p>
<p dir="auto">I suppose I don't have to define any static routes to the mailserver nor specify the mail domain on the spamd it just picks up any port 25 traffic send towards the WAN port 25?</p>
]]></description><link>https://forum.netgate.com/topic/13454/spamd-nat-rules-solved</link><generator>RSS for Node</generator><lastBuildDate>Sat, 17 Oct 2026 06:38:13 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/13454.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 14 Feb 2009 08:45:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Spamd, NAT &amp; Rules [Solved] on Sun, 15 Feb 2009 07:33:19 GMT]]></title><description><![CDATA[<p dir="auto">After some twiddling around it turns out very simple  :)</p>
<ol>
<li>Config spamd: fill in nextMTA</li>
<li>Start spamd</li>
</ol>
<p dir="auto">Don't make any NAT/Rules for port 25 traffic, Spamd will listen on WAN port 25 en forward your mail to the nextMTA after a 25 minutes once the mailserver gets on the whitelist</p>
]]></description><link>https://forum.netgate.com/post/190774</link><guid isPermaLink="true">https://forum.netgate.com/post/190774</guid><dc:creator><![CDATA[UltraLinuz]]></dc:creator><pubDate>Sun, 15 Feb 2009 07:33:19 GMT</pubDate></item></channel></rss>