There is a possible bug in Spamfilter ISP that might cause spammers to relay DEPENDING on the topolgy and settings on your servers. If you have whitelisted f.ex domain1.com in Spamfilter ISP, a spammer can use mailto:*@domain1.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - *@domain1.com as from-address to send spam to people outside our company IF you have the same configuration as we do...
Here's my example :
We run Spamfilter ISP 2.0.1.347
We have the followin topology in our mailsystem :
INTERNET --> SPAMFILTER ISP --> TREND IMSS --> LOTUS DOMINO
A person send mail from the Internet, the mail goes to our Spamfilter ISP server, then it goes to our Trend InterScan Messaging Security Suite server, and then to our Lotus Domino server. Trend IMSS "trusts" the Spamfilter ISP server, because we need to allow Spamfilter ISP to push the mail to Trend IMSS.
Now the possible bug ; When a domain is whitelisted in Spamfilter ISP, it passes every chech, EVEN the Local Domains setting. Even if the recepients domain is not listed in Local Domains it will pass. In my opinion the mail should be dropped here since domain1.com is not listed in Local Domains (it's only in the whitelist).
Since it pass all the checks because the senders domain is whitelisted, it goes to Trend IMSS which again trusts the Spamfilter ISP server, and then Trend IMSS relay the mail to the intended recepient f.ex mailto:idontwantspam@domain2.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - idontwantspam@domain2.com . Trend IMSS is also our outbound mailserver.
There's two things that can be done to solve this.
1. Set Trend IMSS not to "trust" Spamfilter ISP. Then it will only accept mail to the domains specified in the configuration.
2. Make Spamfilter ISP drop all mail sendt to domains NOT listed in Local Domains.
I can solve it by doing #1, but I think it's important to address this issue since it might be others who have the same configuration as we do.
Logsat : Do you consider this issue as a bug? I personally think if a recepient-domain is not listed in Local Domains, it should be rejected, even if it's whitelisted.
Best regards, Morten Authen NSF
|