Unable to configure Outgoing E-Mail Notifications due to error: 501 5.5.4 Invalid domain name
プラットフォームについて: Data Center のみ。 - This article only applies to Atlassian apps on the Data Center プラットフォーム。
この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。 Server* 製品のサポートは 2024 年 2 月 15 日に終了しました。Server 製品を実行している場合は、 アトラシアン Server サポート終了 のお知らせにアクセスして、移行オプションを確認してください。
*Fisheye および Crucible は除く
症状
When configuring e-mail for outgoing notifications, you get an exception: 501 5.5.4 Invalid domain name and if you enable DEBUG logging for outgoing mail, the following appears in the logs:
http-bio-8080-exec-17 DEBUG jiraadmin 805x4100x1 3anfad9 10.1.1.1 /secure/admin/VerifySmtpServerConnection!update.jspa [com.atlassian.mail.outgoing] DEBUG SMTP: connected to host "smtp.mycompany.com", port: 25
http-bio-8080-exec-17 DEBUG jiraadmin 805x4100x1 3anfad9 10.1.1.1 /secure/admin/VerifySmtpServerConnection!update.jspa [com.atlassian.mail.outgoing] EHLO jira.mycompany.com.
http-bio-8080-exec-17 DEBUG jiraadmin 805x4100x1 3anfad9 10.1.1.1 /secure/admin/VerifySmtpServerConnection!update.jspa [com.atlassian.mail.outgoing] 501 5.5.4 Invalid domain name
http-bio-8080-exec-17 DEBUG jiraadmin 805x4100x1 3anfad9 10.1.1.1 /secure/admin/VerifySmtpServerConnection!update.jspa [com.atlassian.mail.outgoing] HELO jira.mycompany.com.
http-bio-8080-exec-17 DEBUG jiraadmin 805x4100x1 3anfad9 10.1.1.1 /secure/admin/VerifySmtpServerConnection!update.jspa [com.atlassian.mail.outgoing] 501 5.5.4 Invalid domain name原因
The first thing that happens after a TCP connection to the SMTP port at the remote mail server has been established is that the client sends the message "EHLO [hostname]" to establish the SMTP connection and state its own hostname. This name has to be a Fully Qualified Domain Name (FQDN) and if it does not follow that format Microsoft Exchange will throw an "Invalid domain name" error and reject the connection. (Other mail servers might have similar issues.)
例
In the log example above, the name "jira.mycompany.com." after "EHLO" has a trailing dot (.) which is not allowed in this SMTP handshake context. This caused Microsoft Exchange to reject the connection.
ソリューション
The SMTP client in Jira fetches the name to use from the hostname defined in the operating system and it needs to be corrected there to be a correctly formatted FQDN. On Linux this name is often found in the
/etc/hostnamefile (but can be in another location, depending on the distribution)
この内容はお役に立ちましたか?