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 Policies
        Settingsarrow
      • Databases
          Accessarrow
        • AdminsAPI tokens
        Notifiers
          MTAarrow
        • Default rulesRetry rulesLock rulesBounce patternsStrategiesKeysISPsPools
      Nodes
        Sendersarrow
      • EmailSMSEvent generatorIntegration with SendsayENS: настройка сендера
        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 Edition to Percona Server for MongoDBAdding sender IP addressesDeduplication request settingsPostgreSQL database for account dataProxy server settingsKeycloak Integration with AltcraftGetting HTTP service statusesConfiguration MongoDB logs rotation
        Configuration of system constants and directoriesarrow
      • Filtering bot actionsDirectory of gender markers
      Platform maintenancearrow
    • Personnel requirementsPlatform maintenance processesPlatform updatingPlatform service monitoringBackup and recoveryTransferring the platform to a new serverCreating, deleting, and populating tables for statistics in ClickHouseUsage of the aktool utilityUsers and directories engaged by the platform
      Custom channels guidearrow
    • OverviewCreating and configuring a channelEntity field configurationTemplate languageEntities
        Pipesarrow
      • Pipe: Basic ConceptsResultErrorsLogPackUnpackHTTP RequestStore SetStore GetSelectorSQLEventerScheduler
        Pipelinesarrow
      • Pipeline: Basic ConceptsMessageScheduleListenerModerateStop
      Extraarrow
    • System page customizationSend Message IDИнструкция по миграции истории в ClickHouseInstructions for migrating history to ClickHouseUtility for importing push subscriptions to Firebase projectUtility for importing push subscriptions to Firebase project
    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 accountDelete 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
  • Settings
  • MTA
  • Bounce patterns

Bounce patterns

Description​

Bounce patterns are templates of responses from email providers (ISPs) about delivery problems. AKMTA analyzes these responses and classifies them to determine the reasons for delivery failures and correctly handle unsuccessful sends.

Types of negative ISP responses​

Negative response templates are divided into three main categories:

  • Hard bounce (HB) includes server-class errors (5xx), which mean the recipient’s mailbox does not exist. Sending to such addresses is blocked to avoid damaging the domain and sender IP reputation. The customer’s email subscription is marked as Hard bounced, preventing further delivery attempts.

  • Soft bounce (SB) contains client-class errors (4xx), indicating temporary unavailability of the mailbox. In such cases, retry or temporary blocking scenarios can be applied.

  • Bounce (B) — this type includes other delivery errors that are not Hard or Soft bounce. Typically, retrying delivery is not advisable, and the message is marked as Undelivered.

Creating, Editing, and Deleting​

To manage ISP response templates, in the main menu select Settings — MTA — Bounce patterns.

The opened list displays existing templates of negative ISP server responses. For most responses, entries already exist in the default AKMTA configuration. To edit an existing entry, click the quick action button on the right side of the list or the entry identifier on the left. To create a new entry, click + Create.

caution

Only custom ISP response templates can be deleted.

Each response template is configured with:

  • Name — the template name.

  • Type — the type of server response (Hard bounce, Soft bounce, Bounce).

  • ISP — the email provider. You can select an ISP record or the All ISPs option to match responses from any provider.

  • Pattern — the pattern used to match the response.

  • Message — the delivery error message text.

Last updated on Feb 25, 2025
Previous
Lock rules
Next
Strategies
  • Description
  • Types of negative ISP responses
  • Creating, Editing, and Deleting
© 2015 - 2026 Altcraft, LLC. All rights reserved.