The task. A receiver rejects or defers messages from one address while accepting the others — and that address must stop being used specifically for it: temporarily, without touching its sending elsewhere and without relying on someone remembering to bring it back.
What it is made of:
The parts have different scopes. Withdrawal applies to an “address and queue” pair, and the radius is set by the queue selector, as with any command. A star turns a pinpoint withdrawal into a withdrawal for all recipients.
How they interact. Proof, action, deadline, reconciliation — these four parts distinguish deliverability management from a pile of forgotten bans. The deadline does the most work: an address withdrawn with a deadline returns by itself, and a wrong diagnosis costs one interval. Reconciliation catches cases where no deadline was set.
The automatic “IP in a blocklist” policy works differently: an address in a blocklist hurts with all receivers at once, while disable source takes only one queue — to a star the engine replies “Invalid queue name: may not be wildcard.” So the policy pauses all sending addresses that send from this address, for the deadline from the rule (four hours by default), and the Hub lifts the pause.
Four parts:
| Part | Command | What it gives |
|---|---|---|
| proof | pmta show domains –vmta=vmta1 –errors gmail.com | the recipient’s errors for a single sending address |
| action | pmta disable source –reenable-after=4h 198.51.100.25 gmail.com/vmta1 | the address is withdrawn only for this queue and will come back by itself |
| reconciliation | pmta show disabled sources gmail.com/vmta1 | what is withdrawn now |
| correction | pmta enable source 198.51.100.25 gmail.com/vmta1 | return before the deadline |
# withdraw the address only for gmail.com and bring it back in four hours pmta disable source --reenable-after=4h 198.51.100.25 gmail.com/vmta1pmta show disabled sources gmail.com/vmta1
pmta show disabled sources