Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guide iconUser guide
Developer guide iconDeveloper guide
Admin guide iconAdmin guide
English
  • Русский
  • English
Login
    Getting StartedAdministrator documentationFunctional characteristics
      Technology descriptionarrow
    • Architecture OverviewComponent Description
        Deployment schemesarrow
      • Basic schemeFail-safe schemeTypical Placement in Infrastructure
    System requirements
      Admin Panelarrow
      • Account areaarrow
        • Accountsarrow
        • Account UsersAccount Virtual SendersAccount Database Indexes
        TariffsExternal data configurationLDAPTasksSchedule JobsGlobal Stop ListsWebversion Store PoliciesIn-App Storage Settings
        Settingsarrow
      • Databases
          Accessarrow
        • AdminsAPI tokens
        Notifiers
          MTAarrow
        • Default rulesRetry rulesLock rulesBounce patternsStrategiesKeysISPsPools
      Nodes
        Sendersarrow
      • EmailSMSEvent generatorIntegration with Altcraft Cloud SMTPAmazon SES integrationAKMTA interaction with SMTP relaysIntegration with Sendsay
        Reportsarrow
      • Audit JournalData Usage
        Toolsarrow
      • ARF decoderURL decoderSMID decoderLicense
      Platform installationarrow
    • Automatic installationManual installationRunning the platform in a Docker container
      Platform configurationarrow
    • Configuration fileDomain settingsLDAP access configurationSending Email via SMTP relayPixel and push domain configurationCluster and Replication SetupSystem notifications configurationProcesses UNIX sockets configurationHTTPS ConfigurationMigrating from MongoDB Community to Percona ServerAdding sender IP addressesData Encryption in Percona Server for MongoDBDeduplication request settingsBackup with Percona Backup for MongoDBPostgreSQL database for Market dataProxy server settingsKeycloak Integration with AltcraftGetting HTTP service statusesConfiguring MongoDB log rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Custom Channelsarrow
    • Creating a Channel
        Pipelinesarrow
      • MessageScheduleListenerModerateStop
          Pipesarrow
        • HTTP RequestPackUnpackEventerSchedulerSelectorSQLStore SetStore GetLogResultErrorRMQ Publisher
      External Objects (Entities)Templating LanguageSending FilesPresets (Field Sets)DebuggingTechnical Limitations
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsing the aktool utilityUsers and directories engaged by the platformEvent Processing Monitoring (procevent)Platform service monitoringProcess and mailing monitoring via Prometheus
      Extraarrow
    • System page customizationSend Message IDClickHouse History Migration GuideInstructions for migrating history to ClickHouseUtility for importing push subscriptions to Firebase projectUtility for importing push subscriptions to Firebase projectIP address warm-upENS: настройка интеграции
    Processing HTTP/HTTPS traffic
      Administrator APIarrow
      • Accounts admin apiarrow
        • Restricted accessarrow
        • Account Activation and DeactivationAccount Freeze and Unfreeze
        Get accounts listAdd a new accountDelete the account
        Account usersarrow
      • Update an Existing AccountAdd a new userDelete a userGet a list of usersSending a Welcome Email
        Nodesarrow
      • Synchronize node MTA configurationGet nodes listGet node MTA statusActivate node MTADeactivate node MTA
        Senders admin apiarrow
      • Create or update AKMTA senderGet AKMTA sender informationAssign account to senderGet senders listDelete senderRestore sender
          Sender queuearrow
        • Get sender queue informationHold sender queueRelease sender queueClear sender queue
        Virtual sendersarrow
      • Get virtual senders listGet virtual sender informationCreate virtual senderUpdate virtual senderClone virtual senderDelete virtual sender
    Documentation Archive
  • Admin Panel
  • Senders
  • Integration with Altcraft Cloud SMTP

Integration with Altcraft Cloud SMTP

Altcraft Cloud SMTP is an external SMTP relay through which the Altcraft platform can send email messages and receive delivery events via HTTP Webhook.

The integration is used when direct email sending from the platform server is not possible or not desirable. For example, when Altcraft is hosted in a private cloud, outgoing connections on SMTP port 25/TCP may be blocked by the cloud provider. In such a configuration, emails are passed to an external SMTP relay, which performs delivery on behalf of the system.

Altcraft Cloud SMTP also sends back delivery events such as delivery and bounce. This allows the platform to correctly record message statuses, generate mailing statistics, and handle non-deliveries.

The connection process consists of three steps: preparing a node with a new IP address, configuring the sender, and binding the sender to a virtual sender.

Step 1. Preparing a node with a new IP address​

Emails are sent through the relay from a dedicated IP address, so this address must first be added to the sending node.

  1. Create a node if one does not exist yet. In the Admin Panel main menu, select Nodes and click + Create. Set a unique name (Name), the network address (Host), and the installation directory (Node installation directory). Detailed instructions for creating nodes with SSH and HTTPS access are provided in the nodes article.
slide-0
slide-1
slide-2
  1. Add a new IP address to the node:

    • Add the IP address to a network interface on the node server.
    • In the admin web interface, open the node edit page and re-save it.
    • Open the node editing again: the new IP addresses will appear in the list.

    The step-by-step instruction is provided in the Adding new IP addresses to a sender article.

  1. Remember the added IP address: it will be needed when creating the sender.

Step 2. Sender configuration​

  1. Go to the Admin Panel, section Senders — Email.

  2. Create a new sender or edit an existing one. For a new sender, specify a unique name (Name) and the accounts that will have access to it (Assigned accounts).

  3. In the Type field, select Email: AKMTA.

  4. In the General block, add the IP address from step 1 to the IP addresses list.

  5. Go to the Relay tab and enable the Enable sending via SMTP relay option.

  6. Specify the relay connection parameters:

    • SMTP relay host — the relay address provided by Altcraft support.
    • Auth type — the authentication type provided by Altcraft support.
    • Username and Password — the relay server credentials issued by Altcraft support.
    • Use Start TLS — disable.
  7. Enable the Use webhook option:

    • In the Webhook type list, select Altcraft Cloud SMTP.
    • The Webhook url is generated automatically. Copy it — this URL will receive delivery events from the relay.
  1. Save the sender.
note

Make sure that the authentication type and credentials match the data provided by the Altcraft technical support.

Step 3. Binding the sender to a virtual sender​

After creating and configuring the sender, you need to add it to a virtual sender through the platform's user interface. To do this, open the platform, go to Settings — Virtual Senders, and configure the rules for sending through the created sender.

You can learn more about virtual senders in this article.

Checking the delivery​

After the setup, send a test email via a campaign or scenario and make sure that:

  • the email is delivered to the recipient;
  • the delivery event is recorded in the mailing statistics;
  • the delivery event is linked to the send in the profile list.

If the emails are not delivered, contact the Altcraft technical support.

Last updated on Oct 7, 2026
Previous
Event generator
Next
Amazon SES integration
  • Step 1. Preparing a node with a new IP address
  • Step 2. Sender configuration
  • Step 3. Binding the sender to a virtual sender
  • Checking the delivery
© 2015 - 2026 Altcraft, LLC. All rights reserved.