Emails sent to the address from the MS-Teams Channel's ... menu's Get email address are returned with the error message "Delivery has failed to these recipients or groups: Could not create the email message on Microsoft Teams: the channel's folder was deleted or renamed. The channel has not been deleted or renamed, as I just got the email address from the channel's ... menu.
How do I fix this?
returned email (ids, servernames, and hashcodes replaced):
Delivery has failed to these recipients or groups:
channelid.corpname.com#amer.teams.ms Could not create the email
message on Microsoft Teams: the channel's folder was deleted or
renamed.
Diagnosticinformation for administrators:
messageId:<(hashcode1).(servername).outlook.com>, serverRequestId:
hashcode2, clientRequestId: hashcode3
Microsoft informed us that it is an Office 365 issue. Nothing for us to do. Microsoft has to fix it on their end.
Related
So I thought I have this setup correctly, but it is not working. Maybe someone can help?
I setup a mailbox called formsmbx (for FORMS MailBoX)
I setup a distribution list (DL) in Exchange 2013 named forms
In this DL, I added one member (formsmbx).
In Exchange, I setup a mail flow rule with these parameters:
If sender is 'outside the organization' AND the To or CC box contains forms#,
Then bcc the message to formsmbx#.
I logged into a Windows computer running Outlook 2019 as formsmbx. I went to File/Manage Ruls & Alerts. I setup a Rule that says:
after message arrives
have server reply using 'auto reply'
So finally, I sent an email from test#gmail.com to forms#domain.com. What I found was the formsmbx# inbox receives the email, but there is never an auto-reply sent out.
If I send an email directly to formsmbx#, I do not get any reply.
I am trying to trigger a Flow that identifies the attachment type (e.g. .pdf and .docx) and save it to a team site library if it's a valid attachment. If not, it sends the "from" email address an email saying the attachment is invalid. I have done this successfully for a site mailbox (created before Microsoft removed the ability to create site mailboxes in SP Online) and my personal mailbox, but I am getting the following error when using an O365 Group email inbox:
"message": "You are not authorized to perform this operation. This error can occur for sandbox (test) accounts or if OData operations are disabled by your Exchange server administrator."
Again, this error only occurs when triggering the Flow with:
I receive calendar invite to my outlook desktop client from one of the applications I use and the organizer email in the meeting invite was "scheduling-assistant+A6B890782A404B77#XXXXXX.com" (Masking the domain with X). When I tried to accept the meeting invite, I received the following exception
Delivery has failed to these recipients or groups:
Scheduling Assistant
The format of the email address isn't correct. A correct address looks like this: someone#example.com. Please check the recipient's email address and try to resend the message.
More information:
scheduling-assistant A6B890782A404B77#XXXXXX.com
Remote Server returned '550 5.1.3 STOREDRV.Submit; invalid recipient address'
ORGANIZER PROPERTY IN ICS FILE
ORGANIZER;CN=Calendar
Services:mailto:scheduling-assistant+A6B890782A404B77#XXXXXX.com
If we take a look at the email address in the delivery failed mail, plus sign was removed.
I have also recently started facing this issue. I think outlook must have made some changes to how it reads the .ics file.
You need to HTTP encode the organizer's email adderss.
I use python (django), and I used django.utils.http.urlquote to encode the email address:
organizer = vCalAddress(u"mailto:{}".format(urlquote("scheduling-assistant+A6B890782A404B77#XXXXXX.com"))) #<-- This is the only difference. I have encoded the email address.
This fixed the problem for me. I have tested this in Outlook and Google calendar.
Here is my original answer.
I have an Exchange 2013 server.
Faced with a strange issue of email delivery what I can not solve.
Exchange is rejecting email
if one of the recipients is not exist in a domain
Email will be rejected totally and sender will receive NDR for not existing user.
scenario:
Exchange mailboxes user#domain.com // valid user
user1#domain.com //**user mailbox is not exist**
Sending email from external domain to my exchange server:
TO: user#domain.com,user1#domain.com
Reciving NDR Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound;
valid user didn't receive email also.
email is rejected
.
I start to google and found that How do I reject incoming email for unknown users in MS Exchange 2013?
exchange has a user validation feature that is enabled by default
I disable it on a console restart transport role.
Set-RecipientFilterConfig -RecipientValidationEnabled $false
run the same scenario again
user#domain.com, user1.domain.com
I receive NDR for not existing user.
but email was delivered to valid user.
Is it a normal behavior for exchange?
What is right by RFC deliver for valid users or reject email?
how it will affect our server hit the public spam list?
Does this not reduce our spam filter resistance?
Please advice.
Thank you.
It's normal for Exchange to send an NDR for non existing users. As you already said, this might also trigger some spam lists because you are sending out mails (NDR) to possible spam honey pots.
A better way to do this would be to have your external MTA (the server which accepts the mail from the internet) check the recipients and refuse to accept mail for non existent email addresses. This way you would never have to send out NDR reports, as the server trying to deliver mail would be informed that it cannot deliver and notifies the sender itself.
If I delete Emails from Dynamics CRM which were tracked from Outlook, will that particular Email get deleted in Outlook as well?
Kindly advise. Thanks.
Deleting a tracked email message in Outlook does not delete the email message from Microsoft Dynamics CRM.
Deleting an email message in Microsoft Dynamics CRM does not delete the tracked message from Outlook.
https://www.microsoft.com/en-us/dynamics/crm-customer-center/deleting-records-that-have-been-tracked-with-crm-for-outlook.aspx