Business email · Practical guide
DMARC alignment across mailboxes, invoices and transactional email APIs
Passing SPF or DKIM is not enough when the authenticated domain does not align with the From domain visible to your customer.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Inventory every system that sends messages
Business email rarely comes from a single server. Employee mailboxes, marketing tools, invoice software, password-reset systems and order-confirmation APIs may each send with different envelope and signing domains. Begin by identifying a real message from each sending path, the intended From address, and who owns the configuration.
Record the SMTP envelope sender domain, DKIM signing domain and message purpose for every source. Include automated billing and customer-service messages that are easy to overlook. An address shown in the From header might differ from the domain authenticated by the transport, and that difference matters when DMARC alignment is evaluated.
Read authentication results from delivered tests
Send controlled messages to more than one receiving service, then inspect the Authentication-Results header. Read SPF, DKIM and DMARC results separately and compare the relevant domains with the visible From address. A DKIM signature may validate cryptographically while failing the domain alignment required by DMARC.
Use DNS and provider dashboards to understand why a result failed, but avoid assuming that a valid TXT record proves messages are signed as intended. The sending provider may still use an old selector or its own domain. Do not expose API secrets or private customer message contents while collecting troubleshooting evidence.
Move from monitoring to enforcement deliberately
Use a monitoring policy and aggregate feedback where suitable to discover real sending systems that are not aligned. Fix these senders at the provider, including custom bounce or signing domains when supported. A rapid switch to strict enforcement before legitimate paths work can cause invoice, login-code or booking mail to be rejected.
After representative paths are passing, plan a controlled transition toward stronger policies if the business needs them. Include forwarded messages and mailing lists in testing because their authentication behavior may differ. Keep the operational contacts and rollback method written down so staff can respond to unexpected delivery problems.
Measure delivery after acceptance, not at submission
A provider accepting an API call does not guarantee the recipient's inbox contains the message. Keep separate observations for the queued request, accepted transport, remote rejection, bounce events and recipient-level confirmation where available. Treat a payment event and the customer's message delivery as different facts.
Monitor failures by sending source and message type, not only one aggregate sent count. A reliable report links the original business event to a message identifier and outcome, without inventing success for mail that has not been verified. This makes future migrations and provider comparisons auditable.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
OlaCheap business email →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.