The block’s name is the path itself to the directory: <spool /var/spool/pmta>. Inside there are four lines, all about the behavior of this directory.
At least one directory is mandatory. Additional ones are added for speed: the manual names the reason directly — to spread the I/O load across several disks.
priority decides which directory is used first: the higher the priority, the earlier it is used, and with equal priorities the directories alternate. min-free-space sets the free space threshold below which the directory stops accepting messages.
The remaining two lines are about special modes. deliver-only turns a directory into “deliver only”: messages from it are delivered, and new ones are not written. delete-file-holders decides the fate of the temporary files the engine keeps to save I/O.
There are also two obsolete forms of the same thing: spool and spool-min-free-space at the node level, both replaced by this block.
# two directories on different disks: primary and backup <spool /var/spool/pmta/primary> priority 50 min-free-space 1G </spool> <spool /var/spool/pmta/secondary> priority 10 min-free-space 1G </spool>
0 relations
spoolGlobalThe replacement: the same location, but with priority, a free space threshold and modes. § 3.3.1.5spool-min-free-spaceGlobalThe replacement lives inside this block: each directory’s own threshold instead of a common one. § 3.3.1.7delete-file-holders<spool>One of the block’s four lines: the fate of temporary files after a message is delivered. § 3.3.2.1deliver-only<spool>One of the block’s four lines: the mode of this location. § 3.3.2.2priority<spool>One of the block’s four lines: the order in which locations are used. § 3.3.2.3
3 articles
◇The activation key is a prerequisite for installation, not a step after itWithout an activation key from SparkPost support the engine neither installs nor runs, and the license tier sets the outbound connection ceiling: on Standard everything above 200 is ignored.◇Cloud restrictionsClouds restrict outbound mail on port 25 until you ask them to lift the limit, and mailbox providers treat their address ranges with suspicion.◇How to turn a sending plan into hardwareTwo constants for sizing any node: about 2 KB of memory per queued recipient and spool space proportional to the total size of the messages.