Fluffy not filtering email after successful install.
Status: Beta
Brought to you by:
waynemcdougall
Menu
▾
▴
#11 Fluffy not filtering email after successful install.
Hi,
I am using a Exchange 5.5 on Windows NT and we are
behind a firewall. Our firewall is set to forward SMTP-
TCP on port 25 to the computer on which the SMTP
server is installed.
After successfully installing Fluffy, I found that it was
not filtering emails. Email were not passing through it
either. The ports and addresses tab had our SMTP
server on port 25 and Fluffy on port 26. The SMTP test
showed no errors.
Please advise.
Many thanks.
Logged In: YES
user_id=1125113
Further to the above, I am now wondering if I need to change
the Services file in winnt.sbs\system32\drivers\etc\services
to show smtp on port 26. Presumably this will ensure that
smtp packets pass through Fluffy first before being directed
to the exchange server. Is this correct?
Logged In: YES
user_id=1125113
Further to the above, I am now wondering if I need to change
the Services file in winnt.sbs\system32\drivers\etc\services
to show smtp on port 26. Presumably this will ensure that
smtp packets pass through Fluffy first before being directed
to the exchange server. Is this correct?
Logged In: YES
user_id=1125113
Correction to the above:
The firewall is programmed to direct SMTP TCP on Port 25 to
the Server computer. Will Changing the Services file on the
server (win nt) to accept SMTP on port 26 for exchange and
setting Fluffy to listen on port 25 make the smtp filter work?
Logged In: NO
Did you get it to work?
Logged In: YES
user_id=1125113
Yes I did thanks. Have been posting my queries to the help
boards since and have found them very useful.
I had to reassign port numbers so that Fluffy was on 25 and
exchange on 26. On windows nt-exchange 5.5, this is done
by changing the services file which is detailed in
http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q173903. I opted instead to set it up on a separate win2k
machine, where I configured the preinstalled smtp server to
relay to the win nt-exchange server. Our firewall was
adjusted to send SMTP to the win2k machine. This gives us
the flexibility to change the receiving smtp server at a
moments notice through the firewall if we notice anything
amiss while testing Fluffy capabilities. With regards to its
performance, apart from a few minor config problems initially
which are always unavoidable when testing, it seems to be
doing pretty good job. As we only have a handful of users, i
have set it up to 'only accept these recipients...' in the local
email tab as the bulk of items we receive are NDRs for
nonexistentusers@mycompany.co.uk. This being the direct
result of spammers forging their solicitations with our domain
address. On top of that, I use spamhaus and sorbs to check if
the emails that get through are on a blacklisted ip and plan to
use the scores to ensure that spamhaus listed IPs are
blocked/deleted and sorbs only listed IPs are tagged as I
found that some legitimate emails ocassionally get picked up
by sorbs. Also sorbs picks up emails that are not picked up by
spamhaus.
Going by the NDRs we've received, I noticed that the spam
trap list may be out of date. GFI essentials which I also
trialled automatically collated details of all emails that passed
through it in an ms access database and from that I managed
to construct a list of newer spamtrap addresses which I have
attached to this post. The list however is not comprehensive
as it was compiled from about a days worth of NDRs and I
have noticed that there are quite a lot more variants that are
in use. I picked up about 6000 and have tried to weed out
the legitimate email addresses but if you do use it, I suggest
you give it a thorough check in case I missed anything!
On a final note, Fluffy's best selling point is
its 'configurability'. For example, the customisable header
checking element, local email, spam trap etc can all be easily
configured to different circumstances making it a valuable tool
for SMTP filtering at the port which in my opinion is a better
approach to the problem of spam than, spam filters that are
designed to work from the server level.
Logged In: NO
Fluffy should be on 25 and exchange moved to 26.