Changes between Initial Version and Version 1 of Ticket #42693, comment 5
- Timestamp:
- 11/26/2017 05:25:46 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #42693, comment 5
initial v1 2 2 > Just a quick note, as some stumbling in here may be wondering, `example.com` doesn't have a valid MX record, so no emails are actually transmitted. 3 3 4 I know what you mean, but I should note that a message is actually sent to {{{you@example.com}}} via yourmail server; it just bounces back as undeliverable. You'll see it if you have WordPress set to send from a real address:4 I know what you mean, but I should note that a message is actually sent to {{{you@example.com}}} via a mail server; it just bounces back as undeliverable. You'll see it if you have WordPress set to send from a real address: 5 5 6 6 {{{ … … 9 9 }}} 10 10 11 But you're right that nobody at example.com is getting mailbombed with these, due to the missing X record.11 But you're right that nobody at example.com is getting mailbombed with these, due to the missing MX record. 12 12 13 13 It would probably be better if the database was initially populated with an address "@example.invalid", instead of using a fake address at the real domain name "example.com". [https://tools.ietf.org/html/rfc2606 RFC 2606] specifies that the ".invalid" TLD is guaranteed never to exist and is intended for purposes like this.