The Sinch Email365 to Mailgun Migration guide is intended to provide a high level overview and basic understanding of the main differences between Email 365 and Mailgun in order to estimate the work required to switch from one platform to the other. ...
The Sinch E-mail 365 - Bounce Classification document classifies email Bounce Records in terms of Hard and Soft bounce against the published SMTP and DSN Codes.
The Provisioning Form for Sinch E-mail 365 must be completed as part of the provisioning process.
Sinch specifically supports deliverability and reputation monitoring using API led metrics such as Hard Bounce/Soft Bounce/Complaints and Unsubscribes and offline metrics such as Sender Score reports. Sender Score reports are published for dedicated ...
Sinch’s validated IP warmup plan for ramping up email volume on shared and dedicated IPs can be used to establish a positive sending reputation with ISPs. The Sinch E-mail 365 IP Warming Template is attached below:
JSON/ RESTful API JSON API is a specification for how a client should request that resources be fetched or modified, and how a server should respond to those requests. JSON API is designed to minimize both the number of requests and the amount of dat...
Sinch E-mail 365 API delivers soft and hard bounces as pre-integrated reports with SAP Marketing Cloud. The bounce reports are delivered as API calls providing email ID, Notification ID, SMTP error code for bounced requests only. Bounce statuses are ...
Yes, the same API interface and infrastructure can be used for marketing as well as transactional emails.
Sinch E-mail 365 is designed to deliver personalized email messages. However, should a customer choose this for delivering a common message to bulk recipients, it can easily be handled by passing multiple recipients in the parameter list. Sinch deliv...
An MX record is a publicly available address for an email recipients mail server. When someone, for example:mtest@test.com sends an email to abc@xyz.com, the sender’s mail transfer agent looks up the available MX record at public DNS registry of xyz....
The core features supported by Sinch E-mail 365 include: Domain and user validations DKIM & SPF based deliverability Support for multiple senders per sub-domain “Reply-to” capability Support for custom “from” tags Soft and hard bounce status reportin...
Yes, the email service runs out of a EU based shared sending Mail Transfer Agent (MTA) infrastructure. This infrastructure has been designed for an initial baseline throughput of 1 million emails/hr and shall be scalable with deployment of additional...
The key parameters of the e-mail API request are as follows: Sender address (for example, info@marketing.customer.com Sender name (if needed); so the sender shows as info@marketing.customer.com Reply-to address (the address where email replies will ...
Sinch E-mail 365 uses both SPF (Sender Policy Framework) and DKIM (Domain Key Identified Mail) for authenticated email delivery: SPF (Sender Policy Framework) Technically, DKIM provides a method for validating a domain name identity that is associate...
Using Sinch E-mail 365, SAP Marketing Cloud customers can have an integrated email communication channel. The E-mail 365 Service - On-boarding Guide for SAP Marketing Cloud Customers describes the high-level architecture and functionalities and provi...
The Deliverability Best Practices Guide for Sinch E-mail 365 API & Service describes e-mail deliverability and outlines the best practices for using the Sinch E-mail 365 service.