Frequently Asked Questions

Our new spam system is integrated with 3rd party global spam fighters. (Mail Filters). This system does learn, but you may wish to report any spam that gets through to your mailbox by emailing it directly to spam@hyve.com. From there it will be scanned and included in the worldwide spam database for future filtering.

If you receive any emails marked as spam that are in fact real emails, you can report those in the same way to falsespam@hyve.com.

Please be sure to attach the email, rather than simply sending it, as this will include the relevant header information as well.

This is the new spam rule. If you are using Outlook we recommend that you set up a rule to automatically delete or move all emails prefixed with **spam** in the subject.

This can be done within Outlook by clicking on Tools > Rules and Alerts. Click on "New Rule" and follow the wizard.

Upload your Access database file (.mdb) to the “/Private” folder which is above your web root. You will then either need to use OLEDB or a System DSN to connect your website to your DB. You may also need to write to Hyve support and ask us to set the appropriate permissions on the private folder. Please test this first and contact us if it is still not working.

OLEDB
OLEDB does not require any server-side configurations, so you would simply write your code to reference the DB with the following connection string:

"Provider=Microsoft.Jet.OLEDB.4.0;Data 
Source=E:\inetpub\vhosts\private\mydb.mdb;User Id=;Password=;"

System DSN
Using a system DNS a slower method of communicating with the server. It is also an older system which requires a server-side configuration. This is how to do it via Plesk:

• Click "ODBC Settings" within domain manager
• Click "Add New ODBC DSN"
• Add the name you wish to use to reference the DB from your code
• Select "Microsoft Access Driver (*.mdb)"
• Follow the wizard and save the configuration

Next, you will need to use the following DSN connection string:

"DSN=myDsn;Uid=myUsername;Pwd=;"

The only reason for using a DSN would be because your site is already written using this older connection technique.

Plesk Resellers
Plesk resellers should follow these steps to enable Custom Error docs

• Log-in to Plesk
• Click the relevant domain
• Click "Setup" under the "Hosting" area
• Check the box next to "Custom Error Documents"
• Click "OK"
• Click "File Manager" under the "Hosting" area
• Click "error_docs"
• Replace the relevant file with your own custom document*.

Plesk Shared Hosting Customers
Please raise a support ticket to request that "Custom Error Documents" are enabled for your domain. You can then upload your own custom error documents to the "error_docs" folder on your FTP root.

Use this classic ASP code to send email on Plesk for Windows

<%
Dim objMail
'Create the mail object
Set objMail = Server.CreateObject("CDO.Message")

'Set key properties
'Name or IP of remote SMTP server
objMail.Configuration.Fields.Item
("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "localhost"

'Server port
objMail.Configuration.Fields.Item
("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
objMail.Configuration.Fields.Item
("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
objMail.Configuration.Fields.Update

'send Email
objMail.From = "from@from.com"
objMail.To = "to@to.com"
objMail.Subject = "subject"
objMail.TextBody = "body"

'Send the email
objMail.Send
%>