Managing Emailing Accounts

Owned by Jules DELEUZE (Unlicensed)
Last updated: Nov 13, 2019
5 min read

Accounts Management

Operation

WEDIA works with an email service provider in order to route your marketing campaigns. As such it is therefore necessary to achieve a minimum configuration within the system in order to be able to send campaigns.

To send email campaigns it will be necessary

  1. to have a valid account with our service provider,

  2. to declare at least one sender on this account,

  3. to provide proof that you are the owner of the domain name of the sender,

  4. to declare our supplier as legitimate sender for your name from domain.

Several objects are provided within the WXM (and packaged) initialization application are necessary for the proper operation of the application :

Objects related to the management of accounts and senders

mjkey

set of API keys (also called accounts) allowing to the application to work with the service provider

mjdns

all domain names usable by your account

mjsender

all known and usable senders of your account

Objects related to campaign management

mjcampaign

set of marketing campaigns used to interact with email campaign routing service

mjrecipient

recipients of the different campaigns. Necessary for events managements such as unsubscription, errors, etc…​.

mjstats

campaigns statistics

Workflow objects

mjcampaignwkf/mjcampaignwkfaction

marketing campaign workflow

mjkeywkf/mjkeywkfaction

operating account workflow

mjrecipientwkf/mjrecipientwkfaction

recipient workflow

mjsenderwkf/mjsenderwkfaction

senders' worfklow

Account/key management

An account is required to allow users to create and ship emailing campaigns on the WEDIA application. These accounts are managed by our email forwarding service provider and allows to partition the different components of the campaigns (recipients, lists, etc.) contacts, campaigns, statistics, etc…​)

 

Keys are kept within the mjkey object within your WEDIA application.

The account creation with our service provider is done automatically by application via business rules within the application objects when activating an instance of the mjkey object.

 

The name must be globally unique and is limited to 30 characters.

The apikey, apisecret and remoteid properties are automatically generated by the provider and stored within the mjkey instance.

It is possible to declare a default sender who will be automatically created and activated by the application during DNS and SPF/DKIM authentication configurations.

When an account is created with a default sender a new entry is added to the mjdns object for the current key on the corresponding domain to this sender’s email.

When validating the domain name information, the sender will be automatically created on the system.

The supplier’s declaration as a legitimate consignor and proof of DNS ownership are actions to be performed at the configuration level of your DNS.

Domain name management

To allow our provider to send emails on your behalf it is required to provide proof that you are the owner of the domain name used to send the emails with the sender you have chosen.

Also to prove to messaging providers (gmail, yahoo, orange, etc…​) that the emails were sent by a legitimate sender, without spam nor address usurpation, it will be necessary to perform a configuration action on your domain.

Known and declared DNS are stored within the mjdns object on the application.

 

The [sliders] buttons surrounded in red on the image above allow access domain name configuration information.

It is possible to automatically create and activate domain names for everyone the accounts of a WEDIA application.
To do this it is necessary to create the domain on the master account and to activate it automatically when creating an account via the auto_dns parameter of the WXM_Emailing_Mailjet plugin.

DNS Configuration

DNS configuration is required to prove to our provider that the domain with which you want to send your emails really belongs to you.

 

2 methods are possible to prove that the domain in question belongs to you:

  • Host a file at the root of your website

  • add a DNS record to your domain name

SPF/DKIM Authentication

SPF/DKIM authentication is used to prove to messaging providers that that the emails were sent by a legitimate sender, without spam nor usurpation of address.

Shipper Management

Senders are managed within the mjsender object.

An active shipper is always required to ship an emailing campaign.

Senders are automatically activated as soon as their domains are active.

If a sender’s domain name is not enabled (DNS and SPF/DKIM configuration) then it will not be possible to activate the sender.

Enabling feature

The routing functionalities are activated by activating the WXM_Emailing_MailJet plugin.

WXM_Emailing_Mailjet plugin settings

The plugin waits for a certain number of parameters to work.

master_api_key

Main account API key (provided by MailJet) - This parameter override the mailjet_api_key defined in the main administrative settings of the application.

master_api_secret

Main account API password (provided by MailJet) - This parameter override the mailjet_api_secret defined in the main administrative settings of the application.

auto_dns

List of domain names to be created automatically during the creation of a subaccount.
The system will automatically attempt to activate the new domain.

activate_dns_timer

Enables you to activate a scheduled task to run checks on Inactive DNS configurations.

logger_level

Allows you to set the log level of the plugin. Logs are available in a external logger named emailing_provider.log.

show_analytics_events

Show/Hide the analytics Mailjet Events tab in the analytics dashboards

show_analytics_api_calls

Show/Hide the analytics Mailjet API Calls tab in the analytics dashboards

chart_color_open_rate

Opening rate chart color

chart_color_click_rate

Click rate chart color

chart_color_error_rate

Error rate chart color