I believe part of the problem you are having is because you do not have a local DNS server running behind your NAT.  I've run into the same problem myself until I ran the DNS server on the local network.  You may also want to add your 192.168.0.1 to the local domains whitelist under spamfilter configuration, as well as the fully qualified domain name of the box that spamfilter is running on.   Net traffic will not flow into your network if you are using local NAT address's on an outside DNS box.  If you have the mail server on the same box as spamfilter, you will also need to change the SMTP port for IMail and make the destination change in spamfilter to point to the mail server.  I am running the same setup myself almost exactly, except different IPs and IMail version.  PM me if you want details on how to make this work legitly and be legal on the net.

Morten,

Please note that most of SpamFilter's various filters rely on the need to "see" the original IP address of the remote server. Some other filters, like the SPF filter for example, instead *require* to see the IP of the sender, or in some cases they will cause valid emails to be rejected. This is because some domains specify via DNS which IP addresses are allowed to send emails on their behalf. If SpamFilter does not see the original IP address, it will reject the email as it see it coming from an un-authorized IP.

If your SpamFilter is behind a firewall, the firewall will need to be configured so that it does not "mask" the IP of the sender. in your sample post we see the connection to SpamFilter originating from 192.168.0.1, which is your firewall, and not the real IP of the remote machine. This will prevent SpamFilter from working correctly.

Hi Roberto