Skip to main content

此版本的 GitHub Enterprise 已停止服务 2022-10-12. 即使针对重大安全问题,也不会发布补丁。 为了获得更好的性能、更高的安全性和新功能,请升级到最新版本的 GitHub Enterprise。 如需升级帮助,请联系 GitHub Enterprise 支持

Configuring email for notifications

To make it easy for users to respond quickly to activity on GitHub Enterprise Server, you can configure your GitHub Enterprise Server instance to send email notifications for issue, pull request, and commit comments.

Configuring SMTP for your enterprise

  1. 从 GitHub Enterprise Server 上的管理帐户任意页面的右上角,单击

    用于访问站点管理员设置的火箭图� �的屏幕截图

  2. 如果� 尚未在“站点管理员”页上,请在左上角单击“站点管理员”。

    “站点管理员”链接的屏幕截图 1. 在左侧边� �中,单击“管理控制台”。 左侧边� �中的 管理控制台 选项卡

  3. 在页面顶部,单击“设置”。 “设置”选项卡

  4. 在左侧边� �中,单击“电子邮件”。 “电子邮件”选项卡

  5. Select Enable email. This will enable both outbound and inbound email, however for inbound email to work you will also need to configure your DNS settings as described below in "Configuring DNS and firewall settings to allow incoming emails." Enable outbound email

  6. Type the settings for your SMTP server.

    • In the Server address field, type the address of your SMTP server.
    • In the Port field, type the port that your SMTP server uses to send email.
    • In the Domain field, type the domain name that your SMTP server will send with a HELO response, if any.
    • Select the Authentication dropdown, and choose the type of encryption used by your SMTP server.
    • In the No-reply email address field, type the email address to use in the From and To fields for all notification emails.
  7. If you want to discard all incoming emails that are addressed to the no-reply email address, select Discard email addressed to the no-reply email address. Checkbox to discard emails addressed to the no-reply email address

  8. Under Support, choose a type of link to offer additional support to your users.

    • Email: An internal email address.
    • URL: A link to an internal support site. You must include either http:// or https://. Support email or URL
  9. Test email delivery.

Testing email delivery

  1. At the top of the Email section, click Test email settings. Test email settings

  2. In the Send test email to field, type an address to send the test email to. Test email address

  3. Click Send test email. Send test email

    Tip: If SMTP errors occur while sending a test email—such as an immediate delivery failure or an outgoing mail configuration error—you will see them in the Test email settings dialog box.

  4. If the test email fails, troubleshoot your email settings.

  5. When the test email succeeds, at the bottom of the page, click Save settings. Save settings button

  6. 等待配置运行完毕。


Configuring DNS and firewall settings to allow incoming emails

If you want to allow email replies to notifications, you must configure your DNS settings.

  1. Ensure that port 25 on the instance is accessible to your SMTP server.
  2. Create an A record that points to reply.[hostname]. Depending on your DNS provider and instance host configuration, you may be able to instead create a single A record that points to *.[hostname].
  3. Create an MX record that points to reply.[hostname] so that emails to that domain are routed to the instance.
  4. Create an MX record that points noreply.[hostname] to [hostname] so that replies to the cc address in notification emails are routed to the instance. For more information, see "Configuring notifications."

Troubleshooting email delivery

Create a Support Bundle

If you cannot determine what is wrong from the displayed error message, you can download a support bundle containing the entire SMTP conversation between your mail server and GitHub Enterprise Server. Once you've downloaded and extracted the bundle, check the entries in enterprise-manage-logs/unicorn.log for the entire SMTP conversation log and any related errors.

The unicorn log should show a transaction similar to the following:

This is a test email generated from
Connection opened:
-> "220 ESMTP nt3sm2942435pbc.14\r\n"
<- "EHLO\r\n"
-> " at your service, []\r\n"
-> "250-SIZE 35882577\r\n"
-> "250-8BITMIME\r\n"
-> "250-STARTTLS\r\n"
-> "250 PIPELINING\r\n"
<- "STARTTLS\r\n"
-> "220 2.0.0 Ready to start TLS\r\n"
TLS connection started
<- "EHLO\r\n"
-> " at your service, []\r\n"
-> "250-SIZE 35882577\r\n"
-> "250-8BITMIME\r\n"
-> "250 PIPELINING\r\n"
<- "AUTH LOGIN\r\n"
-> "334 VXNlcm5hbWU6\r\n"
<- "dGhpc2lzbXlAYWRkcmVzcy5jb20=\r\n"
-> "334 UGFzc3dvcmQ6\r\n"
<- "aXRyZWFsbHl3YXM=\r\n"
-> "535-5.7.1 Username and Password not accepted. Learn more at\r\n"
-> "535 5.7.1 nt3sm2942435pbc.14\r\n"

This log shows that the appliance:

  • Opened a connection with the SMTP server (Connection opened:
  • Successfully made a connection and chose to use TLS (TLS connection started).
  • The login authentication type was performed (<- "AUTH LOGIN\r\n").
  • The SMTP Server rejected the authentication as invalid (-> "535-5.7.1 Username and Password not accepted.).

Check your GitHub Enterprise Server instance logs

If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that /var/log/mail.log and /var/log/mail-replies/metroplex.log.

/var/log/mail.log verifies that messages are reaching your server. Here's an example of a successful email reply:

Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from[]
Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323:[]
Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id=<>
Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=<>, size=5048, nrcpt=1 (queue active)
Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=<>, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (delivered to maildir)
Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed
Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from[]

Note that the client first connects; then, the queue becomes active. Then, the message is delivered, the client is removed from the queue, and the session disconnects.

/var/log/mail-replies/metroplex.log shows whether inbound emails are being processed to add to issues and pull requests as replies. Here's an example of a successful message:

[2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing <>
[2014-10-30T00:47:23.333 DEBUG (5284) #] Matched /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie
[2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success

You'll notice that metroplex catches the inbound message, processes it, then moves the file over to /data/user/incoming-mail/success.

Verify your DNS settings

In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "Configuring DNS and firewall settings to allow incoming emails."

Check firewall or AWS Security Group settings

If your GitHub Enterprise Server instance is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to reply@reply.[hostname].

Contact support

If you're still unable to resolve the problem, contact GitHub Enterprise 支持. Please attach the output file from http(s)://[hostname]/setup/diagnostics to your email to help us troubleshoot your problem.