| Platforms | |
The Sugarsoft Mail Server is a native Win32 application. This means that it runs
perfectly under both Windows 95, 98, ME, XP, 2000, NT4.0 and even NT3.51. It will not run under
earlier versions of Windows. We do not currently support the Alpha platform for
Windows NT, nor Mac or Linux, but we plan to do that in the future.
Under Windows NT and 2000 you can choose to run the Sugarsoft Mail Server as a System
Service that start automatically at system boot, even if no user logged in.
|
| Compatibility | |
The server uses standard Win32 API calls, i.e. it depends on a few common
preinstalled system DLL's in order to function. Please make sure you have installed
the latest servicepacks and that you have installed and verified a working TCP/IP
protocol based network on your system. If you plan to use the Dial-up feature in the Sugarsoft
Mail Server, please make sure that you can successfully dial and connect to Internet
before using this feature in the mail server.
|
Server
Not client | |
The Sugarsoft Mail Server is a server, not a mail client. You cannot use the
Sugarsoft Mail Server to read or compose emails. This is what a mail client is for.
Examples of mail clients are Eudora, Microsoft Outlook, Netscapes build-in mailer,
Pegasus mail etc. etc.
|
| Protocols | |
The Sugarsoft Mail Server is a standard SMTP and POP3 server.
A mail server takes care of transferring mails from one destination to another using
the mechanisms specified for the SMTP protocol
(RFC821/STD10). The server locates the
destination mail server using DNS lookup and therefore functions as what is typically
referred to as an MTA (Message Transfer Agent) or a
Smart Host.
The Sugarsoft Mail Server implements the full POP3 protocol
(RFC1939/STD53).
This protocol is what mail clients use to log on to a mail server with a login and
password to transfer (or download) mails from a certain mailbox.
|
| Modules | |
The Sugarsoft Mail Server is very compact and gentle to your system configuration. All
executable code is contained within the single MailServer.exe-file. No other DLL's or
components a required, however the two Online Help files may be useful.
Installation of the Sugarsoft Mail Server is performed the first time you run the
executable. A build in wizard guides you through some initial steps and writes the
selctions you make to the system registry. I does not overwrite any other
configurations settings nor files on your system.
|
| Perfomance | |
The 900KByte MailServer.exe file uses appr. 2MBytes of RAM while running idle. The code
itself is very lean and fast. The server actually runs smoothly on older systems such
as a 486/33MHz PC with 32 MByte RAM. You do not need to acquire new state-of-the-art
computer equipment to run the Sugarsoft Mail Server if you plan to service only a few
hundred email accounts.
|
| Backup | |
The Sugarsoft Mail Server have a build-in backup feature that will save the entire
configuration normally held in the system registry to a disk file. The configuration
is everything from TCP/IP address and timer settings to domain names, user mailboxes
and their login/passwords. This file can later be restored if you need it or you can
use this file to easily move the Sugarsoft Mail Server from one PC to another.
|
| File format | |
The Sugarsoft Mail Server store all mail files in standard ASCII
(RFC822 format).
This means you can open any file and edit it if you like. You could even build your own
customized handling of emails by having some script automatically access these files.
The server keep no other track of files it currently holds than what's on the disc. The
implication is that you are also free to move and/or delete files from the mail server's
store.
However, be careful not to change any of the information contained in the
X-SugarSoft-Info header. This is where the mail server
store internally used path-, timing- and transcript information.
|
| Security | |
The Sugarsoft Mail Server provide extensive anti spamming features and a simple way to
block for third party relaying. See the
Security section
for further details.
|
