Forem: Pepipost

Explaining Bots and Its types - Part 1

Vikram Sahu — Tue, 07 Apr 2020 16:59:46 +0000

Fact: Do you know that a normal person interacts at least 3-4 times a day with a bot? but when? and how? impressive isn't it...
It is also said that in the future a person will interact more with a bot than their spouse.

Let's unfold the truth behind this...

Introduction

In simple words, bots are dumb machines that are programmed to do repetitive tasks, which are automated by a human being to save time. This was the definition that I concluded after working on a few bots.

Bots are coming into existence more and more because of their accuracy, speed and much more similar behavior to humans. if you ask me where I can find a bot? I would reply in just a few words "Everywhere on the web".

The most common bot/type of bot that you can experience right now is
Just unlock your phone and speak:

"Hey, Siri" if you have iPhone.
"Ok, Google" if you have Android.

Similarly, you can find Alexa or Google Home/mini which are also home assistants used for many tasks that a human wants to execute within the house like playing music, asking for news or setting reminders and many more.

The above examples are advance bots that were contributed by Gaint technology leaders, but there are many small bots that developers write for their own convenience, it can be chatbots, a web crawler, social bots, and some malicious bots.

Good Bot vs Bad Bot

This is the section, let's dive deep with nature of bots and how they are helpful to us with our day to day task.

So, Bots are developed to automate various repetitive tasks which turns out to be useful in many ways, but few are developed to harm your resource which is classified into good bots and bad bots.

What is a Good Bot?
- Good bots are built to gain profit for the business. These bots are beneficial for both businesses and individuals. The simple example you can assume is whenever you search for any websites, products or any services, you often get next to accurate results, how?
- This is possible because of search engines spider bot which is also known as crawler bot. Bots like
  - Googlebot
  - Slurp Bot [yahoo]
  - Alexa crawler [Amazon Alexa]
- Reputed companies often deploy this bot by following the rules of the webmaster crawling activity and indexing rate at websites robot.txt.
- Besides from these search engine crawlers, there are many different third party bots like
  - Slack bot. (Any complex integration can be done which can be notified directly on the channel).
  - telegram bot.
  - Pingdom bot. (website monitoring bot)

By this time you might be clear about good bots, so any bot who follow the rules and regulation of webmaster and the policies which result in profit for business are good bots.

What is a Bad Bot?
- As we know Bad is always opposite to Good. These bots are built by hackers, cybercriminals, fraudsters so that they get engaged in illegal activities.
- These bots are programmed for doing malicious jobs on the web.
- Let's take an example, you have a business setup for toys and you have a unique toy that is made by you. your competitor may build a bot that can be a scraper that can collect all the content, product reviews, feedbacks and what new toy you are working on and publish fake reviews on other websites.
- The second example is they travel thousands of visits on your website within the minimum span of time, that chokes the availability for other genuine users.

This bot is highly injurious for brand reputation which results in hampering of search engine website ranking.

Types of Bots

Good Bots are used to gain profit for the business and also helps to build your domain and website health. This bot helps by crawling website for search engine optimization(SEO), Collecting information, obtaining marketing analytics and many more.

Social Network Bots: These bots are managed and supported by social networking sites like Facebook, Twitter. Bots help to give visibility to the brand website and drive engagement to their platforms.
Feedfetcher Bots: These bots are used to collect information from different websites and help to keep subscribers updated with the product, events, and blog posts.
Parter Bots: These bots are third party bots that are developed and supported by the SaaS organization like Slack, PayPal, Stripe and many more. these bots help to integrate directly with the program within the organization.
Monitoring Bots: These bots are programmed in such a way that they periodically monitor and updates us about the uptime and health of the server/websites.
Search Engine Crawlers: These are the most common and maybe most used bots in this modern world. No matter, who you are you need search engines for simplicity and get your work done.

Let's look at few Bad Bots

Scraper Bots:
- These scrapers are used to steal vital information, prices, updates, and content. This will help the competitor to undermine the business strategies which will help them to target the company's revenue.
- Point to remember is that competitor ofter use third-party scrapers to perform this illegal act.
Spam Bots:
- These Spam Bots target community forums, lead collection forms, and comments sections.
- They usually target this section by adding unwanted promotional advertisements, links, and flood up the comment section by trolling users.
- The above activities frustrate genuine users to comment or use the forum's information. The main motive of such bots is to insert the link to phishing pages which are build to collect user critical information which included bank account, username, and passwords.
Scalper Bots:
- These bots target ticketing websites, they purchase 100-1000 of tickets and sell them to third party seller due to which the genuine ticket selling website lose their customers.

Each and every activity of a bot depends on the data it can be a training data or real-time data.

I always recommended not to expose your websites on HTTP instead always use HTTPS or use appropriate protocols to restrict such bots to crawl your website.

Concluding...

In this world of Machines and Artificial intelligence, I always want each and everyone to learn how the bot works and why you need a bot.
If you are keen to learn this new world paradigm, "First decode it" that is what I have discussed above in this blog.

I hope you enjoyed reading! Stay tuned for Part 2 where I will be building a Telegram bot from scratch.

Thank You! Do follow and share 🤗

Ref: shieldsquare

Simplifying Computational Complexity {time and space}

Vikram Sahu — Thu, 26 Mar 2020 13:56:17 +0000

Introduction

When someone wants to master computer programming, the best way to start is to learn the complexity of the system. Before you start with coding common questions you should ask yourself are:

Why should I write the program in this way only?
What will be the benefit of this program?
How many resources my program will consume?
How fast it will execute?

These questions will help you write efficient code.

Computational complexity is all about the writing optimized, efficient and blazing fast programs/code.

In this blog, you will be going through a few amazing theories of the computer system with examples.

Before learning complexity

Let's learn a bit about an algorithm:

A sequence of logical computation is called as the algorithm of the program. These algorithms are analyzed by calculating their time or space complexity. It is proved that your algorithm will always execute in worst-case complexity or an average-case complexity.

Worst-case complexity: Maximum resource utilized by your algorithm to execute with respect to the number of inputs.
Average-case complexity: Average resource utilized by your algorithm to execute with respect to the number of inputs.

I hope now you are getting a bit of an idea about the complexity theory. Let's dive deep to clear all our doubts...

Topics:

Resources.
Asymptotic complexity.
Computational models.

1. Resources

What are the resources as per you?
You might be thinking Human, keyboard, electricity, CPU, monitor & all the hardware stuff that you need while using your system then that is wrong❌.

The actual resource that I will be talking about is

Time.
Space.

Time complexity

The time complexity of an algorithm is measured irrespective of hardware and software associated with the system. The complexity considers the maximum time required to run an algorithm which is measured in asymptotic notation.

Space complexity

The amount of memory your algorithm requires to run is called space complexity.

Other complexities are arithmetic complexities which depend on the arithmetic computation that has been used in the algorithm and totally depends upon the size of input n.

2. Asymptotic Complexity

It is difficult to describe the compute of an algorithm precisely which falls between the worst-case and the average-case complexity. So in order to calculate the near to accurate complexity, it is always better to keep the input size n as infinity.

These asymptotic complexities are the boundary limits of an algorithm that includes upper bound(big-oh notation), lower bound(big-omega) and the tight bound(big-theta).

If you are pretty confident that your algorithm is good and won't hamper your system computational complexity below is the table of complexities you can assume your algorithm might take.

For analyzing any algorithm, it is recommended to consider the big-oh notation because it helps us to get the idea of the upper limit of the execution time of the algorithm.

I would recommend a 5 minutes read on hackerearth before proceeding further.

3. Computation Models

This is one of the vast topics which can be totally debatable. The model of computation describes how an output of the mathematical expression is computed when input is given. Similarly, the algorithms rely on these mathematical operations. So it is very important to choose the correct model for computation.

Deterministic models: These models are the exact opposite of random. It helps us to predict the exact event that will occur in the future without any involvement of randomness. So if you have some data you can predict the exact outcome with 100% certainty. for example :
- Rolling a fair die.
- Calculating Kelvin using Celsius.
Non-Deterministic models: These models are the opposite of deterministic where you will start with some sort of straightforward events later randomness will be getting added to it. Here you don't have the idea of what will be the future event. Since every time you run you will get a different output. In order to differentiate you can consider the below image.

Quantum computing models: These models follow the rules of quantum mechanics(the fundamental theory of physics describing the properties of nature.) The very famous example of quantum computing is AI(Artificial Intelligent). you can find more examples here

Concluding...

Any algorithm without proper computational logic is just a waste of resources. you can save those resources or use them in a better way by optimizing, building concise code better.

I hope you understood the very basic fundamentals of Complexity. Do share & comment! 🤗

How does email bounce work in Mautic

Hiteshpandey — Thu, 26 Mar 2020 09:29:21 +0000

Mautic being an opensource marketing solution provides you with various features such as email organization through segmentation and sending targeted emails through campaigns with email monitoring. In order to comprehend the impact of your campaign, you need to track how much of your sent emails are being successfully sent and how many emails are being dropped. You can do this by checking bounced emails in your campaign.

Why do emails get bounced?

Reasons for getting an email bounce notification can be many; from email address being changed, a domain has changed, the recipient's mailbox is full, etc.

Types of email bounces:

Hard Bounces:- A hard bounce of an email is caused by permanent non-deliverable conditions such as the recipient's email address is missing or invalid. Many other reasons for a hard bounce to occur are the non-existence of the recipient’s domain, unknown recipient, error in typing the recipient’s email address, blocking of your email server by the recipient’s email server, or any kind of network glitch at the recipient’s end.
Soft Bounces:- If an email message is able to find the recipient’s email server and recognize the address, but it is not delivered to the recipient’s inbox and bounced back before delivery, it is classified as a "Soft Bounce." The reasons might include: the recipient’s inbox is full, the recipient's email server is down for some reason, or the email box is abandoned by the user.

With this, we can go forward with setting up email bounce filtration in Mautic.

Step 1: Install and enable php-imap extension

If you haven't yet installed the php-imap extension please follow these instructions for the installation:

Install php-imap

$ sudo yum install php-imap // For centos \ RHEL
$ sudo apt-get install php7.0-imap // For ubuntu

Enable the extension

$ vim /etc/php.ini

Uncomment or Add these lines

extension=imap.so
extension=curl.so

Restart the HTTP server

$ service restart httpd\apache // For apache
$ service restart nginx // For nginx

Step 2: Setup Monitored Inbox Settings

Since now we have our PHP IMAP extension enabled we can move onward towards setting up our IMAP inbox with Mautic.

Login to the Mautic panel
Click on the [cogwheel icon] > [Configuration] > [Email Settings]
Set these credentials:

Monitored address - The email address you are going to use

IMAP host - The IMAP enabled email server's hostname

Port - Email server connection port [usually 993]

Encryption - Message encryption [usually SSL]

IMAP username - User name of your email account

IMAP password- Password of your email account

Click on [Test connection and fetch folders] to test the connection and populate the Folders from your email server.

Bounces - Select the bounces folder from which Mautic will be reading bounce notifications from. This can be set as the Inbox folder of your email directory or you can filter your bounce notifications to the Bounce folder which will be a cleaner way to handle this.

You can use Use custom connection settings? option too, for setting up different email addresses for different Requests.

Note:- By any reason you are not being able to see the Monitored Inbox Settings you can do two things to fix this

Check the php imap option is enabled in the php.ini file or not
Delete the Mautic cache folder and reload the page

// Mautic cache folder
/mautic_setup_path/app/cache/

Step 3: Setup Cron (If using IMAP)

Edit the Cron file and put the following Cron in it.

$ crontab -e

* * * * * php /path/to/mautic/app/console mautic:email:fetch

Step 4: Create a segment for bounce emails

Open Segments section in Mautic
Create a new segment named Bounce emails
In the Filters section, Select [Bounced - Email] option apply equals operator and set it to yes save this segment This segment will be updated when mautic:segments:update Cron is executed

Step 5: Enable Bounce Forwarding

After you set your IMAP server settings, Mautic would be checking for bounce notification emails in your specified directory. To receive these bounce notification emails, you might have to enable this in your email service providers panel.

All you have to do is set the email id which you have specified in the Monitored Inbox Settings to be forwarded the bounce email notifications.

In case you don't want to do that or your email service provider doesn't allow the kind of VERP format (more on that later), you can use the webhooks of your email service provider which is discussed in the next step

Step 6: Set the webhook to the Mautic mailer callback URL (Optional if you are using IMAP)

Depending upon the service provider you use you will have to set the webhook to the Mauitc callback URL.

The callback URL would look something like this:

http://<mautic_installation_domain>/mailer/{service-provider-name}/callback

Similar to the IMAP settings you can use this callback URL as a webhook in order to detect bounced emails. In this case, your email service provider provides information about the bounced emails through the webhook endpoint. Refer this section to know more about this.

If you are using a custom SMTP service that is not mentioned in the Email service list provided in the [Mail Send Settings] panel, you will not be able to use this. Regardless of that, if you have no problem with the setup until Step 5, you will be able to detect and interact with the bounced email ids into the Bounce segment.

Process

For IMAP inbox: Mautic uses the configured IMAP mail configuration to detect the Bounced email notifications. This is done by the execution of this Cron mautic✉️fetch

Mautic uses VERP Variable Envelope Return Path (VERP) to detect emails Return-Path header to check for the bounced email which normally is the from-address you are sending from, which is modified by Mautic
The format Mautic expects the return-path should be is

youremail+bounce_receiver-email-id@your-domain.com

When an email is bounced it is sent back with the Return-Path header
Mautic then uses this detail to set the contact as bounced email.
The bounce segment that is created by the user is then updated by the contacts that are marked as bounced. This is done after the execution of the Cron mautic:segments:update

I hope this helps clear some doubts about the bounce email handling in the Mautic service setup.

You can check the original post here - https://pepipost.com/tutorials/mautic-bounce-management/

A quick guide on Mautic installation for Ubuntu 18.04

Hiteshpandey — Wed, 25 Mar 2020 05:53:26 +0000

Mautic is one of the popular free open-source Marketing automation applications which can be used for multiple use cases of marketing paradigm. It ranges from sending bulk emails by uploading an Email list, Scheduling and Creating campaigns, Sending SMS and User journey.
This will be a quick detour on how you can set up Mautic service on your brand new server setup from scratch. But before that, here are some of the basic system requirements:

PHP 5.6.19 + (Magic Quotes GPC off)
MySQL 5.5.3 + (InnoDB support required)
Apache / Nginx
An SMTP service provider like Pepipost

You can check Mautic's official requirements page here

After confirming to these requirements you can now begin with the installation

Installation

Step 1: Enter into the root directory of your remote server

$ cd var/www/html/

Step 2: Create a new directory named Mautic

$ sudo mkdir mautic
$ cd mautic

Step 3: Download the Mautic production file package

To download Mautic at your local machine click here
Fill your credentials and click on the download button
The downloaded file would be named something like this 2.16.0.zip

Step 4: Copy the zip file to the remote server

Enter the following commands in your local machine download file location

$ scp -r 2.16.0.zip root@<your-domain-name/ip-address>:/var/www/html/mautic/mautic.zip

Note:- By any chance, you don’t have access to copy files to your server directory you can use FTP to upload the zip file, or you can use the git repo to clone it to your server directory, but you have to take some additional steps to get it up and running. Check this link for Mautic git repo.

Step 5: Unzip the file contents

    $ sudo unzip mautic.zip

If you don’t have unzip installed, you can install it by using

    $ sudo apt-get install unzip

Step 6: Delete the zip file

    $ sudo rm -rf mautic.zip

Step 7: Install php-fpm and dependencies

$ sudo apt install php libapache2-mod-php libapache2-mod-php php-common php-mbstring php-xmlrpc php-soap php-gd php-xml php-intl php-tidy php-mysql php-cli php-mcrypt php-ldap php-zip php-curl php-sqlite3 php-fpm

Step 8: Setting up MySQL

Install MySQL server

    $ sudo apt install mysql-server

Set MySQL root password

After the installation a temporary password will be generated in the mysqld.log file you can access this password by the following command $ sudo grep 'temporary password' /var/log/mysqld.log
Now you will get a message something like this [Note] A temporary password is generated for root@localhost: ,b*-rkuIR4Zas
Copy this password for the next step
Enter this command $ sudo mysql_secure_installation
This will prompt you to validate your password enter Y
After this, you will be prompted to set your password strength. Enter you choice between LOW, MEDIUM and STRONG.
Enter new password
You can say yes to all the other prompts that come after this
You will now be prompted with multiple questions on how to set up the MySQL installation. You can set Y to all the prompts
You will be able to login with the user root and a blank password Login to MySQL Create Mautic database and add User

mysql > create database mautic;
mysql > CREATE USER 'mauticuser'@'localhost' IDENTIFIED BY 'password';
mysql > GRANT ALL PRIVILEGES ON * . * TO 'mauticuser'@'localhost';
mysql > FLUSH PRIVILEGES;
mysql > exit;

Step 9: Setting up Http Server

(You can install Nginx or Apache server according to your needs)

Nginx: For installing Nginx you can follow these steps

$ sudo apt install nginx
$ sudo systemctl start nginx
$ sudo systemctl enable nginx

You need to make the following changes to nginx.conf file

$ vim /etc/nginx/nginx.conf

server {
       listen       80 default_server;
       listen       [::]:80 default_server;
       server_name  <Your domain name>;
       root         /var/www/html/mautic;
       location / {
               try_files $uri /index.php$is_args$args;
       }
       location ~ \.php$ {
       fastcgi_pass unix:/run/php/php7.2-fpm.sock;
       fastcgi_index index.php;
       fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
       include fastcgi_params;
       fastcgi_split_path_info ^(.+.php)(/.+)$;
       }
   }

Now depending upon your php-fpm setup you either need to add
fastcgi_pass 127.0.0.1:9000;
Or
fastcgi_pass unix:/var/run/php7.2-fpm.sock;
Note: If you are unclear on which value has to be set, you can check this in www.conf file.

    $ sudo vim /etc/php/7.2/fpm/pool.d/www.conf

Search for the listen parameter.

Apache: For installing Apache you can follow these steps

$ sudo apt install apache2
$ sudo systemctl start apache2
$ sudo systemctl enable apache2

You need to make the following changes to apache2.conf file

$ vim /etc/httpd/conf/httpd.conf

<VirtualHost *:80>
DocumentRoot /var/www/html/mautic
<Directory />
       Options FollowSymLinks
       AllowOverride All
   </Directory>
   <Directory /var/www/mautic>
       Options FollowSymLinks MultiViews
       AllowOverride All
       Order allow,deny
       Allow from All
   </Directory>
</VirtualHost>

After this you will be opening http://{your-domain-address} to open Mautic installation panel
There is more to this after the basic setup. But, since this tutorial is already too long here are some links to help you.
For more detailed setup on ubuntu 18.06 (Error resolutions | Setup | Setting up your first campaign) you can follow the original blog here — https://pepipost.com/tutorials/how-to-install-mautic-on-ubuntu-18-04/

Install Mailtrain on Ubuntu 18.04

Hiteshpandey — Tue, 24 Mar 2020 16:32:53 +0000

Mailtrain is a free open-source, self-hosted, newsletter application which is built on NodeJs and MySQL/MariaDB. Mailtrain allows us to send bulk emails by uploading e-mailing lists, with that it has email triggers, segmentation, email template generation from drag and drop to HTML editor. All you need is the SMTP credentials of your ESP.

In this tutorial, you will learn the steps required to successfully install and integrate Mailtrain Open Source Email Newsletter Application on a fresh Linux- Ubuntu 18.04 instance.

Please go through these prerequisites

A hosting server with a minimum of 1GB ram available for Mailtrain service. (To be at safer side, it is recommended to have slightly higher capacity)
Node.js (v7+)
MySQL (v5.5+ or MariaDB)
Redis (for session storage)
MySQL (v5.5+ or MariaDB) With these requirements fulfilled get-go through the installation steps

Installation

Step 1: Check Node version

$ sudo node -v

You can install Node.js using these commands (Skip this step, if you already have NodeJs installed)

$ sudo apt install build-essential
$ sudo apt-get install manpages-dev
$ sudo apt-get install nodejs

Step 2: Check MySQL version

$ sudo mysql -v

For the installation of MySQL server please refer to this article. (Skip, in case you have MySQL already installed):

Step 3: Clone Mailtrain git repository on your server directory

$ sudo git clone git://github.com/Mailtrain-org/mailtrain.git
$ cd mailtrain

Step 4: In this step you will create a new database and a new user, so log in to your MySQL instance and follow the given steps:

mysql> create database mailtrain;

Create a new user with its hostname and password

mysql> CREATE USER 'mailtrainuser'@'localhost' IDENTIFIED BY 'password';

Give user access and exit

mysql> GRANT ALL PRIVILEGES ON * . * TO 'mailtrainuser'@'localhost';

mysql> EXIT;

Step 5: Copy the file config/default.toml to config/production.toml

$ cp config/default.toml config/production.toml

Step 6: Edit config file

$ sudo vim config/production.toml

Step 7: Now you will make changes to the following sections in production.toml file:

Change the MySQL details based on the database you have created.

[mysql]
host="localhost" // your mysql host
user="mailtrainuser" // username
password="password" // mysql password
database="mailtrain" // database

Enable Redis if you have it installed.

[redis]
enabled=true
host="localhost"
port=6379
db=5

For installation of Redis follow the given set of commands

$ sudo apt-get install redis-server
$ sudo systemctl enable redis-server.service

Step 8: Run npm install

$ npm install --production

Step 9: For the final step, you will run the Mailtrain.

$ NODE_ENV=production npm start

You can run Mailtrain like this or you can create a Mailtrain service. To do that, you can now end the currently running instance by pressing [Ctrl + c] and follow the next steps.

Create and run Mailtrain service file

Step 1: Create a new user group forMailtrain

$ sudo adduser --system --group mailtrain

Step 2: Add user group in the production.toml file

$ sudo vim config/production.toml

Add these credentials

user="mailtrain"
group="mailtrain"

Step 3: Add permissions for our Mailtrain user to execute our directory

$ sudo chown mailtrain:mailtrain /var/www/html/mailtrain/ -R

Step 4: Copy our Mailtrain service file to our systemd system directory

$ sudo cp /var/www/html/mailtrain/setup/mailtrain.service /etc/systemd/system/

Step 5: Change the working directory in our mailtrain.service file

$ sudo vim /etc/systemd/system/mailtrain.service

Change "/opt/mailtrain" to whatever your Mailtrain folder path is for example "/var/www/html/mailtrain"

Step 6: Start the Mailtrain service

$ sudo service mailtrain start

And with this, you have the Mailtrain service up and running. You can check the status of the Mailtrain service by using this command

$ sudo service mailtrain status

With this done, you have successfully installed Mailtrain service on your Linux server.

The next step is to set up a reverse proxy.

Setup reverse proxy

Step 1: Edit production.toml file

$ sudo vim config/production.toml

Modify these lines

host="127.0.0.1" 
proxy=true

Step 2: Server config setup

For Apache2, use the commands mentioned below:

$ sudo apt install apache2
$ sudo systemctl start apache2
$ sudo systemctl enable apache2

You can find the Mailtrain server configuration setting for Apache in the following path.

$ vim /var/www/html/mailtrain/setup/mailtrain-apache.conf

Note:- You need to enable Proxy Mod on Apache2 (only if you haven't enabled it yet). This can be done by using the following commands:

$ sudo a2enmod proxy 
$ sudo a2enmod proxy_http

These are the settings you will be adding in your apache2.conf file:

$ vim /etc/apache2/apache2.conf

ProxyPreserveHost On
ProxyPass        "/" "http://127.0.0.1:3000/"
ProxyPassReverse "/" "http://127.0.0.1:3000/"
ServerName example.com
ServerAlias www.example.com

Restart the server

$ sudo service apache2 restart

For Nginx, use the commands mentioned below:

$ sudo apt install nginx
$ sudo systemctl start nginx
$ sudo systemctl enable nginx

You can find the Mailtrain server configuration setting for Nginx in the following path.

$ vim /var/www/html/mailtrain/setup/mailtrain-nginx.conf

These are the settings you will be adding in your nginx.conf file :

$ vim /etc/nginx/nginx.conf

    server {
    listen 80;
    listen [::]:80;

    server_name mailtrain.org www.mailtrain.org;
    access_log /var/log/nginx/mailtrain.log;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header HOST $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:3000;
        proxy_redirect off;
    }
}

Restart the server:

$ sudo service nginx restart

Step 3: Restart Mailtrain service

$ sudo service mailtrain restart

With this, you will be able to access Mailtrain dashboard on your domain URL

http://{your-domain-address}
I hope with these simple steps you are now able to use the Mailtrain set up for your marketing campaigns. For setting up your SMTP credentials and other settings you can refer the following link which is the original post:

Mailtrain setup for Ubuntu 18.04 - https://pepipost.com/tutorials/how-to-install-mailtrain-on-ubuntu-18-04/

For installation on Centos 7 - https://pepipost.com/tutorials/how-to-install-mailtrain-on-centos-7/