Cannot Forward E-Mail to BlackBerry

[DoubleSh0t]

The company I work for has an Exchange 2003 server. We do not have a BES server. I'm to receive e-mails from work on my BlackBerry, but I've run into some major headaches.

1. I cannot add the address through ATT's BIS page. We are using ISA for OWA, and RIM does not support it (View Document)

2. E-mail forwarding does not work properly. The IT department added a new user "Shawn's Blackberry" with my personal @att.blackberry.com address. Internal e-mail sent to me is received on my BlackBerry without issue. E-mail sent from an external address gets delivered to the Outlook client, but not to the BlackBerry.

External senders also get the following message back:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

(myaddress)@att.blackberry.net

Reporting-MTA: dns;(exchangeservername).(our internal domain name).com
Received-From-MTA: dns;(our external domain name).com
Arrival-Date: Wed, 25 Feb 2009 14:28:36 -0500

Final-Recipient: rfc822(myaddress)@att.blackberry.net
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;551 This is not a relay host - mail must be to or from host domain.
X-Display-Name: Shawn's Blackberry

-------

I'm pulling my hair out with this - is there something setup wrong with the Exchange server? From what I understand, this -should- work without issues - all I'm doing is forwarding the e-mail to another address right?

[DoubleSh0t]

It works fine just like any other external address.

[giorgosh]

People who try to send me emails often receive error 5.5.0 too, since we chanced from MS Exchange to a 3rd party mail server. Any suggestions?

[TrespassersW]

I have helped a number of people set this up successfully using the instructions here to forward to the BlackBerry (carrier) email address:-

Forwarding Mail to an External Recipient

I hope this helps.

[giorgosh]

I think I have followed the same steps, and i am receiving most of the emails, however i am missing SOME... How can i fix that or at least find the cause.

[TrespassersW]

Forwarding directly from the Exchange server works fine unless there are rules in place which apply to the server generally and prevent certain things happening. The administrator should be able to check which rule(s) are preventing this working. The good news is that, similar to firewall restrictions, individual users can be specifically exempted from general rules.

[RTakacs]

Have you spoken to your IT Department about this? Have you reported it to the carrier, chances are that they've come across this problem before.