<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Explaining the Mysterious SMTP Advanced Queuing Engine</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx</link><description>This time I have been asked to explain how Advanced Queuing behaves -- how retries work and when we decide to reroute mail. Since I’ve had plenty of questions on this in the past, buckle your seatbelts – this one is going to be interesting. Functions</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Explaining the Mysterious SMTP Advanced Queuing Engine</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx#403299</link><pubDate>Mon, 04 Apr 2005 23:33:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403299</guid><dc:creator>Jesse Cadd</dc:creator><description>Do you know of any way to dynamically reprioritize over-size messages so they won't clog the queue?  I'm not talking about having a different schedule for over-size messages, I know about that setting.  This would let messages flow anytime, but upon detecting a message of over...say...5mb leaving the server, it would set it to lowest priority so it would sit in the back of the queue until alle existing smaller messages were already sent?</description></item><item><title>re: Explaining the Mysterious SMTP Advanced Queuing Engine</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx#403356</link><pubDate>Tue, 05 Apr 2005 23:57:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403356</guid><dc:creator>Scott Landry</dc:creator><description>You are correct, there is no way to exactly what you are describing. I think the biggest reason is that there are plenty of situations where large messages on a busy server configured this way might not ever get a chance to go out.  It is an interesting problem though, so I'll take any offline feedback about why this feature could be important -- it would make a good discussion piece at least.&lt;br&gt;&lt;br&gt;Untested workaround: If you have multiple servers, you could in effect configure this using the max size limit on SMTP connectors and some sort of QOS -- but not on a single server.&lt;br&gt;&lt;br&gt;On a related note: a good best practice is to be mindful of your available bandwidth and load, and then set reasonable size limits. I have seen many a server that there was no mathematical way for the server to push the volume and size of messages through the small network that was available to it.</description></item><item><title>Exchange, Server, LCS, News</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx#403358</link><pubDate>Wed, 06 Apr 2005 00:26:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403358</guid><dc:creator>Windows Server Clustering </dc:creator><description /></item><item><title>re: Explaining the Mysterious SMTP Advanced Queuing Engine</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx#403384</link><pubDate>Wed, 06 Apr 2005 18:43:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:403384</guid><dc:creator>Jesse Cadd</dc:creator><description>How may I contact you offline?</description></item><item><title>Exchange, Server, LCS, News</title><link>http://blogs.technet.com/exchange/archive/2005/04/04/403297.aspx#404850</link><pubDate>Thu, 12 May 2005 04:38:41 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:404850</guid><dc:creator>Windows Server Clustering </dc:creator><description /></item></channel></rss>