05-09-2019 12:03 AM
05-09-2019 12:03 AM
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?
05-09-2019 03:13 AM
Attached the screenshot FYR
05-24-2019 04:58 AM
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?
05-25-2019 03:00 AM
We are working with Microsoft to fix this issue. Please share if you got any solution for this.
05-27-2019 06:30 AM
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 220.127.116.11) 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 18.104.22.168 as permitted sender) Received: from EUR04B.map.protection.outlook.com (22.214.171.124) 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: <email@example.com> Date: Mon, 27 May 2019 08:43:34 +0000 Sender: Werner in Microsoft Teams <firstname.lastname@example.org> 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 126.96.36.199) 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 188.8.131.52 as permitted sender) receiver=protection.outlook.com; client-ip=184.108.40.206; helo=RD00155D56BF15; Received: from RD00155D56BF15 (220.127.116.11) 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=?= <email@example.com> To: <firstname.lastname@example.org> Date: Fri, 24 May 2019 16:29:40 +0000 Subject: =?utf-8?B?TWFyYyBoYXQgZWluZSBOYWNocmljaHQgZ2VzZW5kZXQu?= Return-Path: email@example.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.)