3 ms·
Email is not immutable though? It's pretty easy to just copy an email out of your favorite IMAP client, modify it, and drag it back. Do they not know this?
by mehrdadn 9y ago
Email is not immutable though? It's pretty easy to just copy an email out of your favorite IMAP client, modify it, and drag it back. Do they not know this?
- brongondwana 9y agoWell, duh - if you can delete, edit, and upload a NEW email clearly you can change the state of your mailbox. That's a new email though, it's not the same email. Books are also not immutable - you can throw away a book and print a different book with the same cover. So at that level, nothing is immutable if you have full write access to it. The difference is, who has access to mutate the message? If you mutate it yourself, more power to you. It's your copy. If the SENDER can mutate it right there in your mailbox, that's a different story.
- mehrdadn 9y agoIn what sense is it a "new" email? It has exactly the same headers and message body (except for whatever you choose to modify, obviously), including dates and sender and everything. It's like copying a file on top of another file and claiming the older one isn't modified, it's just a "new" file that you're copying. I mean, OK, but how is this a meaningful or useful statement? The result is pretty indistinguishable from having modified the bits of the original email in-place from the user's standpoint. If you mean it can't be mutated by anyone other than the account owner, then that would be worth clarifying I think? But even then, the same is true of, say, my Google Drive. Nobody can modify my files who hasn't received my explicit permission. So are files on Google Drive "immutable" to you?
- brongondwana 9y ago"modify it" - looks like a new email to me. It's going to have a different secure digest. You can argue semantics here - but the main difference is: YOU can modify the messages in your Inbox. THE SENDER can not. Unless they have write access to your mailbox and can copy things out in a client, edit them, and write them back.
- mehrdadn 9y agoRegarding the "the sender" thing -- see my update above; sorry I was busy editing my comment before you posted this. Regarding the secure message digest: if that's your claim, maybe clarify that "[DKIM-]signed messages are tamper-proof"? Because not all email messages are signed. Also, I think you can still upload messages with broken signatures (not sure?) in most mailboxes, and the user won't necessarily know either (who verifies DKIM signatures manually?)... but I'd have to double-check this.
- brongondwana 9y agoYeah, probably true - I did mention our non-standard DIGEST.SHA1 (I'd like to change that algorithm at some point, though the risks are kind of overblown, particularly since we inject some randomness in the SESSIONID field that's part of the Received header added on every delivery) That said, if you tried to claim that a message was from somebody and used a tampered version, then checking the DKIM signature is something I expect would be done as part of the forensic analysis, as would checking the mail server logs. At least on our servers, you'd be able to tell from the logs that the digest changed when the new copy was uploaded - assuming you claimed something about downloading it and moving it to a new folder with your client.
- skybrian 9y agoIt's not mutable by the sender. If you edit your email history it will change. If you don't edit it then it won't. It's not proof by itself, but might be if you can convincingly claim that you didn't edit your received email.
- brongondwana 9y agoAlso - if it has a DKIM signature on it (or ARC chain), then you can't modify your copy and still have the signature pass. And that signature was probably made with a private key that you don't control.
- ocdtrekkie 9y agoI think the point is that it's immutable to the user. Nobody can go in my mailbox and change the content of emails that are there. You can't unsend an email (except for weird hacks like delaying sending the email in the first place). The use of the term immutable here is not intended to suggest your inbox cannot be modified in any way by yourself. A good example of how Gmail has futzed with immutability with "dynamic" content before is how they embed Google+. It lets you +1 and comment straight from inside Gmail, which is pretty awesome! But... in the case of a notification for a deleted post or comment, the dynamic overlay Gmail uses will try and obscure the content. You end up having to go to a mobile or IMAP client to see what was actually contained in the email notification of the deleted G+ item.
- mehrdadn 9y ago> The use of the term immutable here is not intended to suggest your inbox cannot be modified in any way by yourself. Okay, but then, is this any different from cloud storage? Would you also say Google Drive is immutable for the same reason? Or for that matter, wouldn't the same go for files on your computer?
- brongondwana 9y agoYes - assuming you trust Google not to fiddle it. I would expect that a document I stored in Google Drive wouldn't update itself a week later.
- mehrdadn 9y agoOK, so by "immutable" you really do mean "static" then? Static stuff can change, but stays unchanged until you actually change it. Dynamic stuff can change even without input from you. Mutable stuff is possible to change. Immutable stuff is impossible to change. etc. The bigger issue though is I'm trying to square what you're saying here with your blog post: > I admit it annoyed me when I first ran into it – why can’t you just fix up a message in place If this was a poor wording, maybe go back and rephrase? Because I it seems pretty undeniable that after reading this sentence the reader gets the impression that you claim it's not possible to go back and fix up a email in your own inbox. Which wouldn't really matter, except that people who aren't aware otherwise will actually believe you and spread misinformation on this. Last thing I want is someone reading your blog post and falling for a scam because they read from a presumably reputable source (you) that emails can't be edited post-facto.