Tagline: Send, schedule and receive email from Jira. Templates with logic, per-project rules, scheduled digests, replies that land back on the issue, and an audit trail on the work item. US$3 a month for up to 10 users, then from US$0.60 per user.
Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Mailpost for Jira. You need to be a Jira administrator.
Out of the box Mailpost sends through Jira's own notification service. Nothing has to be set up, and no data leaves Atlassian.
This step is entirely optional and off by default. Turning it on lets mail leave from your own domain and enables inbound replies.
Mailpost puts "Email this issue" in the issue actions menu and an "Email history" panel on the issue. Pick a template, choose who gets it — reporter, assignee, watchers, voters, named users, groups, project roles, the people in any user-picker field, or a typed address — and send. Every send is recorded on the issue, searchable across the site, and optionally posted back as a comment.
Beyond the manual send, Mailpost does the three things a team usually reaches for a second tool to get: rules that email automatically when something happens on a project, scheduled digests that mail a JQL filter's results on a cadence, and inbound mail that turns a reply into a comment on the issue it names.
Mailpost has two delivery paths, and you choose per site.
Jira's own notification mail is the default. No SMTP server, no API key, no mailbox, no third party, no egress — nothing about your issues leaves Atlassian. It reaches Jira accounts, groups and project roles.
A bring-your-own email provider (Postmark) is opt-in. Switch it on and Mailpost can also reach addresses with no Jira account, attach real files, place inline images, and accept inbound mail. Switching it on means data leaving Atlassian, to api.postmarkapp.com and nowhere else, and it means this app is no longer "Runs on Atlassian" for your site. It is off by default; a site that leaves it off makes no outbound request at all. The admin page states this where you make the decision, not in a footnote.
{{issue.summary}}, {{issue.customfield_10010}}, {{issue.Severity}} by field name, {{#if issue.assignee}}…{{else}}…{{/if}}, {{#unless}}, {{#each issue.comments}}. No Velocity, no arbitrary code — a template cannot loop forever, read something it should not, or become an injection vector.Scopes: read:jira-work, read:jira-user, read:issue:jira, read:comment:jira, read:comment.property:jira, read:issue-type:jira, read:user:jira, read:group:jira, read:project:jira, read:project-role:jira, read:field:jira, write:jira-work, send:notification:jira, write:comment:jira, write:comment.property:jira, write:issue:jira, storage:app, and — only when you enable the provider — network access to api.postmarkapp.com.
write:jira-work is broader than what the app does, and it is there for a specific reason: Jira does not honour the narrower granular write scopes for an app-authored write, and inbound mail and rules have no signed-in user to write as. We verified this on a live site — with only the granular scopes, an app-authored comment answers 401 "scope does not match".
Because the scope is broader than the behaviour, the behaviour is pinned by a test rather than by this paragraph: the codebase issues no PUT and no DELETE to Jira, never touches /transitions or /assignee, and POSTs only to /notify, /comment, /issue and the two search endpoints. Mailpost cannot edit, transition, reassign or delete anything.
| Users | Mailpost | Email This Issue (Standard) | (Advanced) |
|---|---|---|---|
| 1–10 | US$3.00 / month flat, every feature | US$10.00 / month | US$40.00 / month |
| 11–100 | US$0.60 / user / month | US$2.00 | US$4.00 |
| 101–250 | US$0.45 | US$1.20 | US$2.50 |
| 251–1,000 | US$0.30 | US$0.40 | US$0.70 |
| 1,001+ | US$0.20 | tapering from US$0.40 | tapering from US$0.48 |
A 25-person team pays US$15/month instead of US$50. A 100-seat site pays US$60 instead of US$190. A five-person team pays US$3/month, against US$10 or US$40 for the same team on either of the incumbent’s editions.
Why we can charge this: the incumbent runs its own mail infrastructure — servers, mailbox connectors, queues, deliverability and the support load that comes with it — and the price has to carry that. Mailpost hands the message to Atlassian's pipeline, or to a provider you already pay for, and stores a few kilobytes in Forge storage. There is no infrastructure of ours for you to fund.
Two honest notes. Above roughly 1,000 seats the incumbent's taper can land below our flat US$0.20 — price-check both. And their Advanced edition exists partly to sell faster inbound processing and faster support; with Mailpost those are not something you can buy, because they are not something we throttle.
Feature-for-feature against Email This Issue (4.4★, ~5,700 installs) Mailpost matches the day-to-day job and goes further on the things their own reviewers ask for: scheduled digests (they have none, on either platform), template version history (none), per-user signatures on Cloud (none), rate limiting to prevent mail storms (none), a configuration audit log (theirs is a paid upsell), and inbound processing that is not queued behind other customers — their documentation puts the Standard baseline at 5–7 minutes "depending on the actual load of all customers".
They remain ahead on mailbox breadth (POP3/IMAP/Gmail/Microsoft 365/S/MIME), on setting fields and running transitions from inbound mail, and on ten years of maturity. The full matrix, with their live pricing and the Forge limits we cannot work around, is in COMPETITORS.md.
One more thing worth knowing when you compare: their Cloud app is an Atlassian Connect app, and Connect reaches end of support in December 2026. Their published migration status still lists Jira event handling and their backend layer as "Planned". Mailpost is Forge-native today.
Email support with a one-business-day response — the same response for everyone, not a paid tier. The template language, the full placeholder list, the send-log shape and the inbound webhook contract are documented, so you can build templates and read the logs from your own tooling.