Email This Issue
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
Email This Issue - for Jira Cloud
Email This Issue - for Jira Cloud
  • ⬇️Overview
  • Email This Issue - for Jira Cloud
  • Features
  • How Email This Issue Works
  • Secure the email channel with Email This Issue
  • Comparing Email This Issue and Jira Cloud
  • 📤Outgoing Emails
    • Outgoing emails overview
    • Manual emails
      • Configuring manual emails
      • Sending manual emails
    • Email notification schemes and email notifications
    • Workflow post functions
    • Advanced email configuration
    • Customizing email templates
    • Canned Responses (default messages)
    • Scope evaluation
  • 📥Incoming Emails (Mail Handlers)
    • Incoming emails overview
  • Mail handlers - adding / editing
    • General handler settings
    • Filtering
    • Finding issues
    • Setting up rules and actions in the actions editor
      • Adding/editing actions
      • Adding recipients to Request Participants
      • Creating an issue
      • Updating an issue
      • Setting field values
      • Adding comments
      • Sending auto-reply emails
      • Executing workflow transitions
      • Creating a customer
      • Using split regexp
      • Conditions
      • Approve request
      • Decline request
    • Maintaining email chains
    • Mail Handler New UI
  • Global Sender Address Filters
  • Attachment Filters
    • Regular Attachment Handling Deprecation
  • 🤓Administration
    • Outgoing Mail Connections
    • Alerting via Webhooks
      • Webhooks
        • Configuring Slack to receive alerts via webhooks
        • Configuring OpsGenie to Receive alerts via webhooks
        • Configuring Microsoft Teams to receive alerts via webhooks
      • Webhook execution logs
    • Mail Queue
    • Email Audit Log
    • Permissions
    • Recipient Restrictions
    • Incoming Mail Connections
    • Email Security
    • Incoming Mail Queue
    • Incoming Mail Log
    • OAuth2 Credentials
      • Enabling OAuth2 Authorization in your Google Account
      • Enabling OAuth2 Authorization in your Microsoft 365 Account
      • Troubleshooting guides for Microsoft OAuth2 Connections
        • How to fix "BAD User is authenticated but not connected" error​
        • How to fix "401 Unauthorized" error
        • How to fix "key expires_in " error
        • How to fix "Need admin approval" error
  • ☁️Server to Cloud Migration
    • 🛫Server to Cloud - Automatic Migration tool
      • Preparing for the migration
      • Doing the migration
      • Finalizing the migration in Cloud
      • Migration with unsupported Jira versions causes errors
    • Server to Cloud - Manual migration guide for Email This Issue
  • ❓FAQ
    • No recipients error in outgoing emails
    • How-to add custom macro to email Template?
    • Why cannot I select custom event types in notification?
    • How to configure the Email This Issue addon user in Jira Cloud?
    • I get an error: Could not create request on behalf of the sender
    • Why is the Incoming Mail Queue size limited?
    • Outgoing mail not sent - Read timeout error
    • Access restriction icon is not appearing when adding internal attachments via Email this Issue
  • 🌪️General
    • Release Notes
    • API
      • API for Velocity Context Objects - 1.7
      • API for Velocity Context Objects
    • Addon Pages
      • Integrity Check
      • Feedback and Support
    • Security Advisories
      • Email This Issue Security Advisory September 28, 2020
    • Appendix
      • Supported Time Zones
    • Integration of Glass Documentation
Powered by GitBook
On this page
  • Encryption
  • Digital Signatures

Was this helpful?

Secure the email channel with Email This Issue

PreviousHow Email This Issue WorksNextComparing Email This Issue and Jira Cloud

Last updated 1 year ago

Was this helpful?

Emailing is accessible and available all the time, but the importance of using it as a secure channel of communication is somewhat neglected. In its purest form, an email is a plain text file. It is easily readable even if it has rich content or is Base64 encoded. Its content may be read and altered by a malicious interceptor entity.

Two techniques are available at hand to secure an email channel:

  • Encryption

  • Digital Signatures

Encryption

Email encryption uses cryptographically secure algorithms to encode the content of emails making it impossible for an unauthorized party to extract and interpret it

Encryption is based on certificates, cryptography protocols and algorithms (such as s/mime and pgp, RSA) and encryption keys (public and private keys).

The sender must obtain the recipient's public key to encrypt the email content. The recipient uses its private key to decrypt the encrypted content.

This flow is now supported by Email This Issue's mail handler. However, some administrative steps must be done first to start using this secure form of emailing.

  1. Obtain the PCKS Certificates (as of now, only S/Mime is supported) containing the private keys

  2. Upload the Certificates in . We store your certificates and private keys in a highly secure, encrypted form to ensure no one can access them.

  3. Associate the certificates with the through which you wish to receive encrypted emails.

  4. Dispatch the public keys to your stakeholders, partners, customers, and colleagues so that they can configure their mailing system to encrypt the emails they send you.

Once everything is set up, Email This Issue will be able to decrypt the emails, extract content and create issues, comments, initialize issue fields etc just like from unencrypted, plain text emails.

An encrypted email's header part is unencrypted and readable plain text. Encryption secures the body content, attachments and embedded files.

Digital Signatures

Digital signatures are encrypted hashes of the email content used to validate that the content was not altered during its journey from the sender to the recipient.

If the validation of a digital signature fails, the content of the email is considered untrustable.

Digitally signed emails may or may not be encrypted. This means that the two techniques may be combined or used separately.

Email This Issue may be able to process digitally signed emails but does not validate signatures. If you are interested in this feature, please .

Email This Issue
Incoming Mail Connections
contact our product support team