Knowledge base

Seeding and seed mailboxes

entries in this scenario: 9
enable-inline-seedingGlobalDirectiveEnables 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>DirectiveThe 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>DirectiveHow 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>DirectiveThe 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>DirectiveExactly forty hexadecimal characters; without it seeding does not work at all.Job headercriticalMechanismThe 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 addressesMechanismThe 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 blockThe 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 blockThe block enables seeding campaigns with the vendor’s addresses; it requires a key and a paid subscription and recommends a restart after adding.