I have users that cannot use our services because Outlook REST API returns the following error code RESTAPINotEnabledForComponentSharedMailbox.
It looks like their mailbox is not a shared mailbox. So what kind of mailbox is that?
Can you tell me more about this error? Is there something we can do?
This means user doesn't have their mailbox in O365 cloud. This can mean that their mailbox is either on premises or they don't even have any mailbox. You should use auto discover to get the right end point to connect.
Related
Using the following endpoint returns all mail (both sent and received) for a work account:
GET /me/messages
However it doesn't return all received mail for personal/family accounts. Both the v1.0 and beta versions display this behaviour.
Is there a way of retrieving all received mail for personal/family accounts?
returns some or returns error? did you give the api access permissions to those accounts?
make sure to check this official document.
The documentation says you can get up to only 1000 emails at once. And from permissions section, it seems only possible to get all emails from within an application given the permission Mail.ReadBasic.All even for work account.
I don't have a work account thus I tested sending an email to myself on my personal account and tested the query on graph-explorer test page here. The first 2 results are those freshly received and freshly sent ones. with this I will say a work and personal/family accounts are no different on getting emails since you said you can get both received and sent mails from a work account.
so in short, you can get up to 1000 emails unless you use an application with permission to read all but with limited properties because Mail.ReadBasic
allows the app to read email in the signed-in user's mailbox except body, previewBody, attachments and any extended properties, and hence I deduce Mail.ReadBasic.All does the same
When creating Calendar Events via the Graph API, the events are created correctly in the calendar of the organizer but the invites to the participants get bounced. The organizer gets a 'Delivery has failed...' message with the following error message:
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic not accepted from this IP. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653 AS(7171)
Sending emails manually through Outlook (web) from the organizer to the participants works fine.
The issue is intermittent. After changing the DNS server, everything worked fine for some time.
I checked https://protection.office.com/restrictedusers as suggested in the answers to similar posts, but this list is empty.
I also tried delisting the IP address (my own?) through https://sender.office.com/, but to no avail.
The tenant is linked to the Microsoft Developer Program and would allegedly have a 'bad reputation'. However, I don't understand how that would explain the fact that it sometimes works and sometimes doesn't when sending exactly the same API request and hence 'triggering' exactly the same emails...
I think the best way to overcome this would be to add a domain to your developer tenant as per the guidance here:
https://learn.microsoft.com/en-us/Exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-5-7-700-through-5-7-750#57750-client-blocked-from-sending-from-unregistered-domain
Add and validate all domains in Office 365 that you use to send email messages. For more information, see Add a domain to Office 365.
I'm not guaranteeing this will resolve it. You have to understand that those developer tenants are only meant for experimentation and so there are checks and balances to ensure they are used in a bad manor.
How many emails are you sending through this tenant?
Calendar events are sent out via email. Add the "Mail.Send" permission to you App Registration.
This solved it for me.
in my organization we have a mailbox that receives email from different sources (about 5) everyday, set to track all incoming emails in the CRM.
All the mails are correctly tracked on the CRM every day, except for one that always fails (same source, similar content every day).
If I send the exact same email from another address, the mail is correctly synchronized with the CRM, so I think it could be something related with Exchange.
This is the message I get if I open the mailbox record:
An unknown error occurred while receiving email through the mailbox "xxxxxx".
The owner of the associated email server profile xxxxx has been notified. The system will try to receive email again later.
Email Server Error Code: Exchange server returned UnknownIncomingEmailIntegrationError -2147220970 exception
Looking for this specific message didn't get me any result, while just searching the error code I found out it could be something related to plugins.
Unfortunately there is no plugin that fires on email creation, same for workflows and so on. By the way, sending the email from another address just works fine.
Has anyone ever had such a problem? Is there some place where I can find other logs and dig deeper in the problem?
Thanks in advance.
For anyone else experiencing this issue: I received the error code -2147218683, which is different, but it turns out this was due to the user in question not having the right security role. Gave the account sys admin and the error went away.
Is ist possible for a user connected to Exchange Server via a client (Outlook Web App) to tamper with the e-mails in his mailbox (inbox, drafts, sent items ect.)?
Like modifying e-mail content (text, subject...) or properties (date, time, recipient...).
The core of the question is: If there is an e-mail in the user's sent items folder and this user did not have access to the Exchange Server (neither physically nor remotely, except for his standard user access), how sure (or probable) ist it, that this e-mail has really been sent on that date and time with exactly that text to exactly those recipients and that it had not been planted there at a later date?
Does it make a difference if that user only has access to his account via Outlook Web App or if he also has access via MS Outlook?
Outlook Web App is just a client so it won't allow you to modify a sent email or fake/import one as that is not a valid task for that client. You could do this at the API level using something like EWS or MAPI but that would require knowledge that most users won't have (but most likly they would have access to do it though). The Mitigation to this is if you have Litigation hold enabled https://technet.microsoft.com/en-us/library/ee861123%28v=exchg.141%29.aspx on the mailbox then any changes they did make to a message would be tracked and you would always be able to see the original version. Also if you looked at the message with a MAPI editor like MFCMapi or OutlookSpy there would be tell tails of somebody trying to fake a message like the Creation time not matching the sent time etc and other properties would most likly give it away.
One thing i would suggest is look at your Message Tracking log as they will tell you exactly what was sent and who is was sent to and the time https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.160%29.aspx while these also aren't immutable it would take an administrative access to the server to modify.
I am new with the "outlook" api. i want to get all calender event,contact and mail from "outlook account".
but i does not get appropriate result with "outlook" account its working fine with "office365" account
i follow this documentation for get all required data
and i create application for getting data from here
but every time when i login with my outlook account it's give me an error like this.
Please help me out.
Thanks in advance...
Just ran into the same problem and found an explanation here. It appears we're going to have to wait for the accounts to be enabled unless you request a testing account as described in the link. Confirmed the same results when using the non-enabled account in the Outlook Oauth Sandbox.
From the first link
Because enabling mailboxes on Outlook.com for the Outlook REST API happens over a period of time, your existing Outlook.com account may take a while to get enabled. To test your app accessing data on Outlook.com mailboxes that have already been enabled, you can request a new, enabled Outlook.com developer preview account by emailing outlookdev#microsoft.com.
If your app accesses Outlook.com mailbox data, it should handle scenarios where the user's mailbox has not yet been enabled for the Outlook REST API. In such situations, when you make a REST request, you would get an error like the following:
HTTP error: 404
Error code: MailboxNotEnabledForRESTAPI or MailboxNotSupportedForRESTAPI
Error message: “REST API is not yet supported for this mailbox.
Step 1 :
Click the Below Link :
https://oauthplay.azurewebsites.net/?code=M657b8bab-e543-f849-134c-0a2f85179a67&state=17661047-2a14-4c90-9edd-0119f841b559
Step 2:
Step 3 :
Step 4 :
Step 5 :