Improve Email Notification

Home
Improve Email Notification
 07-24-2016
13 Comments (13 New)
Completed

All (literally all) Office 365 Network notifications are getting held in Quarantine by Exchange Online Protection.

 

Can you make your messages less SPAMMY so they don't get flagged everytime?

 

Cheers,

Chris

5 Upvote
Comment
Comments
Valued Contributor

I know they are working on this, but will just add it here as well, if you are using a microsoft account (tied to Gmail), you dont even receive the messages at all (not even in spam/junk).

 

Kind of a big deal, especially if you arent gonna give us a mobile app to stay engaged.

Retired

Hi @Chris Moon - this is a known issue and we're working on it. We're also aware (per @Brent Ellis comment) that some users are not receiving email notifications at all. Thank you!

Retired
Status changed to: Under review
 
Community Manager
Status changed to: Completed

Email notifications should function properly now and not be blocked by spam/email gateways or put into clutter.

SPF still fail.

 

Received-SPF Fail (protection.outlook.com: domain of mstechcommunity.onmicrosoft.com does not designate 208.74.204.5 as permitted sender) receiver=protection.outlook.com; client-ip=208.74.204.5; helo=smtp.lithium.com;  

Occasional Contributor

Email notifications are still failing SPF check. SPF (fail (amnh.org: domain of notify@mstechcommunity.onmicrosoft.com does not designate 208.74.204.5 as permitted sender)).  

Occasional Contributor

Email Notifications from Microsoft Tech Community are failing SPF.  The reason being the SPF record for mstechcommunity.onmicrosoft.com has two lines which violates RFC (https://tools.ietf.org/html/rfc4408#section-3.1.2).  When checking the SPF record for mstechcommunity.onmicrosoft.com the following is returned:

 

mstechcommunity.onmicrosoft.com. 3599 IN TXT "v=spf1 include:spf.protection.outlook.com -all"

 

mstechcommunity.onmicrosoft.com. 3599 IN TXT "mstechcommunity.onmicrosoft.com. 3600 IN TXT v=spf1 include:spf.protection.outlook.com ip4:208.74.204.0/22 ip4:46.19.168.0/23 -all"

 

Since the notifications are coming from smtp.lithium.com[208.74.204.5] the SPF check will fail since only the 1st line is evaluated (The order in which the lines are resolved may vary depending on which dns servers are queried).  To correct this mstechcommunity needs to remove the first line listed and only publish the second line.

Regular Visitor

I received another quarantined email from notify@mstechcommunity.onmicrosoft.com just today and was notified by quarantine@messaging.microsoft.com.  Some how it seems a little odd that microsoft flags its own products.  

 

Doug

Community Manager
Status changed to: Planned
 
Community Manager

Hi all,

 

Sorry about the confusion on this Idea, your right its not fixed and we are working to fix it now. We will be changing the email address notifications come from as part of this change and I will post an announcement once the details have been ironed out. 

Community Manager
Status changed to: Completed

Just to let you know we have fixed this today, sorry it took so long. Please note that all notifications coming from the community will now come from notify@mstechcommunity.microsoft.com and will no longer be marked as spam.

New Contributor

I have seen many emails rejected due to Unknown Sender domain... there is no A record and also no MX record in DNS for mstechcommunity.microsoft.com

 

Do you have plans to fix that?

Community Manager
Status changed to: Completed
 
Similar Ideas
No similar ideas