foso,

The *only* exception to any whitelists is virus checking.  The true function of a whitelist is to have it NOT be filtered under any conditions.  So, in effect, you ar saying that you "trust" that IP address.

Regards,

foso,

Spamfilter is for external SMTP only.

If your internal clients are connecting to it, their email just gets sent to your internal mailserver on port 26.

You need to configure you network's clients to connect to the real mail server on port 26. Even better find a way to get your firewall or router to forward incoming port 25 to another port on the internal  network and run spamfilter on that and your internal email server on port 25. That will removing the need to reconfigure your internal clients.

If you can't touch the firewall or router, (because your network admin, didn't get a xmas card and won't allow it.) then you need to find some solution with the same effect. If you have an internal DNS then this can be done without too much work. Add another IP to your box, set your mailserver to run on that, on port 25 (make sure spamfilter doesn't grab the IP too), change the internal DNS record to point to the new IP for internal clients. The external MX record should still refer to the IP spamfilter is running on.

hi lead,

thanks for your comments and ideas !!!!!

during weekend i realized all these mentioned "points" and i posted a new topic today, because of that.

my main-problem is to check outgoing e-mails( i mean e-mails going to internet !!!!) as well as incoming (from internet !!!).   

for outgoing mails(to internet): i will have to look for such an other tool.  

greetings

foso