> And, there's a very real and legitimate reason to ask for a return>From what I recall, there are two separate notifications under the standard. One indicates the message was delivered. The other indicates that the message was opened. Neither indicates that the user actually looked at and comprehended the message, but it's a start.
> receipt.
Supporting read receipts would be a feature worth implementing, agreed.
(Although I am speaking for others here only, as I will never ever use
it.)
Anyway, folks need to understand that requesting a read receipt and not
getting anything in return *is* *not* an *evidence* of not reading the
mail. Which folks don't understand.
If I recall correctly (and I admit I might not), the standard allows for an implementation in which both types of notification can be refused. There's your privacy.
> It's not an invasion of privacy.
It actually is.
> Unless Ximian implements some features that aren't important to Ximian
> but are important to its users, evo will be relegated to "toy" status.
> I'm currently struggling to remain with my current distro of SuSE
> +Ximian in my business, but the lack of meaningful support in both
> components is forcing my hand to look around for another solution.
[...]
Do whatever pleases you. You don't expect to get features implemented by
comments like the above, do you?
|
-- James D. Ivey <james iveylaw com> Law Offices of James D. Ivey 3025 Totterdell Street Oakland, California 94611-1742 +1.510.336.1100 +1.510.336.1122 (fax) ------------------------------------------------------------ Notice: This email communication is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and/or by phone and destroy all copies of the original message. Thank you. ------------------------------------------------------------ |