Warning - BB sends out delivery and read receipts with no control by the user
Blackberry doesn't seem to take it seriously but no matter your settings (at least on a Storm), if someone sends you an email with delivery receipt requested and/or read receipt requested you have a problem.
Delivery receipts are automatically generated by BB and sent back to the sender. This is a security/privacy issue because hackers could validate and know your email address is real.
If they send you an email with a read receipt requested, and you open the email first on your BB (no problem if you open first on your desktop), then the sender will get an email saying that you read their email. You have no control (at least on a Storm (non-entrerprise server environment - may have the same problem there but I can't test it). That means you have no privacy - the sender knows you have read their message.
Setting options on "Send Read Receipts" to NO has no effect. It sends the read receipt anyway.
This may apply to other Blackberry models. I don't know.
If you value your privacy or security I suggest you either:
1 - change vendors
2 - complain to BB (although they didn't seem to care when I did)
Good luck - Buyer beware!
- 05-05-2009, 06:23 PM #8
So what if you go into your email options and set it to not send delivery receipts?
Edit: oh reread and saw you tried that.
But I wouldn't go as far as to feel security is completely compromised
Last edited by gabbott; 05-05-2009 at 06:31 PM.
If you set your options to not send a read receipt ...... its still sends it anyway. Do you like your privacy? If not, then the bug isn't a problem.
I like my privacy ... so its a big problem.
How about if your ex sends you an email and knows you have a BB. Whamo -s/he gets confirmation you read his/her email.
- 05-05-2009, 06:51 PM #12
Just tested this on my curve 8330 and a read receipt is not sent when I have the option on my bb to not sent receipts.
I can test it on a pearl as well.
Sounds like it is a bug in the version of OS you are running on your Storm so I wouldn't go ditching blackberries just because of this.
Edit: Just tested on a Pearl 8130 running 184.108.40.206 and that also does not exhibit this behavior.
Last edited by gabbott; 05-05-2009 at 06:54 PM.
Agree - I haven't tested on other BB models, but I have tested on 3 storms each with a diff rev of the Storm OS - and all had the problem. One was the "official" Verizon release and two others were later Crackberry releases (think releases 109 and 114).
- CrackBerry Abuser
05-05-2009, 07:45 PM #16
- 103 Posts
- T Of Beer Please
Also tried it with 3 different storms and a curve
Storm 1: .109 Bug Confirmed
Storm 2:.141 No Bug
Storm 3: .132 Bug Confirmed
Curve 8330: No bugVerizon Communictions,INC Cellco Partnership,LLC d/b/a Verizon Wireless
Bell Atlantic - GTE - Verizon - NYNEX - PrimeCo
- 05-05-2009, 08:09 PM #18
Tried it on my Storm and and read receipt was sent, my Curve doesn't have this bug. Must be a .132 thing.rooted Motorola Droid X
jailbroken iPhone 3GS Black 32 GB
HTC Incredible: sold!
9530 Storm 1: Ding Dong the witch is dead
Good to know read receipts are fixed in 141. Are you running with a Blackberry Enterprise Server? Because it may not occur in that format.
Also what is date of the 141 release? I reported both problems to BB support 2 weeks ago and their response was pretty cavalier. Tried to BS me that it was either an IEEE or IFIP standard (That was a senior tech too). Told them it was BS - so I'd be interested to see if 141 came out in last 2 weeks.
Also does delivered still get sent in 141. Its the first step some hackers/spammers have used to validate you have a real email address. Less of a problem to send to people you know. Again BB didn't even understand delivery messages. There are typically two delivery messages when you send an email with deleivery receipt. One from your own email system saying that the message was delivered to an SMTP server at the destination domain (that just confirms the destination is a valid domain (knowledge can be gotten from any DNS server anyway) and that the destination has a mail server). The second delivery receipt comes from the destination user's email system. You can prevent that delivery message from being sent in any email system I know (i..e outlook) but the BB automatically sends it (at least the Storm does).
It seems 141 still sends the delivery receipts. Do curves etc?