Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-resolvable Domain Names should be excluded from tests #548

Open
chriswhitingBCH opened this issue Nov 25, 2024 · 2 comments
Open

Non-resolvable Domain Names should be excluded from tests #548

chriswhitingBCH opened this issue Nov 25, 2024 · 2 comments
Labels
enhancement New feature or request exchange Microsoft Exchanage

Comments

@chriswhitingBCH
Copy link

We use internal only domains to route emails between exchange and our email signature management system. DMARC, SPF, etc. etc. should not be run on non-resolvable domains

image

@soulemike
Copy link
Contributor

This one is a bit similar to #549 with the second being you are accepting risk that you trust that domain not to be spoofed by anyone. This is a little more likely to be manipulated too since .cloud is a TLD managed by ICANN, so it isn't an internal only specification.

Similarly though, open to suggestions on how to adequately warn of the risk while ignoring it.

@merill merill added the exchange Microsoft Exchanage label Dec 14, 2024
@merill
Copy link
Contributor

merill commented Dec 14, 2024

We should do the same as what we plan for #549

@merill merill added the enhancement New feature or request label Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request exchange Microsoft Exchanage
Projects
None yet
Development

No branches or pull requests

3 participants