Summary
The consistent advice from experts, marketers, and documentation sources is to immediately cease using a domain you do not own, especially if it's on a blocklist, for sending emails. It severely damages sender reputation, prevents proper email authentication (SPF, DKIM, DMARC), violates RFCs, limits corrective actions against blocklists, and ultimately harms deliverability. Switching to a domain you own, implementing authentication protocols, cleaning email lists, and monitoring sender reputation are vital steps to rectify the situation.
Key findings
- Immediate Cessation Required: The unanimous conclusion is that you must immediately stop using the unowned and blocklisted domain.
- Severe Reputation Damage: Using a domain you do not own drastically negatively affects your sender reputation.
- Authentication Blocked: Proper email authentication (SPF, DKIM, DMARC) becomes impossible without domain ownership.
- RFC Violations: Using a domain you don't own can lead to violations of email standards and RFC compliance issues.
- Blocklist Remediation Blocked: Taking corrective action against being on a blocklist is impossible without domain ownership.
Key considerations
- Transition to Owned Domain: Prioritize transitioning to a domain that you own and control for email sending.
- Implement Authentication: Configure SPF, DKIM, and DMARC to authenticate your emails effectively once using an owned domain.
- Clean Email Lists: Review and clean up your email lists by removing unengaged contacts, especially after a blacklisting incident.
- Monitor Reputation: Actively monitor your sender reputation to identify and address potential deliverability problems promptly.
- Contact Blocking Parties: Consider contacting blocking parties to explain the situation and request delisting, but only after resolving the underlying issue and switching to a controlled domain.
What email marketers say
10 marketer opinions
If your emails are using a domain in the Message-ID that you do not own and that domain is on a blocklist, the overwhelming consensus is to immediately stop using the problematic domain. Using a domain you don't own severely impacts your sender reputation, prevents proper email authentication (SPF, DKIM, DMARC), and can lead to deliverability issues and potential blacklisting. The recommended course of action includes switching to a domain you own and control, properly configuring email authentication, reviewing list hygiene, and monitoring your sender reputation.
Key opinions
- Stop Using Unowned Domain: The most crucial step is to cease using the domain you do not own in your Message-ID or any other part of your email infrastructure.
- Impact on Sender Reputation: Using a domain you do not own negatively affects your sender reputation, leading to deliverability problems.
- Authentication Issues: It becomes impossible to properly authenticate your emails (SPF, DKIM, DMARC) if you are using a domain you do not control.
- Deliverability Problems: Using an unowned and blacklisted domain can lead to emails being flagged as spam and/or being blocked.
- Domain Alignment: It is recommended to align your 'From' address, sending domain, and Message-ID domain for the best results.
Key considerations
- Switch to Owned Domain: Transition to a domain that you own and have full control over to mitigate risks.
- Email Authentication: Properly configure SPF, DKIM, and DMARC for your owned domain to improve email deliverability and trustworthiness.
- List Hygiene: Review and clean up your email lists to remove old, unengaged contacts, as sending to these addresses can further damage your sender reputation, particularly if the domain is blacklisted.
- Monitoring Reputation: Continuously monitor your sender reputation to identify and address any potential deliverability issues promptly.
- Contact Blocking Parties: After fixing the domain issue, you may need to reach out to blocking parties or ISPs to explain the situation and request to be removed from their blocklists (this might not always be successful).
Marketer view
Email marketer from Mailjet Blog answers that domain authentication (SPF, DKIM, DMARC) becomes impossible if you're using a domain you don't own. Suggests switching to a domain you control and properly authenticating it to improve deliverability.
5 Nov 2023 - Mailjet Blog
Marketer view
Marketer from Email Geeks suggests fixing the domain issue first and then reaching out to any blocking parties to explain what happened.
3 Nov 2024 - Email Geeks
What the experts say
3 expert opinions
Experts unanimously agree that if your emails use a domain in the Message-ID that you don't own, especially if it's blocklisted, you must immediately cease this practice. It severely harms your email program due to a lack of control, inability to comply with RFCs, and the inability to properly authenticate your emails. The consistent advice is to transition to a domain you own and control to rectify the situation.
Key opinions
- Stop Immediately: The primary finding is that you must immediately stop using a domain you don't own in your email infrastructure, especially if it's on a blocklist.
- Detrimental Impact: Using a domain you don't own is severely detrimental to your email program, affecting reputation and deliverability.
- Authentication Impossible: It becomes practically impossible to properly authenticate your emails (SPF, DKIM, DMARC) if you lack ownership of the domain.
- RFC Compliance: Using domains you don't own can make it hard to comply with RFC standards.
Key considerations
- Transition to Owned Domain: Prioritize transitioning to a domain that you own and have full control over to regain reputation and control.
- Email Authentication Setup: Once you've transitioned to an owned domain, properly set up SPF, DKIM, and DMARC to authenticate your emails and improve deliverability.
- Potential Blocking: Be aware that continuing to use a domain you don't own, especially if it's blocklisted, can result in your emails being blocked by major providers (e.g., Microsoft).
Expert view
Expert from Email Geeks explains that using a domain that doesn’t belong to them in the messageID is EXTREMELY bad practice and they should stop. Also states that if you use a domain that you don’t own, you can’t be sure you’re complying with the RFCs and that parked domains can trivially be blocked. Recommends the real fix is to stop using a domain that doesn’t belong to them and to enjoy being blocked at Microsoft if they continue.
29 Jan 2024 - Email Geeks
Expert view
Expert from Spam Resource answers: stop using a domain you don't own. Not only does it give you no control over your reputation, but it also makes it nearly impossible to authenticate your emails correctly. Switch to a domain you own and properly set up SPF, DKIM, and DMARC.
16 Mar 2025 - Spam Resource
What the documentation says
5 technical articles
Email deliverability documentation outlines that using a domain you don't own, especially if it's on a blocklist, introduces various risks. It hinders your ability to comply with email standards (RFCs), compromises email authentication (DMARC), impacts sender reputation (Microsoft), and prevents you from taking necessary corrective actions related to blocklist listings (Spamhaus). While IETF provides the broader standards, it emphasizes the importance of sender compliance.
Key findings
- RFC Compliance Risk: Using a domain you don't control risks not maintaining the required uniqueness of Message-IDs and complying with RFC guidelines.
- Blocklist Limitations: You cannot effectively address issues related to being on a blocklist (DBL) if you don't own the domain, as corrective actions are needed from the owner.
- Negative Reputation: Improper email practices, including using domains you don't own, negatively impact your sender reputation, affecting filtering decisions by providers like Microsoft.
- DMARC Alignment Failure: DMARC authentication requires alignment between the 'From' address domain and the domains used for SPF/DKIM, which is impossible if you don't own the domain.
- Sender Compliance: Adherence to general email standards and sender guidelines, as outlined by the IETF, is crucial for ensuring deliverability.
Key considerations
- Domain Ownership: Ensure you own and control the domain used in your 'From' address and Message-ID to maintain control over your email reputation and authentication.
- Corrective Actions: If listed on a blocklist, be prepared to take necessary corrective actions, which requires ownership and control of the domain.
- Authentication Setup: Implement SPF, DKIM, and DMARC to properly authenticate your emails and improve deliverability, which necessitates using a domain you own.
- Compliance Awareness: Stay informed about and adhere to relevant email standards and sender guidelines to avoid deliverability issues.
Technical article
Documentation from Microsoft provides a warning that improper email practices, including using domains you do not own, are viewed negatively and are a factor in calculating sender reputation and filtering decisions.
30 Dec 2021 - Microsoft
Technical article
Documentation from DMARC.org highlights that for DMARC to function correctly, the domain in the 'From' address must align with the domain used for SPF or DKIM authentication. Using a domain you don't own prevents this alignment.
2 Mar 2024 - DMARC.org
Besides Spamhaus, what blocklists are important for email marketers to monitor?
Does being on a blocklist affect Gmail deliverability?
How can I get delisted from Spamhaus?
How do I check Spamhaus for my IP address and understand the listings?
How do I deal with a SORBS listing affecting email deliverability?
How do I deal with a Suomispam blacklist listing affecting my email deliverability?
