diff --git a/src/docs/configuration/configuring_inbound_email.diviner b/src/docs/configuration/configuring_inbound_email.diviner
index 1f25125f17..9caed4f899 100644
--- a/src/docs/configuration/configuring_inbound_email.diviner
+++ b/src/docs/configuration/configuring_inbound_email.diviner
@@ -19,13 +19,13 @@ There are basically a few approaches available:
 
 = Configuring Phabricator =
 
-By default, Phabricator uses a "noreply@example.com" email address as the 'From'
-(configurable with ##metamta.default-address##) and sets 'Reply-To' to the
-user generating the email (e.g., by making a comment), if the mail was generated
-by a user action. This means that users can reply (or reply-all) to email to
-discuss changes, but the conversation won't be recorded in Phabricator and users
-will not be able to take actions like claiming tasks or requesting changes to
-revisions.
+By default, Phabricator uses a "noreply@phabricator.example.com" email address
+as the 'From' (configurable with ##metamta.default-address##) and sets
+'Reply-To' to the user generating the email (e.g., by making a comment), if the
+mail was generated by a user action. This means that users can reply (or
+reply-all) to email to discuss changes, but the conversation won't be recorded
+in Phabricator and users will not be able to take actions like claiming tasks or
+requesting changes to revisions.
 
 To change this behavior so that users can interact with objects in Phabricator
 over email, set these configuration keys: