How to Configure Outbound Proxy for Mailing in Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article describes how to configure proxy server for incoming and outgoing mail in Jira.
Environment
8.13.x onwards
Solution
Atlassian applications allow the use of proxies with our products; however, Atlassian Support does not provide assistance for configuring them. Consequently, Atlassian cannot guarantee providing any support for them. Please test the efficacy of the article in a test environment first.
If assistance with configuration is required, please raise a question on Atlassian Community.
Starting with Jakarta Mail 1.6.0 APIs used in JIRA 8.13.x onwards for mailing functionality. As per published Jakarta Mail FQA, Jakarta Mail supports accessing mail servers through Web or Socks proxy server by setting JVM or System properties. Based on your proxy type either web or socks, you may apply the appropriate JVM properties mentioned below.
Incoming Mail
Web_Proxy | Socks_Proxy | |
IMAP | mail.imap.proxy.host mail.imap.proxy.port mail.imap.proxy.user mail.imap.proxy.password | mail.imap.socks.host mail.imap.socks.port |
IMAPS (Secured) | mail.imaps.proxy.host mail.imaps.proxy.port mail.imaps.proxy.user mail.imaps.proxy.password | mail.imaps.socks.host mail.imaps.socks.port |
POP3 | mail.pop3.proxy.host mail.pop3.proxy.port mail.pop3.proxy.user mail.pop3.proxy.password | mail.pop3.socks.host mail.pop3.socks.port |
POP3 (Secured) | mail.pop3s.proxy.host mail.pop3s.proxy.port mail.pop3s.proxy.user mail.pop3s.proxy.password | mail.pop3s.socks.host mail.pop3s.socks.port |
Outgoing Mail
Web_Proxy | Socks_Proxy | |
SMTP | mail.smtps.proxy.host mail.smtps.proxy.port mail.smtps.proxy.user mail.smtps.proxy.password | mail.smtps.socks.host mail.smtps.socks.port |
Where: host -> proxy address, port -> proxy port, user ->(optional)username , password -> (optional) password
Unfortunately, username and password to log into SOCKS proxy could not be set and needs anonymous access.
Was this helpful?