mailerpress/get-campaign-email-logs returns a paginated per-email log for a campaign from MailerPress’s email logger.
Rows carry the recipient, subject, the SMTP service that handled it, the status and any error message.
At a glance
| Ability | mailerpress/get-campaign-email-logs |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Campaigns & Sending |
| Requires | AcrossAI Pro, plus MailerPress active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
This is the provider-level view, as against the engagement view in mailerpress/get-campaign-logs. It answers whether the email left the site and what the provider said about it.
Filtering to error is the useful mode. A campaign with a hundred failures usually has one cause — an authentication problem, a rate limit, a rejected sending domain — and the error messages say which.
The service column matters on sites with more than one provider configured. Failures concentrated on one driver point at that driver rather than at the campaign.
pending rows are emails the logger has recorded and the provider has not yet confirmed, which on a large send is normal mid-flight and suspicious afterwards.
These rows accumulate indefinitely — MailerPress provides no retention policy — which is what mailerpress/prune-email-logs exists for.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The campaign ID. |
status | string | No | success, error or pending. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
logs | array | Per email: recipient, subject, service, status, error message and timestamps. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Why did some of those emails fail?
It resolves to one call:
{
"ability": "mailerpress/get-campaign-email-logs",
"parameters": {
"id": 44,
"status": "error"
}
}Worth knowing
- Provider-level, not engagement. This is whether the email left the site.
- A hundred failures usually share one cause, named in the error messages.
- Failures concentrated on one service point at that service.
- These rows accumulate forever unless pruned.
Related abilities
- MailerPress Prune Email Logs — the retention problem
- MailerPress Get Campaign Logs — the engagement view
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category