Lets keep this "brief":
Stanislav Sinyagin wrote:
well, I'm not crazy to develop a new ultimate spam killer from scratch :)
http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-12
but those groups don't seem to propose something new either.
Wow, you where able to read the IETF, IRTF and MAAWG lists in such a short time?
I'm just telling that SMTP is not the right protocol for email delivery:
http://www.rhyolite.com/anti-spam/you-might-be.html#senior-IETF-member-5
-- why do client-to-server and server-to-server have to be the same protocol on the same TCP port? These are completely different tasks with different domains of control, so they have to be two different protocols.
Why would you want two different ones?
You do realize that the Internet is a network of networks, and that there is no separation between users and server eh?
-- there's no obligatory identity check. Well, most ISPs have SMTP authentication for users, but on server2server path, there's none.
http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-6 http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-7
-- With wide spread of patent-free cryptography algorithms, why aren't the digital certificates obligatory?
http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-8
... and so on.
I just say that now it's the only chance to deploy something new, as IPv6 deployment is already something new. There won't be another chance for ditching some old rusty legacy stuff :)
http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-12
Lets say that I just suggest you start reading a lot more first ;)
Greets, Jeroen