What to attach so the conversation happens
When you could not figure it out on your own, open a ticket with SparkPost support; trial users and customers with a support contract also have email and phone.
Support has a single tier: for a request during US Eastern business hours, the first response usually comes within a few hours. Attach recent configuration and load changes to the request, and the crash message if there was one.
The main trap is restarting and cleaning up the node before collecting information. The crash message, the dump and the queue state are what they ask you to attach; after a restart and cleanup, some of it can no longer be collected.
What the Hub does. Contacting the vendor remains with the license owner. It is useful to know in advance what exactly is asked to be attached: collecting it after the node restarts is usually no longer possible.
Recommended values
Channels and what to attach:
| What |
Where or what |
| ticket |
the SparkPost support site |
| email |
powermta-support@sparkpost.com |
| attach |
recent configuration and load changes, the crash message |
The channels, the support tier, the response time and what to attach come from the manual (§ 4.2.5–4.2.6). The table is ours.
Example configuration
# version and license — the first things they will ask for
pmta show versionpmta show license
The version and license lines are copied into the request as is.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.