Client Setup for POPTray

This page gives instructions on installing and setting-up SpamPal for use with PopTray which will let you preview your email on your ISP's server, much like MailWasher, except it's completely free and Open Source.

Quick Index

1. Install SpamPal

2. Configure SpamPal

3. Configure your email program
3.1 Change your POP3 settings
3.2 Change your IMAP4 Settings
3.3 Change your SMTP settings
3.4 Create Filter/Message rules

4. Email Virus Scanners and Firewalls

5. Whitelist friends and contacts

::Top::

1. Install SpamPal

Start installation by double-clicking on the SpamPal Setup program (spampal.exe) and follow the on-screen instructions. Upon completion, SpamPal will run, showing its pink umbrella icon in your system tray.

If this installation is an upgrade of SpamPal then the existing configuration of POPTray is retained and the process is now complete. If not, i.e. this is a new installation of SpamPal, proceed with the steps below.

::Top::

All you need to know about extra configuration can be found here

::Top::

SpamPal can either be configured to run in transparent or non-transparent mode.

a) In non-transparent mode, the user has to reconfigure their email program to use it. This can sometimes cause problems for people, as changes have to be made to Username, Server Name and sometimes even port numbers, in order to get SpamPal to filter their email. So before you make any changes, take a note of your user id and pop3 server name

b) In transparent mode, the user doesn't have to reconfigure their email program to use it (apart from a simple message rule).

If you installed SpamPal in transparent mode then you can skip the next section(s) and jump straight to the Create Filter/Message rules section of this manual, which will tell you how to setup a message rule to move the spam that SpamPal has detected, away from your inbox and into the a SPAMTRAP folder.

If you installed SpamPal in non-transparent mode then you have manually set up your email program to fetch your mail through the SpamPal proxy rather than directly from your ISP.

You need to know how you collect mail from your ISP, for example, if you use POP3 to collect your mail then your only need to change your POP3 settings and not the IMAP4 ones.

::Top::

3.1 Change your POP3 settings

Select the Options screen by right clicking on POPTray's systray icon and then select the Accounts tab

To reconfigure your email program, first make a careful note of your original settings.

You should append whatever value you currently have in your Server setting, to whatever you currently have in the Login field (seperated with a @ sign), and change the Server setting to 127.0.0.1.

e.g. if your original values were:

Server: your.mailserver.com
Login: fred.bloggs

then you would, for example, change them to:

Server: 127.0.0.1
Login: fred.bloggs@your.mailserver.com

Screen after changes:

Note 1: if you got the message about SpamPal not being able to use the standard POP3 port...

You may, at this point, get an error message about SpamPal not being able to listen on the standard POP3 port.This is nothing to be worried about; just write down the port number SpamPal tells you and continue with this guide

This message means SpamPal is using Port 1110 instead of 110. You don't have to put it into SpamPal because SpamPal already knows it is using port 110. Instead, you have to tell your email program to use port 1110 instead of 110.

Note 2: If the server name already is localhost

Don't worry; just add @localhost to the username and leave the server name as is

Note 3: If your POP3 username already contains an @

continue regardless; SpamPal copes with usernames that contain two @s without difficulty.

Typical POP3 Server Examples (do not use directly)
Eg. 1: the original values of:	Eg. 1: should be changed to new values of:
Incoming Mail (POP3):mail.btopenworld.com	Incoming Mail (POP3): 127.0.0.1
Username: fred.bloggs	Username: fred.bloggs@mail.btopenworld.com
Eg. 2: the original values of:	Eg. 2: should be changed to new values of:
Incoming Mail (POP3): pop.west.cox.net	Incoming Mail (POP3): 127.0.0.1
Username: johnsmith	Username:johnsmith@pop.west.cox.net
Eg. 3: the original values of:	Eg. 3: should be changed to new values of:
Incoming Mail (POP3): pop.telus.net	Incoming Mail (POP3): 127.0.0.1
Username: fax07734	Username: fax07734@pop.telus.net
Eg. 4: the original values of:	Eg. 4: should be changed to new values of:
Incoming Mail (POP3): 192.168.1.1	Incoming Mail (POP3): 127.0.0.1
Username: mary_jones	Username: mary_jones@192.168.1.1

Note 4: Server names

The above Incoming POP3 Server Name, can be called: Incoming Mail Server, POP3 server, POP3 Username or Account Name depending on your email program.

There are also two ways of specifying the local server name, which should mean exactly the same thing (but on some system only one of them will work): localhost or 127.0.0.1

If you are still having a problem, why not give this setup page a try

::Top::

POPTray cannot use IMAP4

::Top::

3.3 Changing your SMTP settings

POPTray cannot use SMTP

::Top::

3.4 Create Filter/Message Rules

You now need to setup a rule in POPTray to automatically highlight/process the SpamPal-marked messages so that you can more easily review them.

Select Options by right clicking on POPTray's systray icon and then select the Rules tab

You should now click Add Rule and then setup your filter to look like the screen seen below:

Note 1

You could also tick the Delete from server option, which would delete the Spam tagged message automatically

Now click the Save Rule button.

So with the above rule setup, when you check your mail POPTray should now highlight the SpamPal marked messages with a red SPAM icon:

Note 2: If you are using the RegExFilter Plugin

a) In order to get RegEx Filter to scan the whole message body of these emails, you will need to add the
command CHECKPREVIEW into the filters.dat file.

Strictly speaking, RegExFilter also checks messages that are received by the TOP command when CHECKPREVIEW is added to the rule file. Because of speed reasons RegExFilter does not check TOP received messages (message previews) by default

b) You will also need to go to the Connections options, bring up the POP3 port properties and set the amount
of message body to filter for Message Previews and for Full Message fetches to be the same value or perhaps increase both values a little

What happens is VPOP3 first fetches just the message preview (the first entry for the message in your logfile; as you can see, it's not marked as spam), stores the subject line from that, then fetches the message entirely - in the default setting SpamPal will look at more of the message, and in this case RegExFilter finds something further down the
message that causes it to be tagged as spam. However, VPOP3 then puts the subject line it fetched with the message preview onto the message, hence the problem you're seeing.

::Top::

4. Email Virus Scanners & Firewalls

Specific instructions for using a variety of email virus scanners with SpamPal can be found on the main installation page

Some email virus filters want to sit between your mail program and your mail server in just the way that SpamPal does. There's actually no reason why they can't; you just have them up in serial so that your virus filter fetches its mail through SpamPal rather than directly from your mailserver, and then your email program fetches the mail through the virus filter.

::Top::

5. Whitelist Friends and Contacts

In order to speed up the processing of your emails and to prevent SpamPal from marking your friends or contact's emails as spam, it's a good idea at this point to whitelist all your important email addresses.

This can be done in four ways:

a) Use the pop3 automatic whitelist: this will whitelist non-spam email's that you receive on a frequent basis
b) Use the smtp automatic whitelist: which (if setup in 3.3) will whitelist all email addresses that you send out

Note 1: Privacy: smtp automatic whitelist

If you are using this, especially in a business, as this is recording all outgoing addresses, some people might view this as an infringement upon their privacy, (if you are in UK you need to tell staff of this policy before you start collecting data)

c) use the Add to Whitelist option on SpamPal's system tray: to manually whitelist your email addresses by typing in an address (or by using the dropdown box; to select from a list of recently received address):

d) Use the SpamPal Whitelist Email Addresses page to manually whitelist your email addresses:

Note 2: Headers that the whitelist compares against

The whitelist function only looks for email addresses in certain headers of your email.

These headers are currently: From:, Reply-To:, Sender:, Mailing-List: and Return-Path:

Initially, you will notice that using SpamPal makes fetching your email a little slower. This is because SpamPal has to check everything against the DNSBL lists (Public Blacklists) to see what email's are from a spammer and which aren't.

However, through it's Auto-Whitelist feature(s), SpamPal will quickly learn about the people and machines that send you lots of email, and adds them to a list of trusted senders. Because they're trusted, SpamPal doesn't waste time any checking the DNSBL lists (Public Blacklists) for them and so the more you use SpamPal, the quicker it will get.

There are more hints and tip on how to optimise SpamPal here

This completes the installation and setup.

::Top::