FAQ Overview

General Questions

Do I receive full access to the server I am buying?

Yes. You will get root access from plan 3. You will receive root access to the server and access to the PowerMTA panel.

Author: Cloud Server for Email
Last update: 2021-09-03 05:37


Do you accept PayPal payments?

Yes. We accept payments through PayPal.

Author: Cloud Server for Email
Last update: 2021-09-03 23:55


Do you accept payments through Bitcoin and Altcoins?

Yes. We accept payments via Bitcoin, Ethereum, Bitcoin Cash, Litecoin, EOS, Cardano, Monero, IOTA, Ripple, Stellar, Solana, Tether, Polkadot, USD, BUSD, BNB and more.

Author: Cloud Server for Email
Last update: 2021-09-03 23:55


If I don't want to buy a server with you and I just want you to install PowerMTA on my server, is this possible?

Yes, this is totally possible. It is one of our service. It is the Installation service. So yes, we can install PowerMTA 5.0 on your server and configure your IPS, RDNS, DMARC, DKIM, SPF. And even if you want we can warm up your IPs. This is an optional service.

Author: Cloud Server for Email
Last update: 2021-09-03 23:49


How are Gmail opens reported within Email Analytics?

Between November 2013–January 2014, Google rolled out a series of updates to the way Gmail loads images in email. These updates affect the way Email Analytics detects and measures opens.

  • In November 2013, Gmail started to cache images for emails opened in a web browser or a Gmail mobile app.
  • In January 2014, Gmail began automatically downloading images for emails viewed in a web browser and Gmail mobile apps.

These updates can be confusing and hard to explain—this article makes an attempt to clear things up!

The impact of image caching and automatic image downloads

When Gmail automatically downloads and caches images, those cached images—including open tracker pixels, like the ones used with Email Analytics—are stored on Gmail’s servers. Gmail then loads the same images from the same servers for everyone—regardless of whether they open using Gmail in a web browser or a Gmail Android or iPhone/iPad app.

This means that an email opened in Gmail with a web browser will be indistinguishable from an email opened in a Gmail mobile app.

Individual level tracking

Image caching in Gmail means that it is crucial to use individual tracking with Email Analytics in order to properly record analytics. To use individual tracking, you'll need to enter your Email Service Provider's merge tag while setting up your tracking code.

Without individual tracking, Gmail will cache the image/pixel in your tracking code along with all the other images in your email, and serve the same tracking image for all recipients of your email. This means that only the first open using that tracking code will be recorded and you’ll see very few opens for Gmail. Using a merge tag in your tracking code allows us to properly track email opens, even when Gmail is caching images.

How does this change my stats?

While automatic image downloads mean more accurate open rates and a better subscriber experience, it also means some changes to the data available for Gmail opens.

Device and browser detection

Image caching eliminates the ability to determine a Gmail user's specific device or web browser. To be clear, this only affects opens that occur in Gmail, either in a web browser or in a Gmail mobile app. For instance, device tracking will work for an email sent to a @gmail.com address that is opened in Apple Mail, Outlook, the mail client on iOS, etc.

Device tracking will not work for emails opened in the gmail.com interface in a web browser, or using an official Gmail mobile app. In other words, device tracking still works in the places where Gmail is not caching images.

Gmail opens made in a web browser or in a Gmail mobile app are now reported as “Via Gmail's Image Cache.” You'll see this designation for all opens occurring in Gmail products—for both webmail and mobile opens. Emails opened in the native email client on iOS and Android are unaffected.

The table below explains how various types of Gmail opens will be reported by Email Analytics:

Type of Gmail open Reports as Reading environment
Gmail in a web browser Via Gmail's Image Cache* Webmail
Gmail mobile app (Android) Via Gmail's Image Cache* Webmail
Gmail mobile app (iOS) Via Gmail's Image Cache* Webmail
Gmail in a desktop client (sent to @gmail address; opened in Outlook, Apple Mail, etc.) The email client (Outlook, Apple Mail, etc.) Desktop
Email app on Android (sent to @gmail address) Google Android Mobile
Email app on iOS (sent to @gmail address) Apple iPhone Mobile

*Note that CSV downloads will display this as “Gmail using Google Cache”.

Gmail open rates

Now that Gmail automatically enables images, it's likely that you will see increased open rates for Gmail. 

Android open rates

You may see a decrease in Android open rates, especially after January 2014. Before image caching, opens in the native email app for Android and the Gmail app for Android looked the same. After image caching, Android Gmail app opens are lumped together with Gmail web opens and iOS Gmail app opens. In other words, a portion of Android opens have migrated to the Gmail category. Emails opened in the native email client on Android are still reported as Google Android opens.

Mobile and webmail open rate trends

Measuring mobile opens for Gmail is a bit more difficult now, since it's not possible to differentiate Gmail opens with a web browser from opens in Gmail mobile apps. Prior to image caching, Gmail Android and iOS app opens were reported as mobile opens, but with image caching in place, Gmail Android and iOS app opens are reported as webmail opens. Image caching results in ALL Gmail opens looking the same—including Gmail Android app ops.This may make your mobile open rates appear to decrease and your webmail open rates appear to increase. 

Forward and print tracking

Forward and print tracking is no longer supported for Gmail opens.

Geolocation

Since the open tracker pixels used to relay information about Gmail opens are now cached on Google servers, you will see the location of Gmail proxy servers or none at all.

Author: Cloud Server for Email
Last update: 2021-09-11 19:22


About our Services

How many years of experience do you have using PowerMTA, MailWizz, Interspire and Acelle Mail?

We have more than 16 years of experience managing, configuring and solving problems of hard bounces, blocking to IPs, optimizing PowerMTA servers and warm up IPs. We also have several years working with specialized software for sending mass emails, such as Interspire. With this we have helped hundreds of customers to optimize their sendings, optimize MySQL / Maria DB, in addition to creating plugins with improvements.

In recent years we have integrated to our knowledge the use of Acelle Mail and MailWizz, two quite good solutions that provide advanced options compared to the old Interspire. In both software we have provided optimization services and advice on its correct use. Our Acelle Mail servers and the Mailwizz servers we provide are licensed, 100% optimized and ready to offer you the best user experience and optimal results.

Author: Cloud Server for Email
Last update: 2021-09-03 23:56


What version of PowerMTA (PMTA) is installed on the server?

The version that comes installed when you buy a PowerMTA Server is version 5.0

Author: Cloud Server for Email
Last update: 2021-09-03 22:58


What version of Interspire is installed on the server?

 

Author: Cloud Server for Email
Last update: 2021-09-03 23:00


What version of MailWizz is installed on the server?

 

Author: Cloud Server for Email
Last update: 2021-09-03 23:45


What version of Acelle Mail is installed on the server?

 

Author: Cloud Server for Email
Last update: 2021-09-03 23:48


If I don't want to buy a server with you and I just want you to install Acelle/Interspire/MailWizz on my server, is this possible?

Yes, this is totally possible. It is one of our service. It is the Installation service. So yes, we can install Acelle Mail 4.0, Interspire 6.2.1 or MailWizz 1.9.31 on your server. We offer a multiple optional services like configure your IPS, RDNS, DMARC, DKIM, SPF. And even if you want we can warm up your IPs. Those are optional services.

Author: Cloud Server for Email
Last update: 2021-09-03 23:52


MailWizz Questions

What tracking and sending domains actually are?

TRACKING DOMAINS:
If you have mailwizz installed on email.a.com and you send campaigns, all your url links will start with http://email.a.com and this is fine for most of the cases, but what if you want to handle emailing for b.com domain?

In this case, you will have to either install mailwizz in a subdomain for b.com domain like email.b.com or you can still use the install from email.a.com but use a tracking domain for b.com domain.

A tracking domain is simply a CNAME(DNS Record).
In our case, we define a cname for b.com domain, namely email.b.com that will point to email.a.com subdomain.

Once we do this, propagation can take up to 48 hours, so after 48 hours, we can go in the backend of mailwizz website and add a new tracking domain, the email.b.com domain. Once we did this, to check if everything works properly, we have to access http://email.b.com and we should get same page that we get when accessing http://email.a.com. If it’s not showing same page, then you don’t use a dedicated ip address for a.com domain and you should.

Now, our tracking domain is in place, all we have to do si to associate it with a delivery server and all emails that will be sent via that delivery server will change all the links from email.a.com into email.b.com.

SENDING DOMAINS:
You should use sending domains only if your delivery servers do not sign your emails with DKIM, because the only purpose of sending domains is to identify the domain from the “FROM” or “Return-Path” of your headers and generate a dkim signature for them.

Like in the above case, if your domain is b.com and you send emails from [email protected], then you can add a sending domain (b.com) for which mailwizz will generate the dkim records (you have to add the public key into your dns records, as a TXT record).

Once the domain is confirmed, each time when mailwizz finds an email that contains the domain b.com in it’s FROM/Return-Path headers it will append the right DKIM signature.

Note: If you are using CloudFlare or a similar service make sure you change the DNS records from the proper place.

Author: Cloud Server for Email
Last update: 2021-09-03 06:55


How translation works?

Since version 1.3.6.9 we introduced a console command that you can run in order to generate all the translation files at once.
The command name is translate and can be used as follows:

-bash-4.2$ /usr/bin/php /absolute/path/to/apps/console/console.php translate
Please provide the language name(i.e: English) :  Romanian
Please enter the 2 letter language code(i.e: en) :  ro
Please enter the 2 letter region code(i.e: us). This is optional, leave empty if you are not sure. :  
Do you agree to create the translation messages in: /var/www/vhosts/domain.com/httpdocs/apps/common/messages/ro ? (yes|no) [yes]:
Above command will create all the proper files needed for translation and it will also create the language in the web interface.

[Web interface]

MailWizz version 1.1 introduced multi-language, internationalization and translation support.

You can now create new languages from your backend panel and with the help of the “Translate” extension, let MailWizz EMA collect the messages to be translated from the entire application so that later you can translate everything into your language.
Once a translation is ready, it becomes a language pack that can be zip archived and distributed to be installed in any MailWizz EMA installation from the backend panel in a few clicks.

In case there is no language pack available for your language so that you can easily install it, you’ll have to follow these steps to enable translation:

1. Go to languages area (backend) and add your language manually (add language name and language 2 letter code).
2. Go to extensions area(backend) and enable the translate extension.
3. In the extension area, click on the translate extension title so that you are directed to the extension settings page.
4. Activate message collecting.

Once message collecting is activated, all your messages will be stored under the directory /apps/common/messages/lang_code wherelang_code is your language code, i.e: de/it/es etc.

While you browse your website, messages from the sections you visit will be written in files and you can translate them on the fly.
Once you are done translating for your language, you can save the language folder locally on your computer as lang_code.zip and distribute it as a language pack so others can use it as well.

Notes:
1. Once you are done creating translations for a certain language, make sure you disable the translate extension, it doesn’t make sense to always keep it active.
2. Make sure the messages directory(/apps/common/messages/) is writeable by the web server, otherwise translation files will not be created nor messages will be added in files.

Author: Cloud Server for Email
Last update: 2021-09-03 06:59


Apache .htaccess for mailwizz

Assuming mailwizz is installed in your document root, in a absolute path like:

1 /home/yourdomain/public_html

and accessible at

1 http://www.yourdomain.com/

then in

1 /home/yourdomain.com/public_html/.htaccess

you will put:

# BEGIN rewrite rules
<IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteBase /   
   
    # BACKEND APP
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
    RewriteCond %{REQUEST_URI} ^/backend(/.*)?$
    RewriteRule backend/.* backend/index.php
   
    # CUSTOMER APP
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
    RewriteCond %{REQUEST_URI} ^/customer(/.*)?$
    RewriteRule customer/.* customer/index.php
   
    # API APP
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
    RewriteCond %{REQUEST_URI} ^/api(/.*)?$
    RewriteRule api/.* api/index.php
   
   
    # FRONTEND APP
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !.*\.(ico|gif|jpg|jpeg|png|js|css)
    RewriteRule . index.php
</IfModule>
# END rewrite rules

Please note that the above rules can also be generated from backend of your application by going to Backend > Settings > Common.

Author: Cloud Server for Email
Last update: 2021-09-03 07:01


Why do I get the error “This email address cannot be used” while saving a delivery server settings?

Starting with version 1.9.23, the email address that you use in the “FROM” field of a delivery server must be unique across all the customers in the system.
What this means exactly, if you have a customer A that uses a delivery server which has a “FROM” address set to “[email protected]”, then customer B will not be able to create a delivery server and use same email address.

Author: Cloud Server for Email
Last update: 2021-09-03 07:04


Upgrading notes for MaiWizz 1.x to MailWizz 2.x

When upgrading from MailWizz 1.x to MailWizz 2.x there are a few things you need to do before starting the upgrade process.

#1. It is very important you backup your application, be it on your own or by using the Backup Manager.

#2. You need to disable all the extensions and themes you have added to the application. Please note that we’re not talking about core application extensions but extensions you have bought or developed and added into the application.
You can do this from Backend > Extend > Extensions and Backend > Extend > Themes.

3. If you are using a language pack other than english, you need to set your application default language to english. You can do this from Backend > Extend > Translations.
For best results, if your user (not customer) account is using a different language than english, edit it and make sure it also uses english.

Possible problems during/after the upgrade process:

#1. You started the upgrade process without disabling the extensions and now you cannot access your backend dashboard to do so.
In this case, login via FTP and navigate to the apps/ folder and find the extensions folder and rename it to something else, say extensions-disabled.
This should allow you to continue the upgrade process. Once the upgrade is done, rename the extensions-disabled folder back to extensions BUT not before you upgrade all your extensions so they are compatible with MailWizz 2.0.

3. You started the upgrade process and you’re using other language than english and now you’re getting an error related to translations and/or missing translation database tables.
You will have to login via FTP and open the file apps/common/config/main.php and locate this piece of code:

'messages' => [
    'class'                  => 'CDbMessageSource',
    'cachingDuration'        => 3600,
    'sourceMessageTable'     => '{{translation_source_message}}',
    'translatedMessageTable' => '{{translation_message}}',
],

and delete it. Simply remove it and save the file.
This should allow you to continue with the upgrade process. Once the upgrade process is done, simply undo your changes to this file, put back the code you just deleted, and save the file.

If you get any issue which hasn’t been covered in this article, please create a support ticket and explain in details the problem and we’ll do our best to help.

Author: Cloud Server for Email
Last update: 2021-09-04 01:42


Low score in SpamAssassin because of the RAND_MKTG_HEADER rule?

In MailWizz, each install uses unique header prefixes which are generated at install time.
Seems that latest version of SpamAssassin does not like this, so if you run your emails through SpamAssassin, for example on mail-tester.com, you might get something like:

As you see, this new rule takes almost 3 points from our score.

In order to fix this, we need to use the traditional X– header prefix only, so no more X-Whatever- prefixes.
Luckily, with MailWizz this is simple and you don’t need to wait for an application update to have this fixed.
Open the file apps/common/config/main-custom.php which is basically the file generated at install time which contains your database connection info.
Inside your file, you will see something like:

return array(
    // application components
    'components' => array(
        'db' => array(
            'connectionString'  => '...',
            'username'          => '...',
            'password'          => '...',
            'tablePrefix'       => '...',
        ),
    ),
    // params
    'params' => array(
        'email.custom.header.prefix' => 'X-Abcd-'
    ),
);
We need to adjust the X-Abcd- part, so simply edit the file, and make sure you remove the Abcd- part, so that your new prefix is just X-, like:
return array(
    // application components
    'components' => array(
        'db' => array(
            'connectionString'  => '...',
            'username'          => '...',
            'password'          => '...',
            'tablePrefix'       => '...',
        ),
    ),
    // params
    'params' => array(
        'email.custom.header.prefix' => 'X-'
    ),
);
That’s it, save the file and re-run the mail-tester test, this time the results will look much better:



NOTE:
Because MailWizz uses these headers to process bounces, please make sure you change the header prefix only after at least 3 days after you have sent your last campaign, basically give the app at least 3 days to process any incoming bounces using the old header prefix.

Author: Cloud Server for Email
Last update: 2021-09-04 01:46


Internal failure, maybe due to missing functions like proc_open!

When validating a delivery server, and you get an error that says
“Internal failure, maybe due to missing functions like proc_open!”
Most likely the issue is that MailWizz cannot find a valid email template to send the validation email. To fix this, go to Backend > Settings > Email Templates > Common Email Templates, and press the “Reinstall core templates” button.
Then try validating the delivery server again.

Author: Cloud Server for Email
Last update: 2021-09-04 01:47


Track opens for Google emails

Lately, we noticed that the way Google is handling the emails is creating confusion regarding the tracking for the opens.

A little background on email tracking

The email tracker system places an invisible tracking pixel inside each message. Despite being practically invisible for people, this pixel is recognised as an image by the email client.

When rendering the message (upon opening it), the system will call the server where the “image” is stored. This action serves as a trigger for email open and will be saved to the system.

Google’s way of handling images

Google opens all images using its proxy server. Before forwarding the email to the recipient, the server loads the email content which the tracking software views as an email open. As a result, it can trigger false positive results. In addition to that, Gmail proxy server provides false information on the recipient location and device. That is why it is practically impossible to get accurate email tracking metrics if the recipient uses Gmail.

What we learnt

What we found was that Google will use its caching server most likely if the email is opened from the web browser using the Google mail interface (Google image proxy server). Even if the receiver was the one that opens the email, we will not be able to get its real IP and User Agent.

Another situation was when the email was opened as stated above, and the Google Anti-Spam Checker was hit. In this case the open will look something like:

It will have a another IP that belongs to Google (google anti-spam server ip) and the user agent is showing is fake.

On the other hand, if the email is opened with an email client, the correct IP and User Agent of the opener will be the correct ones.

Mailwizz is handling correctly these situations by avoiding the caching and counting correctly the opens. The problem is that we cannot relay on the information about the IP and User agent.

There will be a follow up, mode detailed blog article regarding the tracking here

Author: Cloud Server for Email
Last update: 2021-09-04 01:51


How do i enable command line import for subscribers?

Importing large CSV files from the web interface, like shown in this article, can be problematic sometimes. This is why we offer an alternative. We offer a way to upload your CSV file which will be queued and then processed by a command line command.

In order to enable this, you have to go to Backend > Settings > Import/Export and set the “CLI import enabled” option to Yes.

Next step is to click the info icon near this option. This will tell you to add a new cron job to your server. For example:

Don’t forget to save your changes.

When you will try to import a new CSV file for example, you will get new import options:

Using the new option means that your file will be uploaded on the server first. When the import starts, the file is divided into multiple smaller files and processed in parallel for a faster import.

Author: Cloud Server for Email
Last update: 2021-09-04 01:57


How do i import subscribers?

This is a common question and even though the answer is very very simple, for a reason or another, seems that many people get confused on how they can achieve this, so i will illustrate this, step by step with images.

Step 1: Login as a customer into your application and go to your lists:

Step 2: Click on your list title or on the Info icon for your list

(see highlighted section on Step 1)

to see the list overview page from which you will click on the Tools box :

Step 3: Click on the Import box:

Step 4: Choose one of the import options depending on the file you need to upload:

That’s it, once you select the file, the import will start and your subscribers will be imported into your list.

Possible issues and fixes:
1) if you get an error that the file type is not allowed, you can go to Backend -> Settings -> Import/Export and disable mime type checking.

2) if the app complains that the filesize is too big, go to Backend -> Settings -> Import/Export and increase the allowed size for uploaded files. If the app still complains afterwards, contact your host to alter your PHP configuration and allow bigger files.

3) if the importing doesn’t start, or it dies while processing, then most likely you have set too many Subscribers to process at once from Backend -> Settings -> Import/Export, so make sure you lower down the number to an acceptable one where the server will be able to process the files.

Author: Cloud Server for Email
Last update: 2021-09-04 01:59


What Cron Jobs are, why do i need to add them and how?

What is a cron job?
A detailed explanation about crons is given in the wikipedia at http://en.wikipedia.org/wiki/Cron
Long story short, a cron is a task that runs at regular intervals on your linux server.
Being a task, it means that at the time it runs, it will do an action and in mailwizz case, this means it will send campaigns, process bounces, do cleanup and so on.

Why do i need to add them?
The reason why Mailwizz uses cron jobs is very simple, the tasks that it runs, to send campaigns for example, are tasks that can take a long time to execute and if you run these tasks as a regular web page, then not only we would need to interact with these pages in order to trigger the actions, but also it would mean we need to keep those pages open as long as they execute and that the execution might fail for a dozen of reasons (say script timeout, or memory limit, etc). Using cron jobs, all these actions are handled without our interaction and can run for unlimited time without the need of interaction.

How do i add them?

The bright side is that, control panels like CPanel or Plesk will give you a web interface to add your cron jobs easier.
Youtube has a bunch of videos for CPanelPlesk , DirectAdmin and others, so there shouldn’t be a problem adding yours no matter what control panel you are using.

Author: Cloud Server for Email
Last update: 2021-09-16 02:16


Acelle Mail Questions

Acelle Mail does it work with Windows Hosting?

Acelle Mail is written for Linux environment only. So, you will need a Linux server hosting environment to run Acelle Mail. They do not support Windows yet.

Author: Cloud Server for Email
Last update: 2021-09-04 01:32


Interspire Questions

How Install Interspire Email Marketer

Interpsire Email Marketer - Installation Guide


Requirements
Please ensure your web host meets the application requirements below.
• UNIX or a Linux variant is preferred.
• Apache 2.4.x or Nginx 1.18.x or above
• PHP 7.2 or above
• MySQL 5.6 or above
• To use autoresponders, your need access to a scheduler - usually Cron on your web server.
• To process bounced emails, your version of PHP needs access to the imap_xxx functions (default).
• Please download and run check_iem.php to verify that the system requirements are met before starting
the installation.
Uploading Files
Unzip the Interspire Email Marketer package onto your local hard drive. If you don’t have Winzip, you can
download it for free. Using an FTP program (such as Filezilla, which is free, or a commercial package such
as CuteFTP), login to your web server and copy the Interspire Email Marketer files across into your base
website directory. This directory is commonly called public_html, html, www or website_html. If you’re
not sure what it is, your webhost provider will be able to tell you.
File Permissions
Interspire Email Marketer requires the following files/directories to have ’write’ permissions set. On a Linux
or Unix web host, you can use your FTP program and use the ’CHMOD’ (’Change Mode’) function to grant
write permissions. If a folder listed here doesn’t exist, please create it.
Files, CHMOD this file to 664:
• /admin/includes/config.php
Note: Although it says 664, some webhosts may require 666 instead.
Folders, CHMOD these to 775:
• /admin/temp/
• /admin/com/storage
Note: Although it says 775, some webhosts may require 777 instead.
MySQL Database
Interspire Email Marketer makes use of a MySQL database to store your data. This database must be created
before you run the Interspire Email Marketer installation wizard. Your database user account should also
have full grant access to that database. You will need the database connection details during the setup wizard.

Setting up your database may differ with your webhost and what software they use for your webhosting
control panel (cPanel, Please, etc.)

Setup Wizard

Interspire Email Marketer includes a simple one step installation process.
To start the setup wizard, navigate to the directory that you uploaded Interspire Email Marketer to, for
example: http://www.yoursite.com/iem/. The Interspire Email Marketer setup wizard will appear. It
contains the following fields:
• License Key - Copy the license key you received when you purchased Interspire Email Marketer and
paste it here.
• Application URL- This is the URL to your Interspire Email Marketer installation (not your main
website if this is in a sub folder)
• Email Address - This is the email that will be used for the super admin user that will be created, also
it will be the default contact email which can be changed later via your settings page.
• Password & Confirm Password - This will become the password for your admin user. The username
will be ’admin’.
• Database Information - You will need your database username, password, database name and host
(usually ’localhost’, though this may vary with some hosts).
• Send Server Configuration - This will send information about your server back to us. The data sent will
be basic information such as your PHP version, MySQL version, etc. No information that can identify
you or your website will be sent, it is completely anonymous. This will aid us in future development to
know what versions of PHP and MySQL we can support amongst other things.
Your Interspire Email Marketer configuration details will now be saved into the admin/includes/config.php
file. Your database tables will also been created.
Congratulations, you are now ready to login to the Interspire Email Marketer control panel and start on your
first email campaign! Your control panel will be accessible by adding ’/admin’ onto the end of your website
URL.

Author: Cloud Server for Email
Last update: 2021-09-04 01:37