|
|
|
|
How To Set Up Your Mail |
| |
|
| |
Email accounts are created from your siteadmin which can be
accessed at http://www.your-actual-domain.com/siteadmin/
Back To Top
|
|
|
|
|
Anti-Relay for SMTP
[Sending Mail] |
| |
|
| |
In order for you to use the SMTP services of your account, you
will
have to check your email at least once prior to attempting to send
email.
(If you use a dialup provider, it is likely that you are assigned a
different IP address each time you go online. If so, then you will
need to check your email at least once each time you connect to your
dialup provider.)
Once you've checked your email, you may then use your domain to
send email to other locations.
After getting disconnected and then reconnected to your dial-up
provider, your operating system may remember the IP address of your
previous log-on. If you have trouble sending mail after a dial-up
disconnect, you may have to reboot your computer to clear the
settings.
Alternately, a good long term solution would be to type in the
SMTP settings of your local ISP in the "outgoing mail
server" field of your email software.
Also, you can read and send and receive email from your online
mail reader at:
http://www.your-domain.com/checkmail/
or https://www.secure-access.net/cgi-bin/secureemail.cgi
Back To Top
|
|
|
|
|
Spam Protection
Settings |
| |
|
| |
The SPAM ASSASSIN is a software program that reviews email that is
being sent to you. This program is designed to either delete
the SPAM before it
reaches you, or to change the subject of suspect emails to **SPAM**
and converts any html messages to plain text, thereby disabling any
harmful javascript or tracking images the message may
contain.
The way it determines whether a message is SPAM is based on a
point system; a database of words and attributes has been created
(and is constantly being updated). When a message is sent to
you, the SPAM ASSASSIN software reviews the message and gives the
message score
(a point for each suspect word or attribute the message may
have). If the score is above 6, the message is marked as SPAM.
The SPAM ASSASSIN software is also CUSTOMIZABLE. The site
administrator may access the SPAM ASSASSIN settings for all users
from the /siteadmin. To the right of each user, you will
see the SPAM ASSASSIN icon, an envelope with an X through it. By
clicking on this, you will see the score that must be achieved for a
message to be considered SPAM (default is 6, the lower the number,
the more messages that will be marked as SPAM), a white list
(domains and email addresses you wish to always receive messages
from without being tested), a black list (list of known email
addresses and domains you wish to have all messages from deleted or
marked as SPAM), an option to 'auto-delete' SPAM, an option to
disable the SPAM ASSASSIN and a few other choices that are explained
on the page. If you are not the site administrator, you may
access the specific settings for your own email account by going to www.your-actual-domain.com/personal/,
entering your email username and password and then clicking on the
'Spam-filter' button. You will gain access to the same
settings as those listed above.
You may disable the SPAM ASSASSIN, but we believe, based on a group
of domains already using the program (including our own) and a
number
of requests we have received for such a program, that you will be
pleased with the SPAM elimination solution.
One good way to handle the email marked as spam is to set up a
mail rule within your email software to automatically move all
messages with **SPAM** in the title to a separate folder. That way
you never have to see the messages but you can look back through
them if necessary.
Back To Top
|
|
|
|
|
CGI Information |
| |
|
| |
You can install many CGI scripts in your local cgi-bin. Keep in
mind that cgi scripting is a programming tool. Problems resolving
from these and other cgi scripts are not covered under technical
support.
A few common parameters that you may need in installing your cgi
script are:
First line of perl scripts should be:
#!/usr/bin/perl
Your base directory:
/home/sites/www.your-actual-domain.com/web/
The location of our sendmail program is:
/usr/sbin/sendmail
The location of our date program is:
/bin/date
Tips for CGI Installations
1. Read the documentation for the script you are trying to install!
2. If you don't find any documentation WITH the script, check inside
the script ITSELF, some scripts have the instructions written in
with the coding.
3. If you can't find any help, contact the author of the script
(most scripts have the author's information in the header of the
script)
4. Make sure you have properly set any permissions for the file
(most scripts require CHMOD 755, or read-execute permission to
properly execute on the server)
5. Make sure you have properly set all paths and parameters!
6. Make sure (if it's a Perl script) you transferred it as an ASCII
file (Perl scripts are text files [ASCII] not binary files like some
compiled CGI scripts!)
If you need help installing or writing custom cgi scripts you may
wish to contact one of the following group
of programmers who will get you up and running at a minimum
cost. They will give you an estimate for the job you wish to have
written or fixed. The scripts below are fairly easy to install and
come with installation documents.
Back To Top
|
|
|
|
|
CGI Script URL |
| |
|
| |
To access cgi scripts that you install in your local cgi-bin, you
would normally type the following:
http://your-actual-domain.com/cgi-bin/
For example if your domain was sportscar.com, then your cgi
address would be:
http://sportscar.com/cgi-bin/
Back To Top
|
|
|
|
|
Counters |
| |
|
| |
Your site is already configured for the placement of counters. A
counter may be added to your page by including the following line in
your html document. Make sure to change "anyname.dat" to
the datfile name you'd like to use for your site (It just needs to
end in .dat).
<img
src="/cgi-bin/Count.cgi?ft=5|dd=C|frgb=255;255;255;&df=anyname.dat">
For additional counters simply add your login_name1, 2, 3, etc...
You can modify the look of your counter by changing the following
values:
ft=size of frame around counter dd=A,B,C,D,E - you can try
different ones frgb=color of frame
For additional counter styles click here.
<img
src="/cgi-bin/Count.cgi?ft=1|dd=A|frgb=255;255;255;&df=anyname.dat">
Back To Top
|
|
|
|
|
How To Set Up Simple
Forms |
| |
|
| |
If you would like to create a form that uses our built in
fmail.pl form mailer, the easiest way to create a form page is to
start with one of the form
pages on our site Edit it for your needs, rename it, then
publish it to your site. For syntax information for use with the
fmail.pl script please click here. The
recipient address needs to se something@your-actual-domain.com
If you use a software package like Front Page then you would just
use the built in form maker and follow the instructions within FP.
For information on how to use the fmail.pl script with Front
Page, click here.
Back To Top
|
|
|
|
|
How To Set Up Secure
Forms |
| |
|
| |
Steps to setting up secure forms:
 |
Alternative 1 - secure-access.net server
1. Request a secure directory on the secure-access.net server.
Click here to request secure directory. We will set up the
directory for you and email you the FTP settings for it.
2. Set up the form on your site using the fmail.pl
script. If you are using Front Page you will have to
choose the custom cgi script handler in the form settings, or
paste in the html. For information on how to use the fmail.pl
script with Front Page, click
here.
3. Set the form to email the secure information to the secure
email address on the secure-access.net server. You will be
able to read that email securely using the secure mail reader
at https://www.secure-access.net
/neomail/ |
 |
Alternative 2
For a one time setup cost of $200 (all inclusive) and an
additional $20 per month we can purchase and install your own
secure certificate from Thawte.
We will then set up a separate site like
https://secure.your-actual-domain.com where you can put your forms,
scripts etc.. To order your secure certificate and site click
here. |
Back To Top
|
|
|
|
|
How To Password Protect
Directories |
| |
|
| |
To password protect a directory:
There should be a password protection utility on your site at the
url below (replace your-actual-domain.com with your actual domain.
http://www.your-actual-domain.com/cgi-bin/adminpro/setpass.html
The username and password to access the setpass.html page will be
the same as your site admin username and password.
If you do not have the setpass.html installed on your site,
please email us and we
will upgrade your site to our newest servers with the setpass.html
installed in them.
For password protection scripts that you also may wish to use, go
to: CGI
Resources
Back To Top
|
|
|
|
|
How to check the cause
of web site access problems |
| |
|
| |
If you are having intermittent problems accessing your site,
please read the following:
1. The following web site tracks the performance of the major
backbone providers. Internetweather.com updates their page at 5
minute intervals. http://www.internetweather.com
2. To independently monitor your site, you might use
http://netmechanic.com/monitor.htm
3. To help trace problems with Internet traffic, try the
following:
a. Connect to the internet
b.) If you are running Windows, go to a DOS prompt. To get to the
dos prompt you can normally click the "Start" button, then
"Programs" then select "MS-DOS prompt".
c.) At the DOS command line, type 'TRACERT your-actual-domain.com' (minus
the quotes, replace 'your-actual-domain.com' with your domain name)
d.) Your screen may output information that looks like:
Tracing route to example.com [1.1.1.1] over a maximum of 30 hops:
1 123 ms - 123 ms -123 ms - 38.1.1.1
2 147 ms - 145 ms -182 ms - nc.pop.psi.net [38.147.37.1]
3 120 ms - 134 ms -134 ms - 207.124.104.54
4 160 ms 242 ms 158 ms sl-gw5-sj-1-1-0-T3.sprintlink.net
[144.228.44.1
5 180 ms 262 ms 228 ms sl-gw5-1-0-T3.sprintlink.net [144.228.44.13]
6 198 ms 252 ms 288 ms sl10-sj-155M.sprintlink.net [144.232.3.6]
7 327 ms 227 ms 301 ms sl-bb10-rly-6-0.sprintlink.net [144.232.9.13]
8 343 ms 335 ms 298 ms sl-gw1-rly-0-0-0.sprintlink.net
[144.232.0.58]
9 394 ms 336 ms 339 ms sl-smat-4-0-0.sprintlink.net [144.232.184.26]
10 313 ms 282 ms 282 ms fvl1-S4-0.sprintsvc.net [205.244.203.62]
11 300 ms 370 ms 294 ms fvl1-t-s4-0.sprintsvc.net [208.27.127.10]
12 297 ms 311 ms 343 ms example.com [208.234.1.129]
This is called a traceroute, which traces, hop for hop, all the
jumps you take from your internet connection to the destination. The
first few hops are usually through your service provider's network.
The hops from there are usually through the backbone/upstream
provider your service provider uses to route internet traffic. The
last few hops will be with our upstream/backbone provider through
our network and to your server. Each hop shows timing information
(designated by 3 sets of 'ms' ratings). Timing below 300 ms is good
timing. Anything above that up to 1000 ms indicates some delays
which will ultimately affect your overall connection performance.
Any 'ms' timings represented by an asterisk (*) indicate a time-out
(bad connection). Whatever hops shows asterisks or timings above 500
will, more than likely, be where your connection is having problems.
Check with the appropriate people regarding any performance
problems. If the problems occur, in the first few hops, it is your
service provider. If the problems occur within the midway hops, it
is your service provider's upstream/backbone connection. If the
problem occurs within the last few hops to your site, then it is a
problem on our end. Please note, if the problem occurs in the first
few hops, it will affect most of the hops thereafter.
An alternate location to do a trace route from is: http://www.geektools.com/
Back To Top
|
|
|
|
|
Edit Pages Using
Dreamweaver |
| |
|
| |
General settings for Dream Weaver
Open Dream Weaver and click on the 'Site' menu.

Choose 'New Site'
This will bring up the 'Site Definition' window, enter your site
name and a choose a folder to store the local copy of your site in.
Enter your url below in the HTTP Address: field.

This is the important screen for your FTP connection, fill in as
shown except change 'your-actual-domain.com' to your domain name; change
'username' to the FTP username in the web site settings email and
enter your password in the password field.

Back To Top
|
|
|
|
|
How to Edit Pages On
Your Site Using Netscape Composer |
| |
|
| |
1. Browse over to it with Netscape Navigator
2. Click "File" then submenu item "Edit Page".
This will open the page up in Netscape Composer.
3. Make all the changes you want to make; it basically acts like a
word processor.
4. Click "File" then submenu item "Save". If
it's your main page, make sure the file name you save it as is
"index.html" without the quotes. Otherwise the correct
page name will be the default save file name.
5. Click on the publish button and use the settings below. If you
add any images and want them uploaded, make sure they are selected
in the "Other Files To Include" area of the publish
window.
To edit the page title, description and keywords meta tags: While
you are editing a page, click on the "Format" menu item
then slide down to "Page colors and properties" and type
in the info. Use the important keywords in the title, description,
and at the beginning of the keywords.
FTP access settings using Netscape Composer:
Location to publish to would be: ftp://yourname.com/
User ID / username: use the ftp settings from your "web site
settings" email
Password: use the ftp settings from your "web site
settings" email
For more Netscape help resources click
here.
Back To Top
|
| |
|
|
|
How to FTP Pages /
Images Using WSFTP or the Internet Explorer ftp function |
| |
|
| |
To upload images or pages manually using WSFTP:
1. Download and install a copy of WSFTP from www.wsftp.com
2. Connect to your to the Internet as you normally would, then start
up the WSFTP software and add a "NEW" ftp site using the
settings below:
FTP access settings using WSFTP (use your actual domain name in
place of the your-actual-domain.com below)
Profile Name: your-actual-domain.com
Host Name / Address: your-actual-domain.com or raqXX.dnssys.com (where the
XX is raq number)
Host Type: Automatic Detect
User ID: use the ftp settings from your "web site
settings" email
Password: use the ftp settings from your "web site
settings" email
Save Password Box: Put a check in this box
Anonymous Box: Leave this box blank
Account: leave this box blank
3. Then, within WSFTP (Classic Interface)
a. Browse to the directory where your image or html file is.
b. On the window that shows the server files, get to the directory
where you want the files to go.
c. Double click on the file you want to move from your computer to
the server or vice versa.
4. If you ftp the file to the main directory on the server that
WSFTP will open up in, then the url to view or connect to that image
would be: http://your-actual-domain.com/theimagefilename.jpg
If you ftp to a subdirectory within your site, then the url to
connect to that image would be: http://your-actual-domain.com/the-subdirectory-name/the-image-or-page-name.jpg
FTP using your Internet Explorer browser
You can also FTP to your site and upload, download, and delete
files using the FTP function within Internet Explorer. The steps to
FTP using Internet Explorer would be:
1. Type ftp://www.your-actual-domain.com
into the IE address bar (where the web site url is normally shown).
2. When prompted for your username and password, type in the
username and password that we sent your in your web site settings
email.
3. Now you will be able to paste files or drag files into the IE
FTP window that you have opened. You will also be able to delete and
rename files.
Back To Top
|
|
|
|
|
How do I Register My
Site with the Search Engines? |
| |
|
| |
For Information on registering your site with the search engines click
here.
Back To Top
|
|
|
|
|
What do the error codes
mean? |
| |
|
| |
100 Continue
101 Switching Protocols
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
303 See Other
304 Not Modified
(304 means the file was loaded from the browser cache instead of
being resent by the server)
305 Use Proxy
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found 405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Time-Out
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URL Too Large
415 Unsupported Media Type
500 Server Error
501 Not Implemented
502 Bad Gateway
503 Out of Resources
504 Gateway Time-Out
505 HTTP Version not supported
Back To Top
|
|
|
|
|
When I publish my
pages, the changes don't seem to show up? |
| |
|
| |
When you FTP files to your site or publish Using FrontPage, the
changes are made immediately on the server.
However you might not see the changes for 2 reasons:
1. Your browser is showing you an old page that it has cached on
your local hard drive. To force the browser to reload the current
page form the server, hold down the <SHIFT> key while you
click on the Reload button (Netscape) or Refresh button (Internet
Explorer). Or, if you are using the built in AOL browser, hold down
the <CTRL> key while you click on the Refresh button (Normally
just to the left of the address bar and Home Icon).
2. Another possible reason you are not seeing your changes: If
you are working on your home page and your home page was named index.html
but you now have it named index.htm of Default.htm,
you might be changing the index.htm page but still seeing the
index.html page. index.html has a higher preference
than index.htm as a home page. To resolve this, just rename
your home page to index.html
Back To Top
|
|
|
|
|
How can I stop all this
spam mail? |
| |
|
| |
Spammers get your email address from a few sources, mainly
newsgroup postings, lists sold to them by FFA (Free For All Links)
sites, and by spidering web pages where you list your email address.
To limit spam you can:
1. Use a separate email address for posting to newsgroups.
2. Use a separate email address for submitting your web site to
small search engines and FFA sites.
3. You can't really stop the spammers software from spidering your
pages to capture your email addresses. But, in your email software
(Outlook Express, Eudora, Netscape Messenger) you can set up email
filters or "Inbox Assistant" type filters to delete emails
that contain certain words in the subject, or body of the email.
4. Sign up for a spam filtering account from someone like: http://spamcop.net/
You can have the email from your domain forwarded to your SpamCop
account, filtered, and then forwarded to your secret pop account.
You might lose legitimate emails using spamcop.net.
5. Buy and download spam killer software from http://spamkiller.com
(very good).
Also, many times spammers will send out email without a complete
"From" address (not containing an @). In that case our
mail server will append the @precisionweb.net or
@precisionwebhost.net etc. to the "From" address. This
makes it look like we, your hosting provider, are sending the spam.
We are definitely not sending it nor have we sold your email
address.
Other useful links:
http://www.cauce.org -- the
Coalition Against Unsolicited Commercial Email (CAUCE), includes
information on Spam and how to prevent it.
http://www.mail-abuse.org
-- Mail Abuse Prevention System, an organization whose mission is to
defend the Internet against Spammers. Take a look at their Realtime
Blackhole List information
Back To Top
|
|
|
|
|
Where can I learn more
about Webalizer Statistics? |
| |
|
| |
 |
Main Headings |
Hits represent the total number of requests made to the
server during the given time period (month, day, hour etc..).
Files represent the total number of hits (requests) that
actually resulted in something being sent back to the user. Not all
hits will send data, such as 404-Not Found requests and requests for
pages that are already in the browsers cache.
Tip: By looking at the difference between hits and files,
you can get a rough indication of repeat visitors, as the greater
the difference between the two, the more people are requesting pages
they already have cached (have viewed already).
Sites is the number of unique IP addresses/hostnames that
made requests to the server. Care should be taken when using this
metric for anything other than that. Many users can appear to come
from a single site, and they can also appear to come from many ip
addresses so it should be used simply as a rough gauge as to the
number of visitors to your server.
Visits occur when some remote site makes a request for a
page on your server for the first time. As long as the same site
keeps making requests within a given timeout period, they will all
be considered part of the same Visit. If the site makes a request to
your server, and the length of time since the last request is
greater than the specified timeout period (default is 30 minutes), a
new Visit is started and counted, and the sequence repeats. Since
only pages will trigger a visit, remotes sites that link to graphic
and other non- page URLs will not be counted in the visit totals,
reducing the number of false visits.
Pages are those URLs that would be considered the actual
page being requested, and not all of the individual items that make
it up (such as graphics and audio clips). Some people call this
metric page views or page impressions, and defaults to any URL that
has an extension of .htm, .html or .cgi.
A KByte (KB) is 1024 bytes (1 Kilobyte). Used to show the
amount of data that was transferred between the server and the
remote machine, based on the data found in the server log.
 |
Common Definitions |
A Site is a remote machine that makes requests to your
server, and is based on the remote machines IP Address/Hostname.
URL - Uniform Resource Locator. All requests made to a web
server need to request something. A URL is that something, and
represents an object somewhere on your server, that is accessible to
the remote user, or results in an error (ie: 404 - Not found). URLs
can be of any type (HTML, Audio, Graphics, etc...).
Referrers are those URLs that lead a user to your site or
caused the browser to request something from your server. The vast
majority of requests are made from your own URLs, since most HTML
pages contain links to other objects such as graphics files. If one
of your HTML pages contains links to 10 graphic images, then each
request for the HTML page will produce 10 more hits with the
referrer specified as the URL of your own HTML page.
Search Strings are obtained from examining the referrer
string and looking for known patterns from various search engines.
The search engines and the patterns to look for can be specified by
the user within a configuration file. The default will catch most of
the major ones.
Note: Only available if that information is contained in
the server logs.
User Agents are a fancy name for browsers. Netscape,
Opera, Konqueror, etc.. are all User Agents, and each reports
itself in a unique way to your server. Keep in mind however, that
many browsers allow the user to change it's reported name, so you
might see some obvious fake names in the listing.
Note: Only available if that information is contained in
the server logs.
Entry/Exit pages are those pages that were the first
requested in a visit (Entry), and the last requested (Exit). These
pages are calculated using the Visits logic above. When a visit is
first triggered, the requested page is counted as an Entry page, and
whatever the last requested URL was, is counted as an Exit page.
Countries are determined based on the top level domain of
the requesting site. This is somewhat questionable however, as there
is no longer strong enforcement of domains as there was in the past.
A .COM domain may reside in the US, or somewhere else. An .IL domain
may actually be in Israel, however it may also be located in the US
or elsewhere. The most common domains seen are .COM (US Commercial),
.NET (Network), .ORG (Non-profit Organization) and .EDU
(Educational). A large percentage may also be shown as
Unresolved/Unknown, as a fairly large percentage of dialup and other
customer access points do not resolve to a name and are left as an
IP address.
Response Codes are defined as part of the HTTP/1.1
protocol (RFC 2068; See Chapter 10). These codes are generated by
the web server and indicate the completion status of each request
made to it.
Back To Top
|
• To place an order now call: 1-800-446-7161 •
For pre-sales questions call: 1-800-446-7161
• Precision Web Hosting •
|