Click for SpamPal's Homepage
Contents > LAN Mail Servers

SpamPal is designed as a personal mail filter that will run on same local machine as your email program.

However, SpamPal can be used on a LAN (local area network) with a LAN Mail Server to provide spam protection for more than one user.

For more details on how to get your software to work with SpamPal, choose from the following list of email Lan Mail Server software

LAN Mail Servers
Example Server Setup
SpamPal can be set up as an SMTP relay server between the internet and your incoming mail server. This provides spam tagging for all email coming to your mail server.

I'm assuming that you have a router or firewall forwarding port 25 from your public IP address, to protect your network. Using
Exchange as the mail server software name (doesn't matter what you're really using).

For all configurations on the internet side of an incoming mail server:

1. Go to Advanced/LAN Configuration and change the IP address to the public IP address, like 192.168.1.1 , instead of 127.0.0.1.

2. Go to Advanced/Access Control and add either 0.0.0.1-255.255.255.255 or 0.0.0.0/32 to the Access Control List

If you have two computers, one for SpamPal and one for the mail server:

Starting with:

192.168.1.1 Exchange listening on port 25
192.168.1.2 SpamPal on local port 25, server 192.168.1.1:25
router using NAT to forward port 25 to 192.168.1.1

Change to:

192.168.1.1 Exchange listening on port 25
192.168.1.2 SpamPal on local port 25, server 192.168.1.1:25
* router using NAT to forward port 25 to 192.168.1.2

This all assumes two computers. It's very safe because a quick change to your router can bypass SpamPal and the filtering.


If you have one computer:

Start:

192.168.1.1 Exchange listening on port 25
192.168.1.2 SpamPal on local port 25 on test machine, server 192.168.1.1:25
router using NAT to forward port 25 to 192.168.1.1

and test to make sure that SMTP to the SpamPal machine gets to the Exchange server. This is safe because your real mail still works fine - it goes directly to Exchange.

First change to:

*192.168.1.1 Exchange listening on port ANY OTHER, say 32025
*192.168.1.2 SpamPal on local port 25 on test machine, server 192.168.1.1:32025
router using NAT to forward port 25 to 192.168.1.1

and test to ensure that an SMTP connection to 192.168.1.2 port 25 gets to the Exchange server listening on port 32025. If it doesn't, fix this Exchange configuration problem first. This is risky because while you're in this state, your mail is cut off.

Then quickly change to:

192.168.1.1 Exchange listening on port ANY OTHER, say 32025
*192.168.1.1 SpamPal listening on port 25 local, server localhost:32025
192.168.1.2 SpamPal on port 25 on test machine, server 192.168.1.1:32025
router using NAT to forward port 25 to 192.168.1.1

and test to make sure that it works. Until it does, your mail is cut off.

The test machine here is just to give you a chance to verify the SpamPal and Exchange settings. Any workstation will do, since it doesn't have to handle all of your mail traffic. You can temporaruily have the router forward port 25 to it just to verify that all is working as you expect, then point it back to the main machine before running it all on the single machine.

Standard Email Programs
Click here for information on how to setup email programs

Webmail Software
Click here for information on how to setup webmail software for use with Hotmail/Yahoo


Annotations

Users can now annoate manual pages with their own hints and tips. To share your insights with your fellow SpamPal users, you can use the form of the bottom of the page.

Annotate this page

Unfortunately, owing to a high volume of attempted abuse, new annotations are no longer being accepted for this page. Please accept my apologies for any inconvenience caused.