Home

Missing sender name - notification from Teams in outlook

%3CLINGO-SUB%20id%3D%22lingo-sub-551284%22%20slang%3D%22en-US%22%3EMissing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-551284%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20you%20receive%20notification%20from%20Teams%20in%20outlook%2C%20please%20watch%20out%20the%20%22Sender%20Name%22%20.%20Some%20times%20sender%20name%20missing%20in%20the%20conversation%2C%26nbsp%3B%20It%E2%80%99s%20not%20consistent%20and%20neither%20is%20replicable%20on%20demand.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20facing%20the%20same%20issue%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EJenkins%20NS%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-551284%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-551294%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-551294%22%20slang%3D%22en-US%22%3EHaven%E2%80%99t%20seen%20this!%20Do%20you%20have%20a%20screenshot%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-551984%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-551984%22%20slang%3D%22en-US%22%3E%3CP%3EAttached%20the%20screenshot%20FYR%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-551986%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-551986%22%20slang%3D%22en-US%22%3E%3CP%3EAttached%20the%20screenshot%20FYR%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552026%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552026%22%20slang%3D%22en-US%22%3E%3CBR%20%2F%3EThanks!%20Haven%E2%80%99t%20seen%20this!%20Is%20this%20user%20still%20existing%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552043%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552043%22%20slang%3D%22en-US%22%3EYes%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-643535%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-643535%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20facing%20this%20issue%20as%20well.%20Most%20teams%20notifications%20have%20the%20correct%20sender%2C%20but%20some%20mails%20don't%2C%20regardless%20of%20the%20person%20who%20tried%20to%20reach%20the%20recipient.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20news%20on%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ekind%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-645915%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-645915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F348142%22%20target%3D%22_blank%22%3E%40Soeren_Fuhrmann%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20working%20with%20Microsoft%20to%20fix%20this%20issue.%20Please%20share%20if%20you%20got%20any%20solution%20for%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-650312%22%20slang%3D%22en-US%22%3ERe%3A%20Missing%20sender%20name%20-%20notification%20from%20Teams%20in%20outlook%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-650312%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77952%22%20target%3D%22_blank%22%3E%40Jenkins%20Nesamony%20Sundararaj%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20case%20might%20be%20slightly%20different%20from%20yours%2C%20since%20outlook%20web%20shows%20the%20sender%20name%20correctly.%20Only%20mail%20clients%20are%20missing%20the%20%22From%22%20header%20completely.%20Subsequently%20the%20%3CSPAN%20class%3D%22ILfuVd%22%3E%3CSPAN%20class%3D%22e24Kjd%22%3ESender%20Policy%20Framework%20soft-fails%20checking%20the%20wrong%20domain.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EAuthentication-Results%3A%20spf%3Dsoftfail%20(sender%20IP%20is%2052.114.88.14)%0A%20smtp.mailfrom%3Dgolem.de%3B%20golem.de%3B%20dkim%3Dnone%20(message%20not%20signed)%0A%20header.d%3Dnone%3Bgolem.de%3B%20dmarc%3Dnone%20action%3Dnone%20header.from%3D%3B%0AReceived-SPF%3A%20SoftFail%20(protection.outlook.com%3A%20domain%20of%20transitioning%0A%20golem.de%20discourages%20use%20of%2052.114.88.14%20as%20permitted%20sender)%0AReceived%3A%20from%20EUR04B.map.protection.outlook.com%20(52.114.88.14)%20by%0A%20DB3EUR04FT046.mail.protection.outlook.com%20(10.152.25.36)%20with%20Microsoft%20SMTP%0A%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%0A%2015.20.1922.16%20via%20Frontend%20Transport%3B%20Mon%2C%2027%20May%202019%2008%3A43%3A34%20%2B0000%0ASubject%3A%20%3D%3Futf-8%3FB%3FV2VybmVyIGhhdCBlaW5lIE5hY2hyaWNodCBnZXNlbmRldC4%3D%3F%3D%0ATo%3A%20%26lt%3Bxxx%40golem.de%26gt%3B%0ADate%3A%20Mon%2C%2027%20May%202019%2008%3A43%3A34%20%2B0000%0ASender%3A%20Werner%20in%20Microsoft%20Teams%20%26lt%3Bno_reply%40email.teams.microsoft.com%26gt%3B%0AEncoding%3A%20utf-8%3C%2FPRE%3E%3CP%3E%3CSPAN%20class%3D%22ILfuVd%22%3E%3CSPAN%20class%3D%22e24Kjd%22%3EThe%20%22Sender%22%20header%20is%20present%2C%20but%20the%20%22From%22%20header%20is%20not.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22ILfuVd%22%3E%3CSPAN%20class%3D%22e24Kjd%22%3EAs%20comparison%3A%20a%20teams%20notification%20with%20sender%20name%20present%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CPRE%3EAuthentication-Results-Original%3A%20spf%3Dpass%20(sender%20IP%20is%2052.114.76.65)%0A%20smtp.mailfrom%3Demail.teams.microsoft.com%3B%20golem.de%3B%20dkim%3Dnone%20(message%20not%0A%20signed)%20header.d%3Dnone%3Bgolem.de%3B%20dmarc%3Dpass%20action%3Dnone%0A%20header.from%3Demail.teams.microsoft.com%3B%0AReceived-SPF%3A%20Pass%20(protection.outlook.com%3A%20domain%20of%0A%20email.teams.microsoft.com%20designates%2052.114.76.65%20as%20permitted%20sender)%0A%20receiver%3Dprotection.outlook.com%3B%20client-ip%3D52.114.76.65%3B%20helo%3DRD00155D56BF15%3B%0AReceived%3A%20from%20RD00155D56BF15%20(52.114.76.65)%20by%0A%20BY2NAM05FT050.mail.protection.outlook.com%20(10.152.100.187)%20with%20Microsoft%0A%20SMTP%20Server%20(version%3DTLS1_2%2C%20cipher%3DTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384)%20id%0A%2015.20.1922.10%20via%20Frontend%20Transport%3B%20Fri%2C%2024%20May%202019%2016%3A29%3A40%20%2B0000%0AFrom%3A%20%3D%3Futf-8%3FB%3FTWFyYyBTYXV0ZXIgfCBHb2xlbS5kZSBpbiBNaWNyb3NvZnQgVGVhbXM%3D%3F%3D%0A%20%26lt%3Bnoreply%40email.teams.microsoft.com%26gt%3B%0ATo%3A%20%26lt%3Bxxx%40golem.de%26gt%3B%0ADate%3A%20Fri%2C%2024%20May%202019%2016%3A29%3A40%20%2B0000%0ASubject%3A%20%3D%3Futf-8%3FB%3FTWFyYyBoYXQgZWluZSBOYWNocmljaHQgZ2VzZW5kZXQu%3F%3D%0AReturn-Path%3A%20noreply%40email.teams.microsoft.com%3C%2FPRE%3E%3CP%3EIt%20features%20%22From%22%20and%20%22Return-Path%22%20headers%2C%20and%20passes%20SPF.%20Instead%2C%20the%20%22Sender%22%20header%20is%20not%20present.%20(It%20also%20has%20a%20DKIM%20signature%2C%20which%20adds%20Authentication%20Results.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Jenkins Nesamony Sundararaj
Contributor

Hi All,

 

When you receive notification from Teams in outlook, please watch out the "Sender Name" . Some times sender name missing in the conversation,  It’s not consistent and neither is replicable on demand.

 

Anyone facing the same issue? 

 

Regards

Jenkins NS

 

8 Replies
Haven’t seen this! Do you have a screenshot?

Adam

Attached the screenshot FYR

 

Highlighted

Thanks! Haven’t seen this! Is this user still existing?

Hi,

 

We are facing this issue as well. Most teams notifications have the correct sender, but some mails don't, regardless of the person who tried to reach the recipient.

 

Are there any news on this?

 

kind regards

@Soeren_Fuhrmann 

We are working with Microsoft to fix this issue. Please share if you got any solution for this. 

@Jenkins Nesamony Sundararaj 

My case might be slightly different from yours, since outlook web shows the sender name correctly. Only mail clients are missing the "From" header completely. Subsequently the Sender Policy Framework soft-fails checking the wrong domain.

 

Authentication-Results: spf=softfail (sender IP is 52.114.88.14)
 smtp.mailfrom=golem.de; golem.de; dkim=none (message not signed)
 header.d=none;golem.de; dmarc=none action=none header.from=;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
 golem.de discourages use of 52.114.88.14 as permitted sender)
Received: from EUR04B.map.protection.outlook.com (52.114.88.14) by
 DB3EUR04FT046.mail.protection.outlook.com (10.152.25.36) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
 15.20.1922.16 via Frontend Transport; Mon, 27 May 2019 08:43:34 +0000
Subject: =?utf-8?B?V2VybmVyIGhhdCBlaW5lIE5hY2hyaWNodCBnZXNlbmRldC4=?=
To: <xxx@golem.de>
Date: Mon, 27 May 2019 08:43:34 +0000
Sender: Werner in Microsoft Teams <no_reply@email.teams.microsoft.com>
Encoding: utf-8

The "Sender" header is present, but the "From" header is not.

 

As comparison: a teams notification with sender name present:

Authentication-Results-Original: spf=pass (sender IP is 52.114.76.65)
 smtp.mailfrom=email.teams.microsoft.com; golem.de; dkim=none (message not
 signed) header.d=none;golem.de; dmarc=pass action=none
 header.from=email.teams.microsoft.com;
Received-SPF: Pass (protection.outlook.com: domain of
 email.teams.microsoft.com designates 52.114.76.65 as permitted sender)
 receiver=protection.outlook.com; client-ip=52.114.76.65; helo=RD00155D56BF15;
Received: from RD00155D56BF15 (52.114.76.65) by
 BY2NAM05FT050.mail.protection.outlook.com (10.152.100.187) with Microsoft
 SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
 15.20.1922.10 via Frontend Transport; Fri, 24 May 2019 16:29:40 +0000
From: =?utf-8?B?TWFyYyBTYXV0ZXIgfCBHb2xlbS5kZSBpbiBNaWNyb3NvZnQgVGVhbXM=?=
	<noreply@email.teams.microsoft.com>
To: <xxx@golem.de>
Date: Fri, 24 May 2019 16:29:40 +0000
Subject: =?utf-8?B?TWFyYyBoYXQgZWluZSBOYWNocmljaHQgZ2VzZW5kZXQu?=
Return-Path: noreply@email.teams.microsoft.com

It features "From" and "Return-Path" headers, and passes SPF. Instead, the "Sender" header is not present. (It also has a DKIM signature, which adds Authentication Results.)

 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies