We use BES for Exchange 4.0, when emails come into our server BES picks them up and fires them off before they are even filtered out by our spam detection software, I know this because once I recieve the spam message on my BB when I look in my Outlook or OWA I do not see the email at all, and I do know our spam server is setup to delete all spam emails.

Is there away to force BES not to fire the emails until after they have been declared spam or not?

Thanks
Andrew

You could up the polling time on your BES from 20 seconds to however long it usually takes for the spam software to check...

Where are you filtering your SPAM though? You need to make sure you're filtering high enough up in your organisation to remove the mails before they get thrown on to the BES server.

Yep, typically, your need to filter the Spam at the exchange server, Using something as simple as spamcop's ip blackist can do wonders. Here:
SpamCop.net - SpamCop FAQ: How do I configure my mailserver to reject mail based on the blocklist?

Alternatively, you could upgrade to BES 4.1 and turn on 'hard delete' support, which will remove orphaned messages on the handheld (if no reference message can be found in Outlook).

I have had great success in using Exchange upgraded to SP2. Implementing the IMF & sender filters agressively with the Reject option. 70% of the spam is gone. Quite amazing.

BES registers with exchange to be notified of new messages as they arrive. BES does not poll the exchange server for emails.

BES does poll for the task, calendar and emails to be reconciled between the handset and the Exchange server.