Click Add new subdomain from the Websites & domains tab.

Enter the subdomain name in the Subdomain name field, e.g.: test.example.com

Under “Hosting settings”, the Document root option specifies where the website files are stored.

If left as default, files will be stored in the main domain directory. You can change the directory later.

When done, click OK.

A confirmation message will appear indicating the subdomain was added successfully.

When you try to view your Web Statistics data on Plesk Panel, a screen asking for a username and password may appear. If you frequently monitor these statistics, entering the information every time can be tedious. The following steps will allow automatic login.

Log in to your panel and go to the hosting settings of the account whose statistics you want to view.

Web statistics (accessible via password-protected directory ‘/plesk-stat/webstat/’)

Uncheck this checkbox and click Save.

After saving, you will be able to access the Web Statistics section without entering a username and password.

First, we need to activate the error pages from our panel to make them usable.

After activating the error page, go back to the Websites & domains tab and open the Virtual Directory section.

Click on the Errors_docs directory, and select your 404 error page from the list (not_found.html — some panels may not display it as 404).

When opened with the HTML editor, enable the Save as checkbox, make the necessary adjustments as /404.asp, and save.

With the subdomain addition feature in Plesk panel, you can run different sections of your site as separate websites. For example, you can open a subdomain like support.sitename.com for your company’s technical service, set up a separate site there, announce your technical support policy to your customers, and allow them to receive technical service through support.sitename.com.

First, log in to Plesk panel and click the Add new subdomain button from the Websites & Domains tab.

On the page that appears, there are 2 fields to fill in:

Subdomain name: Enter the subdomain site name you want to set up. E.g.: support.sitename.com

Document Root: This section specifies which directory the subdomain files will be placed in. If left empty, files will be stored in the main domain directory. This directory can also be changed later.

Once you have completed all the steps, you will have added the subdomain to your account.

You can now upload your subdomain site files to the server via FTP and activate your site.

The main purpose of these two-page articles is to stop mail spam attacks from compromised machines via PHP socket opening method and to prevent our mail servers from being blacklisted. The tools we use to achieve this are all Open Source projects that are still being actively developed.

To briefly explain the structures we use and their functions: we used the relay server concept to control and log different machines under a single structure. The main programs used in this structure are Postfix as MTA, Spamassassin which automatically checks the content of emails, and Policyd Cluebringer which handles the bulk of the work.

Policyd, a Postfix plugin, with its lightweight structure checks only the headers of incoming mail without looking at the content, verifies whether the sender is our customer, and allows mail to be sent if the user is authorized in the system. As you can imagine, with this structure we can block outbound mails at a rate 60% higher by blocking mails not defined in the system, while delivering registered users’ mails without any issues.

Note: Ubuntu 15.04 was used in this installation.

1 Postfix, Spamassassin, Policyd Installation and Configuration

1.1 Redirecting Exim Cpanel Server

nano /etc/exim.conf

Edit the smart route line if it exists, or add it yourself:

smart_route:

driver = manualroute

domains = !+local_domains

transport = remote_smtp


This ensures all incoming port traffic on the Exim MTA system is forwarded to the other machine

route_data = <RELAY SERVER IP>

1.1.1 Testing the Redirect

echo “This is the body of the email” | mail -s “This is the subject line” user@example.com

Send a mail to any address using this command and listen on the relay server machine with tcpdump. If output appears on the page, the redirect was done correctly.

tcpdump host <CPanel IP>

If we can receive packets from our server here, we can proceed to the Relay server where the main operations will be performed.

1.2 Postfix Installation

1.2.1 Prerequisites for Postfix Installation

• Root privileges for installation
• The mailutils package containing mail commands like mailx for testing Postfix:

  apt-get install mailutils

1. Downloading Postfix

   apt-get install postfix

   
   

   1. Configuring Postfix - Editing main.cf

      
      

      sudo nano /etc/postfix/main.cf

      
      

      smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination
      
      myhostname = SERVERNAME
      
      alias_maps = hash:/etc/aliases
      
      alias_database = hash:/etc/aliases
      
      mydestination = localdomain, localhost, localhost.localdomain, localhost
      
      relayhost =
      
      mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128, 31.192.215.72
      
      mailbox_command = procmail -a “$EXTENSION”
      
      mailbox_size_limit = 0
      
      recipient_delimiter = +
      
      inet_interfaces = all

      
      

      sudo service postfix restart

   
   

   2. Testing the system

      
      

      echo “This is the body of the email” | mail -s “This is the subject line” user@example.com

1.3 Spamassassin Installation

apt-get install spamassassin spamc

groupadd spamd

useradd -g spamd -s /bin/false -d /var/log/spamassassin spamd

mkdir /var/log/spamassassin

chown spamd:spamd /var/log/spamassassin

1.3.1 Activating Spamassassin

nano /etc/default/spamassassin

Change ENABLED=0 to ENABLED=1

Change CRON=0 to CRON=1

SAHOME=“/var/log/spamassassin/”

OPTIONS=“–create-prefs –max-children 5 –username spamd -H ${SAHOME} -s ${SAHOME}spamd.log”

service spamassassin start

1.3.2 Integrating Spamassassin with Postfix

nano /etc/postfix/master.cf

Replace: #smtp inet n - - - - smtpd

With: smtp inet n - - - - smtpd -o content_filter=spamassassin

spamassassin unix - n n - - pipe user=spamd argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f ${sender} ${recipient}

service postfix restart

1.3.3 Customizing Spamassassin Configuration

nano /etc/spamassassin/local.cf

rewrite_header Subject [***** SPAM SCORE ****]

required_score           5.0

use_bayes               1

bayes_auto_learn        1

service spamassassin restart

tail -f /var/log/spamassassin/spamd.log

apt-get install postfix-cluebringer

apt-get install mysql-server mysql-client

/usr/bin/perl -MCPAN -e ‘install Net::Server’

/usr/bin/perl -MCPAN -e ‘install Net::CIDR’

apt-get install libconfig-inifiles-perl

apt-get install libcache-fastmmap-perl

/usr/bin/perl -MCPAN -e ‘install Mail::SPF ‘

mysql –version

cd

mkdir policyd-cluebringer

cd policyd-cluebringer

wget http://download.policyd.org/v2.0.14/cluebringer-v2.0.14.tar.xz

unxz -c clue | tar xv

cd clue*

cd database

for i in core.tsql access_control.tsql quotas.tsql amavis.tsql checkhelo.tsql checkspf.tsql greylisting.tsql

do

./convert-tsql mysql55 $i

done > policyd.mysql

1.4.5 Activating the Database

mysql -p

mysql> create database cluebringer;

mysql> use cluebringer;

mysql> CREATE USER ‘cluebringer’@‘localhost’ IDENTIFIED BY ‘mypassword’;

mysql> GRANT ALL PRIVILEGES ON cluebringer.* TO ‘cluebringer’@‘localhost’;

exit

mysql -u root -p cluebringer < policyd.mysql

1.4.6 Configuring Cluebringer for Database

nano /etc/cluebringer/cluebringer.conf

DSN=DBI:mysql:dbname=cluebringer;host=localhost

DB_Type=mysql

DB_Host=localhost

DB_Port=3306

DB_Name=cluebringer

Username=cluebringer

Password=mypassword

service postfix-cluebringer start

service postfix-cluebringer status

1.4.7 Integrating Cluebringer with Postfix

nano /etc/postfix/main.cf

smtpd_recipient_restrictions = check_policy_service inet:127.0.0.1:10031, permit_mynetworks

smtpd_end_of_data_restrictions = check_policy_service inet:127.0.0.1:10031, permit_mynetworks

nano /etc/postfix/master.cf

policy-spf  unix  -       n       n       -       -       spawn

     user=nobody argv=/usr/sbin/postfix-policyd-spf-perl

1.4.8 Cluebringer WebUI Configuration

nano /etc/cluebringer/cluebringer-webui.conf

$DB_DSN=“mysql:host=localhost;dbname=cluebringer”;

$DB_USER=“cluebringer”;

$DB_PASS=“mypassword”;

cd /var/www/html

ln -s /usr/share/postfix-cluebringer-webui/webui/

apt-get install php5-mysql

1.5 Final Notes

• Our server is now practically operational. All further configurations depend on your server’s situation and how you define permissions in Policyd.

1.6 References

• Postfix Installation


• Spamassassin Installation


• Policyd Installation

SCP (Secure Copy) is a command used to transfer files between two servers connected to the internet. The general usage of the command is as follows:

scp SourceFilePath DestinationServerInfo

For example, suppose you want to transfer a file located at home/share/demo.tar.gz on your server to another server. The destination server IP address is 192.168.1.1 and the transfer directory is /home/linux/demo. Note that if the destination server uses a different port, you must specify it with -P after the scp command. Let’s say the destination server port is 1064. The command to use is:

scp -P1064 home/netinternet/demo.tar.gz root@192.168.1.1:/home/linux/demo

After running this command, the server will connect to port 1064 of the destination server and display its MAC address, asking whether you want to proceed. After answering yes to the yes/no prompt, it will ask for the root password of the destination server. After entering the root password and pressing Enter, the file transfer will begin. Once the transfer is complete, you can verify the file exists in the directory specified in the command on the destination server.

To install Proticaret, the following steps need to be completed;

• Download the latest version to your computer from the Proticaret website
  (www.proticaret.org)

• Upload the files to your website’s http folder via an FTP client.

• In MaestroPanel (if you are an Administrator), go to Tools > Asp.Net module and grant Full Trust
  permission to the website where you want to install Proticaret.

• In MaestroPanel, go to the ASP.NET area at the website level and set the .Net Runtime to v2.0.

• After going to the website in MaestroPanel,
  grant write permission to the Upload folder and the Web.config file from the File Manager.

• In MaestroPanel, go to the Ms SQL area at the website level and create the database and user that Proticaret will
  use.

After completing these steps, you can begin the Proticaret installation,

Note:

If you encounter an error during installation, you must create a technical support notification from your Customer Panel. Our Support team will assist you as
soon as possible.

Newly created email accounts sometimes require verification. If you are receiving an error like in the image, click on the verification URL in the email content, enter the
verification code on the page that opens, and press Enter.

After approximately 15 minutes, the mail account will be verified and will be in normal usable condition.

DeliveryReporter API internal failure: DBD::mysql::db selectall_arrayref failed: Table ‘./eximstats/smtp’ is marked as crashed and last

If you are encountering an error report like the
one above in the Mail Delivery Reports section, it means the exim table on your server is corrupted via SSH. You can fix it with the following command.

mysqlcheck –repair eximstats