We are testing the new DNSBL feature in our test environment and have run into a problem. Our SMTP server sits behind our SideWinder firewall. The firewall is a store and forward. The problem is that all the incoming connections are coming from the firewalls IP address and not the spammers IP address.Has anyone run across this issue and how did you resolve it. Would we not have this problem with any other third party vendor?
I would appreciate any thoughts.
Subject: DNSBL Behind a Firewall
I’m not that familiar with the Sidewinder but if it’s using some sort of proxying then the only solution would be to disable it for smtp mail and use standard port forwarding to your Domino server. This would disable some of the security features but you could make that up by putting something like ISS’s BlackICE for Server on your internal Domino server. This would probably work better than Sidewinder’s security in any case - and the two combined would be even better. Not an expensive solution either.
The downside of using Sidewinder’s DNSBL is that you won’t be able to flag spam and move it to a spam folder in the user’s e-mail database for later perusal. DNSBL systems do block the odd legitimate e-mail and that could be a concern.
Dale
Subject: DNSBL Behind a Firewall
In this case, you shouldn’t use Domino for DNSBL. You should use the firewall. SideWinder can do this, the last time I checked.