> These extra trips through different email servers strip the emails of information about the sending server which is critical to protect against spam and email forgery.
Sure, a forwarder can strip information from a forwarded message; but that's a rogue SMTP server. And this would be your previous email provider; so you'll know whether they're rogue before you start forwarding messages through them.
> Email was designed in the 1960s
s/1960s/1970s/
You get your own domain; then host your email at a provider that offers bring-your-own-domain. Now you have a portable email. Your domain registrar cannot interfere with your messages, unless you choose to host your email with your domain registrar.
I agree that an email address is a poor identity token. As with SQL, an identity should be an opaque object with no embedded meaning. In addition to being an identity, an email address is a communications endpoint, and is parseable, so it's not opaque.
> These extra trips through different email servers strip the emails of information about the sending server which is critical to protect against spam and email forgery.
Sure, a forwarder can strip information from a forwarded message; but that's a rogue SMTP server. And this would be your previous email provider; so you'll know whether they're rogue before you start forwarding messages through them.
> Email was designed in the 1960s
s/1960s/1970s/
You get your own domain; then host your email at a provider that offers bring-your-own-domain. Now you have a portable email. Your domain registrar cannot interfere with your messages, unless you choose to host your email with your domain registrar.
I agree that an email address is a poor identity token. As with SQL, an identity should be an opaque object with no embedded meaning. In addition to being an identity, an email address is a communications endpoint, and is parseable, so it's not opaque.