1. habibhb's Avatar
    I am a Blackberry Engineer at Pakistan working for WARID Telecom. For last 1 days a lot of users are receiving emails in the following format

    Y2UuIEtpbmRseSBmaXggdGhpcyBhc2FwLg0KLS0tLS0tT3JpZ2 luYWwgTWVzc2FnZS0tLS0tLQ0K
    U3ViamVjdDogDQpTZW50OiBNYXIgMTAsIDIwMTAgMTI6MjYNCg 0KVGhpcyBpcyBhIHRlc3QgbWFp
    bA0KDQotLTAwMTYzNmM1YzA3NTBkMDgxYTA0ODE2ZDJmODQNCk NvbnRlbnQtVHlwZTogdGV4dC9o
    dG1sOyBjaGFyc2V0PUlTTy04ODU5LTENCg0KPHA+VGhpcyBpcy BhIHRlc3QgbWFpbDwvcD4N
    dG1sOyBjaGFyc2V0PUlTTy04ODU5LTENCg0KPHA+Cg0K
    LS0wMDE2MzZjNWMwNzUwZDA4MWEwNDgxNmQyZjg0LS0NCg0KDQ pTZW50IGZyb20gbXkgQmxhY2tC
    ZXJyea4gc21hcnRwaG9uZSBmcm9tIFdhcmlkLg==

    Any body can please guide what could be the reason as this is for sure not an encoding problem because i already have verified that.

    Any suggestions or solutions

    regards,
    Muhammad Habib
    Blackberry Certified Support Specialist
    03-10-10 05:09 AM
  2. Lady_Jane's Avatar
    Hi,

    I think it's some kind of a global problem. A few people (including me) on the Curve 8520/30 Forum also experience the same problem. Still waiting for some advice...
    03-10-10 05:21 AM
  3. F0nage's Avatar
    Why do you say it's not an encoding problem. It sure looks like base64 to me.
    03-10-10 05:39 AM
  4. xmen81's Avatar
    on my 8520 I am also facing same issue since morning. But this is only in my Gmail account, other exchange accounts are not facing this issue.
    03-10-10 06:00 AM
  5. habibhb's Avatar
    I have tried changing the encoding type but it does nothing.
    According to recent update from my carrier an activity on BIS by RIM is under going since 7:00AM GMT 10 March, which is causing this issue as soon as the activity is completed issue will be resolved.
    Thanks.
    03-10-10 06:27 AM
  6. Lady_Jane's Avatar
    It's okay now.
    03-10-10 06:36 AM
  7. F0nage's Avatar
    I have tried changing the encoding type but it does nothing.
    According to recent update from my carrier an activity on BIS by RIM is under going since 7:00AM GMT 10 March, which is causing this issue as soon as the activity is completed issue will be resolved.
    Thanks.
    I didn't suggest it was your error, but that doesn't mean it wasn't an encoding error.
    03-10-10 06:51 AM
LINK TO POST COPIED TO CLIPBOARD