TekkieDave
Technical User
Apologies if this has been posted before, but I could not find it using the search options.
Basically, I have a user on Verizon BB, that is hooked up to our 3.6 BES. The user can send/receive e-mails fine. Everything works. However, whenever anyone sends this user an e-mail, it kicks back a message to them that the message was undeliverable. The odd thing is, however, that he receives the e-mail fine. It still gets kicked back though.
Here is the message that is kicked back to the sender:
The following message to <user@tmo.blackberry.net> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 554-'5.7.1 Invalid Recipient'
Another odd thing is that it lists "@tmo.blackberry.net", and the user has a verizon account, so I think it should be @vzw.blackberry.net no?
I contacted verizon, and they were no help.
I deleted the service books, re-synced, deleted the service books, and messed with the host routing table. I reloaded the user on the BES as well.
I'm hoping someone else has seen this.
Thanks in advance for your help.
**Okay, have you tried rebooting the machine?**
Basically, I have a user on Verizon BB, that is hooked up to our 3.6 BES. The user can send/receive e-mails fine. Everything works. However, whenever anyone sends this user an e-mail, it kicks back a message to them that the message was undeliverable. The odd thing is, however, that he receives the e-mail fine. It still gets kicked back though.
Here is the message that is kicked back to the sender:
The following message to <user@tmo.blackberry.net> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 554-'5.7.1 Invalid Recipient'
Another odd thing is that it lists "@tmo.blackberry.net", and the user has a verizon account, so I think it should be @vzw.blackberry.net no?
I contacted verizon, and they were no help.
I deleted the service books, re-synced, deleted the service books, and messed with the host routing table. I reloaded the user on the BES as well.
I'm hoping someone else has seen this.
Thanks in advance for your help.
**Okay, have you tried rebooting the machine?**