Can I
have both an E-mail Forward and an Auto-Responder?
No !!
How
do I setup a catch-all email account?
Every
account starts out with a default
"catch-all" account for its
domain. This email box will grab all mail heading to
ANYNAME@yourdomain.com. The login for this box is simply the same main
account login you received after signing up. Thus, if your root account
is "test@homepage.net" (login of "homepage" - first 8 letters of your
domain), there is no need to request an alias to your root account,
because all names under your domain already are filtered into this
account.
Why I
Can't send mail?
Our
SMTP servers are configured as
secure relays. This means that you
cannot simply reference "mail.yourdomain.com" as an Outgoing mailserver
unless you successfully log in via one of your pop3 accounts at
"mail.yourdomain.com' before you try to send. This is a mandatory
setting to prevent spammers from using our mailservers as havens for
unsolicited email. If you are getting a "relaying prohibited" or
"disconnected by administrator" error, it means that you haven't logged
into the pop3 server at your domain before you tried to send through
the smtp server at your domain. To log in, you need to check for mail
first.
In addition to this, you might not be able to send regardless of if you
check mail successfully. Some ISPs have it set so that their users
cannot use an outbound SMTP server to relay messages. If you are still
experiencing problems sending through your domain, and are certain that
you have logged in via pop3 to an account at your domain, you might
want to contact your local ISP to see if they do allow their users to
use outbound smtp servers.
How
can I enable webmail for an account?
All e-mail
accounts created from the "Add/Remove accounts" section of
your Mail Menu have webmail access - there is nothing you need to do to
enable it.
What
is the correct URL to login to webmail?
You can
either login via your control panel, or by visiting
http://yourdomain.com/webmail/ , notice the following / (thats
needed!). You can also use: http://yourdomain.com:2095/ - the username
would be the FULL e-mail address for that account, and the password
would be the password established for that e-mail account.
TOP of Page
What
is CGI?
CGI, Common Gateway Interface, includes
programs that run on the server
to enhance the quality and functionality of a web site. There are many
resources on-line that allow the downloading of free cgi scripts.
( For instance: http://www.worldwidemart.com/scripts )
or ( http://www.cgi-resources.com/Programs_and_Scripts/
http://www.hotscripts.com/Perl/Scripts_and_Programs )
Do you
allow CGI to run on your servers?
We do allow
running of cgi scripts on the servers, however they must
conform to our acceptable server resource usage policy. If we deem that
a script is using an excessive amount of server resources, your account
will be disabled.
Whats the
correct path to perl?
Before a
cgi script will work certain modifications must be made to
them. Certain paths must be specified in some scripts. After the "#" in
the first line of the perl script, the path to perl must be specified.
/usr/bin/perl should suffice for this path. Below is a printout of a
"whereis perl" from our system.
perl:
/usr/bin/perl
What
is the exact physical path to your root directory on the webserver?
The path to
your root directory is: /home/username/ Obviously,
substitute "username"
with the login you were assigned when
you first received your account details. Also, keep in mind that when
you configure your CGI, that your /public_html is included in your
path. For instance, if you have a guestbook.pl script in your /cgi-bin,
the exact physical path to that file is:
/home/username/public_html/cgi-bin/guestbook.pl
Why doesn't
my CGI work?
Make sure
when you upload the CGI file DO NOT upload in binary mode,
instead use ASCII mode. Uploading in binary will cause the server not
to recognize the scripts as executables. Most FTP clients will upload
.pl or .cgi files in binary mode by default so you will need to change
this. You will need to upload the scripts into your cgi-bin directory
for security reasons, however they will execute from anywhere within
your account.
The last step is to set the file permissions. This is otherwise known
as chmoding and can be done from most FTP clients.
Links
to places where you can learn CGI/Perl?
The
following is a list of sites we recommend
http://www.ora.com/info/cgi/intro.html
http://208.16.5.2/~myrkatz/journal/cgitutor/
http://www.web-consult.com/web/perl.html
http://www.extropia.com/Scripts/Book/Mis/appendix_a.html
http://lightsphere.com/dev/class/
I get
a permissions error when executing my CGI program, what should they be
set at?
CGI Scripts: chmod 755
Data Files: chmod 664
I am
having a problem with my CGI script. Do you have any advice before
contacting support?
Below
are solutions to some of the more common CGI script problems.
When I
activate my CGI program, I get back a page that says "Internal
Server Error. The server encountered an internal error or
mis-configuration and was unable to complete your request."
This is
generally caused by a problem within the script. Check your
script settings again to see that you have entered the correct server
information and have set the correct permissions for the script. If
this information is correct, you'll need to contact whoever wrote or is
distributing the script for further assistance.
I am
being told "File Not Found," or "No Such File or Directory."
Upload
your Perl or CGI scripts in ASCII mode, not binary mode.
When I
test my Perl script in local mode (by Telnet), I have the
following error: "Literal @domain now requires a back slash at
myscript.pl line 3, within string. Execution of myscript.pl aborted due
to compilation errors."
This is
caused by a misinterpretation by Perl. You see, the "@" sign
has a special meaning in Perl; it identifies an array (a table of
elements). Since it cannot find the array named domain, it generates an
error. You should place a back slash (\) before the "@" symbol to tell
Perl to see it as a regular symbol, as in an email address.
I am
getting the message "POST not implemented."
You are
probably using the wrong reference for cgiemail. Use the
reference /cgi-bin/cgiemail/mail.txt. Another possibility is that you
are pointing to a cgi-bin script that you have not put in your cgi-bin
directory. In general, this message really means that the web server is
not recognizing the cgi-bin script you are calling as a program. It
thinks it is a regular text file.
TOP of Page