BESx Activation Email Issue

[joshlamerritt]

Here is the setup:

- Active Directory with Exchange 2003 running on a DC.
- BESx running on a member server.

Got BESx up and running on the member server (had fun figuring the whole MAPI/CDO thing, but anyway...). Everything up and running fine. Able to add new users, even able to send emails to the users via Blackberry Administration Service. However, users are not receiving the Activation email. Have checked SPAM filters, that's not the issue.

When I create the new users, here is the message I get:

-----start snip-----
The following user information has been created and added to the BlackBerry Enterprise Server.

The activation password has been set. This password will expire in 48 hours.
An activation email is being sent from the blackberry.net domain with an ETP.DAT attachment.
To ensure this email is not blocked or modified, the blackberry.net domain should be whitelisted against any anti-virus, anti-spam, or blacklisting software utilized by the email system or gateway.

Each user must access the Enterprise Activation screen on the device and enter their email address to complete the activation.

Ensure the BlackBerry device is ready to be activated using the BlackBerry Expert Support Center
-----end snip------

However, no activation email is every received. I've run iemstest.exe against the user I am trying to activate, and it succeeds without any errors.

Any assistance would be greatly appreciated.

[gkl]

Make sure the user does not have any rules set up in their Outlook to automatically move emails out of their default inbox. BESx only looks in the default inbox.

[joshlamerritt]

No rules. As a matter of fact, I created a brand new email account and attempted to send to that account and receive nothing. I also have checked the SPAM service (all inbound emails are sent through a cloud based SPAM filtering service) for *blackberry.net and while I did find some hits, none were for the registration email. The hits I found appeared to be from users who are using the Desktop Redirector.