Hello,

1. Invalid Mime Content Error Code 19736 Outlook For Macbook Pro
2. Invalid Mime Content Error Code 19736 Outlook For Mac Os
3. Invalid Mime Content Error Code 19736 Outlook For Mac Osx
4. Invalid Mime Content Error Code 19736 Outlook For Macs

• Code Message Description Suggested fix; SVG5601 'SVG Path data has incorrect format and could not be completely parsed.' The SVG Path string isn't formatted correctly, or contains unrecognized commands.: Check the format of the commands.
• Summary: Video errors, black screen with sound only, out-of-sync, jerky videos, YouTube playback error, etc., on Windows PC are common. Learn how to fix video playback problems on your computer.

The message undelivered returned email from Office 365 onmicrosoft.com is a mailer-daemon equivalent mailing system which notifies the sender of the delivery issues. These issues can range from user-not-found to mailbox full, or attachment rejections. If you are having trouble with this message, leave a detailed comment at the bottom! Here is an example rejection Continue reading Email.

I know this is an Apple community but I thought I'ld run it by yous anyway. I have a mac (Sierra), Office 365 is installed on it. I use Outlook v15.32 on the mac. In Exchange v2016 we have created a public folder named 'zoro'. In exchange admin center, I go into the public folder > public folder > click on zoro then click on manage. I set my account as an owner with full perms. Now this I cannot remember where I did this but I added my account to allow my account to send as.

Back on my mac I opened Outlook > Tools > Public Folders, clicked on zoro and subscribed. I outlook in the left window pane it lists my in-box, drafts, sent, deleted items and our domain. Under our domain is a folder 'SubscribedPublic Folders' under which zoro shows up. I can see all of the emails in this folder. Now, I click new email, set From = zoro, send myself an email. The status bar at the bottom of outlook says sending ... That will eventually timeout and the email will be put in the drafts folder.

Invalid Mime Content Error Code 19736 Outlook For Macbook Pro

In the lower right of outlook I see a triangle with a ! in it. Opening that reveals errors

An unknown error has occurred in Outlook. Mail could not be sent. The message has been moved to your Drafts folder.

A message in your Outbox could not be sent. The account which created the message cannot be found.

zoro is a mail enabled public folder, not an account. I am able to use zoro as the From in outlook on windows, even though it is not an account, but not in Outlook 365 on mac.

Any ideas/help is appreciated.

Joe

Posted on May 8, 2017 12:09 PM

The Knowledgebase is a searchable database of technical questions and answers to troubleshoot a variety of issues. Compiled by the Barracuda Technical Support team, this interactive tool is designed to be an easy way to solve technical issues. Im running 2016 on probably 25 Mac's and haven't seen this issue yet, but I have had weird issues with Outlook in general that aren't worth the time messing with and just adding the account back again will fix saving all of our times. Cause Resolution; The user's personal site has not been provisioned. The user should open OneDrive for Business and follow any instructions to provision the site.

This article describes error codes that are returned by the OneNote APIs in Microsoft Graph whenever a request sent through the API fails.

Error response example

When your request generates an error, the OneNote API stops performing the request and returns an error response as a JSON object. An error response contains the associated error code, a message, and a link to the appropriate section of this article. The following example shows how an error response looks.

For more information about Microsoft Graph errors, see Microsoft Graph error responses and resource types.

Codes from 10001 to 19999

The service is having problems or is sending information to the application.

10001

An unexpected error occurred and the request failed.

10002

The service is not currently available.

10003

The current user's account has exceeded the maximum number of active requests. Your app will have to repeat the request.

10004

The service can't create a page in the requested section because that section is protected by a password.

10005

The request contains more than the maximum number of image tags in which the data-render-src attribute contains a PDF. See Add images and files.

10006

The OneNote API was unable to create a page in the specified section because that section is corrupt.

10007

The server is too busy to handle the incoming request at this moment. Please try again later.

10008

One or more of the document libraries on the user or group's OneDrive contains more than 5000 OneNote items (notebooks, sections, section groups), and cannot be queried using the API. Please make sure that none of the user or group's document libraries contains more than 5000 OneNote items. See the OneNote Dev blog for mitigation steps.

10012

Unable to create or update the entity because the library that contains the notebook requires items to be checked out before they can be edited. For more information, see Set up a library to require check-out of files.

Either remove the check-out requirement from the library, or move the notebook.

10013

One or more of the document libraries on the user or group's OneDrive contains more than 20,000 items and cannot be indexed for querying using the API. Please make sure that none of the user or group's document libraries contains more than 20,000 items. See the OneNote Dev blog for mitigation steps.

10014

Azure Key Vault is too busy to handle the incoming request at this moment. Please try again later.

10015

SharePoint is currently unavailable. Please try again later.

10016

Document library on the user or group’s OneDrive exceeded unique security scopes threshold limit. The maximum number of unique security scopes set for a library cannot exceed 50,000.

10017

Bad Request.

19999

The request failed because an undetermined error occurred.

Codes from 20001 to 29999

The application code has done something wrong.

20001

The request is missing the required 'Presentation' part. Exactly one is required.

20002

The request contains two or more 'Presentation' parts. Exactly one is required.

20003

The content type of the 'Presentation' part can be only text/HTML or application/XHTML+XML.

20004

The 'Presentation' part HTML contains an image tag with both the src and the data-render-src properties set. The API will ignore the src property and use the data-render-src property.

20005

The request URI is too long. The maximum size of the URI (including all parameters and data) is 16 KB or 16,384 characters.

20006

The 'Presentation' part HTML contains an image tag with neither the src nor the data-render-src properties set. The API will ignore the image tag.

20007

Invalid Mime Content Error Code 19736 Outlook For Mac Os

The 'Presentation' part HTML contains a created date/time string that does not match any of the allowed formats.

20008

The size of the request is too large.

20009

The request contains parts with duplicate names. Part names must be unique.

20010

The Content-Disposition header was not supplied for the specified content type.

20011

The request contains a malformed multipart payload. Problems could include missing blank lines, a missing last line, incorrectly formatted part separators, and so on. If you're building the multipart message by hand, carefully check the logic, or consider using a third-party library.

20012

The request doesn't supply a content type for the specified part.

20013

The request doesn't supply Content-Type and Content-Disposition headers for the specified part.

20014

The length of a part in the multipart message exceeds the maximum size of 25 MB.

20015

The count of parts in the multipart message exceeds the limit of 500.

20016

The length of the multipart message exceeds the limit of 75 MB.

20017

The email MIME was malformed.

20018

The meeting MIME or ICal was malformed.

20019

No ICal was found.

20020

Encountered malformed Json in request body.

20100

Something is wrong with the syntax of your request.

20101

The property that you requested doesn't exist.

20102

You requested a resource that doesn't exist.

20103

The expand query is not supported for this request. See Supported OData query string options.

20104

The pagelevel query option is supported only when querying for the pages collection in a section or for a specific page. For example:

20106

Your request contains a query operator that is not supported.

20108

Your request contains unsupported OData query parameters.

20109

The payload in the PATCH request is not constructed correctly.

20110

Page create requests with data parts require the content to be multipart, with a 'Presentation' part.

20111

Your request uses an OData feature that isn't supported.

20112

Your request contains an invalid ID for the target notebook, section group, section, or page entity.

20113

The resource specified in the request has been deleted.

20115

The name contains invalid characters. A notebook name cannot contain any of the following characters: ? * / : < > ' '

20117

An item with the name you specified already exists in the location that you specified.

20119

The HTML in the 'Presentation' part contains a data-attachment attribute that either doesn't have a valid format or includes one or more of these invalid characters for a file name: / : * ? < > '. The request substituted the value indicated in the error message.

20120

Your request specifies a PATCH target that can't be located.

20121

Your request contains an invalid PATCH argument. See Update page content.

20122

Your request specifies an unsupported PATCH action. See Update page content.

To find a complete list of all emulators click on the appropriate menu link in the website header.Find the complete list of ROMs for this console on the page.How to Install.

20123

The PATCH request is unable to alter the specified page.

20124

Your multipart PATCH request doesn't include a 'commands' part with the PATCH action JSON structure. See Update page content.

20125

Your PATCH request contains no actions. See Update page content.

20126

The message body contains either incorrectly formatted JSON or fields that are not supported for this operation.

20127

Your request specifies the name of an unknown property.

20128

Your request contains an OData syntax error at the position indicated in the message.

20129

Your request contains a top query string option whose value is too high. For page queries, the maximum value is 100, and the default value is 20.

20130

Your request contains a URI that points to an HTTP resource that can't be found.

ErrorCode (SOAP)

20131

Your request contains an invalid value for Content-Type. Use the value indicated in the message.

20132

Your request contains invalid content. Common causes for this are a missing Content-Type request header and/or no content in the body of the request.

20133

Your request specifies a PATCH target that is not supported. See Update page content.

20134

Your request specifies an invalid element as the target of the PATCH action. If the target uses the data-id identifier, make sure it's prefixed with a # symbol. See Update page content.

20135

Your request specifies an entity type that is not supported for the PATCH operation. See Update page content.

20136

Your request contains an invalid or missing data-render-src or data-render-method attribute. See Extract data from captures.

20137

The target page does not support PATCH requests.

20138

The target element type in your PATCH request doesn't support the append action. See Update page content.

20139

Your request contains an invalid data-tag attribute value. See Use note tags.

20140

Your request contains an invalid data-tag status value. Check box note tags can have a completed status.

Example:

See Use note tags.

20141

The target in your PATCH request doesn't support the specified action. See Update page content.

20142

Your request contains an expand expression for a parent of child entities or a child of parent entities, which is not supported. See Supported OData query string options.

20143

The OData query is invalid.

20144

Your request contains an expand expression for a non-navigation property. Only navigation properties can be expanded.

20145

The select or expand expression in your request contains an invalid term.

20146

The style='position:absolute' attribute is specified on an element, but the body element does not specify data-absolute-enabled='true', which is required to support positioning. All position settings will be ignored. See Create absolute positioned elements.

20147

The style='position:absolute' attribute is specified on an element that is not a direct child of the body element, which is not supported. If the element is a div, img, or object, make it a direct child of the body; otherwise the position settings will be ignored and its content will render inside an absolute positioned div. See Create absolute positioned elements.

20148

The style='position:absolute' attribute is specified on an element type that does not support it. Only div, img, and object elements that are direct children of the page body support positioning. See Create absolute positioned elements.

20149

Your request specifies a target element that cannot be found.

20150

The request is not valid for this authentication type. Use the ./me/onenote/ path instead.

20151

The request is not valid for this authentication type. Use the ./me/onenote/section/{id}/pages endpoint to create a page in a specific section.

20152

There is no name value specified for the entity. The name must be defined, and it cannot contain whitespaces only.

20153

The entity name contains invalid characters. The name cannot contain the following characters: ? * / : < > & # ' % ~

20154

The entity name cannot start with a space.

Invalid Mime Content Error Code 19736 Outlook For Mac Osx

20155

The entity name is too long. Notebook names have a 128-character limit. Other entity names have a 50-character limit.

20156

The specified ID for the destination resource does not exist.

20157

The specified ID for the destination entity is invalid.

20158

Unable to get metadata for the site URL specified in the request. Check the format of the supplied URL. Supported formats include https://domain.sharepoint.com/site-a and https://domain.com/sites/site-a.

20160

Unable to find an Office 365 unified group that has the specified ID.

20161

The context does not specify a valid user ID. One common error is that PUID/CID was passed in as a long instead of a hex.

20166

The application has issued too many requests on behalf of a user in a short period of time. To help ensure that the OneNote API remains stable and responsive, the API returns a 429 status code and this error when it detects that an application is using too many resources.

For more information, see Microsoft Graph service-specific throttling guidance.

See Full List On Docs.microsoft.com

20168

The video source specified in the request is not supported. See Supported video sites for the current list.

Codes from 30001 to 39999

Something is wrong with the user's account.

30101

The user account has exceeded its OneDrive quota. See OneDrive.

30102

Nothing more can be added to the requested section because it has reached its maximum size.

30103

Resource consumption is too high for the request. Either the target user account has a large dataset, or the service is receiving a high number of concurrent requests to the same site (for example, the user's personal site or a team site).

30104

The user account has been suspended.

30105

The user's personal OneDrive for Business site is not provisioned, which is required to access notebooks. The OneNote service will provision the site now. This process may take several minutes.

30106

OneDrive for Business is being provisioned for the user.

30108

The user's personal OneDrive for Business could not be retrieved. The following table lists some possible causes.

30109

Some users in the request do not exist.

30110

Student Information Services has not been registered for this tenant.

30111

There is a generic error with Student Information Services.

30112

Multiple users affected by the request had the same username.

30113

The notebook is not configured to allow invites.

30114

There is a required parameter missing.

Codes from 40001 to 49999

The user or application does not have the correct permissions.

40001

The request doesn't contain a valid OAuth token. See Notes permissions.

40002

The user doesn't have permission to write to the requested location.

40003

The user doesn't have permission to access the requested resource.

40004

The OAuth token doesn't have the required scopes to perform the requested action. See Notes permissions.

40006

The OAuth token doesn't have the required scopes to perform the requested action. Specifically the edit permission. See Notes permissions.

40007

The user does not have permissions to access this resource.

40008

Access is Forbidden for this resource.

40009

The container is already in use by another resource.

See also

The message encoding options in Exchange Server let you specify message characteristics such as MIME and non-MIME character sets, binary encoding, and attachment formats. You can specify message encoding options in the following locations:

• Remote domain settings

• Mail contact and mail user settings

• Outlook settings:

  • Message format

  • Internet message format

  • Internet recipient message format (Outlook 2010 or earlier)

  • Message character set encoding options

• Outlook on the web (formerly known as Outlook Web App) message format settings

Typically, the default settings for these message encoding options will work fine. However, you might need to change the messaging encoding options for recipients that are using older email clients or messaging systems. They'll likely tell you if messages from your Exchange environment appear to have formatting issues.

For more information about content conversion in Exchange, see Content conversion. For TNEF (also known as or Rich Text) settings, see TNEF conversion options.

Remote domain settings

Remote domains specify settings for messages sent to domains that are external to your Exchange organization. For more information, see Remote Domains.

When you configure message encoding options for a remote domain, the settings are applied to all messages that are sent to recipients in that domain. Some settings are available in the Exchange admin center (EAC), but most are only available in the Exchange Management Shell. The message encoding settings are described in this table:

Mail contact and mail user settings

Mail contacts and mail users represent users that have external email addresses in your Exchange organization. For more information, see Recipients.

When you configure message encoding options for a mail contact or a mail user, the settings are only applied to messages that are sent to that specific recipient. All settings are only available in the Exchange Management Shell in these cmdlets:

• Enable-MailContact, New-MailContact, or Set-MailContact.

• Enable-MailUser, New-MailUser, or Set-MailUser.

The message encoding settings for mail contacts and mail users are described in this list:

• UsePreferMessageFormat parameter*: Specifies whether the message format settings for the mail contact or mail user override the corresponding settings for the remote domain. Valid values are:

  • $true: Messages sent to the Mail contact or mail user use the message format that's configured for the Mail contact or mail user.

  • $false: Messages sent to the Mail contact or mail user use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.

• MessageFormat parameter: This parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are Text or Mime, and the default value is Mime.

• MessageBodyFormat parameter: This parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are Text, Html, or TextAndHtml, and the default value is TextAndHtml.

  The MessageFormat and MessageBodyFormat parameters are interdependent:

  • If the MessageFormat value is Mime, the MessageBodyFormat value can be Text, Html, or TextAndHtml.

  • If the MessageFormat value is Text, the MessageBodyFormat value can only be Text.

• MacAttachmentFormat parameter: Specifies the message attachment format for Apple Macintosh operating system clients. Valid values are BinHex, UuEncode, AppleSingle, or AppleDouble, and the default value is BinHex.

  The MessageFormat and MacAttachmentFormat parameters are interdependent:

  • If the MessageFormat value is Text, the MacAttachmentFormat value can be BinHex or UuEncode.

  • If the MessageFormat value is Mime, the MacAttachmentFormat value can be BinHex, AppleSingle, or AppleDouble.

Outlook settings

As a sender, you can specify the message encoding in Outlook by using any of these methods:

• Configure the default message format to plain text or HTML.

• Configure the message format to plain text or HTML as you're composing the message by using the Format area in the Format Text Rigging formulas free. tab.

• Configure the message encoding options for messages sent to all external recipients. These options are called Internet message format options, and they only apply to remote recipients (not to recipients in the Exchange organization).

• Configure the message encoding options for messages sent to specific external recipients (Outlook 2010 or earlier). These options are called Internet recipient message format options, and they only apply to remote recipients in your Contacts folder (not to recipients in the Exchange organization).

For instructions on configuring these settings in Outlook, see Change the message format to HTML, Rich Text Format, or plain text.

By default, Outlook uses automatic character set message encoding by scanning the whole text of the outgoing message to determine the appropriate encoding to use for the message. This setting applies to internal and external recipients. However, you can bypass the automatic selection and specify a preferred encoding for outgoing messages at File > Options > Advanced > International options.

Outlook on the web settings

As a sender, you can specify message encoding options in Outlook on the web by using either of these methods:

• Configure the default message format as plain text or HTML in the Message format section at Settings > Options > Mail > Layout.

• Configure the message format to plain text or HTML as you're composing the message by clicking More options , and selecting Switch to plain text (if the current format is HTML) or Switch to HTML (if the current format is plain text).

Order of precedence for message encoding options

Some message encoding options are available in remote domain settings, Mail contact or mail user settings, and Outlook or Outlook on the web settings. Message encoding options for outgoing messages sent to external recipients are described in the following list from highest priority to lowest priority:

1. Mail contact or mail user settings (if the use preferred message format setting is enabled)

2. Outlook or Outlook on the web settings

3. Remote domain settings

A setting at a higher level overrides the corresponding setting at a lower level. For example, Mail contact or mail user settings override the corresponding setting for a remote domain. Unique settings are unaffected (there's no higher or lower priority setting that conflicts).

The order of precedence for message encoding options are described in the following sections.

Invalid Mime Content Error Code 19736 Outlook For Macs

Order of precedence for message character sets

The following table describes the order of precedence from highest priority to lowest priority for message character set encoding options.

Notes:

• When you configure the non-MIME character set for a remote domain, the character set is assigned to incoming or outgoing messages to and from the remote domain that don't contain a specified character set.

• The value of the Windows ANSI code page for the Exchange server is used to assign a character set to these types of messages:

  • Internal messages that don't contain a specified character set.

  • Internal messages that contain a specified character set, but don't contain a specified server code page.

• If a message contains a specified but invalid character set, the Exchange server tries to replace the invalid character set with a valid one.

Order of precedence for plain text message encoding options

The following table describes the order of precedence from highest priority to lowest priority for plain text message encoding options.

Note: Only plain text message settings are included here (not plain text settings for MIME encoded messages).

Order of precedence for MIME message encoding options

The following table describes the order of precedence from highest priority to lowest priority for MIME message encoding options.