<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Exchange Online (Office 365) Configuration and Setup &#8211; SpamHitman</title>
	<atom:link href="https://spamhitman.com/kb/exchange-online-office-365/feed/" rel="self" type="application/rss+xml" />
	<link>https://spamhitman.com</link>
	<description>Enterprise Grade Cloud Based Spam Filtering</description>
	<lastBuildDate>Fri, 14 Feb 2020 15:03:05 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.3.2</generator>

<image>
	<url>https://spamhitman.com/wp-content/uploads/2019/11/logo-shield.png</url>
	<title>Exchange Online (Office 365) Configuration and Setup &#8211; SpamHitman</title>
	<link>https://spamhitman.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Configure Office 365 with SpamHitman</title>
		<link>https://spamhitman.com/knowledgebase/configure-office-365-with-spamhitman/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=configure-office-365-with-spamhitman</link>
				<pubDate>Fri, 14 Feb 2020 14:30:11 +0000</pubDate>
		<dc:creator><![CDATA[admin]]></dc:creator>
		
		<guid isPermaLink="false">https://spamhitman.com/?post_type=knowledgebase&#038;p=1748</guid>
				<description><![CDATA[<p>Inbound filtering Basic steps to protect your domain: Ensure the destination route is set to the MX record hostname provided by Office 365. Add a rule to Office365 to ensure email from the filtering servers is always accepted and not wrongly classified as spam. Change the MX records of the domain in the DNS to [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://spamhitman.com/knowledgebase/configure-office-365-with-spamhitman/">Configure Office 365 with SpamHitman</a> appeared first on <a rel="nofollow" href="https://spamhitman.com">SpamHitman</a>.</p>
]]></description>
								<content:encoded><![CDATA[<h2><a name="overview"></a></h2>
<h2>Inbound filtering</h2>
<p>Basic steps to protect your domain:</p>
<ol>
<li value="1">Ensure the destination route is set to the <a href="https://docs.microsoft.com/en-us/previous-versions/exchange-server/exchange-150/mt595791(v=exchg.150)" target="_blank" rel="noopener noreferrer">MX record hostname provided by Office 365</a>.</li>
<li value="2">Add a rule to Office365 to ensure email from the filtering servers is always accepted and not wrongly classified as spam.</li>
<li value="3">Change the MX records of the domain in the DNS to point to the <span class="GeneralSEProductName">Spam</span>Hitman provided MX record hostnames.</li>
</ol>
<h3>IP based rule to always accept from the filtering servers</h3>
<p>In your Office 365 environment, you can create a partner connector and rule to bypass the local spam filtering for the filtering IPs.</p>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="1">Log in to the Exchange Admin Center.</li>
<li value="2">Click <b>on mail flow &gt; connectors</b>.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/flow-connect.png" /></p>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="3">Click the + (plus sign).</li>
<li value="4">Choose <b>Partner organization</b> as the <b>From</b> and <b>Office 365</b> as the <b>To</b>, then click <b>Next</b>.</li>
<li value="5">Give the connector a name, then click <b>Next</b>.</li>
<li value="6">Choose <b>Use the sender&#8217;s IP addres</b>s then click <b>Next.</b></li>
<li value="7">Add the <span class="GeneralSEProductName">SpamHitman</span> IPs listed in <a class="MCXref xref" href="/knowledgebase/delivery-ips/">Delivery IPs</a>.</li>
<li value="8">Ensure that <b>Reject email messages if they aren&#8217;t sent over TLS</b> is ticked and click <b>Next</b>.</li>
<li value="9">Verify the settings and click <b>Save</b>.</li>
<li value="10">Click on <b>Mail flow &gt; Rules</b>.</li>
<li value="11">Under <b>Rules</b>, click on the <b>+</b> (plus button) and choose <b>Bypass spam filtering&#8230;</b> .</li>
<li value="12">Enter a rule name (e.g. Disable filtering for <span class="GeneralSEProductName">SpamHitman</span>).</li>
<li value="13">Choose <b>Apply this rule if&#8230; &gt; Senders IP Address is in any of these ranges or exactly matches&#8230;</b></li>
<li value="14">Add the <span class="GeneralSEProductName">SpamHitman</span> delivery IPs listed in <a class="MCXref xref" href="/knowledgebase/delivery-ips/">Delivery IPs</a>.</li>
<li value="15">Ensure that <b>Do the following&#8230;</b> is set to: <b>Modify the message properties &gt; Set the spam confidence level (SCL) &gt; Bypass spam filtering</b>.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/new-rule2.png" /></p>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="16">Click <b>OK</b>.</li>
<li value="17">Click <b>Save</b>.</li>
</ol>
</li>
</ol>
<p>Spam filtering will no longer apply to the filtering servers, avoiding Office 365 to wrongly mark legitimate emails as spam (e.g. because SPF would fail).</p>
<h3>X Header based rule to accept email from the filtering servers</h3>
<p>The disadvantage of this method is that spammers could technically spoof the header, hence bypassing the build-in filtering. The advantage is that no IP addresses are required to be kept up-to-date.</p>
<ol>
<li value="1">Login to the Office 365 &#8220;Exchange admin center&#8221;.</li>
<li value="2">In the Dashboard, select <b>Rules</b> in the <b>Mail Flow</b> section</li>
<li value="3">Under <b>Rules</b>, click the <b>+</b> button and choose <b>Create a new rule&#8230;</b> .</li>
<li value="4">Enter a <b>Name</b> for your rule, e.g. &#8216;<span class="GeneralSEProductName">SpamHitman</span> spamfilter bypass&#8217;.</li>
<li value="5">Click <b>More Options</b>.</li>
<li value="6">Create Rule <i>&#8220;A message header includes&#8221;X-Recommended-Action&#8221; header includes &gt;&gt; contains &#8220;accept&#8221;</i>.</li>
<li value="7">Click <b>+</b>.</li>
<li value="8">Click <b>OK</b>.</li>
<li value="9">In the &#8220;Do the following&#8221; part, select &#8220;<b>Modify the message properties&#8221; &gt; &#8220;Set the spam confidence level (SCL)&#8221; &gt; &#8220;Specify SCL&#8221; &gt; &#8220;Bypass spam filtering&#8221;</b>.</li>
<li value="10">Click <b>OK</b>.</li>
</ol>
<h2>Outbound filtering</h2>
<p>Basic steps to protect your domain&#8217;s outbound mailflow, you need to:</p>
<ol>
<li value="1">Add your sender Office365 sender domain as an &#8220;Authenticating Domain&#8221;, with &#8220;Re-authentication permitted:&#8221; explicitly set</li>
<li value="2">Setup a connector in Office 365 to relay the outgoing email via the email security smarthost</li>
</ol>
<h3>Setup outbound user in <span class="GeneralSEProductName">SpamHitman</span></h3>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="1">Go to the domain dashboard, choose <b>Outgoing &gt; Manage Users</b>.</li>
<li value="2">At the bottom of the page, select the &#8220;<b>Authenticating Domain</b>&#8221; tab. Specify your Office365 sending domain, and provide a secure random password.</li>
<li value="3">Once the user has been added, click the dropdown icon on the left of the user and select &#8220;<b>Edit</b>&#8220;.</li>
<li value="4">Verify the configuration and ensure the limits are either disabled or match your expected traffic.</li>
<li value="5">Ensure &#8220;<b>Re-authentication permitted</b>&#8221; is selected. This is required for the sending domain to be allowed from Office365.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/re-auth-perm.png" /></p>
<ol>
<li value="6">Save the user settings.</li>
</ol>
<h3>Setup a transport rule in Office 365</h3>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="1">Login to the Office365 &#8220;Exchange admin center&#8221;.</li>
<li value="2">In the dashboard, go to <b>Connectors</b> in the <b>Mail Flow</b> section.</li>
<li value="3">Create a new connector from <i>Office365 to Partner Organization</i> and give it a name.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/new-connector1.png" /></p>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="4">Select <b>Only when I have a transport rule set up that redirects messages to this connector</b>.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/rule3.png" /></p>
<ol>
<li style="list-style-type: none;">
<ol>
<li value="5">Select &#8220;<b>Route email through these smart hosts</b>&#8221; and add <b>port25.smtp.antispamcloud.com</b>.</li>
<li value="6">Check <b>Always use Transport Layer Security (TLS) to secure the connection (recommended)</b> and select <b>Issued by a trusted certificate authority (CA)</b>.</li>
</ol>
</li>
</ol>
<p><img src="https://res.cloudinary.com/qbic-internet-solutions/image/upload/spamhitman/rule4.png" /></p>
<ol>
<li value="7">Validate the connector (e.g. using recipient no-reply@antispamcloud.com) and save.</li>
<li value="8">In the Exchange Dashboard, go to <b>Rules</b> in the <b>Mail Flow</b> section.</li>
<li value="9">Under <b>Rules</b>, click the <b>+</b> button and choose <b>Create a new rule&#8230;</b> .</li>
<li value="10">Enter a Name for your rule, e.g. &#8216;Route sending domain via filtering smarthost&#8217;.</li>
<li value="11">Click <b>More Options</b>.</li>
<li value="12">Set &#8220;<b>Apply this rule if&#8230;</b>&#8221; to &#8220;<b>The sender&#8217;s domain is&#8230;</b>&#8220;.</li>
<li value="13">Specify as sender domain the domain you previously added as an &#8220;Authentication Domain&#8221; outgoing user to <span class="GeneralSEProductName">SpamHitman</span> (similarly you could setup a rule for specific senders addresses only).</li>
<li value="14">Set &#8220;<b>Do the following&#8230;</b>&#8221; to &#8220;<b>Redirect the message to</b>&#8220;, &#8220;<b>The following connector</b>&#8220;.</li>
<li value="15">Set the smarthost connector you previous created.</li>
<li value="16"><b>Save</b> the rule.</li>
</ol>
<p>Once this is done, any traffic matching your outgoing sender domain is relayed via the transport rule and be processed by the filtering servers.</p>
<p>The post <a rel="nofollow" href="https://spamhitman.com/knowledgebase/configure-office-365-with-spamhitman/">Configure Office 365 with SpamHitman</a> appeared first on <a rel="nofollow" href="https://spamhitman.com">SpamHitman</a>.</p>
]]></content:encoded>
										</item>
	</channel>
</rss>
