> Other people being able to verify that an email really was sent by me does serve my interests, because such verification establishes trust. DKIM, the technol

> Other people being able to verify that an email really was sent by me does serve my interests, because such verification establishes trust. DKIM, the technology considered by the article, does not prove this. The D stands for domain; it asserts nothing about the user that may have sent the email. Even if the domain is yours, you might delegate to another service or two, or you may have more than one user, or some automation in place. In any case, the recipient has little, if any, way to verify that and in all likelihood doesn't care that much; if they did, they wouldn't be relying on DKIM. > There are very few legitimate situations where you don't want non-repudiation... As a service provider, I'd probably want this. If it gets me out from the middle of someone else's dispute and doesn't have an ill effect on the service otherwise, I'd welcome it.