---
title: Mail Saglayicilari
title_en: Mail Providers
description_tr: Guncel CMS panelinden API SMTP ve Mail SMTP saglayicilarini yonetme, ekleme ve fallback oncelik akisi.
description_en: Manage API SMTP and Mail SMTP providers from the current CMS panel, including add, priority, and fallback flow.
order: 40
product: cms
section_tr: Security
section_en: Security
owner: CMS Operations Team
lastReviewed: 2026-04-01
productVersion: v1
status: live
cardImage: /img/cms/security/mail-providers/cms-security-mail-provider-poster.webp
---
# Mail Providers

Use `Security > Mail Providers` to manage the email delivery infrastructure used by the system.

This module supports two provider types:

- `API SMTP`: third-party service based delivery
- `Mail SMTP`: classic SMTP server based delivery

<video src="/video/cms-security-mail-provider.mp4"></video>

## Current Panel Overview

The panel shown in the video is used to:

- view the provider list
- add a new provider
- enter host and credential details
- set provider priority
- keep a fallback provider ready

## Provider Types in the Video

- `SMTP`: standard SMTP server connection
- `API SMTP`: API-based mail service provider
- `CRM API SMTP`: API mail provider dedicated to CRM-related sending if your environment uses it

## Multi-Provider and Fallback Logic

If the `API SMTP` provider becomes temporarily unavailable, email delivery should not stop. For this reason, multiple providers are configured with a defined priority order.

Recommended setup:

- Primary: `API SMTP`
- Backup: `Mail SMTP`

## Fields and What to Enter

- `Provider Type`: select the correct mail delivery mode such as `SMTP`, `API SMTP`, or `CRM API SMTP`
- `Provider Name`: enter a short internal label such as `zeptomail` so the provider is easy to identify in the list
- `SMTP Host`: enter the SMTP server host, for example `smtp.zeptomail.in`
- `Port`: enter the provider port such as `587`
- `Username`: enter the SMTP username or API login value provided by the vendor
- `Password`: enter the SMTP password or API key value required by the provider
- `Encryption`: select the encryption mode required by the provider; use the exact mode supported by that server
- `From Email`: enter the sender email address used in outgoing mails
- `From Name`: enter the sender display name users should see
- `Service Type`: select whether the provider should be used as `Primary` or `Fallback`
- `Status`: set the provider to `Active` when it is ready for use

Important:
- `SMTP Host`, `Port`, `Username`, and `Password` must all belong to the same provider account.
- `From Email` should usually be a verified sender address for that provider.
- If `Service Type` is set incorrectly, fallback logic may not work as expected.
- Activate the provider only after all credentials are validated.

## Operational Flow

1. Open `Security > Mail Providers`.
2. Click `Add` to create a new provider.
3. Select the correct `Provider Type`.
4. Enter `Provider Name`.
5. Fill `SMTP Host`, `Port`, `Username`, and `Password`.
6. Choose the correct `Encryption` mode.
7. Fill `From Email` and `From Name`.
8. Set `Service Type` and `Status`.
5. Save the provider.
6. Configure provider priority from primary to fallback.
7. Send a test email to verify both providers work correctly.

## What Is Important Before Saving

- Save one working `Primary` provider first.
- Add at least one `Fallback` provider so email delivery does not stop during outages.
- Use real provider credentials; placeholder values will save incorrectly or fail at runtime.
- Test after every new provider or credential change.

## Notes

- API-based providers can face rate limits or short outages, so fallback should always be configured.
- Keep SMTP credentials secure and never expose them in logs.
- In production, keep at least one tested backup provider active.