{Question / Suggestion} - Is there a way to email files or links directly from Teams?
Hello! I am wondering if there is a way from the Teams desktop app to select a file and either email the link, or a current copy of the file, directly to an email address? This could be useful for possibly keeping a dated log of progress by emailing current copies of the files stored on a weekly/monthly/whatever basis, Or to share files outside of teams more easily than downloading a copy of the file and then sending that out through Outlook. It seems like it would be an easy integration to the Office 365 email service, and would improve ease of use for several scenarios. If this already exists, please let me know where to find it! Otherwise, consider this a suggestion for a new feature. Thanks,Undeliverable notices for Microsoft Teams / O365 Groups
Many of our members, including myself, regularly get non deliverable reports when using groups/teams. The use case is such: our people plan meetings using teams and invite an entire channel. After that we always get a message such as this: Your message to the Office 365 group RvB@jciaalst.be couldn't be delivered. The group RvB isn't set up to receive messages from jeroen.huylebroeck@jciaalst.be. jeroen.huylebroeck@j. . . Office 365 RvB Sender Action Required Sender not allowed How to Fix It Try one or more of the following: · If you're a member of the group, you might be registered with an email address other than jeroen.huylebroeck@jciaalst.be. Resend your message using the email address where you received a welcome message from the group. · Ask the group owner to add jeroen.huylebroeck@jciaalst.be as a group member. If you don't know who the group owner is, contact the organization's customer service department for assistance. · Ask the group owner to allow people outside their organization to send email to the group. More Info for Email Admins Status code: 550 5.7.193 The Office 365 group, RvB@jciaalst.be, is configured to reject messages sent to it from outside its organization -- unless the sender is a guest group member. jeroen.huylebroeck@jciaalst.be isn't part of the organization, and it isn't a guest group member. If you're the group's email admin or owner, check if the sender is a member of the group, but is registered under a different email address. Alternatively, the group owner, or email admin, can add jeroen.huylebroeck@jciaalst.be as a guest member of the group. Original Message Details Created Date: 6/18/2020 11:41:44 AM Sender Address: jeroen.huylebroeck@jciaalst.be Recipient Address: RvB@jciaalst.be Subject: RvB Juli 2020 Error Details Reported error: 550 5.7.193 UnifiedGroupAgent; Delivery failed because the sender isn't a group member or external senders aren't permitted to send to this group. DSN generated by: AM6PR0402MB3606.eurprd04.prod.outlook.com Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 6/18/2020 11:41:45 AM HE1PR0401MB2460.eurprd04.prod.outlook.com HE1PR0401MB2460.eurprd04.prod.outlook.com mapi 1 sec 2 6/18/2020 11:41:45 AM HE1PR0401MB2460.eurprd04.prod.outlook.com HE1PR0401MB2665.eurprd04.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * 3 6/18/2020 11:41:48 AM mail-he1eur01lp2052.outbound.protection.outlook.com xink-rerouter-us.eastus.cloudapp.azure.com esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <jeroen.huylebroeck@jciaalst.be>) 3 sec 4 6/18/2020 11:41:49 AM xink-rerouter-us.eastus.cloudapp.azure.com AM5EUR03FT017.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 5 6/18/2020 11:41:49 AM AM5EUR03FT017.eop-EUR03.prod.protection.outlook.com AM4P190CA0012.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * 6 6/18/2020 11:41:49 AM AM4P190CA0012.EURP190.PROD.OUTLOOK.COM AM6PR0402MB3606.eurprd04.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * Original Message Headers Received: from AM4P190CA0012.EURP190.PROD.OUTLOOK.COM (2603:10a6:200:56::22) by AM6PR0402MB3606.eurprd04.prod.outlook.com (2603:10a6:209:8::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22; Thu, 18 Jun 2020 11:41:49 +0000Received: from AM5EUR03FT017.eop-EUR03.prod.protection.outlook.com (2603:10a6:200:56:cafe::2) by AM4P190CA0012.outlook.office365.com (2603:10a6:200:56::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22 via Frontend Transport; Thu, 18 Jun 2020 11:41:49 +0000Authentication-Results: spf=fail (sender IP is 52.186.121.110) smtp.mailfrom=jciaalst.be; jciaalst.be; dkim=none (message not signed) header.d=none;jciaalst.be; dmarc=none action=none header.from=jciaalst.be;Received-SPF: Fail (protection.outlook.com: domain of jciaalst.be does not designate 52.186.121.110 as permitted sender) receiver=protection.outlook.com; client-ip=52.186.121.110; helo=xink-rerouter-us.eastus.cloudapp.azure.com;Received: from xink-rerouter-us.eastus.cloudapp.azure.com (52.186.121.110) by AM5EUR03FT017.mail.protection.outlook.com (10.152.16.89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22 via Frontend Transport; Thu, 18 Jun 2020 11:41:49 +0000Received: from mail-he1eur01lp2052.outbound.protection.outlook.com ([104.47.0.52] helo=EUR01-HE1-obe.outbound.protection.outlook.com) by xink-rerouter-us.eastus.cloudapp.azure.com with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <jeroen.huylebroeck@jciaalst.be>) id 1jlsvU-000Mwq-EI; Thu, 18 Jun 2020 11:41:48 +0000Received: from HE1PR0401MB2460.eurprd04.prod.outlook.com (2603:10a6:3:83::9) by HE1PR0401MB2665.eurprd04.prod.outlook.com (2603:10a6:3:7f::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22; Thu, 18 Jun 2020 11:41:45 +0000Received: from HE1PR0401MB2460.eurprd04.prod.outlook.com ([fe80::6011:e578:f478:408e]) by HE1PR0401MB2460.eurprd04.prod.outlook.com ([fe80::6011:e578:f478:408e%7]) with mapi id 15.20.3088.028; Thu, 18 Jun 2020 11:41:45 +0000Content-Type: multipart/mixed; boundary="_000_HE1PR0401MB2460BF16E403F609F09367CFBE9B0HE1PR0401MB2460_"From: RvB <RvB@jciaalst.be>To: Jeroen Huylebroeck <jeroen.huylebroeck@jciaalst.be>, RvB <RvB@jciaalst.be>Subject: RvB Juli 2020Thread-Topic: RvB Juli 2020Thread-Index: AdZFZXEzTjPUf8urwkynwnbzmCcxXw==Sender: Jeroen Huylebroeck <jeroen.huylebroeck@jciaalst.be>Date: Thu, 18 Jun 2020 11:41:44 +0000Message-ID: <HE1PR0401MB2460BF16E403F609F09367CFBE9B0@HE1PR0401MB2460.eurprd04.prod.outlook.com>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <HE1PR0401MB2460BF16E403F609F09367CFBE9B0@HE1PR0401MB2460.eurprd04.prod.outlook.com>x-ms-publictraffictype: EmailAuthentication-Results-Original: jciaalst.be; dkim=none (message not signed) header.d=none;jciaalst.be; dmarc=none action=none header.from=jciaalst.be;x-ms-exchange-messagesentrepresentingtype: 2x-ms-exchange-calendar-series-instance-id: BAAAAIIA4AB0xbcQGoLgCAAAAAAFOSZxZUXWAQAAAAAAAAAAEAAAAO6RiNcYCxlIn8AV6maOzsE=x-originating-ip: [52.114.77.37]X-MS-Office365-Filtering-Correlation-Id: 02394f8a-f95d-4984-b031-08d8137c96afx-ms-traffictypediagnostic: HE1PR0401MB2665:MeetingMessage|AM6PR0402MB3606:x-ms-oob-tlc-oobclassifiers: OLM:308;OLM:308;X-Microsoft-Antispam-Untrusted: BCL:0;X-Microsoft-Antispam-Message-Info-Original: Qyg4MREnk6YuTqoh6qRpuPLnVvzGsWDt/47zGjywcWS4n9ibFwdDUJPNq9JheD2rbfx9XAhaM009xYY2SQj2T2v9I3KIBjy4pzaT1Z2XPRQQ4FNJcEUdkkXftkMApL1qtLJTdoQfxNlB6F7JVmamNc2u0LigYFlIjVIcE0NcvPO+32/ZqGe61UlA+YZNrrQGhy70ITMaqwZQJpwgEs7OzyS9Toey/pBPHnRPj+js+Da7IMwCocZqEDCdsLrsoW1R+I6q94rQjopC0cuaS8XwVFlbzcH+hOrlalbmxsiJAuEzQmwwDJ2TmgAVXLCVaEHcJ4bYxQ1ufcAYXxotYMddCfxgCgUwzGfhvRUnCKeoSHU=X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255;CTRY:;LANG:nl;SCL:-1;SRV:;IPV:NLI;SFV:SKI;H:HE1PR0401MB2460.eurprd04.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:INB;SFP:;x-ms-exchange-antispam-messagedata: Cw4POwgmyI2HvN/daqhRAudDzPdiTd+WqWes7Auw1rR463klMlfHF/sq1JWw8feQlbAdWkT5ikN1kgdwBf5iDU5/0HDkLKKNJmSnzXd8RfcXMW9Mq03HFj2/NW3cRu2ZKR/K9+7ufgVoZJw4wuxexgZGYmSZxYDSW+SG2r8E11CfILdzLC7/P/pNOoCcG5O9gRbwViND8GMsOTvDFwfdwvIaY6dxl2PtM4RFrkTpwWVrRs1wH3xqlTzRRsiSvEq0lYJUrWcJ6uC5OdG6QhZq30kEugoYHXxHCGvWeY7+tNJUSDF4mHNepsVZNM6zn5FGruMrxcJuNZx893JWyNp4R0nk1gpVA471XLS+XVm/VI4sDSiOVGDvrgoTCJ3OwWZkJsLNi7JoQC5QP97EtCwpM90R11nGfVHKflyhCQixTgE=x-ms-exchange-transport-forked: TrueMIME-Version: 1.0X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0401MB2665X-Xink-Passed: YesReturn-Path: jeroen.huylebroeck@jciaalst.beX-EOPAttributedMessage: 0X-MS-Exchange-Transport-CrossTenantHeadersStripped: AM5EUR03FT017.eop-EUR03.prod.protection.outlook.comX-Forefront-Antispam-Report: CIP:52.186.121.110;CTRY:US;LANG:nl;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:xink-rerouter-us.eastus.cloudapp.azure.com;PTR:xink-rerouter-us.eastus.cloudapp.azure.com;CAT:NONE;SFTY:;SFS:(26005)(186003)(7696005)(55016002)(21480400003)(110136005)(5660300002)(9686003)(33656002)(7846003)(6506007)(45080400002)(336012)(52536014)(166002)(7116003)(7636003)(8936002)(1096003)(356005)(7596003)(8676002)(71200400001)(83380400001)(82310400002)(15398625002);DIR:INB;SFP:;X-OriginatorOrg: jciaalst.beX-MS-Office365-Filtering-Correlation-Id-Prvs: 6104467b-e863-4d4e-b023-08d8137c93ecX-Microsoft-Antispam: BCL:0;X-Microsoft-Antispam-Message-Info: =?us-ascii?Q?b4EoeGaduLdkiSG6cN4TEvBbm45r3RD/XsC0Msu0wexv0cub4e22xs5CTAzo?= =?us-ascii?Q?QWxfHyhBq93DVnVXThC1xhJ0+fcy3b2o5n5n2z55FN8yJBIkghE/WJCvMFu7?= =?us-ascii?Q?UMCJceemxDHn0RQcn+lv228fSSlPTK6oJ/UQb/Hm1IATMODVaDqDtxd08M4R?= =?us-ascii?Q?hRe71AREWAZWXCSoJ8GxKs6R3JFBOX+Cq9pQlDvZgja8VlM7mOu/bcYx98Wm?= =?us-ascii?Q?aQL4axcrgSWA0iprMjIxxG5qDxxoShSHF19rfJxnbi/Iaqk3cPgkScDnlMME?= =?us-ascii?Q?ejECbN9qWo8fzUO8sSIu685LpFrdxefnLlKhhU3o7vxXwma7CmZrq9BZCaCO?= =?us-ascii?Q?NDK4fhcOOO7yrhjgJkNdj1IDWO8IQpFA6bKlbK6pwe/CXW87mtE4rOfhlqzd?= =?us-ascii?Q?xD02PCczjAszGDm3JURLGO7J9KMV+Uofwbar0BzMGu8Y+Hcid5RMlvR5mcDQ?= =?us-ascii?Q?nTek2s3hQt1UqdpKpDMV1Kbj1U33SsWiGLOHrpL+x7lSFbFoE39XNLtrSMiV?= =?us-ascii?Q?sVcXYSV913er+lxFCkc3Lo9vxBPO5S4o1Hxf1a5ACQ4CpEuOzOJe5dzoDx52?= =?us-ascii?Q?GfMtREzVAGU3rJEGtUwTNuO+9f6DMaBfrb4l3aOuWvY/zE1kj2eOQbUwhOTD?= =?us-ascii?Q?sMylBU6iSYUfStwK4C1xwQ5Dr6qziO9EZiioAy6M8KYoBicufemthkSHB6zk?= =?us-ascii?Q?OjrltmV5ZrHzoqkxRfteO7Yb6oavowP8kil2J+QBaIWSvKFWW6x0l71JGTfS?= =?us-ascii?Q?AeBFdFBPitz3oq0J4smToHxNEQYT2E0+rBq+TQX+PYYXOi07SfFvjsUR8Swa?= =?us-ascii?Q?Zgqk9Xwe3J/vHpapvk0vItM8hHHeGZcKiDsc1ZtXfiVMjonHrOLx0pTCGB5X?= =?us-ascii?Q?HWV89essBpN4V+UZyoAf5wSv6ZKSKTzFMUEXVNRP6RUXVUt7cXuNHxhclFBT?= =?us-ascii?Q?x+oDr9DUrGGKmoMsmLMguArGJVrSyIpc3wZ/nbOZer9euGOjPAhuRid7u4WH?= =?us-ascii?Q?aV17/EuTxgV2S0pFbe9ND2uqcntItE2KrgvBor8q05IHZ03Ft+ikA3+V1sFv?= =?us-ascii?Q?WQSm1VqgXAMc2YRdd3I45TDnPHYWvoYgTQXQi5wcB7ITzN3NfwuLcDLHUuSY?= =?us-ascii?Q?rlcPm3XVbjhESJJRjp6LMm1V8Jg8EG7cwUslORtwWxVRzJHtgsV56LffgQZ2?= =?us-ascii?Q?9segF0/3N0L6KnNgqgBuogc3b//p2ePUASRlMK1WWYchI8KCUin4J+72QTQ?= =?us-ascii?Q?=3D?= This seems highly surprising, as I am a member of the group: Any ideas as to how I can troubleshoot this effectively?
Microsoft Teams e-mail notifications (mentions, chat, etc.) not working
Hi, I'm evaluating the notification features of Microsoft Teams. Unfortunatly notifications are not sent to users via e-mail. I double checked all settings in Teams, Admin-Center, etc., changed them, waited hours....nothing. It does not work in my trial tenant, in another production tenant, with internal users, guests, or any other account. No notification emails. A few weeks ago I got a notification email from a partner tenant about an missed chat. But since then nothing was in my inbox. All other email notfications, invitations (Planner, Teams-Invitation, etc.) are working! Has anyone else an similar issue? Kind regards Marc
Using IM option to reply to email - no Subject line passed to Teams conversation
Back in the olden days - 2018 - when we used SfB instead of Teams for IM, one of the neat features was if you replied to an email with an IM it put the email Subject line in the SfB Title bar meaning the recipient could see the context of the reply. Now that we have migrated to Teams, if I do the same operation it starts a conversation with the sender OK but does not include the Subject line, so unless I am responding to a recent email the recipient doesn't have a clue what I am talking to. A couple of years ago during the Teams preview phase I raised a query regarding the lack of a Subject line in Chat and was told it wasn't needed in Chat and was only available in Teams conversations. The real reason is that persistent chat doesn't lend itself to Titles/Subjects because it is just an endless scrolling dialogue. Whatever the MS Product Marketing guys say Teams does NOT have feature parity with SfB yet as this omission means one of the best features of SfB - reducing internal emails by replying with a chat - is not possible in a practical sense. Maybe they should take a look at Parlano if they want to see how a persistent chat app works.... The same comment applies to the lack of a visible Conversation History folder, search is NOT the answer to everything. I am surprised these comments don't come up in the internal dog-fooding phase, or is it just because most MD dev guys don't have any real life experience of corporate messaging because they have grown up with Facebook/WhatsApp?
How to use autogenerated Teams email as a distribution list of that team?
1. I have created a team in Teams called X. 2. I can see in the Admin page that Teams has created a group called X and X@Company.com associated email. 3. I would like to use X@Company.com as a distribution list for the team members. How do I do that?MFD scanning to Teams channel email address
I hope that by posting this it will help others who have similar issues. Our issue was: - Moving departments from file shares to teams, staff were user MFD scan to file share functionality. Our immediate response was: - No problem we can setup Scan to Email, where the the user sends to the Teams / Channel email address When we did the testing it worked fine. What we discovered was that our testing (5 pages) and what actually was going on (50 to 100 pages) caused issues. Small documents - scan to Teams / Channel email : no problem Big documents - scan to Teams / Channel email : never appeared in the Channel. So we tried to figure out where the emails went. It turns out they were going via this route from the MFD scanner to the Teams / Channel : paper document put document into MFD scanner scanner creates PDF and emails it Middleware software provided by our printer provider gets the email, then sends it to MS Exchange Mail relay, which accepts the scanner's email and attachment MS Exchange Mail relay sends the email and attachment out as a valid email to M365 mail system (which provides some spam removal and protection Reference) which sends it on to Teams channel which saves the attachment in '<ChannelName>/Email messages' SharePoint folder Along the way we found multiple places where LARGE documents were getting stopped. To get things flowing we did the following: To reduce the size of the documents we reduced the default DPI setting on the MFD scanner to 200dpi, but after testing we left the Auto Color setting. We found a 20Mb limit on the Middle ware software, which we increased We also found a 20Mb limit for our Microsoft exchange mail relay, which we increased Though there is a stated limit on the size of emails to channels we haven't seen that come into play in our testing (we're not sure why). Reference With these settings we found that the scans turned up as attachments in the Teams / Channel. Yeah! But it took 3 of us (1 user and 2 IT staff) about a week off an on to figure this out, mostly because once the email reaches the M365 world there is no obvious logging / tracking or error notifications. We are looking at other printer/scanner MFD middleware software that would allow "Scan to sharepoint" based on the printer's logged in user i.e. I go to the printer, fob login, then see a list of all the SharePoint sites I am a member of. I hope that this helps others who are having similar issues by helping them understand where the scanned attachments may be being stopped.
daily alerts from excel
Does anyone have a solution for adding an alert to a group email from an excel sheet in Teams? I have a spread sheet that group A will input data, and I would like an alert to be emailed to group B that this data is outstanding and needs action. once the action is done group B will check it off/mark it done and it will be removed from the email alert setup.
Unable to email channels when "Only members of this team" is configured
It appears that when a channel is set to accept emails from "Only members of this team", no one is able to send an email to the channel. We've tested this on multiple Teams/channels, but consistently get an email bounce back with "The sender is not a member of the team and does not have permission to send email to this channel." Is anyone else experiencing this?
