How to send bulk emails with your email domain

If your recipients use MS Outlook, Hotmail, Gmail and other common mailing services, they can see that an email was sent from your provider's server on your behalf (this information is available in the sender field).

In this case, any text can be displayed in the sender string: “UniOne_Smith <postman1847554@usndr.com>; on behalf of; UniOne_Smith <smith.john@gmail.com>” or “UniOne_Smith john.smith@gmail.com from domain usndr.com”.

SMTP base email transfer protocol does not provide sufficient level of sender authentication. That is why any email address can be specified in the sender field. This may permit unsanctioned bulk emails on behalf of a trusted brand or personal email addresses of free email domains. Recipients cannot be sure that the incoming email was sent by the address specified in the sender field. Such emails can be blocked by the spam filters of email providers and have a negative effect on your bulk email sending rate. All major mail services, including AOL and Yahoo, have strict anti-spam policies.

In order to display the correct name of the bulk email sender, as well as to prevent unauthorized mailings of messages on your behalf on the server of your mail domain, you must perform a special authentication. The following methods can be used for such authentication: Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM).

The DKIM/SPF authentication is performed by adding special records to the DNS server for your domain. To receive these records, send email to support@bpmonline.com

1.Create a TXT record and specify the servers allowed to send email from. If sending from that domain is run only through Unisender, the record is as follows:

2.If you already have a TXT record with SPF information, then at the end of this record, before its last statement (for example, ?all, ~all, or -all), add the following line:

It is recommended to to verify the SPF record you created using SPF testing tools.

This record will enable you to add DKIM electronic signatures to emails sent from your domain.

If you already sign your emails with DKIM or DomainKeys than you have this record so it doesn't need to be changed.

2.In the DNS settings, specify a unique DKIM value received from the bpm'online support team:

Detailed information about DKIM/spf authentication is available in this article.

Please take the following into consideration when working with SPF and DKIM records:

1.Before the changes made to DNS take effect, new and modified records must be verified. Record verification may take 2-24 hours (new records are usually verified within 10-15 minutes, while modified records may take more time, depending on DNS).

2.Some records may not pass the verification. This may occur due to differences in DKIM record formatting requirements of various DNS services. For example, certain DNS require the “\” character before “;” at the start and end of DKIM records. Other DNS services have no such requirement.

3.When creating a DKIM record, be sure to obtain formatting requirements from your hosting provider or support service.

Below are links to websites of common DNS providers and their DKIM record formatting specifics:

Bluehost	DKIM records are usually formatted automatically (control characters are automatically replaced with correct text).
GoDaddy	DKIM records are usually formatted automatically (control characters are automatically replaced with correct text).
CloudFlare	DKIM records are usually formatted automatically (control characters are automatically replaced with correct text).
DynDNS	The field where you enter value of each record must be enclosed in double quotes.
MS Office 365	DKIM records are usually formatted automatically (control characters are automatically replaced with correct text).