Here goes: I subscribe to phonetag.com, a service which translates voicemails to emails. For more than a year, I have had the transcrbied messages sent to me at [email protected]. NOW, after changing devices (to the Tour), instead of a transcribed voicemail, I get a series of attachments ("text/plain" and "1 attachment") which are empty. Both RIM and VZW tech people don't know what to make of it, since "regular" and HTML email come through fine to that email address. KICKER: My wife has the same phone and settings, and when phonetag messages come to her ([email protected]) they are PERFECT!!
I've compared every single setting, re-sent the Service Books, and am at the end of my rope! Can someone help??
how about having it forward to a different email address that is sent to your blackberry .. does that have the same problem?
it could be you dont have the BB attachment services files installed. hook your phone up to desktop manager, download and install 4.7.1.40 and run an update
Hi,
I contacted two tech people at phonetag.com, and they were totally helpless about the problem. I changed the email address to my gmail account (which also goes to the device), and it works fine. The usually helpful RIM tech people tested everything, and couldn't figure it out. I already have 4.7.1.40 installed... is there something I'm missing? I don't know whaty "BB attachment services are."
Thanks!
I am currently experiencing the same issue on my Corporate BES account on my VZW 9630 (aka Tour) with OS v4.7.1.40. When I receive an e-mail message with one or more attachments from someone outside of the Corporate domain, I often (but not always) receive another unnamed "attachment" of type "text/plain" that I cannot open from the device -- this text/plain appears to be the e-mail body. Within Outlook on my desktop, the message is displayed correctly. As a work-around to view the message on the BlackBerry, I can either:
Forward the message to myself from the desktop Outlook client (the message body is visible in the sent message only); or
Forward the message to another e-mail address that I can receive on the device. (FYI, if I cc: my Corporate account, I still cannot read the body on that account.)
I am waiting for a response to the ticket that I submitted to my Corporate help desk.
What 3rd-party apps, if any, have you installed on your Tour? A post on another BlackBerry forum indicated that it appears that it is a combo of a bug in the RIM OS for the Tour (v4.7.1.40) plus a 3rd-party app that registers itself as a handler for the "text/xml" type. Specifically, the OP narrowed it down to PodTrapper in his case, but that is not one that I have installed -- I am pulling out my hair in an attempt to resolve this.
Check out this thread http://forums.crackberry.com/f132/te...chment-243433/ -- I am deleting SmrtGuard as we speak (waiting for device reboot). Others that have been named as culprits are PodTrapper and RSA SecurID.
I been having this problem too and for the life of me can't figure out the culprit. I even updated to the leaked .42 OS and the issue is still there. I am deleting SmrtGuard as I type this to see if it resolves the issue for me also. Will suck if that's the culprit as I paid for a full year too.
Just "upgraded" SmrtGuard to version 1.98... rebooted, but no change. Still can't get texts with audio attachments on my Tour. Very unhappy. I guess it's bye-bye SmrtGuard...
Just "upgraded" SmrtGuard to version 1.98... rebooted, but no change. Still can't get texts with audio attachments on my Tour. Very unhappy. I guess it's bye-bye SmrtGuard...
They haven't released a version that fixes the issue yet. Just wait till the next version. They mentioned in this thread that it will be fixed.
Just "upgraded" SmrtGuard to version 1.98... rebooted, but no change. Still can't get texts with audio attachments on my Tour. Very unhappy. I guess it's bye-bye SmrtGuard...
Don't give up quite yet -- v1.98 was released BEFORE SmrtGuard was alerted of the issue. They are working to address the issue and hope to have an update out by week's end.
For this problem, our dev team will get to the bottom of this. More on this soon