Configure exim to listen on additional ports
Exim is a popular Message Transfer Agent (MTA) used on Unix systems. By default Exim will be listening on port 25. To make Exim listening on other additional port, say 26, add the following line to /etc/exim.conf.
daemon_smtp_ports = 25 : 26
After this restart Exim using the following commands.
service exim restart
or
/etc/init.d/exim restart
This will make Exim to listen on ports 25 as well as 26. Make sure you open the port 26 in the server firewall.
Horde login error
If you are getting Horde login error in Cpanel like :
Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0
Warning: Unknown: Failed to write session data (files). Please verify that the current setting of
session.save_path is correct (/var/cpanel/userhomes/cpanelhorde/sessions) in Unknown on line 0
Then try this Cpanel script :
/scripts/autorepair phpapps_owner_fix
The above script will reset all the quotas for the Cpanel* users.
Mail Error message: Error 550 The recipient cannot be verified
On servers running cPanel, some times it is found that mail sent to valid users is bounced back by the mail server.
The bounce back messages will be similar to the following.
PERM_FAILURE: SMTP Error (state 9): 550-”The recipient cannot be verified.
Please check all recipients of this550 message to verify they are valid.
If the email account does indeed exist, then it is need to run the following commands to correct the issue.
/scripts/updateuserdomains
/scripts/mailperm
Also check the /etc/localdomains file and verify that the domain name is present. Also verify that the DNS line in the /var/cpanel/user/username contains the domain as well.
DNS load balancer
Load balancing via DNS is achieved by assigning more than one IP address to the same name. For example, to balance the load on http requests for the site example.com, we would add more than one IP address, say 3, to the site. So the site can be accessed with any of the IP address.
The order in which the nameserver answers the dns query for that site is configured by setting ‘rrset-order’ in named.conf file.
For example, the configuration will return A records in round-robin order.
rrset-order {
class IN type A name “*” order cyclic;
};
Other options are,
fixed - returns A record in the order they are defined in the zone file
random - returns A record in some random order
/etc/rndc.key:1: configuring key ‘rndc-key’: bad base64 encoding
This error is due to the mismatch of the secret key in /etc/rndc.conf and the include file /etc/rndc.key. Both the keys should be the same.
After copying the secret key from the file /etc/rndc.conf to /etc/rndc.key, named can be restarted successfully.
root@host [~]# service named restart
Now named status can be checked
root@host [~]# service named status
