Okay so I was actually reading 2 threads here:

Extremly slow mail delivery

and

HELP - BES Delays Delivering Messages

unfortunately both threads are closed.

The thing is I have several (not all) users who experience extreme delays in email delivery to their BB.

BES --> Exchange server latency is: 512ms (this is quite "normal" for us though) - oh and yes we are in Asia and the Exchange server is in South africa..

MAGT 1 logs shows hundreds of this entry for the user:

[40266] (07/01 19:45:30.880):{0x16B4} {user@domain} Queuing new mail through rescan. EntryId=67552

[40266] (07/01 19:45:30.880):{0x16B4} {user@domain} Queuing new mail through rescan. EntryId=67551

[40266] (07/01 19:45:30.880):{0x16B4} {user@domain} Queuing new mail through rescan. EntryId=67550

[40266] (07/01 19:45:30.880):{0x16B4} {user@domain} Queuing new mail through rescan. EntryId=67549

I read on the other thread that this might be caused by an Exchange patch/update blocking UDP packets from BES?

If so, then it should be imperative that all users that has BB and with mailboxes hosted on this Exchange should experience delays too, right? hmmm..let me check with the others...

Do we have further documentation on this that I can show my Exchange admin?

Also, I nead to read on BES' UDP Packets too, any technical whitepaper on this as well?

Any info would be really appreciated!

any info guys?

Not normal for BES though.
Latency should be less than 35ms.
Your latency is way too high for normal operation.

I suspect the network issues are causing the UDP notify packets to be dropped, and this is what is causing your rescans and message delivery delays.

http://www.port3101.org/featured-bla...-exchange.html

im afraid we can not do anything with the latency from the side of the Exchange servers because it's there ISP's issues- what I am hoping to get at is that issue with the Exchange updates.

Thanks Penguin, but i'll open this up with my network colleagues too.

Why not just move your BES to the same LAN as the Exchange server?

I can't. ;)

Were on an inter-continental WAN.

2 BES serving 50+ Exchange servers scattered worldwide

any ideas? I am quoting this from the other thread:

There have been issues in the past with MS updates blocking UDP packets. Can't remember the specific updates.

Also, if your Exchange is remote and the link has high latency, there could be dropped UDP packets.

In your logs you will probably see "Queuing new mail through rescan" more than "Queuing new mail through notification"

What UDP packet is BES using? WHat UDP port? Thanks!

I do not have in depth knowledge about the "mapi advise" session protocol.
but, you can configure mapi to you static TCP ports.
If this also configures the mapi advise notifications to run over TCP (but I dont know this), most of your problems should be gone.

here:
Exchange Server static port mappings

is a description from M$ how to do this.

I don't know what you're looking for anyone to tell you.
Your BlackBerry environment is poorly designed and your WAN is too slow.
As a result, you're seeing all of the "classic" problems you should be seeing.

Either move your BES closer to Exchange... add more BES machines... or speed up your WAN. Ideally, do all of that.

thanks so the packet being said in the previous thread was just MAPI..MAPI is what BES uses to query the mailboxes anyway right? okay let me check on this..

@Penguin, I am not quite sure either what I need to look at, but I really have to start somewhere..

Improving our WAN is on the way, we are planning to have just 2 central Exchange servers- it's just that it's not going to be a fun and fast ride- we have to go through all the bureaucracy and all that..I wish we can just plan it in a month and implement in 3 months- but I think it's goin to take us years to consolidate all worldwide users into 2 Exchange servers in 2 sites- for the meantime my task is to put "patches" in these small wounds (classic problems as you call them)..

Thanks!

Give this a read: Managing BES <> Exchange Mappings - Port3101.org : Your BES Connection

I'd recommend giving this a try. Make sure no Exchange server is talking to both BlackBerry Enterprise Servers ... isolate users from a given mailbox server to a given BES. This'll help minimize the load on a given Messaging Agent.

Then, move users to other Exchange servers if you can, further isolating ... The last thing you should then do is implement the NumAgents registry key as it'll help ... but make sure you have enough resources on the BES.

hmm you never cease to amaze me..

let me read on that and discuss with my exchange admin- the way you wrote it in your site it seems to be a quite common issue. Was there any official move from RIM to actually address this?

There really isn't much of anything RIM can do short of not using MAPI ... which we'll hopefully see soon enough.

That said, I heard from WES last year that RIM uses 15 Messaging Agents per BES with a max of 100 users per agent. Now that info is over a year old and BES 5.0 has been deployed, so I'm not sure if it is different ... but that is how I heard it was with 4.x.

But honestly, as a first step you could at least minimize the number of Exchange servers each BES is communicating with ... move what users you can; it very well may fix the problems.