ERROR:

You getting emails from Plesk, or getting Following error while pressing “Retrieve Keys” from Plesk >> Server >> License Management

Licensing Server Unreachable: Unable to connect with licensing server.
Please make sure that your network allows communication to ka.swsoft.com:5224.
For more details check system help pages

SOLUTION:

Plesk connects Parallels license server at 5224 port for the license update procedure. Make sure that the outgoing connection to ka.swsoft.com:5224 is not blocked on Plesk server or somewhere in the net. This can be examined with commands:

# nmap -P0 -p5224 ka.swsoft.com

[root@support ~]# nmap -P0 -p5224 ka.swsoft.com

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2008-11-05 10:00 EST
Interesting ports on ka.parallels.com (64.131.90.38):
PORT     STATE    SERVICE
5224/tcp filtered unknown

Nmap run completed -- 1 IP address (1 host up) scanned in 2.205 seconds

# telnet ka.swsoft.com 5224

[root@support ~]# telnet ka.swsoft.com 5224
Trying 64.131.90.38...
Connected to ka.swsoft.com.
Escape character is '^]'.

Getting error accessing VPS through SSH:

Difference Between MSSQL Server 2005 Express, Standard and Work group Edition

MS SQL 2005 Express Edition features are as follows :

* CPU : No
* 1 GB max memory limit for buffer pool : Yes
* 4GB max database size : Yes
* SQL Server Agent : Yes
* Full Text Search : Yes
* IMPORT/EXPORT : No
* Basic Integration Services : No
* Advanced Integration Services : Yes

MSSQL 2005 Standard Edition features are as follows :

* CPU : Yes
* 1 GB max memory limit for buffer pool : No
* 4GB max database size : No
* SQL Server Agent : Yes
* Full Text Search : Yes
* IMPORT/EXPORT : Yes
* Basic Integration Services : Yes
* Advanced Integration Services : Yes

MSSQL 2005 Workgroup Edition features are as follows :

* CPU : Yes
* 1 GB max memory limit for buffer pool : No
* 4GB max database size : No
* SQL Server Agent : Yes
* Full Text Search : Yes
* IMPORT/EXPORT : Yes
* Basic Integration Services : No
* Advanced Integration Services : No

How to fix Input/Output error on a VPS?

Recently we came up with the following error on one of our server and could not fix the same.

The server is a Virtuozzo Server with Plesk but this fix works for cPanel and other Control Panels as well.

And the error is as follows;

mv: cannot stat ‘<filename>: Input/Output error
**Note with the filename indicating the corrupt files or broken files

1) Now fora temporary fix Input/Output error try the following:

• find /vz/private/vps_ID/ | grep “file_name”

**Note with the filename indicating the corrupt files or broken files

• Then “ls” on directory where file is stored.

• Remove the broken file and try to restart the VPS.

Explanation for the error with an e.g.

Now the Problem occurs when there are a few broken files inside private area of of the VPS here for e.g we use vps_ID as 1000000

[root@xx ~]# ls /vz/private/1000000/root/var/www/vhosts/domainname.com/httpdocs/images/
ls: /vz/private/1000000/root/var/www/vhosts/domainname.com/httpdocs/images/ln_9.gif: Input/output error
ls: /vz/private/1000000/root/var/www/vhosts/domainname.com/httpdocs/images/logo.jpg: Input/output error
ls: /vz/private/1000000/root/var/www/vhosts/domainname.com/httpdocs/images/ln_7.gif: Input/output error

Here the system cannot stat the files and cannot move them away and these are the files which suggest that the file system on server can be corrupted.

2) Now for a permanent fix for the Input/Output error perform “fsck” for /vz partition.

What is SPF? [Sender Policy Framework]
SPF (Sender Policy Framework) is a standard that was created in order to stop and eliminate the forged or spoofed sender email addresses in the mail envelope SMTP MAIL FROM or Return-Path that commonly used in spam message. SPF is not directly about stopping spam – junk email. SPF works as an extension to the Simple Mail Transfer Protocol (SMTP), and allows relay MTA (Mail Transport Agent) to identify and reject those e-mail spam sent from unauthorized and unapproved mail server. SPF was created in 2003 to help close loopholes in email delivery systems that allow spammers to “spoof” or steal your email address to send hundreds, thousands or even millions of emails illicitly.

How SPF Work?
SPF enable domain’s email delivery operation works in such a way, Owner of an Internet domain name defines SPF records using a special format of TXT records in the domain zone DNS name server. The SPF specifies which machines are authorized to transmit e-mail for that domain. When an email is received by a mail server, the MTA will query the SPF records from DNS resolver to determine whether the email is originated from a legitimate server. If SPF PASS result is returned, the email is accepted and got delivered. Else if SPF FAIL result is returned, the email is rejected and bounced.

Is SPF is Must?
SPF records is not must, but it’s a good to set up the SPF records to stop spam fault from illegally spoofing. If your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer).
Now many mail servers such as AOL and Hotmail now require valid SPF record for inclusion in their whitelist program so if you don’t have one your email will probably not be delivered to that server.

How to Set up SPF record for a domain?
The major issue for SPF records are how to write and create a properly SPF record which is valid and correct for the domains, as all SMTP server that sends email for the domains must be defined.

For SPF to work you have to add, to each DNS zone a record similar to this:

domain.com. 14400 IN TXT "v=spf1 a mx -all"

note:- “.” is necessary after the “domain.com” otherwise SPF fails to work.
“domain.com” is the domain for which you were adding SPF record.
Syntax used is as follows,
You will notice that all SPF record start with v=spf1. “v=” defines the version of SPF used, and is mandatory to identify it’s the SPF record. Currently only the only version supported is spf1.
A :- If the domain name has an A record corresponding to the sender’s address, it will match. (That is, the mail comes directly from the domain name.)
MX :- If the domain name has an MX record resolving to the sender’s address, it will match. (That is, the mail comes from one of the domain’s mail servers)
ALL :- Matches always, used for a default result like -all for no other IP’s are allowed to send emails.

You can read all the options that you have by visiting: http://www.openspf.org/SPF_Record_Syntax