There are probably a couple of applications running on your server, listening for incoming connections from the outer world.
But these connections from the internet only reach the router, and the new router has no clue what computer inside your network might be interested in "unexpected incoming traffic".
Say you run Outlook Web Access on the server. You'd then want to tell the router (under "port forwarding" or "Virtual servers") that external traffic to TCP port 443 should be forwarded to the same port on the internal ip address of your server.
Same would apply for pop (TCP 110) and (hopefully secured and authenticated) SMTP (traditionally on TCP 25, but in parallel ports like 587 or 465 may be used, since port 25 is stopped by many network operators.)
In addition, you need to know on what ports BES (the BlackBerry server) listens. I have no clue.
As a proof of concept, provided that your server has up to date internal firewall and AV security, you could try to TEMPORARILY enter the internal IP address of your server in the router setting for DMZ, so that all incoming traffic that isn't an obvious reply to previous outgoing traffic, will be thrown towards your internal server. But this should only be used temporarily, since the router would forward lots of bad things, as well.
One more thing, of your internet connection has dynamic ip address, then it's possible that the previous router was automatically updating a dyndns entry.
Finally, when you get everything to work:
1. Save a backup of the router configuration.
2. Note down the router settings you've done. (in case the replacement router won't construe the backup file you just saved.)