DrugTestNetwork sends email on behalf of subscribers for notifications, reports, reminders, Signature Documents, and other system communications. To help ensure reliable delivery, DTN provides each subscriber with an email address on the drugtestnetwork.com domain that can be used as the From address for email sent through the platform.
For example, a subscriber whose normal business email address is:
DrugTests@Acme-TPA-Services.com
might use a DTN sending address such as:
Acme TPA Services <acme.tpa.services@drugtestnetwork.com>
Why DTN Uses Its Own Sending Domain
Modern email systems use authentication methods such as SPF, DKIM, and DMARC to determine whether a server is authorized to send email for a particular domain.
If DTN sends a message using DrugTests@Acme-TPA-Services.com as the From address, the message is actually being transmitted by DTN’s mail system rather than by Acme TPA Services’ own email server. Unless the subscriber’s domain has been specifically configured to authorize that activity, receiving mail systems may consider the message suspicious or unauthenticated.
That can cause otherwise legitimate email to be placed in a spam folder, quarantined, or rejected.
By using an address on drugtestnetwork.com, DTN can control and maintain the DNS and authentication records used to verify the messages it sends. This provides a consistent sending environment without requiring each subscriber to make changes to their own domain configuration.
The Subscriber’s Name Still Identifies the Sender
The email address used for delivery does not prevent the subscriber from being clearly identified. The Email Display Name can show the subscriber’s business name to the recipient.
For example:
Acme TPA Services <acme.tpa.services@drugtestnetwork.com>
The recipient sees Acme TPA Services as the organization sending the communication, while the drugtestnetwork.com address provides the authenticated technical address used to transmit it.
Using the Subscriber’s Own Domain
Subscribers who prefer to have DTN-generated email sent using an address on their own domain may also use DTN’s alternative email configuration. With this option, the subscriber’s domain is configured to authorize DTN’s email system through the domain’s SPF record.
This allows DTN to send email on behalf of the subscriber’s domain while providing receiving mail systems with verification that DTN is an authorized sender. Depending on the subscriber’s existing email security configuration, additional DNS authentication settings may also be appropriate.
For most subscribers, the DTN-provided email address offers the simplest configuration and requires no changes to their domain. The subscriber-domain option is available for organizations that prefer to manage the necessary DNS authorization and use their own email domain as the sending address.