Blackberry Can not send email

Posted on 2009-12-22
Last Modified: 2013-12-17
Dear Experts,

Will you please help me solve the below issue?
I have found a number of answers on this issue but non of the answers solved my problem.

When configuring the send as permission in the active directory the BESadmin account has passed on all users as it should be except 2 users that the besadmin send as privilege was automatically revoked from the exchange.

Now i have checked the differences between the accounts that where loosing the send us permissions with the other ones and made changes on the differences as a result for the besadmin send us to not be removed again.

I thought after managing to solve the problem with the send us being removed that the problem with sending the email would had been solved but unfortunately it didn't. The specific 2 users still cannot send an email. After trying to send the email i get the X cross error.

The blackberry logs show the following:
[40700] (12/22 10:24:51.281):{0x15C8} {} Receiving packet from device, size=131, TransactionId=781554842, Tag=13621, content type=CMIME, cmd=0x3
[30112] (12/22 10:24:51.281):{0x15C8} {} Receiving message from device, RefId=139474363, Tag=13621, TransactionId=781554842
[20265] (12/22 10:24:51.328):{0x15C8} {} MAPIMailbox::Send(ppMAPIMessage) - SubmitMessage (0x80070005) failed
[20472] (12/22 10:24:51.343):{0x15C8} {} Send() failed: ERR_SUBMIT_MAIL, Tag=13621
[40277] (12/22 10:24:51.343):{0x15C8} {} Sending message error to device for message 139474363
[40583] (12/22 10:24:51.343):{0x15C8} {} Sending packet to device, Size=43, Tag=8475, TransactionId=-886511513
[40279] (12/22 10:24:51.343):{0x15C8} {} SubmitToRelaySendQ, Tag=8475
[40279] (12/22 10:24:51.343):{0x15C8} {} SubmitToRelaySendQ, Tag=13621

Please help this matter has driven me crazy.

Thank you,
Question by:LeonidasWB
    LVL 19

    Expert Comment

    Just confirming you've worked through right?

    Accepted Solution

    Yes i have followed the above link.
    I was troubleshooting a bit more within the AD and found the problem.

    In the security tab the users that "send us" was removed they where both members of the account operators group. When removed it solved the problem.

    I cant believe it was so easy to conclude.

    Thank you for your support Johny

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Do You Know the 4 Main Threat Actor Types?

    Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

    Suggested Solutions

    Email statistics and Mailbox database quotas You might have an interest in attaining information such as mailbox details, mailbox statistics and mailbox database details from Exchange server. At that point, knowing how to retrieve this information …
    Use email signature images to promote corporate certifications and industry awards.
    In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    10 Experts available now in Live!

    Get 1:1 Help Now