The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can emails from Jira automation be signed?

Michael S_ Williamson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 9, 2026

Cryptographic signatures solve a lot of anti-spam problems, and at my organization are not subject to alteration by their "safelinks" product. Can this be enabled? I'd be willing to buy a cert if needed.

2 answers

2 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Gabriela - LeanZero
Atlassian Partner
July 9, 2026

Hi Michael, no, the Send email action can't attach a cryptographic signature. Automation hands the message to Atlassian's mail servers to send, so there's no point where you can sign it with your own S/MIME or PGP certificate. Buying a cert won't help here because the action gives you nowhere to apply it.

Arkadiusz is pointing you somewhere useful though. What you can improve for anti-spam is domain authentication, so SPF, DKIM and the DMARC record he linked. That's what mail providers check to decide your automation mail is legitimate, and getting all three aligned is usually what keeps these out of spam. On Cloud, Atlassian already publishes SPF/DKIM for its own sending domain; your part is the DMARC record, and if you send from your own domain, aligning that domain's SPF/DKIM too.

If a per-message cryptographic signature is a hard requirement, the route is to take the send off the native action: use a Send web request (or your own SMTP relay/gateway) to a mail service that signs with your certificate, and let that system deliver the message. The signing happens on your side, not inside Jira.

Which of the two you need comes down to the goal, deliverability is the domain-auth route, a genuinely signed message is the external-relay route.

3 votes
Answer accepted
Arkadiusz Wroblewski
Community Champion
July 9, 2026

Hello and Welcome to Atlassian Community @Michael S_ Williamson 

It depends a little on what kind of “signature” you mean.

Atlassian Support it partly What are the DNS records required for configuring DMARC? | Atlassian Support

Best,

Arek🤠

Michael S_ Williamson
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 9, 2026

S/MIME cryptographic signatures of the email message itself is what I'm looking for. We have this inline product called "Safelinks" at my institution that annoyingly re-writes URLs on all unsigned emails, making them pretty much unreadable. 

Like Steffen Opel _Utoolity_ likes this
Arkadiusz Wroblewski
Community Champion
July 9, 2026

Hm, you can also Use Automation's Send web request action to route the notification payload to an external service or internal mail gateway that handles S/MIME signing before delivery.

You need either policy tweak or external relay.

 

Like # people like this
TAGS
AUG Leaders

Atlassian Community Events