Ex:

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: xxx@xxx.xxx

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 503 503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server. (state 14).

Solution:

Firstly check if the mailbox you created within Plesk or within the MailEnable administration console has a valid mapped email address. You can check within MailEnable by right clicking on a mailbox and accessing the properties window. Next navigate to the “Addresses” tab and ensure that a valid email address has been created for the mailbox.

If the mailbox does have a valid email address assigned then the next step is to ensure that you have not enabled inbound SMTP authentication. You can check this under the MailEnable SMTP settings bu navigating to: Servers>localhost>connectors>SMTP. Right click on SMTP and access the properties window and navigate to the “inbound” tab. Click on “Settings” within the “port settings” section and ensure that the option for “Requires connections to authenticate before sending email”.

If the above option is disabled next is to check the under the SMTP “Advanced SMTP” options under the “inbound authentication” section. Ensure that the drop down menu is not set to “Require authentication for all connections”.

If all is ok it might be the configuration files are corrupted. You can run the plesk utility mchk.exe to fix the same.

in command prompt open “C:\Program Files (x86)\Parallels\Plesk\admin\bin” depending on your plesk install location.

mchk.exe –all –fix=all

That should fix your configuration files.

Cheers

The server principal “someuser” is not able to access the database “somedb” under the current secuity context )microsoft sql server, error code, 916

To fix this SQL Server Management Studio 2008 bug please do the following:

1. Open SQL Server Management Studio 2008
2. Connect to the database server as normal
3. Press F7 to open the “Object Explorer Details” window or click “View” >> “Object Explorer Details”
4. In the object explorer details window expand by double click on “Databases”
5. Right click on the header bar (“Name”, “Policy health state”, “Recovery Model”, etc) and deselect “Collation” from the menu that will pop up
6. From the object explorer, refresh the “Databases”

Login to SSH (make sure you have access to  SSH, contact your hosting provider)

Now type following command to import sql data file:
$ mysql -u username -p -h localhost data-base-name < data.sql

If you have dedicated database server, replace localhost name with actual server name or IP address:
$ mysql -u username -p -h 192.168.1.10 databasename < data.sql
OR use hostname such as mysql.hosting.com
$ mysql -u username -p -h mysql.hosting.com database-name < data.sql

If you do not know the database name or database name is included in sql dump you can try out something as follows:
$ mysql -u username -p -h 192.168.1.10 < data.sql

Okay, you just wan’t to know how to fix this? Easy. After switing back to mod_fcgid, you need to log in the terminal as root and open the php.conf file.

/usr/local/apache/conf/php.conf

(This is the cpanel apache location, you might need to change it to your actual file location)


You need to add the following line:

MaxRequestLen 15728640

However, even with that change, it might be throwing 500 errors. So add the following  too:

PHP_Fix_Pathinfo_Enable 1

These are the final additions I made to the php.conf file


MaxProcessCount 1000
DefaultMaxClassProcessCount 100
IPCConnectTimeout 60
IPCCommTimeout 60
PHP_Fix_Pathinfo_Enable 1
IdleTimeout 900
IdleScanInterval 120
BusyTimeout 300
BusyScanInterval 120
ErrorScanInterval 9
ZombieScanInterval 9
ProcessLifeTime 3600
MaxRequestLen 15728640

Restart Apache and you are well on your way…

Fix:

Login to WHM

Navigate to WHM -> Security -> Security Center

Click on Apache mod_userdir tweak.

If the tweak is enabled, you will not be able to access via ~username.

Symptoms:

1. To view and edit the Plesk DNS zone database you will need to use an MS Access database viewer such as MDBPlus, and then open up the pleskmain.db located at:

   C:\Program Files (x86)\Parallels\Plesk\admin\db – Note: password is the same as Plesk admin login.

2. Check dns_zone records for the problem domain’s entry (domain.com for example):
   1. if there are multiple entries for the same domain; remove the entry that has the incorrect setting of 2;
   2. if there is only one entry for the domain, adjust the value in the “status” column from 2 back to 0.
3. Save the database.
4. Go back into Plesk and navigate to the DNS zone settings tab for the affected domain.
5. Select “Restore Defaults” to rebuild the appropriate entries for the domain

You should now be able to resolve the domain correctly.

Occasionally when the server is busy and a domain is being deleted the site is deleted off IIS, Mail Server and DNS Server but it still remains on the Plesk and shows like an Suspended account.

(Reason for that is Plesk uses DNS zone to perform its suspension, when an account is suspended from a server plesk turns down the DNS zone of the domain, so when it see’s the DNS zone missing it interprets as the domain is suspended)

In such occasions the domain needs to be deleted from the PSA database of plesk.

Plesk Uses 3 database models you can find which one you are using by doing the following:

To determine database provider it is necessary to run regedit.exe and go to

for x86

HKEY_LOCAL_MACHINE\SOFTWARE\PLESK\PSA Config\Config

for x64

HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\PLESK\PSA Config\Config

The value of key “PLESK_DATABASE_PROVIDER_NAME” is the database provider which Plesk uses for database storage.

The database providers that could be listed here are:

- Jet
- MySQL
- MSSQL

For Jet – its an Access MDB File

For editing the MDB file you can use “MDB Viewer Plus” a free application (we use the same) click here

Open the file from C:\Program Files\Parallels\Plesk\admin\db\psa.mdb (depening on your install location)

Navigate to domains tab >> Delete the line containing the domain name.

For MySQL

cd %plesk_dir%\mysql\bin && mysql.exe -u admin -P8306 psa -p

PASSWORD (enter your plesk admin password)

use psa \G

delete from domains where id=(SELECT id FROM domains where name=’example.com’);

Jmail is an asp mail component available for free from www.Daimac.Net

Download the latest version of w3Jmail from Daimac WebSite

Using the windows installer install the application with typical settings.

once installed go to C:\Program Files\Dimac\w3JMail (assuming thats where you installed it) and you will find the jmail.dll file.

For ASP.NET applications to be able to access the jmail component you will need to configure the ASP.NET User permissions to access the jmail.dll file.

Make sure you give the user read and execute permissions for the component to work for them.

Once the steps are completed you can use the following test jmail script to verify if your component is working.

<%
‘—————————————————————————-
‘
‘    Send email using the Jmail component
‘
‘—————————————————————————-

Option Explicit

dim sName, sEmail, sMessage

if Request.Form(“Action”) <> “” then
sName = Request.Form(“Name”)
sEmail = Request.Form(“Email”)
sMessage = Request.Form(“Message”)

dim oJMail
Set oJMail = Server.CreateObject(“JMail.SMTPMail”)
with oJMail
.Sender = “you@yourdomain.com”
.SenderName = “Your Name”
.From = sEmail
.Subject = “Message from website”
.Body = sMessage
.ServerAddress = “localhost:25″
.Execute
end with
Set oJMail = Nothing

response.write “Thanks for your message!”
else
%>
<form method=”post” action=”<%=Request.ServerVariables(“SCRIPT_NAME”)%>”>
<p>Name:<br /><input type=”text” name=”Name” /></p>
<p>E-mail:<br /><input type=”text” name=”Email” /></p>
<p>Message:<br /><textarea name=”Message”></textarea></p>
<p><input type=”submit” name=”Action” value=”Send” /></p>
</form>
<%
end if
%>

You can download the script here email_with_jmail

WARNING:  THIS IS ADVANCED AND COULD MESS UP YOUR SERVER.  PROCEED WITH CAUTION!

Manually Upgrading from MailEnable to SmarterMail
1)  Run Services.msc.
a) For each “MailEnable” Service, STOP it and set its Startup Type = Disabled

2)  Install SmarterMail

3)  Log into Plesk
a)  Go to Home > Server Components > Refresh; Go to Home > Server Components > Mail Server and select:
MailServer = SmarterMail (Type in password)
Antivirus = None
Spam Filter = None
Webmail = SmarterMail

4)  Update:
HKLM\Software\Plesk\PSA Config\Config\MAIL_PROVIDERW_DLL to:
C:\Program Files\Parallels\Plesk\admin\bin\smartermailproviderw.dll
or
C:\Program Files(x86)\Parallels\Plesk\admin\bin\smartermailproviderw.dll (FOR 64-BIT SYSTEMS ONLY)

5)  Update:
HKLM\Software\Plesk\PSA Config\Config\Packages\mailserver\(default) to:
smartermail

6)  From a command line (CMD), run:
cd %plesk_bin%
mchk.exe –all –fix=all

The server will now be running SmarterMail

hMailServer mail server is not included in the Parallels Plesk Panel distribution package and cannot be automatically installed.

Supported versions

For the latest supported hMailServer version, see your Parallels Plesk Panel version release notes or the “Third-Party Software Supported by Parallels Plesk Panel” section in this guide.

Note: The use of hMailServer with Windows Server 2008 is not recommended, while Windows Server 2008 is not in the list of operating systems supported by hMailServer.

Note: Parallels Plesk Panel does not support traffic calculation by the statistics.exe utility on the hMail mail server.

Manual Installation

To install hMailServer mail server manually as Parallels Plesk Panel component, follow these steps:

Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.

1. Stop the old Parallels Plesk Panel mail service.This is necessary for the hMailServer mail server that is being installed to properly register itself in the system.
2. Obtain a hMailServer mail server distribution package and install the application on the Parallels Plesk Panel server by running the package installer.Note: No additional configuration steps are required after running a manufacturer-supplied application installation package.
3. Complete the installation of hMailServer server as Parallels Plesk Panel component by following the general integration procedure. The hMailServer mail server entry appears in the Parallels Plesk Panel components list.

Manual Upgrade

To upgrade hMailServer mail component manually as Parallels Plesk Panel component, follow these steps:

Log in to the Parallels Plesk Panel server as administrator by using Remote Desktop.

1. Obtain a hMailServer mail server upgrade package and apply the upgrade to the existing installation.
2. Complete the upgrade of hMailServer mail component by following the general integration procedure. The upgraded hMailServer mail component entry appears in the Parallels Plesk Panel components list.