Just got a blackberry the other day for work, it was wiped about 3 times and we setup my BES account but I am still recieveing personel e-mail from the guy who had the Blackberry before me. It says it recieved it from unknown (its an optonline account). Tried all the settings and hard wipes. I've been searching this fourm since yesterday morning haven't found anything that would help. Any ideas? (there's no cmime in service book for this account either...it does not exsist on the handheld but comes through in the message folder with my BES account).
Thanks in advance
-Bry

Wirelessly posted (8700g: BlackBerry8700/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

The BIS setup is done at the carrier's BIS site, and removed there. Talk to previous owner, if you can, or talk to carrier, to remove BB from previous owner's account.

The previous owner has to contact the carrier and have them cancel the BIS account. If it is a company paid for device, then have the BES Admin do it.

I was able to contact the previous owner, we tried every username and password he can think of and none of them work. Even the username for which the email is setup for. We also tried the carrier's website....still nothing.

Wirelessly posted (8700g: BlackBerry8700/4.2.1 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Have previous user call carrier's help line..... Ask to either cancel the BIS service or at least remove that blackberry from his account.

The previous owner needs to call the carrier and have them delete/cancel their BIS account. This will release the IMEI and PIN for you to use.

Why is everyone so afraid to pick up the phone and call?

re-read the question.... contact the previous user. have them change it.

Contact the person who is in charge of phones for your company. Have them call customer service of Wireless provider to expain the situation. They should be able to delete the email accounts. If it is a business account you might need the federal tax id number. I had this exact problem with cingular and they were able to correct the issue using the steps above.


JT