Demo
Demo

Knowledge base

PMTA knowledge base›Block Global›Directive§ 3.3.1.56.2

pickup-retry-interval

Globaldeprecated

Retry interval for the pickup directory — deprecated
in the configuration this is a linepickup-retry-intervalinside the block Global
A line the manual is silent about

The manual gives this directive a separate section (§ 3.3.1.56.2) and writes nothing in it except the mark Deprecated. No purpose, no syntax, no default, no pointer to a replacement.

From the name and its place in the section on the pickup directory, one can assume that the line set how often the engine rereads the directory — but that is our guess, not a fact from the manual.

The directive names no replacement. Judging by the description of the submission method itself, the engine now processes the directory on its own and needs no frequency setting.

The main trap is taking silence for a description. The section exists, it has a number, the name is telling — and this creates the impression of a working setting. In fact nothing is known about it, including whether it has any effect at all.

A line found in an old configuration is better removed than given a value by trial.

What the Hub does. It does not write it: the pickup directory is not declared at all.
Recommended values

What to set. Nothing:

Value When
do not write always: the directive is deprecated and not described

If the line turns up in an old configuration — remove it. Testing its effect by trying values is not worth it: the manual gives neither a range nor a default, and there is nothing to compare the result with.

The deprecation mark is the only thing the manual says about this directive, § 3.3.1.56.2. There is no purpose, syntax, default or replacement there. The guess about its meaning from the name is ours.
Example configuration
# the manual has no example: the section contains only the deprecation mark
# pickup-retry-interval <value not described>
There is nothing to show in an example here: the manual gives neither syntax nor default. A line from an old configuration is better removed.
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▶

Taking a telling name for a description

§ 3.3.1.56.2

What it costsNothing is known about the directive — including whether it has any effect. Time goes into tuning whose result has nothing to be compared with.
How to spot itThe line is in the configuration, and nobody can say what it does.
How to do it rightRemove it and do not try values: the manual gives neither a range nor a default.

Leaving deprecated lines in the configuration “just in case”

our experience

What it costsThe configuration grows with lines nobody knows anything about. At the next investigation they take up time, and they do not explain the node’s behavior.
How to spot itThe configuration contains directives marked as deprecated.
How to do it rightRemove them along with the move to the replacement — and where there is no replacement, simply remove them.
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
pickup-retry-interval <time-interval>
Values
not described in the manual
Applying
reload, no restart needed
Queue
will not touch what is already queued
Where to write it
Global
How many times
once in the block
Everything here comes from the manual, with the section.
Inheritance
The directive is written at the root of the configuration file, like the other pickup directory settings. The manual says nothing about scope or inheritance — as about everything else in this section.
⇄

Related directives

1 relation

Applies to

pickupGlobalBelonged to the same pickup directory; today it has one working setting left. § 3.3.1.56.2

How to check on the node
The only meaningful action is to look for the line in an old configuration:
grep -n 'pickup-retry-interval' /etc/pmta/config
Found — remove it. There is nothing to check its effect with: the manual gives neither a default nor a range, so there is nothing to compare the result with.
In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Neighboring settings of the block Global:always-allow-relayingsmtp-listenerrelay-debugrelay-addresspickupAll 108 directives of the block →