|
@Mail Server Frequently Asked Questions
1. Background
1.1 What is @Mail?
1.2 Why was @Mail created?
1.3 Why the name "@Mail"?
1.4 How does @Mail compare to
other servers?
1.5 How thoroughly tested is @Mail?
1.6 What are the future plans
for @Mail?
1.7 Whom do I contact for support?
1.8 Is there any more information
on @Mail?
1.9 Where can I purchase @Mail?
1.10 Who is develops @Mail?
1.11 Can I get a demo version
of @Mail?
2. General Technical Questions
2.1 What Hardware does @Mail require?
2.2 How much harddisk space do
I require?
2.3 What to do if I have problems
getting @Mail Setup?
2.4 How compatible is @Mail with
my existing webserver setup?
2.5 Is @Mail compatible with sendmail
8.9.3? Are there any compatibility issues?
2.6 Is @Mail compatible with Apache
web server? What versions is it tested with?
2.7 What does @Mail use to read
emails?
2.8 Does the software require
cron or crontab?
2.9 How do I submit a patch to
the @Mail Group?
2.10 May I include the @Mail
software on a CD or other package I'm distributing?
2.11 How do I get the most out
of my @Mail server?
3. Installing @Mail
3.1 What do I need for @Mail to
run?
3.1.1What
modules do I need for @Mail to run? And where do I get them?
3.2 Can you remotely install the
software for me?
3.3 Does @Mail run under windows
platforms?
3.4 What MTA does @Mail support?
3.5 How to I configure sendmail?
3.6 How to I configure my WebServer?
4. @Mail Feature Questions
4.1 How do I setup Email to SMS
gateways under @Mail?
4.2 Advantages using an SQL database
to store user emails
4.3 Which languages are supported?
Can
it be modified to support another language?
4.4 Can we use our own branding
and remove '@Mail' in the script and pages?
4.5How do I modify the user-interface
of @Mail to suit the design of my website?
4.6 Can I disable the frames
4.7 What does the full site license
include?
4.8 Do we have to buy any plug-ins?
4.9 Can we send Email messages
to mobile phone?
4.10 Does @Mail work with MTA's
other then sendmail?
4.11 Does @Mail run under Virtual
Servers?
4.12 Does @Mail support large
user bases?
5. Configuration Questions
5.1 How do I configure @Mail to
host multiple domain-names for WebEmail?
5.2 What is the error 'xxx not
available for sendmail programs'?
5.3 Can I use an external SMTP
server to send Email?
5.4 What browser should I use
with @Mail?
5.5 Why does @Mail send a cookie
on every response?
5.6 Does @Mail support SSL?
1. Background
1.1 What is @Mail?
@Mail is the total WebEmail solution. Server driven, it allows users
to read and compose Emails via a webbrowser or access Email accounts
via POP3 or IMAP. Users have the ability to sign-up for a new account
and have it activated instantly, on the administers selection of domains.
Users can also access Email via the WAP protocol on Mobile phones or
PDA's or have basis account information sent via SMS.
Written in 1998, the @Mail software has been completely rewritten
by a growing international technical team, and now supports a new release
based on client feedback every three months.
1.2 Why was @Mail created?
70% of all connections to the Internet are primarily to check eMail.
Web or POP3/IMAP Email is an important aspect for ISP's, businesses,
Educational institutions or website as a way to attract users or manage
internal accounts. In 1998 we saw a lack of quality and customizable
web Email programs, hence the creation of @Mail. Since then we have
endeavored to offer a open source program that is based on client feedback
and latest technologies.
1.3 Why the name "@Mail"?
The name was given by the team who developed the software; AT MAIL
describes the nature of the software, and hey, it gets rated first in
alphabetic search engines ;-)
1.4 How does @Mail compare to other servers?
@Mail has been shown to be substantially faster than many other WebEmail
servers. @Mail is currently supporting sites that generate millions
of hits per week, and they have experienced no performance difficulties.
Also, @Mail is full source code, allowing clients to modify features
as required.
1.5 How thoroughly tested is @Mail?
@Mail is used by many large ISP's, Governments and Corporations worldwide.
Millions of people have active Email accounts which are hosted by the
@Mail system, each day the userbase of the software grows. The software
has been tested thoroughly by both developers and users. The @Mail Group
works closely with users of the software, we are always busy implementing
new features and functionality to the software on our clients requests.
When bugs do show up, we release patches and new versions as soon as
they are available.
1.6 What are the future plans for @Mail?
To continue to be a full-source code product to keep up with advances
in HTML/DHTML and web developments in general, to collect suggestions
for fixes/improvements from its users, to respond to needs of large
volume providers as well as occasional users. To grow the @Mail user
base to >10 million users who has a registered account with the system
To integrate WAP support in the system, allowing users to send and receive
emails using their Mobile Phone
1.7 Who do I contact for support?
Clients of @Mail receive technical support for the software by the
original developers - The team is available via Email at info@CalaCode.com,
and can be contacted via telephone or real-time chat on request. Clients
who have questions regarding installation and configuration should first
consult the online documentation available at
http://atmail.nl/docs/ before consulting the @Mail team via Email
- Due to the popularity and large userbase of our software, we are constantly
swamped with requests via Email, however try to respond within 12-24
hours.
1.8 Where is there any more information available on @Mail?
1.9 Where can I purchase @Mail?
You can find out how to download the source for @Mail at the Purchase
Page.
1.10 Who develops @Mail?
CalaCode are the providers of the
@Mail software. The company started off as 'CGIsupport' , with a head
office in Sydney Australia. As the company grew, management changed
hands and is now an international organization.
1.11 Can I have a demo version of @Mail?
Presently we can offer you the fully functional demo on our website,
at www.webbasedemail.com
Here you can test the @Mail program to see its capabilities, and find
out how @Mail would benefit your business. If you would like to see
how other companies have used @Mail you could visit our client site.
2. General Technical Questions
2.1 Which Hardware do I require: CPU, harddisk, memory
etc.
@Mail will run under any operation system that supports Perl 5 and
that is configured with a webserver. We recommend that you use a Pentium
II 500mhz+ with 64 or more MB ram, and 6gig + harddrive to store emails.
If the option is available, we recommend you use a Linux server, and
Mod-Perl, because it is more reliable for the system and has the power
to run @Mail at its full capacity.
2.2 How much harddrive space do I need?
That all depends on how much mail is stored by your clients. Because
you have the power to adapt @Mail to your needs, you can restrict your
customers in how many emails they keep. Therefore the space needed is
flexible to suit your hard-drives capacity! The formula is as follows:
number of users x user quota = hard disk space required for @Mail
2.3 What can I do in case of problems
If you are having trouble with your @Mail server software, you should
take the following steps:
Check your webservers errorlog.
@Mail tries to be helpful when it encounters a problem. In many
cases, it will provide some details by writing one or messages to
the webservers error log. Sometimes this is enough for you to diagnose
and & fix the problem yourself (such as file permissions or the
like). The default location of the error log is /usr/local/apache/logs/error_log,
but see the ErrorLog directive in your webservers config
files for the location on your server, or check out the Admin.
Check the FAQ.
The latest version of the @Mail Frequently-Asked Questions list
can always be found at the main @Mail web site.
Check the @Mail bug database
Most problems that get reported to The @Mail Group are recorded
in the bug
database. Please check the existing reports, open and closed,
before adding one. Users of the software are encouraged to report
any problems they experience using the software by submitting a report
via the bug database.
Email the developers of the software
A lot of common problems are addressed in the
@Mail Online Documentation and FAQ
- The developers are available via Email at info@calacode.com
but we ask you to first consult the online documentation before contacting
us as your question may already be answered.
2.4 How compatible is @Mail with my existing webserver setup?
@Mail attempts to offer all the features and configuration options
under any HTTP WebServer. The software was developed under the Apache
WebServer and is our choice HTTP-Server for use with the @Mail system.
The @Mail software can be used under any webserver that supports CGI
script execution.
2.5 Is @Mail compatible with sendmail 8+? Are there any known
compatibility issues?
Any version of Sendmail will comply, however we recommend using the
more recent versions for @Mail to run at its full potential. @Mail supports
other Mail Transport Agents, although we prefer the use of sendmail
to send/receive Email
2.6 Is @Mail fully compatible with Apache web server? What
versions has it been tested with?
@Mail is completely compatible and tested to run with Apache; infact we
recommend using this over other web servers. Although @Mail will work
on any version, we again recommend using the newer versions for maximum
reliability.
2.7 What does @Mail use to read emails?
@Mail works using an SMTP agent to receive emails for your domainname.
This allows @Mail to internally receive user emails, which can be stored
in an SQL database server or flat text file for later retrieval. @Mail
also has the ability to read external POP3 accounts on the Internet.
2.8 Does the software require Cron or Crontab?
@Mail does not require cron or crontab to run, although you can choose
to run a cron job each day to update the portal-information on the users
startpage (the news/informational services).
2.9 How do I submit a patch to the @Mail Group?
The @Mail Group encourages patches from outside developers. There are
2 main "types" of patches: small bugfixes and general improvements.
Bugfixes should be submitting using the @Mail bug report page. Improvements,
modifications, and additions should follow the instructions below.
To submit your patch, send Email to info@calacode.com
with a Subject: line that starts with [PATCH]
and includes a general description of the patch. In the body of the
message, the patch should be clearly described and then included at
the end of the message. If the patch-file is long, you can note a URL
to the file instead of the file itself. Use of MIME enclosures/attachments
should be avoided.
2.10 May I include the @Mail software on a CD or other
package I'm distributing?
No, Not without written permission from CalaCode. The @Mail software is
copyright Calacode.com and may not be repackaged and sold in any other
form. We do offer an attractive reseller agreement, please contact us
for more information.
2.11 How do I get the most out of my @Mail Web server?
@Mail will run under any Operating System that supports Perl5 and is configured
with a webserver. This includes popular OS's like Linux, Windows 2000/XP
and all flavors of Unix. We recommend the WebEmail system to be setup
under a Unix Operating system due to the performance and stability over
Windows servers. The webserver which runs the @Mail system should be optimized
just for the single purpose of hosting the WebEmail system, the webservers
configuration files should be clean and compact without any unnecessary
modules and configuration values defined. For sites which host a great
number of user accounts the system should be spread out over multiple
machines - The @Mail system can be setup so all user-emails are stored
on a central server which hosts the SQL database server, all incoming
user emails and user configurations details are stored in the database
server while incoming http requests by users are handled by separate machines
on the network.
3. Installing @Mail
3.1 What do I need for @Mail to run?
@Mail is written 100% in pure Perl. This allows you to run the application
on any system which supports Perl5. @Mail has been successfully installed
under Linux, FreeBSD, Sun Solaris, Irix, LinuxPPC for Macintosh, Windows
2000/XP systems.
Although for the correct operation of @Mail the system depends on a
HTTP-WebServer and a SMTP mail-delivery agent. We recommend running
the @Mail service under a Unix machine with the Apache webserver and
for the Email delivery we suggest you use the popular sendmail daemon
available at www.sendmail.org
3.1.1 What modules do I need for @Mail to run? And
where do I get them?
@Mail requires 3rd party-modules for SQL database access, URL parsing,
POP3 fetching & Misc modules for Date/Time manipulation. The base
modules for @Mail to operate are included in the atmail/libs directory.
If your system has a correctly installed version of Perl5 there will
be no need to configure additional modules for your system.
@Mail requires the following modules for correct operation:
| Module Name |
Use + Description |
| Net::POP3 |
Used to interface with POP3 servers to access Email remotely |
| Net::SMTP |
For SMTP server communications ; used to send Email to remote
SMTP servers |
| Mail::Internet |
A module to decode Email Headers + Body's |
| Time::CTime |
For reading Email dates |
| Time::ParseDate |
Used to convert dates into different formats |
| CGI |
Common module for CGI programming |
| DBI |
A module for SQL database communication ; this module acts as
a common interface for all SQL database server types. You need to
install the relevant DBD::databasename module, where databasename
is the type of SQL server installed on the machine. mySQL, Oracle,
Sybase, and ODBC are supported just to name a few |
| FinBin |
Used to find the CWD of the directory |
| LWP |
A module to communicating with HTTP servers |
| URI::URI |
Used to parse URI's and decode them into the appropriate strings |
If @Mail reports an error that 'XXX module could not be loaded, @INC
path is ...' you need to visit the CPAN
website to download the modules missing on your system. Once you
have download the required module from CPAN,
simply uncompress the archive and:
Perl Makefile.PL; make ; make test ; make install
This will make the module for your system and install it into the
library path for Perl5
3.2 Can you remotely install the software for me?
We are happy to install @Mail remotely for you when you purchase the
latest @Mail Pro and above. Please visit https://netbasedsoftware.com/install/
for a secure place to send server details.
The @Mail team can remotely telnet to your Unix server and configure
the software via a terminal. For Windows users we prefer to use VNCviewer
for remote installations.
3.3 Does @Mail run under Windows Platforms?
Yes, @Mail has included support for Windows Platforms. The @Mail system
runs under Windows 2000 / XP . For the operation, @Mail requires a HTTP
webserver and If you wish to use @Mail to sign-up new users using an
email address at your domain, the software requires a Mail Transport
Agent (MTA) to deliver the Email
We recommend the following setup under Windows Platforms
Use Apache as your HTTP Web-Server (IIS is supported, but we recommend
Apache) Sendmail acting as the SMTP Daemon Use the windows-port of MySQL
as the mail-database backend Install the latest version of Perl5
3.4 What MTA does @Mail support?
@Mail supports any Mail Transport Agent which can pipe incoming
emails for the domainname to an external binary. We have tested and
configured @Mail on the following MTA's
Sendmail (Unix, Windows) Exim
(Unix, Windows) SMTPd (Unix) Postfix (Unix)
@Mail depends on an external SMTP daemon to deliver user-emails
to the system; standalone @Mail can read any external POP3/Imapd account
on the Internet without the need of an MTA to be configured on the
server that @Mail runs.
3.5 How do I configure sendmail?
For @Mail to receive emails for accounts created on the system your Mail
Transport Agent (MTA) needs to be configured to deliver all emails for
the domainname to the @Mail saveemail.pl script in the base installation
directory. Click here to read the Installation documentation on
how to setup @Mail under Sendmail.
3.6 How do I configure my WebServer to
execute @Mail?
@Mail requires your webserver to execute .pl files as CGI-scripts
and to allow CGI scripts to be executed in the @Mail directory. To persuade
Apache to execute scripts you must tell it how to recognize them - and
also that it's okay to execute them. For this, you need to use something
like the AddHandler directive in the Apache configuration.
In an appropriate section of your server configuration files, add a
line such as
AddHandler cgi-script .pl
The server will then recognize that all files in that location (and
its logical descendants) that end in ".pl"
are script files, not documents.
Make sure that the directory location is covered by an Options
declaration that includes the ExecCGI option.
For further information on how to setup the Webserver to execute @Mail
read Step2 of the Installation Documentation
4. @Mail Feature Questions
4.1 How do I setup Email to SMS gateways under @Mail?
@Mail allows you to setup gateways to deliver Email-reports to users
mobiles via SMS messages. The @Mail server can be configured to send
the headers of Email messages to your mobile phone, alerting you of
incoming Email The software can be configured to only forward a specific
type of message to your mobile phone; allowing you to configure the
service to send you emergency notification of events happening on the
Internet.
For the delivery of Email to mobile-phones, @Mail can be configured
in two different ways. Either by connecting a mobile-phone directly
to the @Mail server; or forwarding messages via the Internet to the
@Mail SMS node. Both steps are explained in detail below
Direct Connection: Connecting a Nokia Mobile-Phone directly to the @Mail
server allows the system to easily send SMS messages to users mobile
phones on the network. When new Email arrives for a specified user;
they will receive via their mobile-phone the Email-headers and the first
few sentences of the Email message. Due to the SMS protocols restrictions
only 160 characters can be sent per message. @Mail supports only the
Nokia 3810 / 6010 range of Mobile-Phones for the SMS server. The @Mail
team have developed support for these mobile phones under @Mail, the
software directly communicates with the mobile-phone via the COM port
or Infrared. For more information on how to setup your own SMS gateway
connected to the Internet contact info@CGIsupport.com
SMS Forwarding: Rather then setting up your own SMS gateway with mobile-phones
connected to your server, we have created a global SMS-node which registered
users of our software can access to send SMS messages to any mobile-phone.
Our SMS node can be accessed via the Internet and allows users to receive
emails to their mobile-phone. The SMS node has access to all the major
telecommunication backbones, users from Europe, Asia, Australia, North/South
America & Africa can receive messages from our network. Only registered
users of @Mail are permitted to access the SMS node. For information
on how to login to the @Mail SMS node contact info@CGIsupport.com
The future of Mobile Communications
The @Mail team have been busy developing support for the new WAP (Wireless
Application Protocol) on mobile phones. Leading company's such as Nokia
& Ericsson are beginning to push the new technology to the consumer
market by promoting the use of WAP-phones. We are focused on supporting
the new technology by programming support for WAP. @Mail allows users
to access their Email-desktop directly on their mobile phone. This allows
users to receive entire Email messages, compose new messages and perform
basic administrative tasks to their Inbox. Such a service is very useful,
for when you are traveling you can still keep in touch with what's happening
on your Email Users can easily compose new Email messages and send them
to any address on the Internet. Using @Mail your Email is only a mobile
phone call away ...
4.2 Advantages using an SQL database to store user emails
Firstly, you should consider how large a userbase you want to support.
If you wish to use @Mail to host a large number of active user-accounts
it is highly recommended you use an SQL database server to store all
incoming Email By using SQL, @Mail can access user emails with ease
and speed. The performance is dramatically increased and allows 'multi-serving'
of the WebEmail service. The @Mail software can be setup on multiple
machines which all distribute the load of the system.
Recommended Setup for large sites
Use a Unix Server to host the core SQL database; using a fast/stable/free
SQL database server like mySQL to store all incoming emails for
user accounts. The machine should be setup for the task of maintaining
the SQL database server, do not use the machine to run any other services.
Setup 1+ Linux machines with a stripped-down kernel especially for the
task of http-serving. Load @Mail onto the server and configure the software
to communicate with the SQL database server to access user emails. @Mail
allows you to distribute the load over multiple machines, insuring a
reliable Email service for users.
4.3 Which languages can it support? Can it be modified
to support another language?
@Mail has been translated into many languages, please Email
us . @Mail has been designed on a multilingual template so that
conversion to the language that best suits you is quite possible. Since
the source-code and HTML files are separated, all that needs to be done
is to translate the Language file. We are constantly looking for people
to translate @Mail into other languages, and we welcome you to do this.
In returns we will may give you a discount on the price of the @Mail
you have purchased.
For more information about translating @Mail, please see our Translation
Guide
4.4 Can we use our own branding and remove '@Mail' in the
script and pages?
We understand that your Email-service should be a reflection of your
company, so using your own branding is important. Once you have customized
the program, you can have your personal headers and html, thus deleting
any @Mail references. Although we encourage you to place the following
notice on your front-login screen
WebEmail System Developed by CalaCode.com
4.5 How do I modify the user-interface of @Mail to suit
the design of my website?
Since @Mail includes the Full Source Code you can modify any element
of the software to suite the design of your website, or clients project.
We have designed the system on the idea of HTML-templates, the entire
user-interface of @Mail can be easily changed by modifying the content
of the files located in @Mail/html directory, or for quick interface
customization, use the Branding feature in the @Mail Admin. The WebEmail
system support multi-language, view the html directory in the base installation
directory for further information.
If you would like us to customize it for you, simply Email us with
the exact details of what you would like to be changed, and we will
reply with a quote for the modification.
4.6 Can I disable the frames?
One of the best features of @Mail is that the source code is provided.
Therefore you have the options to modify the system to best suit your
needs. So if you wish for your clients to have non-frame options, then
this is possible. It is fairly simple to change the output, you will
need to work with HTML, however if you have any problems doing this,
then please contact us and we will assist you.
Again, if you would like us to customize it for you, simply Email
us with the exact details of what you would like to be changed, and
we will reply with a quote for the modification.
4.7 What does the full site license include?
@Mail Corporate includes the full site license, you can configure
the software to run with as many domain names as you like. However,
the license is only valid for your own company. If you are interested
in reselling the @Mail program to your clients, you will need to purchase
individual licenses. We offer an attractive reseller agreement.
4.8 Do we have to buy any plug-ins?
No, when you download @Mail you receive the entire package, as specified
on our website. Users of @Mail Pro and above are also entitled to future
versions, upgrades and patches when they are released, so you can always
have the latest webbased Email service for your business.
4.9 Can we send Email messages to mobile phones.
Currently @Mail supports SMS messaging to mobile-phones; when users
receive Email for their account, the system can be configured to send
the message direct to the users mobile phone. We have also programmed
support for users to compose emails on their phone, and send them via
the net.
@Mail WAP allows Email access via any device that supports the WAP
protocol, such as mobile phones or PDA's. With the use of these two
services, you can use the newest way of communication and promote your
Email-service above the crowd.
4.10Does @Mail work with MTA's other then sendmail?
@Mail can operate under any MTA which can divert all incoming Email
for a domainname to an external binary. We have successfully used Qmail
and SMTPd under Unix to configure the @Mail service. Running under Windows
Platforms users can choose to use Sendmail, configuration is the same
as the Unix versions.
We recommend the use of EXIM under
both UNIX and Windows
4.11 Does @Mail run under Virtual Servers?
Running under a Virtual Server @Mail can be easily configured to send/receive
Email Depending on the level of features your Virtual Server has, you
may need to ask your provider to modify the sendmail configuration file
to divert all Email to the @Mail saveemail.pl script. Users of @Mail
Pro are entitled for remote-installation by the @Mail Team, Email info@CGIsupport.com
and one of our technical staff can install @Mail on your Virtual Server.
4.12 Does @Mail support large user bases?
@Mail heavily depends on the hardware of the server : When using @Mail
for a user base over 50 000 we recommend using more than one server,
For more information please see The Install Guide
and the Large Userbase Information .
5. Configuration Questions
5.1 How do I configure @Mail to host multiple domain-names
for WebEmail?
Via the webadmin control panel the administrator can configure
extra domain-names for @Mail. The domains.conf file in the base installation
directory defines which hostnames are active for WebEmail ; domains specified
in this file enable users to select the domain for the Email account via
the sign-up page. For each domain you wish to use for WebEmail, you must
follow the same steps in diverting all Email for the domain to the saveemail.pl
script.
5.2 What is the error 'xxx not available for sendmail programs?'
The sendmail.cf file can be configured to use a feature called Secure
Mail Shell ; the smrsh is the only program that prints the "xxx not available
for sendmail programs" message. The SMRSH does not permit sendmail to
divert Email to an external binary ; although you can allow sendmail to
divert Email by making a symbolic link from the /etc/smrsh directory to
the saveemail.pl script provided /etc/smrsh is really the directory
that your version of smrsh uses, of course, otherwise replace with the
proper one
Create a symbolic link from your smrsh directory to saveemail.pl
ln -s /www/atmaildir/saveemail.pl /etc/smrsh/saveemail.pl
This will permit sendmail to divert Email to the saveemail.pl file
If you still can't get it to work, my suggestion would be to not use
smrsh at all - its major motivation is to protect against a long-gone
bug in sendmail. Just build a new sendmail.cf from a .mc file that doesn't
include FEATURE(smrsh) (i.e. it isn't the default to use this in any version
of the standard sendmail config).
5.3 Can I use an external SMTP server to send Email?
@Mail can use any external SMTP server on the Internet to send Email via.
You may choose to use an external SMTP server the relay all user-emails
via; be sure that you have permissions to relay Email via the server
first. By using the webadmin control panel you setup @Mail
to use an external SMTP server, or modify the atmail.conf file by hand.
5.4 What browser should I use with @Mail?
Any browser which supports frames can use @Mail Although to use some
of the advanced feature of @Mail we recommend you have a recent webbrowser
such as IE4/5 or Netscape 6 and above. Since @Mail uses Javascript and
DHTML to spice up the user-interface it is required to use a recent
browser to take advantage of these features.
Note: New versions of Netscape can cause some problems with @Mail in
particular the HTML editor. We are not able to solve these problems
as its to do with the integration with netscape from their end.. Please
contact the staff for more information. Recent surveys found that 70%
of internet users use Internet Explorer so most of your users will not
be affected. As Netscape increases it's DHTML support, we will inform
all @Mail administrators.
5.5 Why does @Mail send a cookie on every request?
To keep track of user authentication, @Mail uses cookies to save user
login details. Since @Mail depends on cookies you must use a webbrowser
which supports them ; be sure your browser is configured to accept cookies
before using @Mail. On each request the browser sends a cookie which contains
user-login information and a unique SessionID verifies user-login details.
5.6 Does @Mail support SSL?
Yes, using SSL with @Mail is highly recommended for security reasons.
Since the web-server is the upper-layer, @Mail needs no extra modification
to run in SSL mode. Simply setup an SSL WebServer (ApacheSSL is recommended)
and move the atmail directory into the DocumentRoot of the SSL webserver.
SSL @Mail is now enable
|