{"id":204,"date":"2010-03-17T10:06:13","date_gmt":"2010-03-17T15:06:13","guid":{"rendered":"http:\/\/www.ownwebnow.com\/blog\/2010\/03\/exchangedefender-grows-again\/"},"modified":"2010-03-17T10:09:26","modified_gmt":"2010-03-17T15:09:26","slug":"exchangedefender-grows-again","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2010\/03\/exchangedefender-grows-again\/","title":{"rendered":"ExchangeDefender Grows Again"},"content":{"rendered":"

First of all, thank you for your tremendous support of ExchangeDefender 5 and to all of our partners that make it possible for us to keep on building ExchangeDefender and growing it into a significant part of business. We\u2019re growing again \u2013 and with growth comes responsibility to do it in a way that is reliable and improves availability \u2013 so we\u2019re announcing a new IP address range that ExchangeDefender will soon start delivering mail from:<\/p>\n

\n

Introducing ExchangeDefender \u2013 LA3:<\/p>\n

206.125.40.0\/24 (or: 206.125.40.0\/255.255.255.0)<\/p>\n<\/blockquote>\n

If you are currently using IP restrictions (highly recommended) please add the range above to your IP restriction list which should include at least 65.99.255.0\/24 and 64.182.140.0\/24. You can download the Exchange 2003 and 2007 IP Restriction Guide here.<\/a> The process takes less than a minute so please take care of it as soon as possible, by March 29th, 2010 at the latest.<\/p>\n

For your convenience, here is a guide on how to add this new range to Exchange 2003 and 2007. If you\u2019re enforcing restrictions on your firewall then it will depend on the manufacturer but should be pretty straight forward.<\/p>\n

Exchange 2003<\/strong><\/h3>\n

1. Open Exchange System Manager <\/p>\n

2. Expand Servers, servername<\/b>, Protocols, SMTP <\/p>\n

3. Go to properties on Default SMTP Virtual Server <\/p>\n

4. Go to the Access Tab and then click connections <\/p>\n

\"clip_image001\"<\/a> <\/p>\n

5. Click Add on the IP restrictions and select Group of computers. The subnet address is 206.125.40.0\/24 <\/p>\n

\"clip_image002\"<\/a> <\/p>\n

Confirm that you still have at least 65.99.255.0\/255.255.255.0 and 64.182.140.0\/255.255.255.0 present. Do not remove any IP ranges. <\/p>\n

Exchange 2007<\/h3>\n

1. Open Exchange Management Console <\/p>\n

2. Expand Server Configuration and select Hub Transport <\/p>\n

\"clip_image003\"<\/a> <\/p>\n

3. On Exchange 2007 select Default servername<\/b> receive connector and go to properties <\/p>\n

a. On SBS, the connector may be called SBS servername<\/b> Internet <\/p>\n

4. Navigate to the Network tab and click add on Receive Mail from remote servers that have this IP address<\/b> and set the IP as 206.125.40.0\/24 <\/p>\n

\"clip_image004\"<\/a> <\/p>\n

Confirm that you still have at least 65.99.255.0\/255.255.255.0 and 64.182.140.0\/255.255.255.0 present. Do not remove any IP ranges. <\/p>\n

Support<\/font><\/h3>\n

If you have any questions or concerns please open a support request at https:\/\/support.ownwebnow.com<\/a>. We\u2019ll begin notifying clients via phone, email and postal mail (US only) starting 3\/17\/2010.<\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-204","post","type-post","status-publish","format-standard","hentry","category-exchangedefender"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=204"}],"version-history":[{"count":1,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/204\/revisions"}],"predecessor-version":[{"id":205,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/204\/revisions\/205"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}