Email delivery
Email delivery sends a generated document to one or more recipients — typically as part of a scheduled export. It is provided by the Exportelier Automation app.
BYO and Managed delivery
- Bring your own provider (BYO): you supply your own provider credentials, and messages are sent through that provider. BYO recipients do not count toward Exportelier's Managed Mail cap.
- Managed Mail: Exportelier sends through its provider. At launch, Managed Mail is capped at exactly 500 recipients per Jira site and UTC calendar month. Each recipient counts, so one message sent to five addresses uses five recipients. If a send would exceed the cap, Exportelier rejects it before calling the mail provider.
Who the message comes from
The two modes differ in what recipients see:
| Sender shown to recipients | Configured by you | |
|---|---|---|
| Managed Mail | [email protected] (fixed) | The reply-to address — replies go there |
| BYO | The address you authenticated with your own provider | The from address |
Managed Mail cannot send under your own address. Email providers only accept a message as genuine if its cryptographic signature matches the sender's domain, and Exportelier can sign only for its own domain. A message claiming to come from your domain but signed by Exportelier's would fail your domain's DMARC policy — quarantined, or silently rejected at strict recipients. Putting your address in Reply-To keeps replies with you without breaking that check.
If recipients must see your own domain as the sender, use BYO and authenticate your domain in your own provider account.
Choosing BYO
BYO gives you control over three things that Managed Mail decides for you:
- The sender. Authenticate your own domain in your provider account and recipients see your address, correctly signed.
- Your own sending quota. BYO recipients do not count toward the Managed Mail cap.
- Tracking and unsubscribe headers. Brevo adds an open-measurement pixel and a one-click
List-Unsubscribeheader based on account settings. In BYO those are your account's settings, so you can disable or anonymise them yourself. In Managed Mail they follow ours.
That last point matters more than it looks. A recipient who clicks the unsubscribe button is blocklisted by the provider, and further scheduled exports to that address will fail. With BYO you decide whether that button exists.
If your organisation is privacy-sensitive, BYO is the cleaner mode — the data path ends at your own provider account, under your own contract.
Handling the API key safely
- Create a dedicated API key for Exportelier rather than reusing an existing one. A Brevo v3 API key grants account-wide access, so a key shared with other integrations cannot be revoked without breaking them.
- The key is stored encrypted and is never shown again after saving. Exportelier displays only a masked placeholder.
- To disconnect: remove the configuration in Exportelier and revoke the key in your provider account. Doing only one of the two leaves a working credential behind.
Configuring recipients
Add recipient addresses to a schedule or delivery rule. You can template the subject and body so each message has meaningful context.
Email delivery with recipients and an optional subject.
Attachment size
Very large documents may exceed email attachment limits. Download the generated file directly or split the export into smaller result sets — see Large exports & background jobs. Slack and Microsoft Teams webhooks send notification metadata only; they do not deliver the generated document.
Email is sent only by the Automation app, with the egress isolation described in Security architecture.