useful. Thus, I developed and refined this software when a recent spammer forged my @3dmail.com domain. Many people
believed that the forged mail came from @3dmail.com and sent their compliants not realising that we are equally
a victim of such spams.
We had used some of the testing concepts at Abuse.Net and ORBS.ORG (now discontinued, but there are others to replace it like ORDB.ORG)to develop this
software. We will make available this source code at a later date as we are still refining / developing it.
Currently, I felt that Abuse.Net program only allows you to do a detail testing on a specific
server. In my opinion it does help to identify various servers that allows Open Mail Relays from a message header.
This is where, this software helps you to find out and understand what to look for.
If you want to test a specific server IP, you should still visit Abuse.Net to test 17 or more
server settings to see if there are any loopholes in that server. Currently my program is targeted only to
provide you information of any servers that specifically have Open Mail Relays.
Most common mail servers that had attempted to block open mail relays would
have passed upto the first 7 common anti-spam tests. We prefer to be a little
stricter in our test and decided that a server should at least past 12 tests that this program will check.
Currently, our mail servers have been tested and passed the 17 tests. We do not expect all other mail servers
to achieve such a standard. If they have passed the 12 tests, most likely we can consider that the
postmaster of such a mail server has made a good attempt to protect their servers from allowing spammers
to use it. If you use the test at Abuse.net and found that the specific server failed some of the tests
you can forward the information to ORDB.ORG to let their program further test the server.
So long as a server fails any one of the 12 tests, my program will consider the server an OPEN RELAY MAIL server.
Which is most likely how the spammer had used it to sent you a spam.
This software retrieves all mail server & IP address. It will do a test to see if a server has willingly or
unwillingly opened port 25 (SMTP server is running). Note: By right all authentic received: header should
have been received by a mail server who has port 25 up and running.
Those servers which is found to be unknown or cannot be connected, are seemingly
forged details. It could also be a personal SMTP used by the spammer during the period when he connects to
a dynamic IP to sent out spams. If the program found that an IP is no longer reachable, it means that the
dial-up session could be closed after the spammer logged out of their ISP.
I recommend that you use the link provided at http://www.ordb.org
to test, notify and track that Postmaster of the `offending' mail server that allowed Open Mail Relays.
One good thing I like about using the program at ORDB.ORG is that it will track the response or no response
from the Postmaster of the mail server that allows Open Relays. If they do not do anything say after a week,
ORDB.ORG will post the domain to a `blacklist'.
I appeal to you not to sent us a complaint note but rather use this software that I created to
identify the offending websites. Please understand our situation as it would create more unnecessary traffic.
Please note that this software does not automate the process of reporting to the various
affected parties. We feel that some Administrators does not like that. So instead, it
aimed to help you find out the source. We leave the notification to you or you can use
the link to ORDB.ORG to do that for you.
This system is `used as it is' meaning that we will NOT BE HELD RESPONSIBLE for/nor ascertaining
the accuracy of spams or used as a referee. However, I believe, that this program will provide
or (try to provide) you a pretty accurate identification of the spam source.