5 ms·
For some cases, yes. For most cases, I'm not so sure. I will state that this is probably not a solution for everyone and for many cases the traditional function
by jrussbowman 15y ago
For some cases, yes. For most cases, I'm not so sure. I will state that this is probably not a solution for everyone and for many cases the traditional functionality of email may be not only preferred, but necessary.
On point 1, how often, for the practical purposes email is intended for, does the average person not what the sender to know they've received their email? It's a messaging platform and acknowledgement is part of communication.
On point 2, does the recipient really need to see the message as it was first sent, or do they need to see the message the sender intended to send?
Working as a sysadmin myself, I can see where it may be necessary to keep a revision history of the message. I'd of course have to disclaim that up front to parties using it for sending.
But, thinking about that, it also means server side I'd have a bit more control over controlling it as a spam delivery platform. The only thing sent to recipients is a link. If there's spam or malicious content within the body of the message I could delete all the messages server side. No more worrying about they guy who's on vacation that comes and clicks on the link when he gets back. On that front it might make sense to build the server as a commercial product at some point, though really this functionality could easily be baked into Exchange, Zimbra and other products if the Enterprise went with webmail interfaces only.
- mooism2 15y agoI usually don't mind the sender knowing I've read their e-mail, but I do mind them knowing exactly when I read their e-mail, and I mind them being able to infer when I read e-mail in general. I mind the sender being able to delete messages from my mail archive. The sender being able to update the message they sent me is fine, so long as I can still get at the original message and forward it to my boss. If you can remotely delete spam after spammers have sent it from your server, then spammers can update all your sent messages to be spam as soon as they break into your server.
- jrussbowman 15y agoI see your point on the first item. Going to have to give that some thought. Archive history for any messages read will probably be necessary no matter what. I'll basically have to version all edits and make sure access can be granted in some cases to archived messages both for the sender and recipient. As for the last point, that can basically be done on any email provider that allows you to store messages on the server.