[OT] Re: [Fwd: Re: [Evolution] read receipt function in evo]

And, there's a very real and legitimate reason to ask for a return

Supporting read receipts would be a feature worth implementing, agreed.
(Although I am speaking for others here only, as I will never ever use

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.

It's not an invasion of privacy.

It actually is.

I may be more paranoid / concerned about privacy than you are, but
leaking the information when (if at all) I do read my mail isn't
acceptable at all. I refuse to use any MUA that doesn't empower me to
keep my personal information private.

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?


char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]