Using Perl to make changes to your DNS files
Example : You would like to change “v=spf1 a mx ip4:1.2.3.4 ?all” to “v=spf1 a mx ip4:1.2.3.4 -all”
of course, where 1.2.3.4 should be replaced by your server IP.
If you’d rather do this to all of your domain, you can use perl
cd /var/named
perl -pi -e ’s/\?all/\-all/’ *.db
change /var/named to the appropriate directory for your db files for your OS (/etc/bind, /etc/namdb)
Restart named after making the changes.
Get exim to listen on another port other than 25
Some ISP’s are now blocking outgoing port 25 which prevents user from using smtp via their server. The workaround is to get exim to listen on another port other than 25 to bypass the ISP’s block.
For example, to get exim to listen on both port 25 and port 587, you’d add the following code to the very top of the /etc/exim.conf file:
daemon_smtp_ports = 25 : 587
Once saved, restart exim:
Redhat:
/sbin/service exim restart
FreeBSD:
/usr/local/etc/rc.d/exim restart
More: http://www.exim.org/exim-html-4.40/doc/html/spec_13.html#SECT13.5
SPF record
An SPF record is simply a TXT type dns record which is used to store information about what IPs are allowed to send email for a specific domain. A receiving mailserver can do a lookup on this TXT record get get this data, and use the information to decide if an IP sending email from a specific domain really is allowed to be sending email for that domain.
There are a few options you can use with SPF records to govern the severity of encforcement on these rules.
Details on these rules can be found here: http://www.openspf.org/SPF_Record_Syntax
Setup your SPF record to use the -all option insetad of the ?all option so that email can *only* be sent from your server. This means that you *must* get all of your clients to send their smtp through your server, or they will be tagged as spam for spoofing. If they’re blocked on port 25 to your server, tell them to send on port 587 to your server (same thing, just not block by the ISP) value of -all, you can either change your DNS zone manually from:
Directadmin-> Admin Level -> DNS Administration -> domain.com or User Level -> DNS Management
change:
“v=spf1 a mx ip4:4.2.2.2 ?all”
to be
“v=spf1 a mx ip4:4.2.2.2 -all”
of course, where 4.2.2.2 should be replaced by your server IP.
Restart named after making the changes. Allow at least 4 hours for the new records to propogate.
Service Container on a Parallels Virtuozzo Containers hardware node can be created using ‘vzsveinstall‘ utility:
# vzsveinstall -D DISTRIB_DIR -s SERVICE_CT_IP
- DISTRIB_DIR - path to Virtuozzo distribution directory hierarchy on a server.
- SERVICE_CT_IP - IP address to be assigned to Service Container;
In case you have downloaded Virtuozzo distributive already (example for 64-bit PVC 4.0) as file “virtuozzo-4.0.0-${build_version}-x86_64.sfx”, please extract it in the following way:
# mkdir -p /vz/full_distr
# bash /path/to/virtuozzo-4.0.0-${build_version}-x86_64.sfx -d /vz/full_distr –extract
Create Service Container then using this command (make sure old Service Container #1 does not exist):
# vzsveinstall -v -D /vz/full_distr -s SERVICE_CT_IP
Please refer to man page on ‘vzsveinstall‘ utility for additional information.
Reference: http://parallels.com
updating Parallels Plesk Panel inside Parallels Virtuozzo Containers using EZ templates.
Install the vzaiproxy package on the hardware node. You can download this package from http://autoinstall.plesk.com/vzaiproxy
Change line 16 in file /etc/init.d/vzlinkmgr to the following:
Change line 32 in file /usr/sbin/vzaiproxy to the following:
DefaultAgentCmd = (’vzctl’, ‘exec’, ‘1′, ‘/opt/vzagent/bin/vzlcon’)
Install all EZ templates from Parallels Plesk Panel distribution on the hardware node.
Run Parallels Plesk Panel installation or upgrade using Parallels Products Installer (either via the web-interface or command line interface) or Parallels Plesk Panel GUI (Home Page > Updates).
Follow the instructions presented on the screen to complete the upgrade.
Refer to Parallels Plesk http://parallels.com/Plesk/
