Skip to main content

Legitimate Emails going into Junk

Legitimate Emails going into Junk

  1. Pull out the headers of the email first either from Outlook or OWA. Please find attached documents to help with the same.

     
  2. Paste the headers in the message analyzer section in https://testconnectivity.microsoft.com.



  1. Click on Analyze headers button.

     
     



 
  1. Scroll down in the Other headers section and look for X-Forefront-Antispam-Report. In this you will find one attribute which says à SFV.

     

For more details about analyzing the X-Forefront-Antispam-Spam report you may please refer to this link à  https://technet.microsoft.com/en-IN/library/dn205071(v=exchg.150).aspx


Scenario 1: If the SFV is SFV: BLK

This would mean that the end user has blocked the sender of the email from his or her Outlook/OWA. Once you remove the sender from End User Blocked Sender list the issue would get fixed.

Scenario 2: If the SFV is SFV: SKS

This would mean that there is a transport rule create by one of the admins which is causing the emails to go into Junk. Once you check and modify/remove any such rules the issue would stand fixed.

Scenario 3: If the SFV is SFV: SPM

The email got marked as spam by the spam filtering service. Now the email could be from a known trusted sender for the recipient and might be a legitimate email but it matched one or the other criteria on the spam filter engine which marked it as spam.

In order to ensure that such emails do not go to Junk folder we can create a transport rule to bypass spam filtering for certain good senders of the users.

  • Go to office 365 portal using link outlook.office365.com/ecp
  • Go to Mail Flow à rules à Click on + symbol drop down à create a new rule.
  • Give it a name of your choice and select more options given at the end of the window in blue.
  • From Apply this rule if section à Select The Sender à is this person à In the pop up window please type in ID of the external sender in the box at the end and then click on check names. Please do this for other external senders as well.
  • From Do the following à Modify the message properties à set the spam confidence level à From drop down bypass spam filtering
  • Click on save to save the save rule. Once saved double click and edit the rule again and go to Priority option and set it to 0 and also tick mark the option Stop Processing more rules. Save the rule.



     

Comments

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...

Block users from saving data on System Drive on Intune Managed Device

Recently i delivered a project for Intune Deployment and came up with a requirement as follows End Users Should not be able to save data locally on C or D Drive, instead they should be allowed to save data only in One Drive for business (synced with System)  Based on the requirement i did my research and found the Following. its possible to control the Local System settings on a Azure AD joined Machine and Managed by Intune. There is no options to define exceptions in policies to allow data saving in certain folders.  Now most of us will think WIP (windows information protection) policy will help us protecting the data on device, however that's not completely true as . User can change the File Ownership to personal if the WIP policy is set to Allow Override. User can save the file locally on the system User will not be able to copy the data from work file to Personal file if policy is set to Allow override. Unenlightened apps cannot differentiate between personal and corporate...