Blogs

Migrate from cPanel to Plesk Using Plesk Migrator

Plesk Migrator is a tool that Plesk provides. This extension provides pre- and post-migration checks, error reporting features, etc. It allows us to re-sync data between an old and new server after migration to make the migration process easy. We can use Plesk Migrator for updating Plesk to the latest version. This process is also known as ‘upgrade by transfer.’ Upgrade by transfer helps to move all hosting data and settings from the current Plesk server to a server with the latest version installed. Migrate using Plesk Web Interface We can use the Plesk web interface (UI) for the migration of domains from cPanel to Plesk. Login to the Plesk admin panel. Go to ‘Extensions’ and open ‘Plesk Migrator’ under ‘Server Tools’ and click install to install the Plesk Migrator. After the installation completes, go to ‘Extensions’ and click ‘Open’ next to Plesk Migrator under the ‘My Extension’ tab. Click ‘Start a New Migration’. Switch the ‘Panel type’ to cPanel and fill the Source server’s IP address, SSH port number, the login and password of a root user on the source server, etc. Click ‘Prepare migration’ to start the migration process. Plesk Migrator fetches the data from the source server. If the connection fails, then you need to check the source server information and make sure that the firewall does not block the connection and try again. After the completion of the migration process, you can find yourself on the ‘List of Subscription’ tab. In this interface, you can select the subscriptions to be migrated. Also, you can use any of the four available filters: By Subscription: If you migrate a subscription owned by a customer or a reseller, the corresponding customer/reseller account gets migrated unless a custom subscription owner is specified. By Customer: If you migrate a customer account, it migrates all the subscriptions owned by the account. By Reseller: If you migrate a reseller account, all subscriptions owned by the account gets migrated, but it does not automatically migrate the customer accounts owned by the reseller. If you select a reseller account and one or more customer accounts owned by that reseller for migration, the destination server preserves the reseller’s ownership of the customer accounts. By Hosting Plan: If you migrate a hosting plan, all subscriptions based on that hosting plan migrate. Select the content type that must be transferred or migrated. If you want to change any migration settings, then you can do the same by clicking ‘Settings’ in the upper-right corner. After selecting the corresponding settings and migration options, you can click ‘Migrate’ to proceed. Plesk runs the pre-migration checks to detect potential issues and display a report, as shown below. If you detect any issues in the report, we advise to fix that and click Refresh to re-run the tests. When the report is clean after the pre-migration checks, then you can click ‘Start migration’ to begin the migration process. You can monitor the migration process on the ‘Overview’ tab. The status of the migration gets displayed in the overview tab as either completed, successfully, or failed. If you want to perform any additional sync of a subscription’s content after the migration, you can click ‘Re-sync’ next to the subscription’s name. If you want to migrate additional subscriptions from the source server, repeat from step 7 to 13. You can click ‘Finish Migration’ if all the data has been migrated, this removes it from the list of ongoing migrations. Migrate via CLI through SSH Log in to Plesk and install ‘Plesk Migrator’. Connect to the server via SSH. If the configuration directory does not exist, then create the same and switch to that directory. # mkdir /usr/local/psa/var/modules/panel-migrator/conf # cd /usr/local/psa/var/modules/panel-migrator/conf Create ‘config.ini’ in the current directory with below content: # cat config.ini [GLOBAL] source-type: cpanel source-servers: cpanel target-type: plesk [plesk] ip: <destination_server_IP_address> os: unix [cpanel] ip: <source_server_IP_address> os: unix ssh-password: <source_server_root_password> # Uncomment ssh-port string below if the SSH port is not 22 # ssh-port: <replace_with_ssh_port_number> # postgres-password: <password> Note: If any PostgreSQL databases from cPanel server need to be migrated, then you need to make sure that the PostgreSQL administrator password is mentioned in the ‘config.ini’ file. Generate the migration list file using the below command # usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator generate-migration-list You can edit the above file to remove domains that does not need to be migrated, and assign domains to service plans: # vi /usr/local/psa/admin/sbin/modules/panel-migrator/sessions/migration-session/migration-list Start the migration by running the below command. # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator transfer-accounts After the transfer, run the below command to resynchronize the content. This command ignores the files which have already copied, and it re-syncs the modified contents. # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-content To check the operability of the migrated objects on the destination server, you can run the following command after migration. # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator test-all   If you need any further help, please do reach our support department.
Read more

How to Install DotNetNuke Via Plesk Onyx?

The DNN is formerly known as DotNetNuke, and it is a .NET web content management system. The DNN content management system runs based on Microsoft .NET. It was earlier written in VB.NET and shifted to C# with DNN version 6.0.4 and above. The DotNetNuke offers two distributions, such as the Enterprise and Professional editions, and the Community edition. The Community edition of DNN is an open-source CMS. The feature to create an approval workflow in DotNetNuke offers a business-friendly approach as it makes sure that nothing reaches the public eye until it is perfect. The DotNetNuke is a framework, and we can extend the same by creating modules. In this tutorial, we can check how to install DotNetNuke via Plesk Onyx. The DotNetNuke comes with a set of comprehensive features. Some of the features of DotNetNuke are: The DotNetNuke features a robust framework for server complex modules. It comes with extensibility, which makes it easy to create a wide variety of websites. The customizability feature of DotNetNuke makes it easy to create an appealing forum, blog, portfolio, and more without having programming experience. It offers multi-user management. The page and module caching feature of DotNetNuke help to optimize your site performance. In this knowledgebase, you learn the two methods by which you can install DotNetNuke in Plesk. Install DotNetNuke in Plesk Onyx We can perform the installation of DotNetNuke in Plesk by using the following two methods. Method 1 – Quick Installation Method 2 – Custom Installation 1) CREATE A MICROSOFT SQL SERVER DATABASE Before installing DotNetNuke, make sure that you have created a Microsoft SQL server database. To create a Microsoft SQL Server database, follow the below steps: 1) Log in to your Plesk control panel. 2) Navigate to the ‘Database’ section and click the ‘Add Database’ button. 3) On the next page, fill the detailed information about the database, such as database server, database name, username, and password. 4) Then, check the box next to ‘User has access to all databases within the selected subscription’. 5) After that, click the ‘Ok’ button. Now, the Microsoft SQL Server database creation is successful. You can verify the created database from the Databases section. 2) INSTALL DOTNETNUKE IN PLESK Plesk offers one-click installation for DotNetNuke. The two installation methods that you can choose from are quick installation and custom installation. Method 1 – Quick Installation To install the latest stable version of DotNetNuke, follow the steps below. Log in to the Plesk control panel as root or admin user. Navigate to the ‘Applications’ option and go to the ‘All Available Applications’ page. Search ‘DotNetNuke’ in the search box. Then, click the ‘Install’ button next to the ‘DotNetNuke’ application to install DotNetNuke. This step opens the DotNetNuke page. On the next page, specify the location where the application should get installed. Then, select the domain, protocol, and directory. If you have an SSL certificate installed on the website, then you can select https. Click the ‘Install’ button to start the installation. The installation takes some seconds to complete. After that, you can view the general information and configuration settings of the DotNetNuke application. Method 2 – Custom Installation You can use the custom method to select the desired version of DotNetNukefor installation. This installation method also allows you to select auto-update settings, set up the administrator user, and more. To install DotNetNuke in Plesk using the custom installation method, follow the below steps: Log in to the Plesk control panel as root or administrator user. Navigate to the ‘Applications’ option and go to the ‘All Available Applications’ page. Search ‘DotNetNuke’ in the search box. Click the down arrow next to the ‘DotNetNuke’ application and click the ‘Install (custom)’ option. Then, select the version that you need to install from the list. The above step opens the ‘Installation of DotNetNuke’ page. Read and review the license agreement. After that, click the checkbox next to the ‘I accept the terms of License Agreement’ line and click the ‘Next’ button. On the next page, Specify the location, protocol, directory, and domain. If you want to make sure that the domain name goes directly to the application, then leave the text box next to the directory name blank. To make sure that the application is up-to-date, select the checkbox next to the ‘Automatically Update this app when updates are available’ option. Then, select any of the following under the ‘Administrative access’ section. Use administrative credentials not connected to any particular user – You can select this option to create a dedicated administrative account for your DotNetNuke application. Grant administrative access to existing User – You can select this option to grant administrative access of DotNetNuke application to an existing user or account. In the Portal’s Preferences section, fill the email address of the administrator in the textbox next to the ‘Portal Administrator’s Email’ option. Then, fill the desired username and password for the administrator account in the textbox next to the ‘Portal administrator’s login’ and ‘Password’. Fill the name of the web portal in the ‘Portal name’ textbox. Type ‘localhost’ in the SMTP Server textbox. Fill the database details created in the ‘Database name’ and ‘Database user password’ text boxes, or you can accept the default value. Type the password again in the ‘Confirm password’ textbox. Click the ‘Install’ button to start the installation. The installation takes some seconds to complete. After that, you can view the general information and configuration settings of the DotNetNuke application.
Read more

How to Block the Traffic from a Particular Country in ISP Manager?

Firewall in ISP Manager is a software system that is configured on the server to deny/allow services based on a specified rule. The rule defines which services will be allowed through the firewall and which one should be avoided. The firewall module is used to handle the network connections and also create Firewall rules to accept or deny connections. There is an option in ISP Manager firewall to filter the requests coming from a particular country. In this tutorial, we are going to discuss how we can block a countries request in the ISP Manager Control Panel. 1) Login into the ISP manager. 2) Click on “Firewall” under the “Cluster Settings”. 3) Click on “Countries” which will lead to another page in which it will list all the countries. 4) In this page, you can see all the countries listed with their country code. You can select any country you would like to block the traffic and then click on “Block” as shown in the screenshot. 5)Click on “OK” to confirm your request. 6) Now you have blocked the traffic from the particular country you have selected. The glowing bulb means the traffic is blocked and the off bulb means the traffic is unblocked. This page shows which all countries traffic is blocked on the ISP manager control panel by looking at the status of the bulb symbol. If you need any further help please do reach our support department.
Read more

Various Reasons for IP Address Block in CSF

By any chance, if you get access denied when accessing cPanel account, do not try to login multiple time at that situation! If you are using wrong login credentials to access the cPanel and you have already tried 10 or 20 times in 5 minutes, then by that time your public IP will be blocked in the CSF firewall. So before trying to login to your cPanel account, you have to make sure that the Login credentials are correct and valid and they are the exact one in the Welcome Email Guide, that was sent to the registered email account with the hosting package. Block due to failed POP3/IMAP login attempts If you are seeing the error windows of IMAP/POP3 failed authentication in your email client, then most probably the login credentials you are currently using for the email account are outdated/incorrect. In this case, also you will end up with your IP get blocked in the CSF as the email client will not stop trying to access the mail server with that wrong credentials. Block due to failed SMTP login attempts Another way is that in any case if the SMTP authentication gets invalid so that you are unable to send email from the email client. So it is important to take care of the SMTP credentials to login, make sure that you are using the full email address and the correct password. Incorrect email client settings In some cases, the email client settings also cause for an IP block. Failed FTP/SSH loginIf you are accessing the server via FTP with some FTP client, then make sure that you are using the correct login details with the FTP client. Also if you are using incorrect port number to log in then also your IP get blocked in the firewall. Failed web page loginIn some cases, if the website needs authentication to further check as the website has some type of protected directory. Please make sure you use correct login details in the authentication box. Otherwise, there is a chance for your IP get blocked.   Edit CSF Configuration 1) SSH to the server. 2) Open the file csf.conf. # vi /etc/csf/csf.conf   3) Check the following parameters in the file csf.conf you have opened,  LT_POP3D = “value” In the place of value if you replace with a number then the failed POP3 login attempt times per hour per account per IP address is greater than the IP gets blocked. Put the value to zero to disable the option. Please keep in mind that the IP is blocked temporarily and it automatically unblocks after an hour! LT_IMAPD = “value” CSF will check the value corresponding to the LT_IMAPD and compare it the number of IMAP login failure and if the failure count is greater than the value mentioned hen the IP will be blocked. Using a high number is recommended other than putting zero as (0=option as disabled). Since this is the temporary block for an hour after that the IP will be unblocked!   LF_SSHD = “value” LF_SSHD_PERM = “value” These are the option in CSF to enabled to detect the login failure for sshd connections to the server. LF_FTPD = “value” LF_FTPD_PERM = “value” This option is enabled to check the login failure of ftp connections, compare the value with the login failure count and if the login failure is greater corresponding IP will be blocked. LF_SMTPAUTH = “value” LF_SMTPAUTH_PERM = “value” This parameter in the CSF will check the login failure of SMTP AUTH connections and the failure counts gets higher than the value set then the IP gets blocked. LF_POP3D = “value” LF_POP3D_PERM = “value” This option is enabled to check the login failure of pop3 connections to the server. LF_IMAPD = “value” LF_IMAPD_PERM = “value” Through this option enabled the CSF will check the login failure of imap connections to the server. 4) You need to restart the csf after that for the changes made to take effect server wide. Run the below command to restart the CSF.  # csf -r
Read more

Directory Structure of DirectAdmin Explained

About Control Panels A web hosting control panel is a web-based interface that allows administrator to manage the websites easily, and it is also very helpful for customers to easily manage their server even without any technical knowledge. There are so many type of control panels are available, such as: 1) DirectAdmin 2) cPanel 3) Plesk 4) Webmin Directory Structure The organization of files into a hierarchy of folders is known as the directory structure. The directory structures is modeled after the hierarchical tree model. Let’s take a closer look at the DirectAdmin directory structure in detail. Apache /etc/httpd              – Apache /etc/httpd/conf/         – Configuration files are stored in this directory /etc/httpd/conf/ssl.crt/    – SSL certificates are stored here /etc/httpd/conf/ssl.key/   – SSL certificate key stored here /etc/httpd/conf/extra/    – Contains virtual hosts /var/log/httpd/          – Apache log /usr/local/etc/rc.d/httpd start/stop   – For Apache start or stop   DirectAdmin /usr/local/directadmin              – DirectAdmin Installation directory /usr/local/directadmin/scripts/        – Contains scripts /var/log/directadmin/               – DirectAdmin log /usr/local/directadmin/custombuilds   – Contains build scripts /usr/local/directadmin/data/templates  – DirectAdmin templates Mail /var/spool/virtual/ – Mail directory /etc/virtual – Email virtual /etc/exim.conf – Configuration file /var/log/exim/ – Exim log /etc/virtual/acrilicos.com – Domain specific mail settings /etc/virtual/acrilicos.com/aliases – Email aliases /etc/virtual/acrilicos.com/quota – Email quota /etc/virtual/acrilicos.com/passwd – Email password /usr/local/etc/rc.d/exim start/stop – For Exim start or stop Named(BIND) /var/named/etc/namedb/named.conf – Configuration file /var/named – BIND directory /etc/namedb/domain.db – Database files /usr/local/etc/rc.d/named start/stop – For DNS start or stop Database /usr/local/directadmin/conf/mysql.conf – MySQL password stored here /etc/my.cnf – Configuration file /usr/local/mysql/data/ – Database path /var/lib/mysql/ – MySQL log /usr/local/etc/rc.d/mysqld start/stop – MySQL start or stop FTP /etc/proftpd.conf – FTP configuration file /etc/proftpd.passwd – FTP password /etc/proftpd.vhosts.conf – FTP virtual hosts /var/log/proftpd/ – FTP log /usr/local/etc/rc.d/proftpd start/stop – FTP start or stop SSHD /etc/ssh/sshd_conf – SSHD configuration file /var/log/messages – Log   If you need any further assistance please contact our support department
Read more

Too Low or 0.00 Disk Usage in DirectAdmin

To check the partition on our server, need to run the following commands. df -h The result would depend on what kind of partition we used on the server. If the server having an /home partition, then your quota_partition value will be /home. If it was not, then it will be /, so your quota partition will likely be /. In some cases, you might have a symbolic link like: /home –> /usr/home. In such cases, your quota will be same as above /usr. Set the partition value here, as needed: /home To check how much space is consumed by the system, DirectAdmin will run the following: /usr/sbin/repquota /home NOTE: repquota is a command used to print the overall summary of the server disk usage and quotas for the specified file system. Where /home is the quota_partition value being set in the /usr/local/directadmin/conf/directadmin.conf file. (Just like above examples: /home, / or /usr ). Then it will return the result with a list of numbers, example: /usr/sbin/repquota /home *** Report for user quotas on device /dev/hda3 Block grace time: 7days; Inode grace time: 7days Block limits                File limits User            used    soft    hard  grace    used  soft  hard  grace ———————————————————————- root      —  417796       0       0           7446     0     0 nobody    —       4       0       0              1     0     0 bin       —   56880       0       0            510     0     0 majordomo —       8       0       0              2     0     0 diradmin  —       8       0       0              2     0     0 admin     —     200       0       0             44     0     0 user123   —     100       0       0             22     0     0 user456   —     100       0       0             22     0     0 If the second column ” used ” is not showing anything or users are not in the list. Then we can run the following quotacheck command. On Redhat:  /sbin/quotaoff -a; /sbin/quotacheck -avugm; /sbin/quotaon -a; FreeBSD: /usr/sbin/quotaoff -a; /sbin/quotacheck -avug; /usr/sbin/quotaon -a; If the repquota throwing errors then we need to check in deeply this with the filesystem /etc/fstab file, it will be created automatically once the OS is installed. Whenever changes happen on the filesystem it will be modified automatically. To check with this, need to ensure that it contains rw, userquota, groupquota line beside the partition that is using the quotas. For an example: # Device                Mountpoint      FStype  Options            Dump    Pass# /dev/ad0s1a             /home           ext3     rw,usrquota,grpquota 1       1 /dev/ad0s1e             /tmp            ext3     rw                 2       2 proc                    /proc           procfs   rw                 0       0   In this case, the quota_partition is /home based on server configuration. Maybe it will / or /usr in your system. Or if it was shows, you may consider switching to journaled quota to avoid running quotacheck after an unclean shutdown: In that case, instead of “,usrquota,rpquota”, add “,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0” to your fstab file. Once the repquota program is returning a normal value, then you can run the tally to get the correct usage to show up in DirectAdmin: echo “action=tally&value=all” >> /usr/local/directadmin/data/task.queue This task.queue command will get picked up by the dataskq binary.   It calls the repquota command and dumps it into /home/tmp/quota-dump. Check /var/log/directadmin/errortaskq.log for any errors with this. Running the tally manually for a User can also help with debugging these issues.   If you need any further help, please do reach our support department.
Read more

How to Use IPv6 Address in DirectAdmin

As we all know that what is an IP address?. It is nothing but a logical numeric address that is assigned to each and every single computer, printer, switch, router, mobiles or any other device that is part of a TCP/IP-based network. An IP address is the most significant and important component in the networking phenomena that binds the World Wide Web (www) together. Direct Admin also supports IPv6 address from the version 1.37.0 onwards. Let’s look into how we can use IPb6 address in Direct Admin.   To Add IPv6 Address This is the first step. In order to use IPv6, we have to tell the Direct Admin that we need to use IPv6 address instead of IPv4. 1) Login to the server via ssh as the root user. 2) Open the DirectAdmin configuration file vi /usr/local/directadmin/conf/directadmin.conf 3) Find the ipv6 from the above configuration file. Then edit it as to 1 if it is mentioned as zero. Ipv6=1 3) Save the configuration file. 4) Then the very next step is to restart the service for the same. Execute the below command. service directadmin restart You can also add this by from the front end. 1) Login to the DirectAdmin panel using username and password. 2) Adding the IP address to DirectAdmin is done the same way as with we adding the IPv4 address. Select Admin Tools >> IP management. You can add the IPv6 address on the IP filed. Please be noted that the netmask 255.255.255.0 can only apply to an IPv4 address and should be ignored while adding an IPv6 address to the DirectAdmin. By default, the netmask of the IPv6 address is /64. But it is not yet supported. So that whenever we are adding the IPv6 address to the DirectAdmin, we need to use the full or short forms of the address. As we are giving in short forms of the address, the DirectAdmin will expand it to the full form of the IPv6 values. And please note that don’t give or use  around the IP address here. It is just fine with 1:2::9 Now the DNS system is ready for IPv6. We have dns_a.conf file and dns_aaaa.conf file default records for newly created zones. Each of these template files will check on the IP type. When an IP is sent to the template, the IP type is also included, so the template can choose to ignore adding any records if the IP type doesn’t match its format, or (with customization) you can add some other value if you’d like. For most people, leaving it alone will be best. How to Access the DirectAdmin via IPv6 address. 1) Login to the server via ssh as the root user. 2) Execute the following commands. /sbin/sysctl net.inet6.ip6.v6only=0 3) Set this in the /etc/rc.conf: ipv6_ipv4mapping=”YES” 4) Then verify with the sockstat command. If it is working correctly, It will give an output as follows. freebsd7-64# sockstat -l | grep direct | head -n1 nobody   directadmi 50362 0  tcp46  *:2222                *:* Otherwise, freebsd7-64# sockstat -l | grep direct | head -n1 nobody   directadmi 50362 0  tcp6  *:2222                *:* We have to get tcp46 in the output. If it is not, this means that the IPv6 is not enabled. 5) DirectAdmin should be restarted after this option is set. For the apache service, it already supports IPv6. So that no need of changes here. But we have to modify the exim and dovecot. Exim does not support IPv6. So we need to ensure it is compiled in. 6) Run the following command. /usr/sbin/exim -bV | grep Support Then you will get an output like as follows. Support for: crypteq IPv6 Perl OpenSSL move_frozen_messages Content_Scanning Old_Demime DKIM DNSSEC Event OCSP PRDR 7) If you are not seeing IPv6 in the output, then you’ll need to recompile exim, either using rpms, or from the source.  The latest Makefiles should have the required HAVE_IPV6=YES to ensure it’s included. 8) For the dovecot, edit the configuration file to the IPv6 support format. vi /etc/dovecot.conf 9) Find out the following line. #IPv4 listen = * #IPv4 and IPv6: #listen = *, :: 10) Change them to look like below. #IPv4 #listen = * #IPv4 and IPv6: listen = *, :: 11) Then restart the dovecot. service dovecot restart 12) For the older versions of dovecot vi /etc/dovecot.conf Add the following line. listen = “*, [::]”   If you need any further help, please do reach our support department.
Read more

Restore Exim Configuration

We all are familiar with the name EXIM; it is a mail transfer agent which is included with cPanel. We can configure the EXIM from WHM interface itself. There is a certain setting we need to edit on our exim configuration to make EXIM functional according to our requirement. For example, if we wish to relay emails through anti-spam software like MailChannels etc we need to add some configuration settings on the EXIM configuration. By default, Exim sends emails from the server primary IP address we can configure Exim to send emails from each domain dedicated IP address by adding some settings on the same. So while doing all these stuff initially before making changes we need to take a backup of the exim configuration files and if anything wrong happens we can easily restore the Exim configuration with those backups. We can save the backup either on the server itself or you can download the same to local backup using the Exim Configuration Manager. Also, we can use this option to clone the Exim configuration setting we have configured on one of the servers to another by taking the backup of the exim configuration and restoring the same to all the needed systems. You can access the Exim configuration from WHM >> Home >> Service Configuration >> Exim Configuration Manager   Please refer the below screenshot for better awareness. 1) Login to your WHM using the username and root password. 2) Click the option ‘Service Configuration’ to list all the configuration settings. 3) Open the ‘Exim Configuration Manager’. 4) From the Exim Configuration Manager, select the ‘Restore’ option. 5) We have two options for restoring the backup. We can restore the backup from the local system or can restore the backup saved in the server itself.
Read more

Email Deliverability in WHM

This interface will help you to identify the problems with your mail related DNS records such as SPF, DKIM, PTR etc. The system uses these records to verify that other servers can trust it as a sender. The Email deliverability feature in WHM displays the following details. Domain: The server’s hostname. Mail HELO: The server’s HELO configuration. In the next section, we deal with the SPF, DKIM, PTR records. SPF record is a Sender Policy Framework which helps to identify which servers are authorized to send mail for a domain. This will help you to reduce Spam activity in your domain. DKIM record is another method to validate the authenticity of email messages. Here the sender sends a mail which includes the private key and then the recipient server check the DNS server for the domain for the public key to verify the signature. This will also help to reduce the spam from your domain. PTR record is a DNS record that resolves the IP address of your hostname/domain name. To access the ‘Email Deliverability’ feature in WHM, please follow the below steps: 1) Login to your WHM interface. 2) Click on the option ‘Email Deliverability’ under the ‘Email’ section. From that interface, you can manage all the mail related DNS zones for the server. You can add records like SPF, DKIM and PTR records for your server hostname from there. Also, there is a feature called ‘Customize an SPF Record’ is available there, using this you can simply customize the system recommended SPF record for the domain.
Read more

Email Migration to cPanel Using Outlook

Email Migration is a method to migrate an email or multiple email messages from one email client to another email client. The protocols mainly used in email communication are POP3, IMAP, and SMTP. Post Office Protocol (POP) is a standard email protocol. It is used to receive emails from a remote server to a local client. The IMAP (Internet Message Access Protocol) is used to access emails that are on the remote web server from a local client. These two protocols are the commonly used email protocol for retrieving emails. Whereas, the Simple Mail Transfer Protocol (SMTP) is the standard protocol used by the server to send emails across the Internet. How to Change an Account from POP to IMAP in Outlook You can use the following steps to change the email protocol from POP3 to IMAP in Outlook. 1) BACKUP YOUR MAILBOXES If you switch from POP3 to IMAP, it deletes all the existing emails. So, it is recommended to take the backup of your mailboxes to avoid losing any relevant emails. 1) Open Outlook and select ‘File’. 2) Select the ‘Import/Export’ option under the ‘Open & Export’ section. 3) Select ‘Export to a file’ option from the Import and Export Wizard and click ‘Next’. 4) Select ‘Outlook Data File (.pst) as the file type and click ‘Next’. 5) Now select the mailboxes you would like to backup. It is recommended to backup all your mailboxes by selecting your email address in the Export Outlook Data File window. Also, ensure that you have checked the ‘Include subfolders’ box and then click ‘Next’ to continue. 6) Select a location on your computer to save the backup and click ‘Finish’. You can secure this backup file by creating an optional password for the file. 2) DELETE THE POP ACCOUNT FROM YOUR COMPUTER Once you save the backup to the system, you can delete the POP account in Outlook. Also, make sure that you delete the account on other devices that you use for email. To do that, follow the steps given below. 1) Select the ‘File’ option in Outlook and click ‘Info’. 2) Click the small arrow next to ‘Account Settings’ to select the ‘Account Settings’ option. 3) Select the email account and click ‘Remove’ to delete it from Outlook in the Account Settings window. The system warns that the offline messages will get deleted. Click ‘Yes’ to continue. 3) SET UP THE IMAP ACCOUNT ON YOUR COMPUTER 1) Click the ‘New’ button in the Account Settings window to create a new email account on your computer. Alternatively, you can add the same by clicking the file in the top menu and then click ‘Add Account’. 2) Select ‘Manual setup or additional server types’ option and click ‘Next’ to continue. 3) Select POP or IMAP option under the ‘Choose Your Account Type’ window and click Next. 4) Enter the IMAP server settings for your email account. You can see your server settings from the cPanel ‘Email Accounts’ option. After filling all the details, you can click ok and then ‘Next’ to proceed. 5) Then click Close and Finish. 4) RESTORE YOUR MAILBOX If you wish to restore all your old emails to the new set up, then you can follow the below process. 1) Choose ‘File’ from the top menu of Outlook and then select ‘Import/Export’ under the Open & Export option. 2) Select ‘Import from another program or file’ option and click ‘Next’. 3) Select the file type as Outlook Data File (.pst) in the Import a File window and click ‘Next’ to proceed. 4) Now select the backup file and also the options to configure how Outlook treats duplicate items and click ‘Next’ to continue. If the backup is secured, then you need to authorize the import by entering the password. 5) Select which folder you would like to restore your data into and click Finish to complete. How to Transfer Emails to cPanel Mail Account Using Outlook The following conditions should be met to transfer the emails from the old mail provider to cPanel. 1) You should have active email services in both the end. 2) The email client should support IMAP/POP/SMTP protocol. By using this method, we can set up two email accounts with old and new mail provider and then drag-and-drop existing emails to the new email server. You can use the below step by step instructions to transfer emails to the cPanel mail account using an Outlook email client. 1) SETUP EMAIL ACCOUNT HOSTED ON THE OLD SERVER If the email account is not set up in your email client, then you need to contact your previous email provider for setup instructions. If the email account is already set up in the old server, then you can skip this step. 2) SETUP EMAIL ACCOUNT HOSTED ON THE NEW SERVER Make sure to set up the email account on the new server. If you have not set the email account, you can follow the following steps to set up an email account in cPanel. 1) Log in to your cPanel and select the ‘Email Accounts’ under the Email section. 2) Navigate to the ‘+Create’ button. 3) Select the domain name from the drop-down and set the username and password for the same, then click ‘+Create’. 4) Click ‘Check Email’ next to the email account to login to the webmail. It is recommended to configure the server hostnames as incoming-outgoing server names instead of the ‘mail.yourdomain.com subdomain. Always make sure that the email account hosted in cPanel is set up as IMAP. 3) EMAIL TRANSFER FROM THE OLD SERVER TO THE NEW SERVER After the setup of both the accounts, you can see them in your email client window. The old server account has all the existing emails, and the new one should be empty. To transfer emails, you can select the old account and drag-and-drop them to the new account folder. If all the emails transfer or tasks are complete, then consider the email migration
Read more
Cart

No products in the cart.