How-To Configure hMailserver and ASSP to filter SPAM
Jason Weir jason.weir@comcast.net 4/14/2004
This configuration was tested with both hMailserver and ASSP running on the same Windows 2000 Professional box, but it should work on almost anything that will run hMailServer
Check the “Show Advanced Configuration Options” checkbox and click the “Apply Changes” Button
Change the following Settings
SMTP Destination = 127.0.0.1:125
Check “As a Service” checkbox
Listen port = 25
Local Domains = list the domains you have hMailServer configured for
Test by trying to telnet to 127.0.0.1:25 you should see the mail server banner.
This gets ASSP working in Test Mode, mail should now pass through ASSP to hMailServer. You will notice messages building up in the spam and notspam directories. If you see spam in the notspam folder or vice versa you must manually move those messages to the correct folder. Once you have 100 or so messages build up in the spam and notspam folders run the rebuildspamdb.pl script, this builds the spam database. Read the ASSP documentation regarding turning off test mode as well as automating rebuildspamdb.pl
Do I understand you correctly that you are suggesting to have avast listen on port 25 for SMTP-traffic and then routing it to hMailServer on port 125 (avast taking the place of ASSP in the tutorial)? How would I go about to make that connection?
What if I would add ASSP to my configuration as well? In that case avast would block port 25 for ASSP in the same way as it is now blocking HMailServer, would it not?
Makaio, I’m not an expert on internet traffic and ports connection.
Anyway, I’ll try, not more than this, the following:
avast could listen on port 25 for SMTP-traffic and this is the default.
It does not have to ‘route’ to 125 for hMailServer, it will be taken there is the hMailServer is set to listen on port 125. Well, I suppose the same I have for pop ports: avast listen on 110, Outlook Express + spam killer at 120 (for instance). Each program have its own configuration.
If both programs listen the same port, you’ll get them in conflict.
Maybe, we need a programmer here :-[
From my general understanding I would think that your proposal would not be working. If I would simply accept SMTP, POP and IMAP traffic on any other ports while paralelly accepting it on port 25 for avast, avast would be rendered useless, as any scanned mail would run into a black hole. The same mail would come through on the designated other port without being scanned. That’s why I was asking for a way to “route” traffic from one port to another, after its having passed the avast proxy.
If both programs listen the same port, you'll get them in conflict.
Maybe, we need a programmer here :-[
Yep, that's the problem at hand. Any experts in the matter with ideas?
I don’t think so. At least for POP (inbound mail). I do scan the emails, caught virus, delete messages through avast. The email body has an added note, the icon appears on the system tray, the email header is maked as scanned by avast. And, after all, avast listen 110 and the message is taken by 120 (email client).