How are E-Mails Handled in Jira?

[Slifer]

I have set up an outgoing SMTP mail server in Jira with the address jira@mydomain.com. I have also created a mail handler (IMAP) with the address myproject@mydomain.com for a Jira project.

New Mails to myproject@mydomain.com will be created in myproject,

This e-mail address is also stored in the notification scheme. So when a Issue gets Updated a mail will be send from myproject@mydomain.com.

I did not (to my knowledge) gave jira@mydomain.com "Send As" permission for myproject@mydomain.com

When a E-Mail Message is send from my project ,What is the Envelop From adress?

I assume that the Envelop From ( for the MTA) is jira@mydomain.com and the header from (for the MUA) is myproject@mydomain.com? Am I right about this?

I don't have access the corresponding logs on our company mail server.

[Pablo Brincat]

Hi Slifer,

Your setup in Jira for handling emails involves both incoming and outgoing mail configurations. Let’s break down how Jira typically handles these emails based on your setup:

Outgoing SMTP Mail Server (jira@mydomain.com)

This server is used by Jira to send notifications, issue updates, etc. The “From” address for these emails is usually determined by the Jira mail server configuration.

• Envelope From Address: Typically, the envelope from address (used for SMTP communication) will be jira@mydomain.com, as this is the address configured for the SMTP server in Jira.

Incoming Mail Handler (IMAP with myproject@mydomain.com)

This is used to create issues or comments from incoming emails sent to myproject@mydomain.com. When someone sends an email to this address, Jira processes it according to your mail handler’s configuration.

• Handling Incoming Mails: Emails sent to myproject@mydomain.com are processed by Jira to create or update issues in the designated project.

Notification Scheme with myproject@mydomain.com

You mentioned this email address is stored in the notification scheme. This implies that notifications about issue updates from your Jira project might be sent using this address.

• Header From Address: The “From” address in the email header (what the recipient sees) could be myproject@mydomain.com, especially if it’s specified in the notification scheme.

Understanding ‘Send As’ Permission

The ‘Send As’ permission allows one email address to send emails as if they are coming from another address. In your case, you didn’t explicitly give jira@mydomain.com the “Send As” permission for myproject@mydomain.com. However, how this is handled depends largely on your mail server’s configuration and policies.

Envelope From vs. Header From

• Envelope From: This is typically the address the email is sent from at the SMTP level, likely jira@mydomain.com in your case.
• Header From: This is the address the end users see, which could be myproject@mydomain.com if specified in your notification scheme.

Verification and Testing

Since you don’t have access to the mail server logs, you can test this setup by:

1. Sending Test Emails: Create or update an issue and see what the outgoing email looks like from a recipient’s perspective.
2. Inspect Email Headers: Look at the full headers of the received email. Most email clients allow you to view the source or headers of an email, which will show both the “Envelope From” and “Header From” addresses.

Conclusion

Based on your description, it seems your assumption is correct:

• The Envelope From is likely jira@mydomain.com (SMTP level).
• The Header From (visible to users) is likely myproject@mydomain.com.

However, this can vary based on specific server configurations and Jira settings. Testing and inspecting email headers will provide more clarity.