But the point is not to have to do much to get it to work, I mean right click maybe, add key, and it's done... seems an easy way to eliminate such a HUGE problem?
I like SpamCop, but what I like more about mine would be A) the completely open source free nature to it. B) The fact that it would cost nothing. C) It uses a fool proof approach. There is absolutely NO way to evade this method, because each time you sign up at a site (newsgroup, etc.) they each get a unique address, meaning that they can spoof all they want, get as tricky as they want, no matter what - they have to send it to somewhere, and since there will only be one address per website, there's no way they can ever evade it.
Hi, I'm thinking about creating a website, and writing the applications to support something like this. Would this be useful to you guys? I know the documentation is sketchy, let me know on any ideas.
I want to develop a free site for people to login to that will basically allow them to completely eliminate, and trace the orgin of spam. Here are the program specs, what do you think?
Program Title:
SpamRouter
Program Description:
A set of scripts to route mail to the correct destination address, as well as collect statistics
on where the "spam" was sent to, which will provide a direct link to where the address was
provided allowing us to track spammers efficiently, and accurately. Also allowing the user to deactivate the address provided, eliminating spam from that source.
Author:
Nick Hoover
Systems Engineer
720 Studios
Copyright Information:
This document and all of its accompanying scripts are (c) 2001 by 720 Studios
No parts of this program may be redistributed for profit without explicit
written consent of 720 Studios. You may modify this program as you wish, however
no warantee is presented modified, or unmodified. Meaning, use at your own risk.
Detailed Description:
This will be discussed in a single user environment, in future versions however - multiuser
environments will be present to allow the program to have a realistic use in the real world.
SpamRouter will have three seperate things going on. The key attachment to all of these
scripts will be a flat file (for now, however that may be put into a mySql database eventually
if the need is ever that high) database which will contain the following information:
useremail - the destination email address, which will be in the future used for the user's login
userpass - dummy for now, eventually an encrypted password for multiuser
userid - a generated ID that will be part of the generated keys
totalkeys - total number of keys (described below) generated
This database will contain the primary information for our users. There will be a second
set of databases, which will be generated for each user. These databases will contain
the generated keys, and will have the following information per record:
key - the generated key
origin - the site and or party given the address (this is for tracking)
date - date the key was generated
totals - total number of times the key has been flagged (ie. sent an email)
Each email that is sent to a key will be copied and put into a file named after its
key then followed by its count (ie. the sixth email sent to key X240213sd would be
X240213sd.5 [0-5]) that way we can track messages as well.
Now that you have an entirely confusing description of the data we'll be storing, time to explain
how this thing works.
Here's the life of a SPAM message sent to an address covered by spam router:
User is asked to provide their email address to a website for whatever purpose.
User logs into spamrouter and generates a new key, and enters in the website's URL
and other information so he or she can remember what they gave it for.
User is given a key generated address.
User gives that address to the website, and goes about their business.
IF the website the user gave their address to is a spamming website, and tries
to spam the email address provided, spamrouter becomes a knight in shining armor.
Email is sent to key at spam router such as: x9237823sijd783@spamrouter.org, spam
router receives the email, and copies it into a file for future reference, increments
the count on that particular abusing website in its database, and sends it to the
destination address (we're not trying to block spam [unless the user turns that
key off], just trying to trace it to whom it really came from.) An email is sent to the
destination address alerting them that the email was SPAM and sent from whatever
website the user registered it with. This allows the user to have a real copy
of the email, the information as to whom it came from - so that they can contact
the company, or whomever, and rip them a new one and have absolute proof that it was
from them, furthermore, the user can then turn off that key. Basically, no one will
ever receive your REAL email address (unless you give it to them) which lets you decide
who can contact you, and who can't. The problem with most "filters" is they filter who
it's from, not who it's sent to.
Kind of complicated, and maybe not really all that useful... but I created it for myself
because I want to know WHO is using my address for spam, that way I can get these people
to stop. Furthermore, once I've finished my business with a particular site, I can turn
that key off, basically eliminating spam from that address.
Slashdot Mirror
But the point is not to have to do much to get it to work, I mean right click maybe, add key, and it's done... seems an easy way to eliminate such a HUGE problem?
40+40+40 != 100
I like SpamCop, but what I like more about mine would be A) the completely open source free nature to it. B) The fact that it would cost nothing. C) It uses a fool proof approach. There is absolutely NO way to evade this method, because each time you sign up at a site (newsgroup, etc.) they each get a unique address, meaning that they can spoof all they want, get as tricky as they want, no matter what - they have to send it to somewhere, and since there will only be one address per website, there's no way they can ever evade it.
What do you think?
Hi, I'm thinking about creating a website, and writing the applications to support something like this. Would this be useful to you guys? I know the documentation is sketchy, let me know on any ideas.
I want to develop a free site for people to login to that will basically allow them to completely eliminate, and trace the orgin of spam. Here are the program specs, what do you think?
Program Title:
SpamRouter
Program Description:
A set of scripts to route mail to the correct destination address, as well as collect statistics
on where the "spam" was sent to, which will provide a direct link to where the address was
provided allowing us to track spammers efficiently, and accurately. Also allowing the user to deactivate the address provided, eliminating spam from that source.
Author:
Nick Hoover
Systems Engineer
720 Studios
Copyright Information:
This document and all of its accompanying scripts are (c) 2001 by 720 Studios
No parts of this program may be redistributed for profit without explicit
written consent of 720 Studios. You may modify this program as you wish, however
no warantee is presented modified, or unmodified. Meaning, use at your own risk.
Detailed Description:
This will be discussed in a single user environment, in future versions however - multiuser
environments will be present to allow the program to have a realistic use in the real world.
SpamRouter will have three seperate things going on. The key attachment to all of these
scripts will be a flat file (for now, however that may be put into a mySql database eventually
if the need is ever that high) database which will contain the following information:
useremail - the destination email address, which will be in the future used for the user's login
userpass - dummy for now, eventually an encrypted password for multiuser
userid - a generated ID that will be part of the generated keys
totalkeys - total number of keys (described below) generated
This database will contain the primary information for our users. There will be a second
set of databases, which will be generated for each user. These databases will contain
the generated keys, and will have the following information per record:
key - the generated key
origin - the site and or party given the address (this is for tracking)
date - date the key was generated
totals - total number of times the key has been flagged (ie. sent an email)
Each email that is sent to a key will be copied and put into a file named after its
key then followed by its count (ie. the sixth email sent to key X240213sd would be
X240213sd.5 [0-5]) that way we can track messages as well.
Now that you have an entirely confusing description of the data we'll be storing, time to explain
how this thing works.
Here's the life of a SPAM message sent to an address covered by spam router:
User is asked to provide their email address to a website for whatever purpose.
User logs into spamrouter and generates a new key, and enters in the website's URL
and other information so he or she can remember what they gave it for.
User is given a key generated address.
User gives that address to the website, and goes about their business.
IF the website the user gave their address to is a spamming website, and tries
to spam the email address provided, spamrouter becomes a knight in shining armor.
Email is sent to key at spam router such as: x9237823sijd783@spamrouter.org, spam
router receives the email, and copies it into a file for future reference, increments
the count on that particular abusing website in its database, and sends it to the
destination address (we're not trying to block spam [unless the user turns that
key off], just trying to trace it to whom it really came from.) An email is sent to the
destination address alerting them that the email was SPAM and sent from whatever
website the user registered it with. This allows the user to have a real copy
of the email, the information as to whom it came from - so that they can contact
the company, or whomever, and rip them a new one and have absolute proof that it was
from them, furthermore, the user can then turn off that key. Basically, no one will
ever receive your REAL email address (unless you give it to them) which lets you decide
who can contact you, and who can't. The problem with most "filters" is they filter who
it's from, not who it's sent to.
Kind of complicated, and maybe not really all that useful... but I created it for myself
because I want to know WHO is using my address for spam, that way I can get these people
to stop. Furthermore, once I've finished my business with a particular site, I can turn
that key off, basically eliminating spam from that address.