Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
D
e
m
o
Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
D
e
m
o
Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog
Home
Knowledge base
Knowledge base
PMTA knowledge base
›
Scenario
Seeding and seed mailboxes
entries in this scenario: 9
enable-inline-seeding
Global
Directive
Enables seeding at the node, pool or sending address level; the default depends on whether the seeding block is declared, and the value true without a subaccount does not inherit it.
batch-frequency
<inline-seeding>
Directive
The interval of requests to the service for counters and seed assignments; the default is fifteen seconds, the range is from 15 seconds to five minutes.
eligibility-ttl
<inline-seeding>
Directive
How long the job eligibility flag is kept; the default is five minutes, the range is from 5 minutes to an hour.
persist-threshold
<inline-seeding>
Directive
The number of messages of one job before contacting the service; the default is five, the range is from 5 to 999.
api-key
<inline-seeding>
Directive
Exactly forty hexadecimal characters; without it seeding does not work at all.
Job header
critical
Mechanism
The
x-job
header tags a message with a job; the node reads it only if the source is allowed
process-x-job
, and then the job is visible in accounting, the monitor and pause commands.
Seeding campaigns with control addresses
Mechanism
The engine mixes the vendor’s addresses into a mailing, and the result is viewed in the vendor’s deliverability tool; independent of event export.
<signals>
Configuration block
The block enables sending accounting data to the vendor’s service; the engine chooses the data composition, the scope is set with a separate line.
<inline-seeding>
Configuration block
The block enables seeding campaigns with the vendor’s addresses; it requires a key and a paid subscription and recommends a restart after adding.