Scope this workflow to Spotler Mail+
Spotler is a product family, not a single universal sending configuration. This guide covers the Mail+ domain-authentication workflow documented in its own Help Center. It does not substitute the same instructions for SendPro, MailPro or another Spotler product. Establish the account’s exact product and intended sending domains before obtaining DNS instructions. The catalogue title is retained, while implementation acceptance remains limited to the evidenced Mail+ route.
Mail+ requires proper DMARC authentication for sending through the product. Its setup page describes checking the domain state, requesting authentication and having the domain administrator implement the supplied records. This product prerequisite must not be reduced to an optional recommendation. It also must not be expanded into a claim that authentication guarantees delivery or that every mailbox provider has identical rules. Spotler Mail+ setup instructions
Begin with a reply address and DNS responsibility
The provider says a reply address must exist in Mail+ before this setup, and someone must be able to modify the domain’s DNS settings. Record both responsibilities. The Mail+ account operator can obtain the application instructions, while the DNS administrator must evaluate and approve the actual record changes. Neither role should assume that the other has checked every sending system sharing the domain. Spotler Mail+ setup instructions
Inventory the intended reply domains alongside their business use. The documented settings view associates reply addresses with reply domains, and the provider directs users with several domains to configure each one. A successful setup for a corporate root domain is not evidence that a separately used subdomain or another brand domain has been configured. Identify each actual domain string and avoid collapsing related-looking names into one acceptance row.
Do not collect DNS passwords, private signing keys or unrelated mailbox contents in this inventory. The change request needs public record details, account context, an approver and the intended outcome. It does not need broad access to the domain administrator’s credentials. This guide describes preparation and review; no authentication request or DNS modification has been made.
Interpret the three initial states correctly
The documented navigation is the bottom-left account menu, Settings, Security and Deliverability. Mail+ shows the reply addresses, domains and a DMARC status column. The page distinguishes Active, A problem occurred and No DMARC Authentication. If a configuration already exists but Mail+ is not fully authorized, the instruction page identifies missing records for the domain administrator. A domain with no authentication proceeds to the request step. Spotler Mail+ setup instructions
Preserve the initial state and timestamp before proposing a change. “A problem occurred” is a reason to inspect the specific missing authorization, not a reason to delete an existing organizational DMARC policy. Likewise, a blank or inactive product state does not establish that the domain has no DNS records at all. The application view and the authoritative DNS view answer related but different questions.
Request the correct account instructions
From Deliverability, the provider describes using the domain’s context menu to request DMARC authentication. The dialog asks for the DKIM key format and recommends 2048-bit, with compatibility confirmation from the domain administrator. The state then changes to authentication requested, and the requesting user receives an instruction email. Use that account-specific instruction set rather than borrowing another customer’s values or guessing a selector. Spotler Mail+ setup instructions
The provider’s separate key-size troubleshooting answer involves support removing the current authentication before a different configuration can be requested. Do not interpret that as permission to delete live keys or downgrade an existing deployment without assessing its dependencies. A change in signing configuration can affect messages still being generated or awaiting delivery. Plan any transition with the responsible account and DNS owners; this manuscript does not perform such a transition.
For a domain used in multiple Mail+ accounts, the provider says to configure one account and contact support. That is a specific cross-account coordination requirement, not evidence that copying records into every account independently is safe. Keep the accounts and their owners visible in the worksheet. No support communication has been sent for this draft. Spotler Mail+ setup instructions
Review SPF and DKIM before the DMARC policy
The administrator instructions put DKIM and SPF first and say to include other sending servers as well. Treat the supplied values as inputs to a complete policy review. Existing SPF authorizations should not disappear when a new service is added. Keep one applicable SPF policy at the relevant owner and evaluate the full nested path against the protocol limits. These are DNS and SPF requirements, not merely visual checks in a product screen. Spotler Mail+ setup instructions RFC 7208, multiple records and lookup limits
For DKIM, preserve the full owner name, record type and public value provided for the account. Confirm how the DNS editor interprets owner names and long TXT content. A TXT record can contain multiple character strings; that is not an instruction to create several unrelated key records. Do not add whitespace to the key material while splitting its presentation. RFC 1035, TXT format RFC 6376, key storage
The provider supplies an illustrative DMARC policy including monitoring and reporting fields. Do not paste its explanatory address placeholders into production, automatically lower an existing enforcement policy, or enable failure reporting without an approved recipient and data-handling purpose. Review the organization’s existing policy and other legitimate senders. The source’s suggestion to merge existing configurations means reconcile the intended settings into a valid policy, not concatenate two complete DMARC records.
DMARC evaluates the relationship between the visible author domain and a qualifying authenticated identifier. A passing aligned SPF or DKIM path can support DMARC; the application’s request to configure both mechanisms is a product workflow requirement rather than a change to that protocol rule. Preserve both distinctions in the acceptance record. RFC 9989, identifier alignment
A green check is not the final acceptance test
After the administrator completes the records, the provider directs the user to check for DMARC authentication active in Deliverability. However, the same page warns that a green check can coexist with sending failures because its precheck does not always catch malformed input, including unintended spaces. That qualification matters more than a broad promise of guaranteed delivery. Record the product status as one observation, not the conclusion for every message route. Spotler Mail+ setup instructions
The release owner should require authorized public DNS observations and actual received-message identities for the intended domain and account. The evidence table should distinguish visible author, envelope identity, signing domain, selector, recipient authentication outcome and observation time. A configuration screen cannot establish what another server evaluated on a particular message. Authentication is also not proof that the content is safe or that a recipient will place it in the inbox. RFC 9989, scope and receiver actions
Fictional diagnosis: one domain, two accounts
The fictional organization Juniper Arts uses two Mail+ accounts for separate teams. One team sees an active domain and tells the other to copy its instructions without coordinating account ownership. A reviewer notices that the second account was never included in the setup decision. This is an invented planning scenario, not an observed incident or an executed test.
The reviewer follows the documented cross-account support boundary, retains the current valid configuration and gathers the two account contexts before requesting any change. Each team still needs evidence for its actual message route. The lesson is not that a second account necessarily requires duplicate DNS records; it is that a shared domain requires an explicit supported account relationship.
Blank acceptance worksheet
- Exact Spotler product and account identifiers: ______
- Reply address prerequisite confirmed: ______
- Sending and reply domains with business owners: ______
- Other Mail+ accounts sharing the domain: ______
- Initial product status and timestamp: ______
- Account-specific instruction set and key format: ______
- DNS approver, full record owners and values: ______
- Existing SPF and DMARC reconciliation: ______
- Approved report recipients and handling purpose: ______
- Final product status and input-format review: ______
- Actual received-message identity evidence: ______
- Rollback, subject-matter review and release approval: ______
All operational fields remain unresolved. The original catalogue evidence, human review, source applicability, production routes, visual accessibility and owner release gates remain open. No support request, authentication request, DNS edit or message test was performed.