Forum Discussion
How dynamic delivery works and why you sometimes have to wait for attachments
The answer is "it depends". Clearly, the volume of inbound traffic containing attachments that might need to be checked and the number of user accounts configured for this level of protection are contributory factors that might slow delivery. My practical assessment is that the delay ranges from a minute to three or four, depending on the time of day. Most of the time, it is around two minutes.
I see internal documents even with the transport rule in place taking 40 mins for a 10 page document. Little hard to tell a users to wait 40 min to open the document. Sending the users to web interface to have to relogin every time is cumbersome and then there is no review just blank screen. Microsoft has put little if any development into this product, to make it more administratively friendly, their answer is go outside the application to control product thru transport rules.
I don't see - and have never experienced - a 40 minute wait for attachments. Two minutes is about all I ever see, and it is pretty consistent. The wait is most obvious with mobile clients as you get notification for the original message and then another when the attachment is ready. But I do not see those extended delays that you report.
- The dual notification is the main reason I've reverted to "Replace" instead of "Dynamic". It's actually quite annoying.
Delays more in the area of minutes, but never excessive. Dual notification is indeed annoying - most users I talk to also prefer waiting bit (Replace) more rather than having 2 notifications (Dynamic) and having to wait for the 2nd one as they usually need the attachment.
