Discussion Locked

Blocking Spam Mail on GWise Mail Server

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Just found out yesterday that spammers are using our GW 5.5 Mail server to send spam mail everywhere. As soon as I found out, I stop SMTP relay under NWAdmin>>GWIA>>Access Control>>SMTP Relay.
It actually did not block receiving the messages.
Whatit did is that it does not retransmit the e-mail messages that are spam, but it stores them under the following subdir on the NW server:
F:\apps\gwdomain\wpgate\GWIA\GWPROB
We have a Sonicwall 100 Firewall and have the ports 25 and 110 open for our mail server.
Any ideas if there is something else could be done on the GW Server to stop receiving those messages and filling the server's HD?
Btw: However is doind this, is constantly changing the IP address where it is comming from and the port number, so it is not easy to block by ranges of IP addresses on the firewall.

9 replies

by pierrejamme

Be patient, once they find out they can't use you they will quit. We had the same problem. It didn't last long after we turned off relaying.
Nw4.1SP9 and GW5.2SP4.

I suspect if you respond in any way they will only try harder.
Do you have "Return to Sender" from Intellisearch (now discontinued but invaluable) to look in your GWProb and handle messages there?

by mike.seitz

I also had to deal with this problem. Back in April of this year. After doing what you did it took about 2 weeks for the junk e-amil to stop arriving. It stoped gradually over this 2 week period. Hang in there it will get better.

by oz_media

Nexic Symphony, can be found at the Novell site. It is a new tool that seamlessly integrates with GW and opens a simple, right-click menu that instantly creates rules to block mail as oposed to manually entering addresses.
Great tool, killed all my junk mail. Sorry I don't have the URL handy but it's a basic search on the Novell site.

by paul.slade

GW6 is better at handling spam as the GWIA does address checking at the daemon level. When a messages comes in for an invalid user it does not accept the message.

The daemon rejects unknown users, and will not move messages to the problem directory or send to the postmaster as it did in GroupWise 5.x versions.

GW6 doesn't have this problem as any invalid addresses are dumped before they hit the post office so don't waste server time or clog up the server hard drive.

This discussion is closed to new replies.