Browse Source

Clarify README with risk of using a NTLD Domain

Added one additional bullet point under "Troubleshooting" section based on my experience implementing emailwiz with a New Top-level Domain (NTLD) and sending emails to colleagues at large F500 companies.
pull/116/head
gnubytes 4 years ago
committed by GitHub
parent
commit
927c34b3d2
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
  1. +5
    -0
      README.md

+ 5
- 0
README.md View File

@@ -135,3 +135,8 @@ support me at [lukesmith.xyz/donate](https://lukesmith.xyz/donate.html).
[Vultr](https://www.vultr.com/docs/what-ports-are-blocked) for instance [Vultr](https://www.vultr.com/docs/what-ports-are-blocked) for instance
blocks this by default, you need to open a support ticket with them to open blocks this by default, you need to open a support ticket with them to open
it. You can't send mail if 25 is blocked it. You can't send mail if 25 is blocked
- Keep in mind that .xyz domains are considered "NTLD" or NEW Top Level Domains
and Spam Assassin and other spam blockers (especially corporate/enterprise spam blockers)
will block these NTLD's purely based on this fact alone. Some corporate and/or enterprise
email filters are much more agressive than Gmail's. Keep this in mind when you try to send
an email to a friend who works at a large company and they never receive your email.

Loading…
Cancel
Save