Problem
Currently, when adding a domain in Usesend, DNS records are automatically generated with fixed naming conventions:
- DKIM selector:
usesend._domainkey
- MAIL FROM:
mail.<domain>
This creates limitations for users managing multiple domains, especially when integrating with providers like Amazon SES.
Why This Matters
For users operating multiple domains (10+), the current setup leads to:
1. DNS Clutter
- Each domain requires unique DKIM selectors and MAIL FROM entries
- Harder to standardize and manage across domains
2. Lack of Reusability
- Cannot reuse DKIM selectors across providers or domains
- Cannot align with existing SES configurations
3. Deliverability Concerns
- Default/shared tracking domains may negatively impact reputation
- Custom tracking domains are often required for better inbox placement
Proposed Features
1. Custom DKIM Selector & Key
Allow users to define:
- DKIM selector (e.g.,
default, s1, mailer)
- Option to import existing DKIM private key
Example:
selector: default
record: default._domainkey.example.com
Benefits:
- Reuse across multiple domains
- Align with SES or existing infrastructure
- Cleaner DNS structure
2. Custom MAIL FROM Domain
Allow overriding default mail.<domain>
Example:
MAIL FROM: bounce.example.com
Benefits:
- Use a consistent MAIL FROM pattern across all domains
- Easier SES verification and scaling
3. Custom Tracking Domains (Click & Open)
Allow custom domains such as:
click.example.com
open.example.com
Instead of default/shared tracking domains.
Benefits:
- Improves deliverability (avoids shared-domain reputation issues)
- Better branding and trust
4. Template-Based DNS Configuration (Optional)
Allow defining reusable templates:
DKIM selector: default
MAIL FROM: bounce.{domain}
Tracking: track.{domain}
Benefits:
- Apply consistent configuration across all domains
- Saves time for bulk onboarding
Expected Outcome
- Cleaner DNS management
- Better compatibility with SES and other providers
- Improved deliverability
- Scalable multi-domain setup
This feature would significantly improve Usesend for advanced users running multi-domain or production email systems.
Happy to help test or contribute if needed.
Problem
Currently, when adding a domain in Usesend, DNS records are automatically generated with fixed naming conventions:
usesend._domainkeymail.<domain>This creates limitations for users managing multiple domains, especially when integrating with providers like Amazon SES.
Why This Matters
For users operating multiple domains (10+), the current setup leads to:
1. DNS Clutter
2. Lack of Reusability
3. Deliverability Concerns
Proposed Features
1. Custom DKIM Selector & Key
Allow users to define:
default,s1,mailer)Example:
selector: default
record: default._domainkey.example.com
Benefits:
2. Custom MAIL FROM Domain
Allow overriding default
mail.<domain>Example:
MAIL FROM: bounce.example.com
Benefits:
3. Custom Tracking Domains (Click & Open)
Allow custom domains such as:
click.example.com
open.example.com
Instead of default/shared tracking domains.
Benefits:
4. Template-Based DNS Configuration (Optional)
Allow defining reusable templates:
DKIM selector: default
MAIL FROM: bounce.{domain}
Tracking: track.{domain}
Benefits:
Expected Outcome
This feature would significantly improve Usesend for advanced users running multi-domain or production email systems.
Happy to help test or contribute if needed.