i'm disappointed with the new Outlook 2011 that it doesn't have a read receipts.is there anyways to generate read receipts on outlook 2011? if not does Mail on Mac have this feature? or is there anyway to have this feature?
Read receipts are an artifact of a bygone era. They were a feature of AOL. Other systems duplicated the feature, but it tends not to work across domains. That is just as well.is there ANYWAY i can generate read receipts or delivery receipts in Mail or Outlook 2011?
is there ANYWAY i can generate read receipts or delivery receipts in Mail or Outlook 2011?
If you're in an Exchange server environment you can do it with Outlook, but otherwise read MisterMe's explanation on why read receipts are completely pointless.
If you're in an Exchange server environment you can do it with Outlook, but otherwise read MisterMe's explanation on why read receipts are completely pointless.
I certainly understand the limitations, but I would hardly call it "completely pointless." It at least tells me the recipient got the message rather than sidetracked as spam or in their junk folder. Might not be something you want to want to take to a court of law, but it is not pointless.
Well, we could argue about it I suppose- but what's the difference between ending up in the spam folder vs. "clicked on and subsequently ignored" ?
I certainly understand the limitations, but I would hardly call it "completely pointless." It at least tells me the recipient got the message rather than sidetracked as spam or in their junk folder. Might not be something you want to want to take to a court of law, but it is not pointless.
Kind of like the signature I get on a UPS Package. At least I know you got the information. If you ignored it, that's on you. Your comment that this is completely pointless was an exaggeration and you know it.
How does one "get the information" if it is ignored? You are contradicting yourself. Read receipts are pointless, and only serve to comfort the insecure.
I sure hope you don't work in writing standards or their implementation, as your understanding here is poor. Read the MDN RFC. It has been around since 1998, and has nothing to do with AOL, "systems", or domains. It can work perfectly between any two willing MUAs.Read receipts are an artifact of a bygone era. They were a feature of AOL. Other systems duplicated the feature, but it tends not to work across domains.
It appears that you didn't read your own link. First off, AOL had receipts in the early 1990's--nearly a decade prior to 1998. The whole point of the Message Deposition Notification protocol was to develop an Internet standard that generalized the AOL-type "LAN-based" receipt protocols. Far from having nothing to do with MDN, AOL was the inspiration and motivation for it.I sure hope you don't work in writing standards or their implementation, as your understanding here is poor. Read the MDN RFC. It has been around since 1998, and has nothing to do with AOL, "systems", or domains. It can work perfectly between any two willing MUAs.
I understand that; I too was an AOL user way back then. However, I don't see any evidence that MDN was based on AOL's idea or implementation. Can you cite a source that makes that claim?AOL had receipts in the early 1990's--nearly a decade prior to 1998.
Not if you send email to me (at work where we have Outlook/Exchange). I have it set to ask me before sending read receipts and I deny each and every one.
which one are you using? Entourage?
How does one "get the information" if it is ignored? You are contradicting yourself. Read receipts are pointless, and only serve to comfort the insecure.
they may be pointless to you, but that does not make it pointless for everyone else. it's not like your opinion is the center of the universe or something.
I didn't state that my opinion is the center of the universe's. I was merely pointing out a contradiction in another member's already weak argument.
Do you have anything to add to the discussion about read receipts, or are you done playing online moral policeman?
Simple truth: If read receipts were useful, more e-mail clients, servers, and/or protocols would support them. That's the nice thing about capitalism- if something is not worth the time (and money) to include in a software suite, it doesn't get put in. Not sure how you plan on making the case for read receipts since hardly anyone uses them in a meaningful way, but you're welcome to keep trying.
I actually said "AOL-like," but it is just as well. From RFC 3798:I understand that; I too was an AOL user way back then. However, I don't see any evidence that MDN was based on AOL's idea or implementation. Can you cite a source that makes that claim?
It is interesting that each poster who uses an MDN-enabled mail application uses a version of Microsoft Outlook. Outlook is no less proprietary than AOL.Abstract
.... The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based"systems, and often referred to as "read receipts," "acknowledgements", or "receipt notifications." ...
Which three email clients do you use?I use three email client programs that generate request and reply to such requests, so I don't think it's as obvious of a failure as you say.
You might have a point if you could show that an email developer has successfully implemented the RFC 3798 standard for MDN.My contention with your original comment was that it suggested that the support for MDN needs to be cooked into a closed email "system", or brokered between such systems, which is not the case.
All of the above.Again, are you claiming that its adoption failed because it's a bad idea, or because it's hard to implement, or because no one wants to use it?
There is one in every crowd.The OP in this thread is clearly pining for it.