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
  • ISPs

ISPs

Description​

ISPs are email providers through which email messages are sent. The platform allows you to configure rules for different domain groups belonging to specific ISPs.

When is customization needed?​

Configuring ISPs can be useful in the following cases:

  • Sending limits — some providers limit the number of incoming messages as part of bulk mailing policies.
  • Improving domain and IP reputation — setting individual rules for ISPs helps improve email deliverability.
  • Specific response codes from providers — some ISPs use unique error codes and delivery statuses.
  • Adding service headers — some providers may require including additional headers in emails.

Creating, Editing, and Deleting​

To manage email providers, in the main menu select Settings — MTA — ISPs.

The opened list displays existing ISP records in the AKMTA module. For most email providers, entries already exist in the default AKMTA configuration. To edit an existing ISP record, click the quick action button on the right side of the list or the record identifier on the left. To create a new record, click + Create:

caution

Only custom email provider records can be deleted.

ISP Record Settings​

Each ISP record is configured with:

  • Name — the email provider name.

  • Encoding (Global, HTML, Text) — the message data encoding type. Available options: Quoted-Printable, Base64, 8-bit.

  • Domains — the domains of the email provider's mailboxes.

If you need to separately configure delivery to part of the email provider’s domains, create a separate ISP record and move the required domains into it.

Overriding Headers​

In AKMTA ISP records, you can modify email headers:

  • Add a header — by specifying the key and its value.

  • Delete a header — by specifying the key you want to remove.

Last updated on Feb 25, 2025
Previous
Keys
Next
Pools
  • Description
  • When is customization needed?
  • Creating, Editing, and Deleting
  • ISP Record Settings
  • Overriding Headers
© 2015 - 2026 Altcraft, LLC. All rights reserved.