Помощен център Transactional SMTP setup (Amazon SES)

Transactional SMTP setup (Amazon SES)

Transactional SMTP setup (Amazon SES)

The SMSBAT SMTP service is for mail triggered by a user action: sign-up confirmations, password resets, receipts, order status. Sending runs on Amazon Simple Email Service (Amazon SES).

1. What the service gives you

  • Amazon SES infrastructure — sending goes through SES capacity, with no mail servers of your own to maintain.
  • Domain authentication — SPF, DKIM and DMARC records that let the recipient’s provider verify the mail really came from you.
  • Plain SMTP — any CRM, CMS or backend that can send mail will connect.
  • One account with the other channels — email alongside Viber, SMS and push, on a shared balance with shared paperwork.

2. How connecting works

  1. Request. Tell us the sending domain and the volume you expect.
  2. DNS records. We generate the records for your domain; you add them at your registrar.
  3. Verification. Once the records propagate, the domain is marked verified.
  4. Credentials. After verification we issue the connection parameters and SMTP credentials.
  5. Integration. Enter them in your system and send a test message.

3. Connection parameters

The host, ports and credentials are issued individually after the domain is verified, and arrive together with access to the service.

Section in progress

Exact connection parameters, sending limits and code samples for common languages will be added here once the service is publicly launched.

4. DNS records

Three record types authenticate the domain:

  • SPF (TXT) — lists the servers allowed to send mail for the domain.
  • DKIM (CNAME) — a cryptographic signature proving the message was not altered in transit.
  • DMARC (TXT) — the policy the recipient applies when SPF or DKIM fails.

The values are generated for your specific domain in the panel. Do not copy values from someone else’s guide — they will not work.

5. What affects delivery

Landing in the inbox depends on three things at once:

  1. Domain authentication — without correct SPF, DKIM and DMARC a noticeable share of mail is treated as suspicious.
  2. List quality — bounces and spam complaints damage the sending domain’s reputation.
  3. Message content — transactional mail the recipient is expecting performs markedly better than bulk campaigns.

We provide the infrastructure and the DNS setup; your own sending practice builds the reputation. That is why no provider can honestly promise a fixed inbox-placement percentage.