{"id":1427,"date":"2014-05-14T11:17:39","date_gmt":"2014-05-14T11:17:39","guid":{"rendered":"https:\/\/modern-workplace.uk\/\/?p=1427"},"modified":"2014-05-14T11:32:10","modified_gmt":"2014-05-14T11:32:10","slug":"exchange-2007-fortigate-utmerror-451-4-4-0-error-400-4-4-7","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=1427","title":{"rendered":"Exchange 2007, FortiGate UTM,Error 451 4.4.0 and Error 400 4.4.7"},"content":{"rendered":"<h5><strong>Scenario:<\/strong><\/h5>\n<p>Exchange 2007 (no Edge, one server with mailbox role, one server with hub+cas roles) behind a FortiGate appliance<\/p>\n<hr \/>\n<p><strong>Problem:<\/strong><\/p>\n<p>As soon as the UTM part of the FortiGate appliance is enabled, I had a lot of 451 4.4.0 and 400 4.4.7 errors shown in the message queue (outgoing)<\/p>\n<hr \/>\n<p><strong>Solution:<\/strong><\/p>\n<p>First, I had to check the Connectivitytimeout value for the send connector. Fortinet support pointed out that enabling ANY UTM check will add a delay that Exchange could not accept (it is something regarding incoming and outgoing mail, by the way). So, from the Exchange Management Shell I used<\/p>\n<p>&nbsp;<\/p>\n<pre><em>Get-SendConnector | fl<\/em><\/pre>\n<p>&nbsp;<\/p>\n<p>The value was 10 minutes, so no problem here<\/p>\n<p>&nbsp;<\/p>\n<pre><em>ConnectionInactivityTimeOut \u00a0: 00:10:00<\/em><\/pre>\n<p>&nbsp;<\/p>\n<p>With a little bit of search, I have noticed that the problems was limited to a list of specific domains and it looked like something related to the use of HELO.<\/p>\n<p>This post\u00a0<a href=\"http:\/\/www.networkadminsecrets.com\/2010\/04\/421-and-451-exchange-2007-errors.html\">http:\/\/www.networkadminsecrets.com\/2010\/04\/421-and-451-exchange-2007-errors.html<\/a>\u00a0was really useful and\u00a0I have tried the suggested cmdlet<\/p>\n<p>&nbsp;<\/p>\n<pre><em>New-SendConnector -Name ForceHelo -AddressSpaces problemdomain.com -ForceHELO $true<\/em><\/pre>\n<p><em><br \/>\n<\/em>It worked. Probably one of the UTM filters expected to open the connection with the external domain using HELO. I will investigate this one with people inside Fortinet, to have a confirmation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Scenario: Exchange 2007 (no Edge, one server with mailbox role, one server with hub+cas roles) behind a FortiGate appliance Problem: As soon as the UTM part of the FortiGate appliance is enabled, I had a lot of 451 4.4.0 and 400 4.4.7 errors shown in the message queue (outgoing) Solution: First, I had to check [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1432,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":"","footnotes":""},"categories":[18,198,14],"tags":[560,561,564,557,558,563,562,568,565,566,704,559,567],"class_list":["post-1427","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-english","category-fortigate","category-microsoft","tag-400-4-4-7","tag-451-4-4-0","tag-connectioninactivitytimeout","tag-exchange-2007","tag-exchange-2007-utm","tag-exchange-400-4-4-7","tag-exchange-451-4-4-0","tag-exchange-smtp-connector","tag-forcehelo","tag-forcehelo-true","tag-fortigate","tag-fortigate-utm-exchange","tag-queue"],"_links":{"self":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/1427","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1427"}],"version-history":[{"count":3,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/1427\/revisions"}],"predecessor-version":[{"id":1431,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/1427\/revisions\/1431"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/media\/1432"}],"wp:attachment":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1427"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1427"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}