Janice,

SpamFilter does not support auth passthru. Please note that SpamFilter is designed to handle exclusively incoming email only, your users should use your existing SMTP server as their outgoing SMTP server in their email client configuration. There are several ways to do this without having to change their configuration.

I'm including below the content of another posting that can help.

Roberto
LogSat Software

================================================

There are several threads on this subject. The key point is that SpamFilter is designed to process you incoming email only. Your outgoing email must still go thru your existing SMTP server.

If you already added a new IP to the NIC, there is no need to change the port iMail listens on. You can then configure SpamFilter to forward email to eMail on the other IP and port 25. This allows all your clients to not change their configs, and still use iMail as their outgoing smtp server. 

If iMail takes control aof all IPs bound to the NIC, then the above solution will not work, and you will need to change ports. However, if your server(s) are behind a firewall, you can then configure SpamFilter to listen on a different port, 28 for ex., and then configure the firewall to take incoming traffic on port 25 and redirect it to SpamFilter's IP on port 28.

Following is a posting that deals with a configuration similar to yours:

==========================

We assumed that you only had access to one single IP from your provider, and the suggestions we ghave before were based on that. Yes, of course if you have multiple internet IPs available (not internal LAN IP, they have to be internet IPs) things are much simpler.

It's extremely easy to bind multiple IPs to a single NIC card in one computer. We've prepared some screenshots on how to do so, click here to view them.

We see that your MX record for comcast.net points to mx00.comcast.net (24.153.64.1). If that is what your clients use as their outgoing smtp server, and you do not want to change your clients configs (which is what we recommend), you will need to have SpamFilter listen on a different IP, let's say 24.153.64.2 for example. The only thing you will have to change then is the MX record so that it points to SpamFilter's IP, 24.153.64.2.

By doing that incoming email will go where the MX record direct it, SpamFilter in this case. SpamFilter will then forward it to your IMail server on 24.153.64.1. Your clients will not change a thing, and still point to your IMail at 24.153.64.1.

Hope this helps.

iMail takes control of all IPs bound to the NIC! We are using Ipswitch iMail 8.01, no chance to change this now and in the future (as support told us).

But we are using a port mapper to direct incoming traffic for Spamfilter (as you described above), so everything is working fine on one box.