Michael Morris
First Post
SMTP is, in my opinion, a lost cause. I've been pondering what improvements would be needed to cut down on the spam. This is the best I've come up with.
In SMTP the headers of a mail item aren't verified and can be forged. Spammers forge them happily to avoid punishment for their deeds. Well, what if they couldn't be forged.
Instead of accepting all mail recieved, use a protocol which verifies the sender. Here's an outline.
1) Sender generates mail, including their IP and a checksum for the message.
2) Receiver sends the checksum back to the IP in the message.
3) Sender sends confirmation that it exists back to the reciever. Only then is the mail accepted.
Mass mail would still be possible, but IPs couldn't be forged and further the machine sending the mail must be able to respond to all of the receiving servers' queries to confirm it's existance. This would cut down spam by at least half I believe. Thoughts?
In SMTP the headers of a mail item aren't verified and can be forged. Spammers forge them happily to avoid punishment for their deeds. Well, what if they couldn't be forged.
Instead of accepting all mail recieved, use a protocol which verifies the sender. Here's an outline.
1) Sender generates mail, including their IP and a checksum for the message.
2) Receiver sends the checksum back to the IP in the message.
3) Sender sends confirmation that it exists back to the reciever. Only then is the mail accepted.
Mass mail would still be possible, but IPs couldn't be forged and further the machine sending the mail must be able to respond to all of the receiving servers' queries to confirm it's existance. This would cut down spam by at least half I believe. Thoughts?