Demo
Demo

Knowledge base

PMTA knowledge base›Block <acct-file>›Directive§ 3.3.11.3

move-interval

<acct-file>

How often to close the accounting file and start a new one
in the configuration this is a linemove-interval 1dinside the block <acct-file>
Time-based rotation — if there is somewhere to move to

The line sets how often the engine closes the accounting file and starts a new one. The default is 1d.

🔴 It works only together with move-to. Without a destination directory the interval is silently ignored — the manual says so plainly. There will be no warning.

The second closing condition is size, max-size, and it works independently: the file starts over on reaching the ceiling even without a directory.

This line is not for the webhook. There the rhythm of batches is set by http-webhook-max-interval, and the manual refers to it explicitly.

The main trap is mistaking a set interval for working rotation. A line without a destination directory is the quietest kind of misconfiguration: it breaks nothing and does nothing.
What the Hub does. It does not write it — the line was removed from the templates on Aug 29, 2026.

Why it was removed rather than supplemented with a directory. The move has to be on the same volume, so it will not free up space; and delete-after stops working with move-to active, so files would start piling up in the archive directory with no expiry. The accounting file already has rotation: it is closed at max-size 25M and deleted after seven days.

Recommended values

The interval makes sense only with a destination directory:

Value When
1d (default) files are picked up once a day
1h an external collector comes often
without move-to does not work at all

For the webhook — a different line, http-webhook-max-interval.

The 1d default, silent ignoring without move-to and the reference to the webhook line come from the manual (§ 3.3.11.3). The analysis of our configuration is based on the Hub’s template.
Example configuration
# both lines are needed together, otherwise the interval stays silent
<acct-file /var/log/pmta/acct.csv>
    move-to /var/log/pmta/archive
    move-interval 1h</acct-file>
Remove the first line — and the second will stop doing anything without saying so.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
▲

Common mistakes and problems

what people get wrong and how it ends2 mistakes▶

Setting the interval without a destination directory

§ 3.3.11.3

What it costsThe line is silently ignored. The file is not closed by time, and size remains the only limiter.
How to spot itThe accounting file grows to the size ceiling rather than to the end of the interval.
How to do it rightAdd move-to or remove the line.

Configuring the webhook rhythm with this line

§ 3.3.11.21

What it costsIt has no effect on the webhook. Batches keep going out by their own default — every five minutes.
How to spot itThe interval was changed, data freshness is the same.
How to do it rightUse http-webhook-max-interval.
Compatibility
PowerMTA 6.0
described in the manual of this version · platform: any
The vendor does not state the first version for every directive — there is no note here. The name also appears in the 5.0 edition of the manual.
Reference data
Syntax
move-interval <time-interval>
Values
a time interval
Default
1d § 3.3.11.3
Applying
reload, no restart needed
Queue
will not touch what is already queued
Where to write it
<acct-file>
How many times
once in the block
Everything here comes from the manual, with the section.
Inheritance
No inheritance: the line lives inside its own <acct-file>. Different accounting streams close on their own schedule — and for a stream going out via the webhook this line does not apply at all.
⇄

Related directives

2 relations

Does not work without

move-to<acct-file>Without a destination directory the interval is silently ignored — nothing is moved. § 3.3.11.2

Applies to

The telemetry contractSets how often the file of this stream is closed. § 3.3.11.3

How to check on the node
Rotation is visible from the modification times of files in the destination directory:
ls -la --time-style=full-iso /var/log/pmta/archive/ 2>/dev/null | tail -5
The gaps between files should match the interval. Nothing — the directory is not set, and the interval does not work.
◇

What else to read

3 articles

◇What the node tells about itself and through which channelsSeven observation surfaces: the web monitor, the console in four formats, the log, accounting, accounting search, metrics and export to external analytics.◇Two inbound report processors and what to do with themBounces by message and complaints are parsed by two identically structured blocks; each has its own address list and its own pair of decisions about the message’s fate.◇Five ways for a queue to hand off a messageA queue does not have to use SMTP: it can write to a file, run a program, call over HTTP or discard.

In the Hub
Managed at
Analytics → Node accounting
Cost of a mistake
reversible: harms only while it is set
Scenarios
Collect telemetry
Neighboring settings of the block <acct-file>:record-fieldsrecordssynciso-timesmove-toAll 26 directives of the block →