The selected default domain is not showing up in Plesk 11 when assigning it to a shared IP
This is a bug in Plesk. We found a solution by manually editing the ip_vhosts_bootstrap.conf file while logged in as root.
Steps involved for setting default domain for a shared IP
First, make sure you have selected the desired default domain for the desired IP address in Plesk.
Log into Plesk as admin -> Tools and Settings -> IP Addresses -> in the last column, click the number of sites -> select a site -> click Set as Default
In CentOS, we then edited this file :
You'll probably notice, as we did, that multiple "Include" lines point to different domain names. Move the line that points to the domain name you want to disaply as default domain to the top of the file. Then restart apache :
service httpd restart
Then refresh the page to check if the selected domain name shows up as the default domain. If the same domain is showing up, you're out of luck and will need to continue searching for a solution. It appears as though the first domain name/line encountered, for each IP in the system, is the default domain used by Plesk.
Because Plesk 11 doesn't actually print the domain name on the default page, you'll need to upload a test file via FTP and try loading that file in a browser to confirm you have the correct default domain loading on the IP address.
What is Postini and why does it block outgoing email?
In a nutshell, Postini is an outgoing mail filter purchased by Google in around 2009 (from memory) and to this day (some day in August 2012) is still owned and managed by Google.
Fine, except there's a major flaw in it, that the developers won't acknowledge, or if they do acknowledge it, they have no resolution they can offer for it.
The flaw is, when a Postini user sends email, Postini will not successfully deliver the message to the recipient's server. It will bounce the message back to the sender with errors such as :
Postini #550 Host not found for domain:perservices.net - psmtp ##
550 Neither MX nor MTA found for domain: - psmtp
So like any reasonably thinking person, you'd start searching for a solution online. And you won't find one, unless you get really lucky, and come across this post :
Google Product Form us
Some guy named David, worked it out, and some other power posting idiot (God bless him) keeps responding with the stock standard :
"550 Neither MX nor MTA found for domain: - psmtp"
This error is returned when the MX record lookup returned no MX records and the message security service was able to resolve the domain to an A record, but the attempt to connect to the IP address in the A record failed.
I'm sure you're here because you've read that 100 times, and like most people who read it, you also found it to be absolutely useless, because you know your MX records, exist, are correct and conform to the MAIL RFC standards.
Postini it would seem, wants to buck the standards, and expects to find a very high level priority preference MX record. What that means is, that for Postini to deliver the message to your mail server, you not only need an MX record (which you most likely already have) but that MX record must have a priority value of zero. As is :
yourdomain.com. IN MX 0 mail.yourdomain.com.
Your current MX record is probably MX(10). The priority value is simple in meaning. It sets the priority of the mail server, and anything delivering mail to your server, uses the highest priority server available.
For example, if you had 2 mail servers, just in case one mail server went down, you might have these two MX priority values :
yourdomain.com. IN MX 1 mail.yourdomain.com.
yourdomain.com. IN MX 2 mail.yourdomain.com.
The first MX record has a priority of "1", so that is the mail server that will be tried first when attempting to deliver mail to your domain. If that's down, the next highest priority mail server (MX 2) would be tried.
But you, like most only have one mail server. If you want Postini to even try delivering to that one and only mail server, you must set the priority to 0 (zero). Like such :
yourdomain.com. IN MX 0 mail.yourdomain.com.
Worked for David, worked for us. You can do this in Plesk, as the admin, by editing the DNS records for each domain. When editing the MX record, in Plesk 10 and 11 anyway, you have the option to set the priority. Go to the Domain, go to it's DNS settings, click the existing MX record and change it's priority from the default value of 10, to 0.
Or, if you're wanting to edit the DNS records directly, on CentOS they are found in :
and on Ubuntu they are found in :
Then restart the bind server with :
A further peculiarity was that Postini only failed to deliver mail to domains on shared IP addresses. Any mail sent to a domain on a dedicated IP address, even with the MX records set to a priority of 10, was successfully delivered. In any case, the descriptive error given by Google needs to be revised, because it certainly isn't accurate, let alone useful.