Report mail as a spam\junk to Microsoft
One of the most popular Exchange user’s request is related to the ability of: reporting about a specific mail as a “spam\junk mail”
We will not get into a philosophical debate, about the definition and the charters of spam\junk mail or, why a specific E-mail is entitled to be classified as spam\junk mail, but instead, we will focus on how can we report mail as a spam\junk to Microsoft.
The second article in this two article series (Report mail as a spam – junk to Microsoft part 2#2) is an “how to” article, that focuses on the different way that we can use for: report mail as a spam\junk to Microsoft or the contrary scenario, in which we want to report a about a legitimate mail, is classified by mistake as a spam\junk mail.
The term that we use in the current article
In the current article, we will use a combination of two terms that have the same meaning: spam mail and Junk mail. The formal Microsoft articles use the term: Junk, but most of our users use the term: spam. The simple meaning of these two terms is: un-wanted mail.
What is the meaning of: Report mail as a spam\junk to Microsoft?
Microsoft provides a service which enables mail recipients, to report a specific mail item\s as a spam\junk mail. The “element” that receives mail that was reported as a spam\junk described as: Microsoft Spam Analysis Team
Who are the clients that are entitled to use these services?
Well, the answer is not clear because the formal Microsoft article deal with instructions of: How to “report mail as a spam to Microsoft?” and, doesn’t relate to the question of: who are the customers who are entitled to report mail as spam\junk to Microsoft?
In my opinion, the answer is: everyone. Every user who uses Outlook or OWA client and theoretically, even non-Microsoft mail clients that known by E-mail address of the Microsoft Spam Analysis Team.
It looks like the main difference between any “Outlook\OWA” user and Microsoft’s customer such as: Office 365 customers or another type of Microsoft’s customers, is that the “Microsoft customers” have the ability to call a support in case that the option of: “report mail as a spam\junk to Microsoft” fails or doesn’t provide the required results.
False negative versus False positive message
A very popular misses conception among users and sometimes among IT persons, is that we are living in a perfect world, in which
- Our mail client and our mail infrastructures could and would, provide a perfect protection of blocking any kind of spam\junk mail
- Our mail client and our mail infrastructures could and would guess in advance, what are the mail items that in our opinion, should be classified as spam\junk mail
- Prevent the event, in which a legitimate mail is classified by mistake as a junk mail
(And I thought that my dream to look like Brad Pitt was hallucinatory).
In the real world, we will need to need to manage our mail data, hoping that most of the time we can rely on our mail security infrastructure to do a “good work” of protecting us and sometimes, we will need to “help our guard” by “inform him” about one of the passable scenarios:
How can the Microsoft Spam Analysis Team help us with False positive and False negative scenarios?
The answer is by providing us a way to report about two different scenarios:
- False negative – a scenario in which “bad mail items” (spam\junk mail) manage to go unnoticed and the mail appears as a legitimate mail.
- False positive – a scenario in which a legitimate mail, is classified by mistake as a spam\junk mail.
What is the E-mail address of the Microsoft Spam Analysis Team?
The formal E-mail address of the Microsoft Spam Analysis Team that appears in the article: Submitting spam and non-spam messages to Microsoft for analysis are:
- Report about Spam\junk mail – junk@office365.microsoft.com
- Report about non Spam\junk mail – not_junk@office365.microsoft.com
At the current time, when we use Outlook client and the Junk E-mail Reporting Add-in for Microsoft Office Outlook, the “report mail” is sent to the following E-mail address: abuse@messaging.microsoft.com
When using OWA mail client for reporting mail as a: spam\junk mail (or non- spam\junk mail), the email addresses are as specified above ( junk@office365.microsoft.com and not_junk@office365.microsoft.com).
Why do I get spam\junk mail and what doesn’t the spam\junk mail sent automatically to the junk mail folder?
There are two main passable answers to this question:
- Answer 1: the mail is not a spam\junk mail. The fact that users relate to a specific mail item as a “spam\junk” doesn’t mean that the mail is indeed a spam\junk mail.
- Answer 2: the other option for the phenomena in which spam\junk mail is not recognized or classified as a: spam\junk mail described as: false positive. The meaning of this fancy term is that a spam\junk mail manages to “dodge” the mail security infrastructure and although the specific mail was supposed to be recognized as a spam\junk mail, it was not!
What are the available option for me?
There a two major option for reporting spam\junk mail (and non-spam\junk mail) to the Microsoft Spam Analysis Team:
- Manually sending email to the Microsoft Spam Analysis Team – to be able to report a specific mail as: spam\junk mail (or non-spam\junk mail) we can attach the original mail to an “empty mail message”
- Using Outlook and OWA interface – another option that is available for use and, which will be reviewed in details is using the Outlook and OWA menu option to report a specific mail as: spam\junk mail (or non-spam\junk mail).
What do the spam\junk mail analyses include?
This is a good question. The formal answer that is provided in the Microsoft article is: Submitting Spam and non-Spam messages to Microsoft for analysis
The Spam analysis team examines your submitted messages and adjusts the Spam filters accordingly in order to prevent future abuse. As a result, the service is constantly updating and refining the Spam prevention and protection processes. Any submitted items are evaluated at the network-wide level. False-positive submissions are examined and assessed for possible rule adjustment to allow future messages through the Spam filters. Therefore, notifying the service of false positives and also unfiltered Spam is advantageous for you and all customers using the global network. The Spam team examines indicators within each submitted message, such as the following:
- From address
- Sending IP address
- Keywords
- Phrases
- Frequency of transmission
- Other trends and patterns
Reporting about spam\junk mail – the black box syndrome
Ok, and now let’s take about the most obvious question that probably appear in your mind throughout the article: how do I know that the “reporting process of mail as a spam\junk is effective?
- How do I know if someone gets my report about the spam\junk mail?
- How do I know if the Microsoft Spam Analysis Team actually refers to my report, analyzes the specific mail items and adds the information to the “mail security gateway database”?
- How do I know if: the sender of the spam\junk mail will appear in a black list?
Well, like it or not, the simple answer is that probably, we will never get a strict answer to these questions.
As far as I know, there is no formal response or a “follow up” mail that sends to update us about the status of the report that we have sent.
All that we can do is hope that if the mail is really a spam\junk mail, the Microsoft Spam Analysis Team, will classify this mail as a spam\junk mail and implement the proper action as it sees.
The dilemma: manual report spam\junk mail or contact Office 365 Microsoft support?
A popular miss concept of Office 365 customers are that in a scenario in which, an Office 365 users or users report about the “issue” of: “getting spam\junk mail” the best solution is to contact the Office 365 Microsoft support and require firmly, that the issue will be reported and informed up to the highest level!
Other fewer popular options are to use the option of report mail as a spam\junk, by using the available option in OWA or Outlook mail clients.
The answer is by providing us a way to report about two different scenarios the two following reasons:
- The opinion of the user; – If a user says the mail is spam\junk mail, our professional commitment is to verify and check the specific incident. Is it a scenario of “spam\junk mail flood” or, just a minor number of spam\junk mails?
Does the mail that the user “tag” as a spam\junk mail relay a spam\junk or an “Innocent marketing mail”? - Choosing the most effective and fastest solution – In my humble opinion, the most effective and fastest solution is using the OWA\Outlook report mail as a spam\junk option because, all you need to do is to right click on your mouse button and choose the report as junk option.
My point is: that I think that the most effective way simply reports the “problematic” mail by using one of the options that we will review in the next article. Only in very special scenarios, we will need to use the option of contacting the Microsoft support team and report or consult the issue with a “real person”.
This is the simplest and, the easiest way that we can choose for “delivering” the mail that we consider as spam\junk mail the “right place” and to the “right people” that could help us!
Additional reading
- Junk Email Reporting in OWA
- How to report Spam that arrives in Office 365 to Microsoft
- Submitting Spam and non-Spam messages to Microsoft for analysis
- The Junk Email Reporting Add-in doesn’t appear in Outlook
- Anti-Spam Protection FAQJunk Email Reporting Add-in for Microsoft Office Outlook
- Anti-Spam and Anti-Malware Protection
A quick reference for the article series
![]() |
Report mail as a spam – junk to Microsoft part 2#2 This is the second article of a series of two articles that classified as: “how to” article, that focuses on the different way that we can use for: report mail as a spam\junk to Microsoft or the contrary scenario in which we want to report a about a legitimate mail, is classified by mistake as a spam\junk mail. |
We really want to know what you think about the article
The post Report mail as a spam – junk to Microsoft part 1#2 appeared first on o365info.com.