Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Postbox
  • Getting started
    • Overview
    • DNS records
    • Configurations
    • Email event notifications
    • Tracking email openings
    • Click tracking in emails
    • Unsubscribe mechanism
    • Terms and definitions
    • Statistics
    • Limitations on email attachments
    • Quotas and limits
  • Access management
  • Pricing policy
  • Metrics Monitoring
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Rules
  • Email delivery options with mandatory TLS encryption on
  • Applying a configuration to an email
  1. Concepts
  2. Configurations

Configuration

Written by
Yandex Cloud
Updated at July 23, 2026
View in Markdown
  • Rules
  • Email delivery options with mandatory TLS encryption on
  • Applying a configuration to an email

A configuration is a group of rules you can apply to an outgoing email. If you apply a configuration, all the rules configured within it will apply to your email. You cannot apply individual rules separately.

RulesRules

A configuration may contain the following rules:

  • Subscriptions: Notifications about operations with emails, e.g., sending, delivery delay, etc. This allows you to redirect notifications about operations to other services for analysis and set up automatic actions in response to selected operations.

  • Delivery settings: Mandatory TLS encryption when emails go from Yandex Cloud Postbox to recipient servers. Ensures extra data transmission security and protects email contents.

  • Statistics collection settings: Settings for collection of statistics on email opens and clicks. They enable automatically collecting and analyzing the Openings and Clicks metrics.

Email delivery options with mandatory TLS encryption onEmail delivery options with mandatory TLS encryption on

For emails from the client to Yandex Cloud Postbox, a secure TLS connection is used at all times. The transmission protocol depends on the sending method:

  • HTTPS: If using an Amazon API compatible API.
  • SMTP over TLS: If using port 465.
  • STARTTLS: If using port 587.

The Delivery settings option:

  • With Delivery settings off, Yandex Cloud Postbox will still try to use TLS to send emails. If there is a TLS error or the recipient's server does not support TLS, the email will be sent unencrypted.
  • With Delivery settings on, Yandex Cloud Postbox will require a valid TLS certificate issued by a trusted CA and support for the minimum TLS version specified in the configuration settings. If the recipient's server does not meet these requirements, the email will not be delivered, and you will get a non-delivery notification.

Warning

Before you enable this option, make sure the recipient's servers are TLS compliant. If you are not sure that all the recipients' servers are configured correctly and want to prioritize email deliverability, it is best to keep this option off.

Recipient's server issue

Mandatory TLS encryption off

Mandatory TLS encryption on

Minimum TLS version 1.0

Minimum TLS version 1.2

The server does not support TLS

Email delivered without TLS encryption

Email not delivered

The server supports only TLS 1.0/1.1

Email delivered with TLS 1.0/1.1

Email not delivered

The server supports TLS 1.2 and higher with a valid certificate

Email delivered with the highest TLS version the client and server could agree on

Expired TLS certificate

Email delivered with TLS encryption

Email not delivered

Self-signed certificate

Applying a configuration to an emailApplying a configuration to an email

You can apply a configuration to an email using the following methods:

  • By associating the configuration with an address: In this case, the configuration will apply to all emails sent from this address.

    You can associate a configuration only with an address with domain ownership confirmed. One address can be associated with one configuration only; however, one configuration can be associated with more than one address.

  • By providing the configuration name in the X-Ses-Configuration-Set header.

    The configuration must reside in the same folder as the address. If no configuration of the given name is found in the folder the address is in, you will get an error when sending your email. The configuration provided in the X-Ses-Configuration-Set header overrides the configuration associated with the address.

  • By providing the configuration name in the ConfigurationSetName field, if using the AWS-compatible API SendEmail method.

    The configuration must reside in the same folder as the address. If no configuration of the given name is found in the folder the address is in, you will get an error when sending your email. The configuration provided in the ConfigurationSetName field overrides the configuration associated with the address.

Note

The configuration settings are applied to the email the moment you send it. If you change the configuration settings after sending, the change will not affect the emails that are sent but not yet delivered.

Was the article helpful?

Previous
DNS records
Next
Email event notifications
© 2026 Direct Cursus Technology L.L.C.