<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spam on Anything About IT</title><link>https://www.verboon.info/tags/spam/</link><description>Recent content in Spam on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Jan 2020 13:54:51 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/spam/index.xml" rel="self" type="application/rss+xml"/><item><title>User Spam &amp; Phish Submissions configuration in Office 365 – Part 1</title><link>https://www.verboon.info/2020/01/user-spam-phish-submissions-configuration-in-office-365-part-1/</link><pubDate>Sun, 19 Jan 2020 13:54:51 +0000</pubDate><guid>https://www.verboon.info/2020/01/user-spam-phish-submissions-configuration-in-office-365-part-1/</guid><description>&lt;p&gt;Yesterday I noticed a &lt;a href="#"&gt;tweet&lt;/a&gt; from @Pawp81 about a new feature being rolled out in Office 365 to configure user submissions. So, let&amp;rsquo;s have a look at this. When enabling the &amp;lsquo;Report Message&amp;rsquo; add-in in Office 365, users can report misclassified email, whether safe or malicious, to Microsoft and its affiliates for analysis. Until now IT admins had to deploy the &amp;lsquo;Report Message&amp;rsquo; add-in to their end users by configuring the centralized add-in deployment within the Microsoft 365 admin center as described &lt;a href="#"&gt;here&lt;/a&gt; Furthermore when IT admins wanted to receive a copy of a reported message, a transport rule had to be created as described &lt;a href="#"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>