blackberry receives but doesn't send e-mails

[chudyksg]

I am on probation period as a IT Supports/network administrator. I have never had any experience with blackberry. The issue is that blackberry devices (they have got 8 of them) can receive but can't send e-mails. When I try to send an e-mail I get a message

From:network@etp2116.etp.eu.blackberry.net
Date: Wed, 21 Apr 2010 12:34:27
To: <robert@dupa.com>
Subject: RIM_bca28a80-e9c0-11d1-87fe-00600811c6a2

This message is used to carry data between the BlackBerry handheld and an associated server. Please do not delete, move or respond to this message - it will be processed by the server.

BEGINETP 10
A04BAAAAAAAAAQ!!
ENDETP 1187664798

I saw solutions for Blackberry working on BIS but I assume these ones work on BES as it goes through the network server unless there is another way to use blackberry not using BES? Because I read that BES is for Microsoft Exchange and I think they only use windows server I am not to sure because I haven't worked with the server yet as its my first task to solve the blackberry problem

Any solutions? Does it have anything to do with the send as permission?

When an existing message is forwarded then it goes through but a new created message doesn't

[trd2turbo]

That message is the message that BES sends when you attempt to activate a user to a new BES server. Is there an attachment in there?

When you first create a new user in a BES, you select the mailbox from a list that ties back to Active Directory. Then when you add the user, that message gets automatically sent to the mailbox along with an attachment. At which point your supposed to actually choose enterprise activation on the handset itself. It then goes out and pulls that email from the mailbox and syncs with his/her exchange.

Are these new BB's or new deployments?

You are missing TONS of information. Find out.....

a) Are these BB's using BIS or BES. (prob BESX from that message)
b) Are they on a separate server. Meaning if BES, is it installed on the same server as your Exchange server or is there a separate actual BB server. (with 8 BB's Im guessing they installed BESX on something like SBS 2003 server with Exchange.)
c) Who set them up originally? Did they complete an enterprise activation?
d) you need to get in front of the actual BB administrative console so you can see what users are showing.
e) If you are having the send as issue, you need to check the permissions on the user accounts in Active Directory and make sure none are included in the Administrative users...however when you are having the send as issue, you dont get anything back like that. It just doesn't send and you see a red X with something like "Desktop email unable to submit".

[chudyksg]

Yep there is an attachment ETP.DAT.
I will try to find out the information and get back to you but it may take few days. I think that it was working before and now it broke but I will find this out too. But isn't that strange that you cant send a new e-mail but if you forward this message it to another e-mail address it goes through?

[luguicastro]

Could somebody please help me? I've had my BlackBerry for over a month now. Over the past day and a half, I can send e-mails, but not receive them. I receive notifications from facebook, but not my e-mail anymore. Has this happened to any of you? It's been driving me insane!

Posted from my CrackBerry at wapforums.crackberry.com

[glittergirlnz]

If you try to send an email from the blackberry and its fails and comes up with the red X, if you open the email and scroll right up to the top there is an error message in there.

Common issue for receiving but not being able to send its usually a mail quota issue. The blackberry will always stop working before your mail client.

Have you tried a soft activation? Open the enterprise activation menu in the blackberry and hold down the ALT button and type CNFG, change the wireless sync to NO, save, then go back and change it to yes, see if that helps.

[NinjaRAT]

also ensure your bes service account has Send As rights in AD. unable to submit error almost always indicates a permission error. besadmin needs to be able to send as the user.

accounts with elevated priviledges are protected by the adminSDholder process that prevents modification to admin accounts by unchecking the inherit permissions option in advanced security. there is a way to disable this behavior, but best practice is to have a seperate non mailbox admin account