ahh bless, the exciting prospect of 182 new e-mails courtesy of Yahoo! Mail
It's not often I check my Yahoo! Mail (usually about once a week)... but I have been signing up to sites using my Yahoo! addresses long before I got my mits on an all new @Matthew1471.co.uk server..
So what do *I* think is the solution to spam... well a bit of everything really...
Charging for e-mail? :
I disagree that the way forward with SPAM is to start charging a couple of pence per e-mail, from a devloper point of view I think this will not end a few of life's problems, the people who are most supportive of cost mail are businesses.
something like a "token" system would work, they were saying about it before, but not to, the extent im thinking. They were saying that everyone should be issued like "credits" and then each time someone sends an e-mail, it goes to a big server somewhere up in the sky
and deducts a token from them....and people who need more pay a few pennies for more tokens
User side (At least until servers come up with new methods):
1. Never pick e-mail addresses on popular domains like matthew14@msn.com, matthew15@msn.com.. you just know they're gonna get hit..
2. NEVER give out your e-mail address on webpages, always place a "Contact Us" form there
3. NEVER open up e-mails which have spammed images in them, they can detect you've opened them up by opening up a special image which was created just for you...then know your account is live and send you more.
Software / Server side :
1. The Matthew1471! way would be to just store a e-mail serial number on the server which *apparantly* sent it.
2. So once the e-mail is recieved by the destination server...erm say I sent a hotmail user an e-mail....
3. Hotmail would like check it, contact me and say
"Is message 26.3354tko45wk a real e-mail..." and my computer would look it up and go
"yes, that sent message ID exists"...then it'd deliver it to him or her..once a serial lookup had completed, the sending server would then erase the serial from the DB
Yes, so what if the domain *actually* did send the e-mail or the sending server was hardcoded just to send spam and agree to anything? well this is partly down to a few things then...
If the domain is liked...e.g. "Hotmail.com" then I suggest they impliment policies to
1. ONLY allow 1 E-mail address per IP address...
2. ANY accounts sending over 30 e-mails a week...either require cutting off...or requiring investigation..
If the domain is not liked, I suggest banning the domain... The ideologies I have mentioned will ensure that an e-mail
specifially came from
that server... A random spam mail I viewed the headers on :
From : "Malia Natashia [ztxvd0ijdrg@verizon.net]"
Subject : "FDA approved drugs"
Recieved From : stimulos.gravestonesuppressio.com
now I doubt that even did come from Verizon...
so, in my examples... my server would have made a check back to "Verizon.net" (the largest phone company in the world) It could say....
"is message ID 205952kom73 existant?"
"are you responsible for it?"
Verizon would say
"NO! stimulos.gravestonesuppressio.com must have sent that, not me"
(which is where the actual e-mail forementioned did come from)
It's simple and it'd work!
I would like to program this at some point (just a little demo server)...but what with AS exams and everything it'd be stupid to start it now.
.gif)
Matthew1471's ASP 
6:15 PM
| Comments [0] | #BlogX
cmon fire away why I should use Atom?
...) users which seem to take advantage of the Pingback, Trackbacks!
