Hmm, ok. I'm used to having separate send and receive policies. Personally I wouldn't worry about Exchange generating a massive flood of messages while it was down but it was just a suggestion. Our relay eventually stops accepting connections if there are so many thousands of messages queued that disk space gets tight. It is meant to be a buffer at which to accept and queue messages in case we experience Exchange or SAN or other infrastructure problems.
Environments differ - good luck. --------------------------------- Sent from my BlackBerry Wireless Handheld ________________________________ From: Sobey, Richard A <r.so...@imperial.ac.uk> To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> Sent: Thu Jul 02 04:07:26 2009 Subject: RE: MaxMessagesPerConnection - Exchange 2007 As far as I understand it the threshold [of 10] at which the smarthost pushes the mail into a lesser priority queue is a global setting that cannot be changed for specific MTAs. ����ve been told that increasing that figure could, in circumstances such as Exchange going down and then sending a massive volume of mail through afterwards, crash the smarthost. Richard From: bounce-8584092-8066...@lyris.sunbelt-software.com [mailto:bounce-8584092-8066...@lyris.sunbelt-software.com] On Behalf Of Don Andrews Sent: 01 July 2009 16:42 To: MS-Exchange Admin Issues Subject: RE: MaxMessagesPerConnection - Exchange 2007 I was just thinking that 10 messages per connection seems a bit low for a threshol����� our smarthost (actually an appliance) has 25 connections or 500 messages in a 5 minute window as the thresholds for DOS attacks at which point it implements throttling for an hour ��� of course, it only applies this check in inbound connection����� internal servers are presumed to not be the source of poor behavior. Do you have a way to exclude your HT server(s) from this check? ________________________________ From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Wednesday, July 01, 2009 12:55 AM To: MS-Exchange Admin Issues Subject: RE: MaxMessagesPerConnection - Exchange 2007 Hi Don, It is our smart host. We have discussed several workarounds to resolve the issue (including installing additional HT servers to minimise the frequency at which Exchange sends through >10 messages at once) but ideally w����d like t�����f����� Exchange to the 2003 behaviour. Cheers Richard From: bounce-8583005-8066...@lyris.sunbelt-software.com [mailto:bounce-8583005-8066...@lyris.sunbelt-software.com] On Behalf Of Don Andrews Sent: 30 June 2009 17:19 To: MS-Exchange Admin Issues Subject: RE: MaxMessagesPerConnection - Exchange 2007 Can your smart hos����s configuration be modified? or is it your ISP���s server? ________________________________ From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, June 29, 2009 6:26 AM To: MS-Exchange Admin Issues Subject: MaxMessagesPerConnection - Exchange 2007 Hi all Since I have updated our send connectors on Exchange 2007 to use our HT servers to route mail to our smart host, it seems to be sending throug�����too man���� messages per connection. The smart host is thus delaying delivery of those message by up to 15 minutes as it thinks i����s bulk mail (for info, it rejects mail after 10 messages in any single connection). On Exchange 2003, there was a nice setting calle�����Maximum messages per connection��� on the SMTP virtual server tab which now, unfortunately, seems to be absent. Does anyone know a) How many messages per connection Exchange 2007 can submit, and if that value can be changed; b) If not, a creative solution of how to get around this, bar accepting the 15 minute delay, or making unwanted changes elsewhere? Cheers Richard
