Conversation
This is a good example of a doc that we were talking about writing, but then decided against it. It's interesting to see that the AI believes it is important. |
|
Okay, so Cursor is now catching APA style.
|
|
|
||
| Email forwarding is applied on a per-domain basis. | ||
|
|
||
|  |
There was a problem hiding this comment.
This screenshot is out of date and needs to be replaced.
|
|
||
| ## View email forwarding configuration | ||
|
|
||
|  |
There was a problem hiding this comment.
The screenshot needs to be updated
|
|
||
|  | ||
|
|
||
| 1. **From** field - The local part of the email address to forward from (e.g., `hello` for `[email protected]`). |
|
|
||
| 1. **From** field - The local part of the email address to forward from (e.g., `hello` for `[email protected]`). | ||
| 1. **To** field - The full email address where emails should be forwarded. | ||
| 1. **Add email forward** button - Creates the email forward. |
There was a problem hiding this comment.
Create forward button
| ## Catch-all email forwarding | ||
|
|
||
| To create a catch-all email forward, select the **Catch-all** option when creating a new email forward. This will forward emails sent to any address at your domain that doesn't have a specific forwarding rule. | ||
|
|
There was a problem hiding this comment.
could probably add a screenshot here
EMAILS_GAP_ANALYSIS.md
Outdated
| ### Email Hosting | ||
| - ✅ Email Hosting Support (Explanation) | ||
|
|
||
| ## Identified Gaps |
There was a problem hiding this comment.
These are all good gaps that could easily be filled/cross referenced from other categories.
EMAILS_GAP_ANALYSIS.md
Outdated
| ## Notes | ||
|
|
||
| - Some topics (like MX records) exist in the DNS category but should be cross-referenced or duplicated in the Emails category for better discoverability | ||
| - One-click services for email are covered in the Services category, which is appropriate, but the Emails category should have integration guides |
There was a problem hiding this comment.
I'm not sure I agree with integration guides in Email..
content/articles/email-forwarding.md
Outdated
| To get started with email forwarding: | ||
|
|
||
| ## Internationalized Domain Names (IDN) support {#idna} | ||
| 1. Ensure you're subscribed to a plan that includes email forwarding. |
There was a problem hiding this comment.
All plans include email forwarding. Make sure you are subscribed to an active plan, the domain is delegated to DNSimple’s name servers, and DNS hosting is active.
| 1. Click the **Email Forwarding** tab on the left side. | ||
| 1. Click **Add email forward** or the **+** button. | ||
| 1. Enter the email forward details: | ||
| - **From:** Enter the local part (the part before the @) of the email address you want to forward from (e.g., `hello` for `[email protected]`). Do not include the domain name. |
There was a problem hiding this comment.
The From text when creating an email forward does not appear in the UI @sbastn. Shouldn't it be there?
|
Today, I am taking the gaps article and creating the content with Cursor. My plan is to have Cursor merge them into the email-section-rewrite branch. |
| - Confirm deletions | ||
|
|
||
| <info> | ||
| **One-click services:** If you're using DNSimple's one-click services for your old provider, you can remove the service, which will automatically remove the associated DNS records. See [Removing Services](/articles/services/#removing-services) for instructions. |
| **Solutions:** | ||
| 1. **Verify email forwarding enabled:** Check that email forwarding is enabled in DNSimple | ||
| 2. **Check email forwards:** Verify all email forwards are configured correctly | ||
| 3. **Test DNS:** Use `dig` to verify MX records point to DNSimple |
|
|
||
| ### Sender reputation tools | ||
|
|
||
| **Sender Score (sender-score.org):** |
There was a problem hiding this comment.
this doesn't exist. URL is https://senderscore.org/
| - Monitor trends over time | ||
| - Address issues that affect score | ||
|
|
||
| **Google Postmaster Tools:** |
There was a problem hiding this comment.
| - Monitor Gmail-specific metrics | ||
| - Address Gmail-specific issues | ||
|
|
||
| **Microsoft SNDS (Smart Network Data Services):** |
There was a problem hiding this comment.
|
|
||
| ### Blacklist monitoring | ||
|
|
||
| **MXToolbox:** |
There was a problem hiding this comment.
| - Address blacklist issues immediately | ||
|
|
||
| **Other tools:** | ||
| - Spamhaus |
There was a problem hiding this comment.
|
|
||
| **Other tools:** | ||
| - Spamhaus | ||
| - BarracudaCentral |
There was a problem hiding this comment.
| **Other tools:** | ||
| - Spamhaus | ||
| - BarracudaCentral | ||
| - SURBL |
There was a problem hiding this comment.
- Remove EMAILS_GAP_ANALYSIS.md (working document, no longer needed) - Clarify distinction between managing-email-forwards.md (step-by-step guide) and email-forwarding-management.md (UI reference) - Add cross-references between articles for better navigation - Focus each article on its distinct purpose
|  | ||
|
|
||
| 1. **Email Forwarding** tab - Email forwarding management options for the domain. | ||
| 1. **Add email forward** button - Create a new email forward. |
There was a problem hiding this comment.
| 1. **Add email forward** button - Create a new email forward. | |
| 1. **Add** button - Create a new email forward. |
|
|
||
| 1. **Email Forwarding** tab - Email forwarding management options for the domain. | ||
| 1. **Add email forward** button - Create a new email forward. | ||
| 1. **Current Email Forwards** section - List of all configured email forwards. |
There was a problem hiding this comment.
| 1. **Current Email Forwards** section - List of all configured email forwards. | |
| 1. Current Email Forwards section - List of all configured email forwards. |
- Delete content/articles/email-forwarding-with-subdomains.md - Remove references from emails.md and email-forwarding.md
- Add links to Record Editor where mentioned - Add links to 'What Is' articles for SPF, DKIM, DMARC - Add links to advanced authentication topics (alignment, gradual DMARC, multiple DKIM selectors) - Add links to email bounce articles - Add links to email security and authentication best practices - Expand and reorganize Related topics section with categories - Remove .vscode/tasks.json from repository - Add .vscode/ to .gitignore
…icles - Add links to reputation monitoring tools (Sender Score, Google Postmaster Tools, Microsoft SNDS, BarracudaCentral) - Add links to blacklist monitoring tools (MXToolbox, Spamhaus, SURBL) - Add links to email testing tools (Mail-Tester, Litmus, Email on Acid) - Add links to DMARC reporting tools (dmarcian, Postmark) - Add links to dashboard tools (Google Analytics, Google Data Studio, Tableau) - Improve tool descriptions with brief explanations
- Add context about SPF as part of email authentication (SPF, DKIM, DMARC) - Add links to integration guides for Google Workspace and Microsoft 365 examples - Add link to third-party email services integration guide - Improve mechanisms section with clearer reference to detailed guide - Add troubleshooting section with link to troubleshooting guide - Add comprehensive Related topics section organized by category: - Email authentication (SPF, DKIM, DMARC articles) - Email service integration (Google Workspace, Microsoft 365, third-party) - DNS management (Record Editor, TXT records)
- Update categories/emails.yaml to include all 48 articles from email-section-rewrite PR - Organize articles by Diataxis framework (Getting started, Explanation, How to, Reference) - Add missing meta descriptions to emails.md and enabling-email-forwarding.md - Ensure all articles have both excerpt and meta fields for SEO
|
This PR has been split into 11 smaller, more manageable PRs for easier review: Split PRs:
All PRs are currently in draft status and ready for review. This large PR is being closed in favor of the smaller, focused PRs above. |
|
This PR has been split into 11 smaller, more manageable PRs. See the comment above for the list of new PRs. |

Start with the content from all articles in the Emails and replace the existing articles with new articles using the Diataxis framework (https://diataxis.fr/) and following the voice from articles in the DNSSEC and DNS category, . Produce a list of gaps of missing articles for the Emails category that should be added in the future based on functionality provided by DNSimple related to email. Create a new pillar page for the Emails category using https://support.dnsimple.com/articles/dnssec/ as an example template.
Using the code in dnsimple-app review the articles in the Email section and correct any outdated documentation.