Why Email is a Bad Collaboration Tool 245
An anonymous reader writes "Isaac Garcia follows up his popular "The Good in Email" article with "The Bad in Email or (Why Steve Ballmer is the CTO of Microsoft)":
"In spite of email's universal success (as a collaboration tool), and in spite of its many good traits, email contains deep, inherent flaws that force users and markets to seek alternatives to collaborating via email."
Amen (Score:5, Funny)
Wait a few minutes
Yeah, I think I'd pretty much wait for you in the parking lot after work. And I wouldn't be there to give you a hug, ifyaknowwhatimean.
Oh, by the way, my boss has it somehow set to default that it's urgent and he needs a response once I've read it. Same with his secretary. Urge to kill rising
Re:Amen (Score:2)
Would it be to prank the Stiffly Stifferson to death with a tire iron?
Re:Amen (Score:5, Interesting)
IMHO a simple improvement to email would be no more than twice a day delivery. People would know the corporate email shows up at 6:00 a.m. and 2:00 p.m. Therefore, if that time has passed, you won't get a reply before the next email dump. This removes the pressure on the recipient, who knows he has at least 8 hours before anything has to be done with that email.
A side benefit is that there is only new email twice a day; when you arrive, and mid-afternoon. No more checking it every five minutes, no more boss yelling "did you get my email yet", no little dings/mailbox flags, etc, going off and distracting you from your job. Go a step farther, and let an intelligent agent apply your rules of priority to the message "has the word "superbowl video", so file it under "never"", rather than the sender's, and some of the issues are gone.
For colllabortion between more than 2-3 people, use a Wiki or Notes. Email should be for person-person, ephemeral, communication.
Re:Amen (Score:2)
Perhaps this doesn't work with an Exchange account, but I can do this all with POP or IMAP accounts.
Re:Amen (Score:2)
Worst thing with the "dings": they distract your coworkers too!
Folks, if you absolutely must have an überflashy desktop, please keep it just flashy (visual), but don't add bells, whistles and airhorns (audio) too...
For colllabortion between more than 2-3 people, use a Wiki
Good idea...
Bad idea...
mail should be for person-person, ephemeral, communication.
Re:Amen (Score:4, Interesting)
In case anyone is interested, here is the setup we had in a little company (now long sold) I setup with friends a while back (I wasn't the one who came up with the idea) to manage the "info" mail account (standard email addresses were still used back then) :
This would let you know who did what and it kept an archive in a platform independent format as well. It was used for other "global" addresses as well.
People could browse news in the same client (Netscape at the time) they used for email, which was convenient. We ran a mix of Linux, BSD, Windows and Irix.
Re:Amen (Score:5, Insightful)
Re:Amen (Score:4, Funny)
Great typo - seriously. You've inadvertantly invented a term that has accurately described more workplace collaborative efforts than I care to remember. Thanks!
Re:Amen (Score:2, Interesting)
Me personally I try to at least respond to an email asap, but I may not fill the person's request immediately. But everyone has their own service level standards, based on who your customer is and how many responsibilities you have. I think a good t
Re:Amen (Score:3, Insightful)
Once upon a time, there were these things called "newsgroups"...
Wikis (or if your group is HTML literate, just setting up a local website on space everyone can access) are fine for producing documents, but are lousy at capturing threaded discussions over time. Setting up a local NNTP server works well for this.
Notes, of course, is a bloated proprietary monster that should have been killed long ago.
Re:Amen (Score:2, Insightful)
Vested interest? (Score:3, Funny)
IMHO a simple improvement to email would be no more than twice a day delivery.
Let me guess. You have stock in fax machine manufacturer?
Re:Amen (Score:5, Interesting)
The disease I'd like to complain about today is the "read receipt". I can only imagine how much time people waste looking up whether I've read their message or not. You can turn that off, too, but some people really go crazy if they don't get their read receipts.
Re:Amen (Score:2)
Of course, no one has ever once sent me something marked "low priority", so whenever I received a low priority message, i knew it meant high priority.
I just liked the fact that when my boss looked over my shoulder, all his messages were marked "low priority".
Re:Amen (Score:3, Funny)
Re:Amen (Score:3, Funny)
Re:Amen (Score:3, Interesting)
Re:Amen (Score:2)
> can only imagine how much time people waste looking up whether I've read
> their message or not. You can turn that off, too, but some people really
> go crazy if they don't get their read receipts.
Read receipts aren't all bad; I've used them on occasion when working with coders in different time zones or on different shifts. When I got the receipt, it let me know they had checked in and I should probably get ready for a phon
Re:Amen (Score:2)
It's better for your carreer and for your outlook (pun intended) in court (due to a lack of witnesses), when you shift the waiting place to the dark corner of an underground parking at 2:30am.
An alternative may be a crouded subway station at rush hour. That would be the more, uh, final approach to solving this little issue.
Read Recipts (Score:2)
Oh, and if you tag it as important. i ignore it that much faster.
Yes i know you were joking.. however i wasnt...
Re:Amen (Score:3, Funny)
Problem solved.
Another alternative would be to greylist them with a delay of 2 days, hehe...
Re:Amen (Score:2)
Actually, the sender-assigned priority thing works pretty well. I just assume that anyone who sets their own message's priority for me is an idiot or ass-clown and I read those last, if at all.
Not all bad, just inappropriate sometimes (Score:5, Insightful)
A few problems: (Score:5, Informative)
The summary states the title of the article as: "The Bad in Email or (Why Steve Ballmer is the CTO of Microsoft)"
Two problems with that:
Problem #2 is especially difficult to understand, as the article itself correctly identifies Ray Ozzie as Microsoft's CTO.
How many times (Score:5, Insightful)
What I mean by silo'ed is that email traps information into personalized, unsharable, unsearchable vacuums where no one else can access it - the Email Inbox. Think of your Email Inbox as a heavily fortified walled garden. Not mentioning the difficulties many have accessing their Email Inbox outside the corporate firewall, the Email Inbox contains a hodgepodge of business, personal and private information that most people do not want to share with others.
Unfortunately, the Walled Gardens of our Email Inboxes are deceivingly warm and cozy. This feigned-comfort of safety whispers into our ears like a wily devil to, "Just email the document to me" or "Just email that document to yourself" with the false-belief that it will remain safe, secure and locked away. But that is just it......its locked away so that NO ONE ELSE CAN ACCESS IT. This is counter-culture to team collaboration.
And how many times have you sent out a document for comment and gotten back 30 different versions with markups, which you then have to reintegrate into one document and somehow handle inconsistencies and overlap? Then of course you need the document, but don't have a copy where you're at, so you retrieve one from an email and use that, but it's an old version, so you have to recreate revisions. And then someone always emails you their revisions late, after you think you're all done (usually it's your boss, so it's not like you can just leave them out).
If nothing else, you need a document collaboration tool, to avoid this nightmare of multiple files, and email is not it.
Re:How many times (Score:2)
The Real Problem (Score:4, Interesting)
Sort of like posting on slashdot.....
Re:The Real Problem (Score:4, Funny)
Re:The Real Problem (Score:4, Funny)
Re:The Real Problem (Score:5, Insightful)
I believe the problem with Email is usually only 10% of what you are trying to communicate is actually understood.
Sort of like posting on slashdot..... :-)
I know your joking but you're absolutely correct. This is a very serious problem with e-mail and why using the phone should be prefered over it. You see, when you're speaking to someone face to face or even over the telephone a lot of the information is contained in the delivery. Your body language and intonation help to create context and help the message get across to the listener.
E-mail, by contrast has none of this. Writing an e-mail that your audience will understand first time - both in tone and in content - takes considerable effort and skill. E-mails are often not considered fully. Hands up if you've sent an e-mail quickly and realised the tone of the e-mail makes it sound very hard and demanding? I suspect most of us have!
Because writing clear e-mails is difficult, people often resort to writing bullshit instead. The idea being is that if you can bedazzle the recipient enough with your buzzwords and other pseudo-words that they feel inferior and are unlikely to ask for clarification.
Why do we need software to collaborate? Humans have always collaborated best when sat around a table talking to each other. In my opinion, the software solves a problem that would be better solved by taking the time to see each other in the flesh.
It may be expensive but it's less expensive than getting it wrong and ruining the reputation you had with your client.
Simon
Re:The Real Problem (Score:2)
It is possible to convey "intonation" in text - using italicised and boldfaced text. It's just a
Re:The Real Problem (Score:2)
Writing an e-mail that your audience will understand first time - both in tone and in content - takes considerable effort and skill.
Sure it does.
Conflicting statements? (Score:4, Insightful)
The single worst trait of email is that it's silo'ed.
Then he says:
For many folks, the Email Inbox contains their most intimate secrets all mashed together into a single location: business correspondences, contracts, proposals, reminders, tasks, love letters, indiscreet online purchases, dirty jokes, pictures of your spouse (and kids), time-wasting games, inappropriate messages from co-workers and friends and lets not forget spam.
To me it seems like the perfect argument for why email should be silo'ed, and that it's one of the reasons why it is still so popular. I completely agree with his comment that there is a wealth of information hidden within emails that others could/would find useful. However, there obviously is even more that most would find useless or that the inbox owner wouldn't want visible. To me email represents the best, if flawed compromise. If the inbox owner wants to, they can redistribute their emails to a wider audience. This can be done by forwarding, or in Outlook, simply dragging the email to a public folder. I think the alternative approach, assume that everything is public and force the user (either sender or receiver) to selectively "hide" or "target" emails falls too far on the "other side" for most companies.
IM (or IRC) and Wiki (Score:5, Interesting)
This has been true for me working on OSS at night with a partner in Qubec as well as working in the same office with a developer two aisles away.
Re:IM (or IRC) and Wiki (Score:3, Interesting)
You need to check your copy-paste functionnality ! (Score:2)
Except the article says :
Therefore, we'd like to present The Bad In Email, or Why Ray Ozzie is the CTO of Microsoft.
There's a bug somewhere... maybe bad RAM, or buggy software, maybe between the chair and keyboard (if your chair hasn't been thrown away by Steve, that is)
Undelivered mail, return to sender (Score:5, Insightful)
It's difficult (if not impossible) for the average user to discern who an e-mail is actually from. Most people have no idea about message headers or IP addresses. It is trivial to send e-mail spoofing the address, and have 95% of people unquestioningly believe it's from the address you specify. This is one of the biggest and easiest to exploit weaknesses in e-mail.
E-mail is incredibly easy to ignore. Really, really, really easy. Claiming you didn't receive an e-mail is a get-out to any number of problems in collaborative projects, mostly because it's so common - it's fairly easy for an e-mailto not get to its recipient, be it an over zealous spam-filtering policy, a misconfigured mail server somewhere along the line or a lack of space on a company intranet (combined with badly configured mail servers which are relatively common).
Re:Undelivered mail, return to sender (Score:2)
Unless I'm running an online business, I certainly don't approach my email as if I have to look at every hour on the dot. Sometimes I even let it sit for a week at a time if I'm not expecting anything.
If someone has something important to say, call me.
And conversely, if someone has something trivial to say (telemarketers, etc), email me so my spam filter can kick in.
Just because email is convenient doesn't mean it should be used in all situations.
Re:Undelivered mail, return to sender (Score:2)
And that's why it is the perfect tool for a work environment.
In all seriousness, remember when email was just about perfect? Except for the occasional server mishap, every message got through, and they were all good. (Except for chain letters, 'Good Times' warnings, etc., from well-intentioned noobs and clueless relatives.) Then along came spammers, followed by imperfect filtering, and now email is j
Re:Undelivered mail, return to sender (Score:2)
Yeah, that's why i really hate "company" mail servers. I've used yahoo and then gmail for
Scare Tactics (Score:5, Informative)
Ah, not necessarily. Especially in the IMAP world, see IMAP over SSL.
[insert story about linux box and IMAP/SSL/MUTT]
Here's the real problem: You tried to scare your audience with concepts that your target audience doesn't understand. You can't scare ignorant people, see low limit Texas Hold'em.
Lots of ill-minded arguments in TFA :( (Score:2)
Email is NOT Secure (Part 1)
[...]
(Anyone using cryptographic e-mail is in the minority and the exception to the rule.)
Anyone needing secure e-mail is in the minority and the exception to the rule.
there is no way to 'retract' your email.
And how are you retracting your mail ?
Email is Prone to Viruses
There is no need to elaborate here.
You should make an effort. I do not understand.
The Al-Queda e-mail method for collaboration (Score:2, Interesting)
There is a way to use e-mail as such a tool, which was the preferred method used by the Spanish Al-Queda cell:
1. Open e-mail account (on your own web mail server, preferably) and publish username/password to members of cell/department/workgroup.
2. Write e-mail detailing plan and save as "draft."
3. After connecting by SSL, other co-workers/conspirators view and edit draft or attach comments for all to browse and update.
4. If server is owned by group, files are as secure as the passwords and OS. If a
This is offtopic.... (Score:3, Insightful)
2. The data is often 'NSFW' (Not Safe For Work).
Why did he use the acronym if he defines it directly after use. The only reason he should do this is if he used 'NSFW' elsewhere in the article, which he does not. The writer should decide whether he feels this acronym is recognizable enough to use without a definition. If it is then use it, otherwise don't!
Fixed:
2. The data is often not safe for work.
E-mail R.I.P. (1968-1999) (Score:2, Interesting)
I stopped using e-mail as my primary form of communications almost 7 years ago (about the time I started using SMS en masse, combined with instant messaging when available). For me, e-mail is no different than TV, radio and telephone -- all technologies that should have been replaced eons ago but
One more reason (Score:2)
Another intended recipient has a local spam filter that somehow checks the messages while still on the POP server. This takes bloody ages, causing the transfer to time out. Lather, rinse, repeat. As a result, he has to use a webmail client to receive large messages.
And then there's Outlook's inability to receive execut
I'm not impressed by the article (Score:5, Informative)
1. "If you are using SMTP (the universal pipe, remember?), you need to know that it doesn't encrypt data/messages. If you are using POP or IMAP, you need to know that they both require you to send unencrypted authentication (username/password)."
None of these is true. Encrypted SMTP, POP and IMAP all exist and we've been using encrypted POP/IMAP where I work for over two years now.
2. In the discussion of encrypted e-mail, he jumps straight into certificates with no acknowledgement or apparently even clue that PGP/etc. exist and are a lot simpler to set up and use (even in Outlook, or even manually if you have to).
3. "Eudora Security Flashback: I still don't know what the hell Kerberos is and what it has to do with a dog much less my email?"
Considering that this guy is, judging from the content of his post, very Microsoft-centered, for him to not know what Kerberos is suggests he is not even close to any kind of expertise in the field.
4. "Most companies spend a fortune locking down their IT infrastructure. This results in either Total Lockdown, also known as Paralysis whereby no one can do anything without a password, passkey, keycard, signature and sign-in sheet; or in No Lockdown, also known as Free-Love-Utopia whereby everyone is equal because everyone is an Administrator."
Um... no? He says "This results" as though these alternatives are the only two possible. This is probably just sloppy writing, but it still sticks out at me.
5. "If everyone used Outlook (70% of Central Desktop users use Outlook), then the ability to assign priority to each message would actually work. But we don't live in a Microsoft world (in spite of what many of you might think) and instead, we usually measure and weigh the importance of an email message by the number of people included in the carbon copy. This is highly subjective and fails to address the need to order and sort messages and task by importance."
I know from personal experience that Eudora among others had the capability to set and recognize a Priority or read-receipt header as long as 10 years ago. Priority fell out of favor because of abuse by spammers, but it does exist. And that was valid for any message sent to or from anyone on the Internet. Can we trust Outlook's read-receipt and priority flags to be as portable?
6. "Its still challenging for multiple people to share business email accounts (i.e. support, bugs and sales messages). IMAP sort of works, but presents its fair-share of limitations."
Such as? How could IMAP be better? Given the inherent needs and limits of sharing what is essentially a file folder, I think IMAP is designed about as well as it can be. There could be improvements, but nothing I can think of that would make me go "wow! It's a whole different IMAP!"
7. "Email is Prone to Viruses - There is no need to elaborate here."
Yes there is, because (say it with me!) E-MAIL IS NOT PRONE TO VIRUSES. E-MAIL CLIENTS ARE.
There are some good points in this article, but you have to filter them out from the sophistry.
Re:I'm not impressed by the article (Score:2)
And a good Collaboration Tool is.......? (Score:4, Interesting)
Thankfully the new project I'll be working will have 2 main developers in the same city so we'll actually have some sit down sessions but so far almost everything is in email. What are good collaboration practices(the article mostly just said email sucks)? For software I'm currently investigating gforge [gforge.org] with the wiki plugin. Does the slashdot community like wikis for collaboration between developers on software development projects or something else? Does all this really get solved when you have a dedicated project manager? Should your collaboration tool also be your project management tool? Any good project management tools(esp. ones that combine collaboration software). Thanks!
Article is full of lies (Score:5, Insightful)
In fact, SMTP offers a number of secure alternatives, included TLS within an otherwise unencrypted pipe, or SMTP/SSL on port 463. POP and IMAP both support TLS for 110/143, as well as POP3S/IMAP4S over 995/993, and have not required plain-text login since the introduction of capabilities negotiation more than a decade ago -- both of them support a version of the AUTH verb. (To give you a sense of time, the relevant RFC's were published before Netscape developed SSL v1, back when sending creds over the wire in clear text was completely standard.)
The guy's trying to sell something, but it would help if he could sell things without lying about them.
Re:Article is full of lies (Score:3, Informative)
Not to mention you can send an unencrypted stream of encrypted data, i.e. PGP encrypt your email.
My biggest problem with E-mail.. (Score:2, Insightful)
Re:My biggest problem with E-mail.. (Score:2)
Then they cant complain since you already told them.
Not surprised (Score:4, Insightful)
Winston Churchill once said [uga.edu] "Democracy is the worst form of government except all the others that have been tried." You could say the same thing about email as a collaboration tool -- it sucks, but for the average user it sucks less than every other option.
None of these objections are so large that they can't be overcome; many people use the tools above successfully. But for the average user, who accepts defaults and isn't interested in learning a new skill just to organize a meeting, they all have flaws that outweigh the flaws of e-mail.
I hate collaboration-by-email as much as the next guy, but until we can come up with something that is an order of magnitude better for the average user right out of the box, we shouldn't be surprised if they keep shooting e-mails around. (sigh)
Re:Not surprised (Score:2)
You could say the same thing about email as a collaboration tool -- it sucks, but for the average user it sucks less than every other option.
The Okham's Razor of technology: What about the good old-fashioned cork bulletin boards? :-D Maybe it should be Knuth's Razor (Prof. Donald Knuth is a vocal critic of email).
Doesnt have to be true (Score:2)
It doesn't have to be like this. My mother runs a counseling service and I installed gpg and a plugin for SquirrelMail - and now my mother, my father, and yes, my grandmother can easily send encrypted mail back and forth. And we have to, if we want to discuss clients over email and stay HIPAA compli
Linux Kernel Mailing List (Score:2)
The solution is to train people in using the tool. On the linux-kernel mailing list, the policy is that you cc the list on any reply to a message on a list, and cc all recipients. If you violate this rule, people compla
Email and Mail (Score:2, Informative)
If you need an instant reply, how about use something like "Instant Messaging", VOIP, a phone call, or come over in person?
I really hate people who expect email to be almost the same thing as instant messaging. Email is a lower priority messaging system, it should not be used for something that you need an instant reply
Re:Better email (Score:5, Insightful)
Good, now that that's out of my system, I'll explain.
Email WITHIN my domain is guaranteed. Honest. If someone (say joe@jupiter.lan) sends mail (to, say, jane@earth.lan), its going through.
If joe@jupiter.lan sends mail to peter@scrape_me.com (whatever), it is rewritten to joe@scrape_this.com, and forwarded to forward_this_shite.net.
After which IT ISN'T MY RESPONSIBILITY. If it can't be forwarded on, it WILL be returned to joe@jupiter.lan. Once accepted, though, I don't care. Not my network. And this makes the world go around.
If there are problems within your LAN or your system, its your responsibility. The original Unix just dropped the mail into the file system. Which is as reliable as the file system. No delivery issues. Linking networks together; as reliable as the linking/forwarding services used.
I can't and won't be responsible for other peoples networking and administration skills.
Ratboy
Re:Better email (Score:2)
When I phone someone, and there is a problem with their telephone or telephone system, I get an engaged tone or equivanent.
All I'm asking is if I send someone an email, and they don't receive it for whatever reason, I know about it. An engaged tone for email, if you like. And no, the email system does not do this.
Re:Better email (Score:2)
Re:Better email (Score:2)
Unless of course I could approve notifications, i.e. if a message comes from an address that isn't already in my address book I can choose to accept messages from that address or not.
Re:Better email (Score:2)
Re:Better email (Score:2)
No, read receipts are not the same. That is for an individual email. I'm talking about the person it comes from, not the email.
And yes, they are extremely annoying.
Re:Better email (Score:2)
See - once you add the "if I can approve" it bit, you necessarily forego the "guaranteed" aspect. Hence the problem with receipts. Your request would be to simply re-invent this wheel.
Re:Better email (Score:2)
If it crosses networks, no such guarantees exist. But, since a positive connection has an "immediate" result, it doesn't matter. Your "busy" or "no connect" signal may, however, be due to any number of reasons (not just that the other party cannot take your call now).
Email, though, is a step away from immediate results. It can be delivered though severly constrained
Re:Better email (Score:2)
All I want is a little red dot next to emails in my sent folder that weren't received by the recipient. I don't think that's impossible. It may be difficult. It may not be to do using the current way email works.
But we'll have it one day and it would be better if it was the OSS community that provided an open way to do this.
Re:Better email (Score:3, Interesting)
as i saw, ratboy stated that this can not be guaranteed unless all participants comply with common rules or all links are controlled by a single entity.
if all links in an email-processing chain (your mail client -> your computer -> your server -> some other mailserver -> other computer -> other mail client) are working as they should, the message simply will be delivered.
now, wether it will be read... no, read notifications is not a good idea.
generally mail syst
Re:Better email (Score:2)
You need to come up with a new protocol that allows for immediate delivery and a backwards flow of delivery information. Something like... hmmmm... I don't know, maybe IM! Which someone already suggested!
It already exists, use it.
Besides, just
Re:Better email (Score:2)
Not an email expert but I think this problem is simply (if not easily) solvable by requiring a positive confirmation from each mail server, with a final confirmation when the recipient client "pulls" it, upon which the confirmation signal would fol
Re:Better email (Score:2)
Even registered US mail only tells you that I signed for the envelop
Re:Better email (Score:2)
SMTP offers guaranteed delivery. It's a connection oriented protocol. If it fails, it lets you know, and it only fails if the other server isn't there. So the only problem beyond that is that local delivery is misconfigured...not really a problem in software design, is it?
I guess that solves the first problem.
Now to make it secure...Kerberos! That's about as secure as you can get. But how to do kerberos+smtp? What about POP3 or IMAP? Can we kerberize those, too? Maybe we can let MIT tak
Re:Better email (Score:2)
No it doesn't. Emails do not get through and sometimes no notification is given. I don't care why this happens, but it does. and that, quite frankly, is rubbish.
Why do you guys always rush to the defense of email. It's a crappy system.
Re:Better email (Score:2)
Email is a great system with a few flaws. Gauranteed delivery is not one of them.
Virtually all email programs will let you request a recieved receipt, and that's about as good as you're going to get. You could probably also find an addon that will notify you by sending an image or other HTML element that tracks back to a server that will send you a reciept. I'm sure someone will sell you that solution, too (or give it to you free i
Re:Better email (Score:4, Insightful)
I find the attitude of the OSS community depressing about this subject. They are too close to the technology and can't see the flaws in it.
Re:Better email (Score:2)
silent loss of a legitimate email is a technical problem. solve it, or find somebody who is responsible for your email system. it can be opensource or proprietary, that doesn't matter much as communication protocols are open.
if you have a problem with your car, you probably find somebody who knows how to fic it or fix it yourself. you don't go around crying that cars are bad.
losing emails is not supposed to happen in current email system, so i don't see the point in blaming i
Re:Better email (Score:2)
The system should be designed so that emails can never be silently lost. If an message doesn't get through because there's a problem with the recipients system, then I want to know about it. The fact that emails can be silently lost is a major flaw in its design.
The OSS community could come up with a better solution, but it seems that they would prefer to defend an imperfect system.
Re:Better email (Score:2)
cars are not supposed to lose a wheel when driving. they are not supposed to develop cracks in a windshield without a visible reason. shit happens, and _when_ it happens, it must be resolved.
currently you are arguing that a perfect and never failing system must be created, not that failures which usually happen because of human error (be it user or some administrator) should be analysed & eliminated.
current system does not lose mail just like
Re:Better email (Score:2)
Re:Better email (Score:2)
In any of these, this doesn't happen. The *protocol* is not connectionless. When one mail server contacts another, the conversation is something like this:
Server 1: Are you a mail server?
Server 2: Yes.
Server 1: I have a message for userX@yoursystem.com. Take it and deliver it.
(One of these three, usually)
Re:Better email (Score:3, Insightful)
Care to share exactly how you would ensure that is true? It can't be solved at the protocol level, the receiving end could make a mistake, or simply lie.
What if the admin accidently pointed my mailbox to
Re:Better email (Score:2)
Oh, wait, they have! MIT makes it and uses it on their own servers and clients! Did we win? Yay!
There is more:
Apparently, the author never heard of SMTPTLS, which, incidentally, GMAIL has implemented.
Now,
Re:Better email (Score:3, Funny)
Maybe the programmers figured the people wanted to read the mail once it got delivered...
Kerberos can't secure email from snooping (Score:2)
Re:Kerberos can't secure email from snooping (Score:2)
Doing ssl is easy. I suppose it was too much to assume that the previous poster already knew about that...
Re:Better email (Score:3, Insightful)
Modern email is pretty much reliable. What is not reliable is the "business" need driven content filters which cause mail to disappear.
SMTP is best effort, and that effort is very, very good. End users can make the best efforts of clued administrators fail.
Reject my email if you think it is spam. Don't filter it out, because then I have
Re:Better email (Score:2)
what kind of an answer is that?
I have posted this plea for better email numerous times on Slashdot and all I ever get is a bunch of responses full of excuses for the current system or reasons why it is not possible or is too difficult.
All I want is a little red dot next to a sent message if it has not been received (or if the system can't tell if it's been received). Yes, I know that there are all kinds of reasons why with the current way email works doing this is problematic. But that's
Re:Better email (Score:2)
let's try this again...
current email system technically provides everything you wanted (though maybe not in the exact ui style you requested).
legitimate email is not supposed to vanish without a trace. if it does, bug somebody who could help you to find the cause and eliminate it. if all you do is whine on slashdot that the system itself is broken (which isn't), don't wonder that people will be telling you how it really is.
Re:Better email (Score:3, Informative)
OK, here's where I think you are confused; perhaps no
Re:Better email (Score:2)
When I worked at NWA, we had it with PROFS/OV (a mainframe-based corporate e-mail system), and they took it away and replaced it with internet mail.
Whose fault is the current situation again?
Re:Better email (Score:2)
I'm not blaming anyone for anything. I think the OSS community rocks. It's just this particular problem is waiting for a solution, and nobody seems to be trying to find it.
Re:Better email (Score:2)
That might not be true in smaller organizations, but it certainly was in those two. The mail servers they replaced PROFS with at NWA were a huge step backwards, IMO.
Re:Better email (Score:2)
Re:Better email (Score:2)
Too right! Just read all the other responses in this thread. It makes me depressed.
One day someone will come out with a better messaging solution and it will take off like wildfire. But if Slashdotter are representative of the OSS community then it looks like it is unlikely to come from the OSS community.
Re:Better email (Score:2)
I am not a troll.
There is a real opportunity here that I believe the OSS community is missing, which is why I was deliberately provocative.
Image if sending emails between OSS clients like Thunderbird was actually better than using, for instance, Outlook. I could say to my contacts, hey use Thunderbird for your email and you'll know that I've received it. They might then say to their contacts the same thing, and the uptake spreads. Firefox spread because it is better than IE. Thunderbi
Re:Better email (Score:2)
I was working as an IT Manager for years and you won't believe me, how often users came to me and asked me what happened to the email they sent around the world or they were expecting a reply to a mail a
Re:Better email (Score:2)
take a hammer and "print" this on your wall :
"Misspelled mail addresses and ignoring the error notification and so on."
re-read it every day. once you can grasp it, try to come up with a list of problems you see in current technical implementation and NOT come up with some problems you have experienced and "don't care why they happened".
i've got to go now so, please, stop this, ok ?
Re:Better email (Score:3, Insightful)
Thunderbird would spread like wildfire if it could do secure, guaranteed (to arrive, or notification if not) email.
It can. For many people, it does. Also, you're confusing a client issue (secure content) and an only partially client issue (secure delivery) with pure server issues (guaranteed delivery) which the client should not and in fact cannot address. And that issue is solved anyway, in SMTP, for what, 30-some years now?
Re:Wait a second... (Score:5, Funny)
Re:What about BCC? (Score:2)