I was reading this http://free.acrconsulting.co.uk/email/other.html
and sounds like it shouldn't be so difficult to implement in ASSP; the idea is that, if a given external host which connects to ASSP starts sending out commands before receiving the initial banner, then it should be considered a "worm" (or in any case a bad behaving host) and btw treated in consequence A refinement of the idea is checking for early talk at each state (not just at the HELO stage) that is HELO, MAIL FROM, RCPT TO, DATA; if the remote host sends out commands before getting back our response then it's an "early talker" Again, I think that such a filter, along with the HELO checks and the graylisting (delaying) may help cutting off a bunch of spam w/o having to perform more complex checks ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
