Copyright: Copyright © Floosietek Ltd
Citation: FTGate version 2.2 Reference Manual


Welcome

FTGate Version 2.2 Reference Manual

Welcome

Welcome to the FTGate reference manual. In this manual you will find everything you need to setup and use FTGate.

Additional information will also be posted to our web site from time to time,
so you may wish to visit our web site at http://www.floosietek.com for the latest updates.


Change Password Dlg

New Password

Enter your new password.

There is no minimum or maximum length (within reason).

Confirm Password

Retype your password as a confirmation.


IP Address Range

IP Address

The 32-bit address defined by the Internet Protocol in STD 5, RFC 791. It is usually represented in dotted decimal notation. See also: dot address, internet address, Internet Protocol, network address, subnet address, host address.

Subnet Mask or Address Mask

A bit mask used to identify which bits in an IP address correspond to the network and subnet portions of the address. This mask is often referred to as the subnet mask because the network portion of the address can be determined by the encoding inherent in an IP address.


Configuring Proxy Servers

Disclaimer:

The information in this section is intended as a guide only and is subject to change. The information is correct, to the best of our knowledge, at the time this document was written.

For more up-to-date details contact the relevant web site.


Set-up guide for FTGate and WinGate V3

WinGate

The WinGate proxy server can be obtained from the WinGate web site at http://www.wingate.com

This guide assumes you have already set-up WinGate v3 to connect to the ISP/Internet.

To set up FTGate to connect to your mailbox(s) at your ISP or just connect to the web via WinGate V3. You need to make the following configuration changes:

You will need to configure WinGate like this:

•	The SOCKS Proxy server should be installed as below. You should also ensure that it is started, (double click the entry below to view the properties and select the ‘Bindings’ tab).  The screen shot shows the GateKeeper window with the control option selected and the SOCKS Proxy server present. (If it were not present it would not be installed, so see your WinGate documentation for how to install it.)

•	If you have the POP3 server in the above window you need to delete it, by right clicking it and selecting ‘Delete’. Click Yes on the Are you sure…? Screen.

•	If you have FTGate and WinGate on the same machine you can use the IP number 127.0.0.1 in FTGate.

•	If you have FTGate and WinGate on different machines you will need to open the properties of the SOCKS Proxy server by double clicking on the entry in GateKeeper and selecting the Bindings Tab.

•	The screenshot shows this page of the SOCKS Proxy server properties with only the 127.0.0.1 IP number available for connections.

•	To start the other IP number double click it to move it to the ‘Available’ window. Click OK to close this window. Then select the SOCKS Proxy server and right click on it and select ‘Start’. This will start the other IP number and allow you to connect to it from other machines.

This should be all you need to do in the way of changes to the WinGate configuration.

FTGate Configuration.

•	Open the FTGate properties pages and select the Dialup Tab.

•	Select the ‘Connect using Proxy Server or Dialup router using defined Schedule’ option.

•	Select the MX Delivery tab.

•	Enable (check the box) the SOCKS V4 option.

•	In the Address field enter the IP number (127.0.0.1 or xxx.xxx.xxx.xxx where xxx is the Intranet IP number of the machine) or the machine name running WinGate,  i.e. ‘douglas’.

•	Leave the port number set to the default (1080).

•	Click Apply and OK for the changes to take effect. Send a test message.

•	Configure your SmartPop accounts to connect to your mailbox at your ISP, as shown in the FTGate manual.

Notes:

•	You cannot use the DNS/MX record delivery option when you are using a proxy server.

•	You may have to enter the IP numbers and mailserver names of the ISP's servers to the hosts file. There are instructions in the file C:\windows\hosts.sam (HOSTS on NT systems) showing the format you must use. If you are running DHCP this should not be necessary.

•	To avoid any timeout errors increase the timeouts on the Ports properties page for the SMTP & POP servers to around 90 – 120 seconds and the timeout for SmartPop on the SmartPop properties page to about the same.


FTGate Connection through WinProxy

The WinProxy proxy server can be obtained from the WinProxy web site at http://www.winproxy.com/

This assumes that you have already set-up WinProxy to connect to the ISP/Internet.

To set up FTGate to connect to your mailbox at your ISP or just connect to the web via WinProxy you need to make these configuration changes:

WinProxy

Select File>Advanced Properties from the main WinProxy screen.

You will be asked if you want to go online. Click NO.

•	On the WinProxy Advanced Configuration screen

•	Ensure that the SOCKS support is Enabled (the box is checked).

•	Disable the mail option (the box is unchecked).

In addition, the port numbers should be changed on the Mail set-up page.

•	Click the Mail set-up button to open the page and change the numbers to say 6500 (this is a port number that will not normally be used). You cannot just delete the port numbers and leave the fields blank. (This prevents WinProxy capturing the port and routing the mail out to the net bypassing FTGate).

•	Leave the Mail Host IP (SMTP) field blank.

•	Leave the POP3 Server IP field blank.

These are the only configuration changes you should need to make to the WinProxy settings.


FTGate Configuration.

•	Open the FTGate properties pages and select the Dialup Tab.

•	Select the ‘Connect using Proxy Server or Dialup router using defined Schedule’ option.

•	Select the MX Delivery tab.

•	Enable (check the box) the SOCKS V4 option.

•	In the Address field enter the IP number (127.0.0.1 or xxx.xxx.xxx.xxx where xxx is the Intranet IP number of the machine) or the machine name running WinProxy,  i.e. ‘douglas’.

•	Leave the port number set to the default (1080).

•	Click Apply and OK for the changes to take effect. Send a test message.

•	Configure your SmartPop accounts to connect to your mailbox at your ISP, as shown in the FTGate manual.

Notes:

•	You cannot use the DNS/MX record delivery option when you are using a proxy server.

•	You may have to enter the IP numbers and mailserver names of the ISP's servers to the hosts file. There are instructions in the file C:\windows\hosts.sam (HOSTS on NT systems) showing the format you must use. If you are running DHCP this should not be necessary.

•	To avoid any timeout errors increase the timeouts on the Ports properties page for the SMTP & POP servers to around 90 – 120 seconds and the timeout for SmartPop on the SmartPop properties page to about the same.


FTGate connection through 602Pro lite Proxy server

The 602Pro proxy server can be obtained from the 602Pro web site at http://www.602pro.com

This assumes you have the proxy server installed and set-up to connect to your ISP/the Internet.

602Pro Proxy configuration.

•	From the screen above, select ‘Configuration Wizard’ from the Settings menu.

•	The first ‘Configuration Wizard’ screen you will see shows the dial up connection. You don’t need to edit this page. Click Next to continue.

•	The second ‘Configuration Wizard’ screen shows the proxy services options. Here you should ensure that the SOCKS proxy is Enabled. Click Next to continue.

•	The next ‘Configuration Wizard’ screen you need to edit is a further 4 next clicks on. This is the POP3 and SMTP server page.

•	You need to ensure that both these fields are blank.

•	That is all you need to do in the proxy.

•	To exit the ‘Configuration Wizard’ Click Next until ‘Finish’ appears and then ‘OK’. The last screen tells you that your changes have been saved.


FTGate Configuration.

•	Open the FTGate properties pages and select the Dialup Tab.

•	Select the ‘Connect using Proxy Server or Dialup router using defined Schedule’ option.

•	Select the MX Delivery tab.

•	Enable (check the box) the SOCKS V4 option.

•	In the Address field enter the IP number (127.0.0.1 or xxx.xxx.xxx.xxx where xxx is the Intranet IP number of the machine) or the machine name running 602Pro,  i.e. ‘douglas’.

•	Leave the port number set to the default (1080).

•	Click Apply and OK for the changes to take effect. Send a test message.

•	Configure your SmartPop accounts to connect to your mailbox at your ISP, as shown in the FTGate manual.

Notes:

•	You cannot use the DNS/MX record delivery option when you are using a proxy server.

•	You may have to enter the IP numbers and mailserver names of the ISP's servers to the hosts file. There are instructions in the file C:\windows\hosts.sam (HOSTS on NT systems) showing the format you must use. If you are running DHCP this should not be necessary.

•	To avoid any timeout errors increase the timeouts on the Ports properties page for the SMTP & POP servers to around 90 – 120 seconds and the timeout for SmartPop on the SmartPop properties page to about the same.


FTGate connection to the Internet via a proxy server using SOCKS V4

A Generic guide.

These days it is reasonably safe to say ‘Most proxy servers support SOCKS V4’. This makes it relatively easy to connect FTGate to the ISP via a proxy server.

General rules.

Proxy servers.

•	Disable the SMTP & POP servers in the Proxy server. (You may need to change the port numbers which the proxy server uses in order for these to prevent the proxy server capturing the port 25 for SMTP & port 110 for POP3). In this configuration mail will pass through the proxy server; it is not relayed by it.

•	Remove any mappings for the mail, whether they are in the Proxy server or they are TCP mappings.

•	Enable the SOCKS server/support in the Proxy server on port 1080 by default.

FTGate Mail server

•	Enable the SOCKS V4 support on the MX Delivery properties page.

•	Enter the IP address or machine name on which the Proxy server is running. If you are using DHCP, you should use the machine name.

•	Select ‘Connect using Proxy server or dial up router…’ on the dial up properties page.

•	Leave the port number set to the default (1080).

•	Click ‘Apply’ and ‘OK’ to accept the changes.

Notes:

•	You cannot use the DNS/MX record delivery option when you are using a proxy server.

•	You may have to enter the IP numbers and mailserver names of the ISP's servers to the hosts file. There are instructions in the file C:\windows\hosts.sam (HOSTS on NT systems) showing the format you must use. If you are running DHCP this should not be necessary.

•	To avoid any timeout errors increase the timeouts on the Ports properties page for the SMTP & POP servers to around 90 – 120 seconds and the timeout for SmartPop on the SmartPop properties page to about the same.


Quick Start Guide

Before installing the mail server onto your system you will need the following:

1.	TCP/IP networking installed on the machine that will run the mail server and on any machine that will be required to access the mail stored in the mail server.

2.	The name or IP number of your ISP SMTP mail server.

3.	Your primary domain name (the bit after the @ in your email address)

If an old copy of the mail server is already installed, the setup program will upgrade the old settings.

To begin the setup procedure run the program ftgate22.exe. You will then be prompted for a series of options as follows:

1. Gateway Configuration

This dialog allows you to configure your default mail gateway and temporary mail folder.

•	Gateway Machine
This is the machine to which you will normally deliver outgoing mail. This machine should act as a relay server for your site. The name is normally supplied by your ISP. If you are unsure of the name to use you can look in your mail client software for the SMTP server settings or ask your ISP. Note: If you are intending to use MX record delivery you should leave this box empty and after installation complete the MX Delivery Properties.

•	Directory
This is the directory into which FTGate will store mail messages.

2. Remote access

This dialog allows you to configure the way in which FTGate will  connect to the internet.

•	Use a direct LAN connection
This option should be chosen if your connection to the internet is by a permanent LAN connection.

•	Use a dialup router or proxy server
This option should be chosen if your connection is handled by a dialup router or proxy server.

•	Use the following dialup profile
This option should be chosen if you want FTGate to manage the dialup connections using a profile on the local machine.

3. Domains

This dialog allows you to configure your domain. The domain is used to determine which messages are addressed to a local FTGate user and which are addressed to remote Internet users. If you are using a shared domain (i.e. there are mailboxes for non local systems with the same domain, e.g. hotmail.com or yahoo.com), you should enter the shared domain and configure the unknown mail handling to forward to the Internet. See Domains Properties Page

•	Primary Domain Name
Your primary domain name

4. Users

This dialog allows you to enter the name of the first user account on the system. This account will be the postmaster of the system. After the setup has completed you can enter other users and mailboxes into FTGate by using the Mailbox Manager.

5. Finished

This dialog indicates that you have completed the setup and the mailserver is now installed.

Your next step should be  to add some mailboxes to FTGate. This is done by running the Mailbox Manager.

You can now start FTGate.


Using FTGate as Service.

FTGate can be run in an unattended mode as a service. In this mode FTGate will start and stop with the machine and will not display a user interface.

Starting the service

To install and start the service you should open the FTGate Properties Panel, switch to the Startup Properties page (click on the Startup Tab). Then select Install and run as an NT service (on an NT system), or Install as a windows 95/98 service.

On an NT system this will install the service and start the service running. Clearing the selection will stop the service and uninstall it. If you wish to stop the service without uninstalling it you should open the Service control panel and select the appropriate action from the service controls.

On a Windows 95/98 system the machine will need to be restarted for these changes to take effect. If you wish to stop the service you should clear the option in the Startup Properties and then reboot the PC.

Monitoring the Service

The state of the service can be monitored through a web browser.

The web browser should be connected to FTGate through the HTTP port on FTGate. By default you can access it by entering the following URL on the machine running FTGate:

http://127.0.0.1:8080/

Or

http://FTGateMachineName:8080/

where FTGateMachineName is the IP number or address of the machine running FTGate.


Mailbox Manager

The mailbox manager is started by either clicking the Mailbox Manager button in the FTGate application windows or by selecting “Mailbox Manager” from the FTGate program group in the start menu.

Mailbox Types

There are eight types of mailbox available in the mailserver, three of which are system mailboxes that cannot be deleted or modified and do not count towards the licensed mailbox count.

The mailbox types are as follows:

•	User Mailbox - See User Mailbox Properties.
A user mailbox provides a location into which incoming mail for a particular user can be stored. The user can then retrieve the mail using a POP3 mail client. Access is via a password which can either be managed by the mail server or verified against an NT domain.
This mailbox uses one licence count.

•	List Mailbox – See List Mailbox Properties
This type of mailbox provides mailing list features. e.g. a discussion list or users group might be a mailing list 'users-group'.
This mailbox uses one licence count.

•	Auto-Responder Mailbox – See Auto-responder Properties
This type of mailbox provides auto-responder features. e.g. a sales information system might use an auto-responder to answer queries about product features.
This mailbox uses one licence count.

•	Robot Mailbox – See Robot Mailbox Properties
This type of mailbox provides automated robot features. e.g. a database might use a robot mailbox to extract data from messages using a custom program, and then insert the data into the database.
This mailbox uses one licence count.

•	Group Mailbox – See Group Mailbox Properties
This type of mailbox provides local mail group features. e.g. a sales team might have a group mailbox 'sales' which would route all mail to sales to each member of the team.

•	Command Processor
This is a system mailbox. It provides an email interface for controlling the functionality of the mail server.

•	List Server
This is a system mailbox. It provides an email interface to the mailing list management options of the mail server.

•	Null Mailbox
This is a system mailbox. It is provided to aid system management and will delete any message sent to it.


Mailbox Manager Screen

The mailbox manager screen allows the administrator to add and edit mailboxes and aliases. The main display is a list of all the mailboxes defined in the mail server.

•	Name
The name of the mailbox

•	Type
The mailbox Type

•	Real Name/Comment
A description of the mailbox taken from the mailbox properties

Clicking on the Title of any of these columns will sort the mailbox list according to that column.

Mailbox Management

The mailbox can be managed by using the 6 buttons at the bottom of the mailbox manager window.

•	Add
This button will display the New Mailbox Dialog where a new mailbox can be defined

•	Add from file
This button will display the Add From File Dialog that will allow user accounts to be created by importing their names from a text file.

•	Add NT users
This button will display the Add NT User Dialog that will allow users accounts to be created by importing the details from the NT user database.

•	Rename
This button will display the Rename Dialog requesting a new name for the mailbox

•	Properties
This button will display the appropriate Mailbox Properties Dialog that is appropriate to the selected mailbox type.

•	Delete
This button will delete the selected mailbox.


New Mailbox Dialog

This dialog allows the user to specify the type of mailbox they wish to create

•	Mailbox/Alias
This is the name of the new mailbox or alias.

•	Mailbox Type
This specifies the type of mailbox to create when the 'Create.' button is clicked.

•	Create …
Clicking this button will create the mailbox and open the appropriate Mailbox Properties Dialog for that type of mailbox.

•	Cancel
Clicking this will cancel the mailbox creation

For example:
To create a user mailbox, type in the name of the user (say 'joe.soap') and then select the user mailbox and click 'Create'. The mailbox will then be created and the appropriate mailbox properties page will open to allow the options for the mailbox to be set.


Add From File Dialog

This dialog permits the administrator to add many users to the system by defining their names in a text file and importing them into the mail server.

The file used should be a plain text file. On each line should be the first and last name of a user, e.g.

fred bloggs
joe soap

The administrator then selects the format for the account name and alias from the list and clicks the Create Accounts button.

Account Name

•	firstinitial.lastname
e.g. j.soap

•	firstname.lastname
e.g. joe.soap

•	firstname.lastinitial
e.g. joe.s

•	firstname
e.g. joe

Aliases

•	firstinitial.lastname
e.g. j.soap

•	firstname.lastname
e.g. joe.soap

•	firstname.lastinitial
e.g. joe.s

•	firstname
e.g. joe


Add NT User Dialog

This dialog permits the administrator of an NT system to import names into the mail server. The administrator should select the names that are to be imported from the list and click on Add. The accounts will then be created and the appropriate mailbox access rights set.


Rename Dialog

This dialog permits the administrator to enter a new name for the dialog. Clicking on OK will then change the name of the mailbox.

•	Rename From
This is the current name of the mailbox.

•	Rename To
This will be the new name of the mailbox.


User Mailbox Properties.

User mailboxes form the main storage of the mail system. Incoming mail for users is stored in a user mailbox until their mail client downloads it. The User mailboxes are accessed through a POP3 mail client.

General Options

•	Mailbox Name
The mailbox name is the name used for mail delivery. All mail addressed to this name will be placed in this mailbox.

•	Real Name
This is the name used for display in the comments section of the mailbox manager.

•	Mailbox Location
This is the directory on the mail server machine that contains the files for this mailbox.

Security

•	Use local password control
When this option is selected the mailserver will manage the password for the mailbox. The password will be stored in an encrypted form and will be checked when a user attempts to logon.

•	Change Password
Pressing this allows the user to change the password for accessing this mailbox. This option is only valid when using local password control

•	Use NT password control
This option causes the mail server to authenticate the password supplied by a user with the Windows NT security system.

•	NT User Id
This field is only valid when using NT password control. The field contains the NT logon name of the user of the mailbox. This permits the NT system to use a real name of say ‘Fred Bloggs’ as the login but allows the mail address to be say ‘fred’.

Message Forwarding

This allows the user to define an address to which a copy of all received mail will be sent.

•	Forward Messages To
This allows the user to enable the specified addresses for forwarding. Several addresses may be placed in the edit box, each separated by a semicolon “;”.,
e.g.  “richard@ftgate.com;sales@ftgate.com”

•	Delete messages after forwarding
This allows the user to specify that the original message is to be deleted after a copy has been forwarded, removing it from the mailbox.

AutoText

This allows the user to specify a text message that will be sent as a reply whenever a message is received. This can be used to send a confirmation message acknowledging the receipt of a message.

•	Send AutoText replies with the following message
This enables the AutoText feature and  specifies the message to be sent as the AutoText reply.


List Mailbox Properties

List mailboxes allow a single message to be sent to many list members. A list has several options to control how it works and can be configured to allow members to subscribe and leave the list by the use of simple messages. It is also possible to use an Auto-responder to add a member to the list and send a message regarding the use of the list to the subscriber.

General Options

•	Mailbox Name
The mailbox name is the name used for mail delivery. All mail addressed to this name will be placed in this mailbox.

•	Mailbox Location
This is the directory on the mail server machine that contains the files for this mailbox.

•	Real Name
This is the name used in the mail header for outgoing messages from this mailbox, and for display in the comments section of the mailbox manager.

•	Change Password
Pressing this allows the user to change the password for accessing this mailbox.

Mailbox Options

•	List Owner
This defines the owner of the list. All list problems and error messages will be sent to the list owner.

•	Moderated
This option prevents any user posting to the list except the list owner. Any messages sent to the list by users other than the defined list owner will be sent to the list owner for acceptance. The list owner will then need to post the messages to the list if they are deemed suitable.

•	Maintain archive of postings
This option causes the mail server to keep a copy of each message sent to the list in the mailbox directory. If this option is not selected the messages are deleted after processing.

•	Set header "Reply-to:" to this list
This option causes the "reply-to" field of the sent messages to be set or replaced with the address of the list rather than the sender. When a list member replies to a message the message would then go to the mailing list. If the option is not selected any replies sent to a message will go directly to the originator of the message and not the list.

•	Allow only list members to post messages
This option prevents messages being posted by non list members.

•	Allow SUBSCRIBE
This allows a potential list member to send a message to the list server and subscribe or unsubscribe to the mailing list

•	Hide from server "LIST" command.
This option prevents the list from being included in the response to the list servers "LIST" command.

•	Include Sender in postings
If this option is enabled the originator of the posted message will receive a copy of the message.

•	Advanced
This button causes the List Mailbox Advanced Settings dialog to be displayed

Recipients

This shows a list of the current recipients or members of the list.

•	Add …
This displays a dialog into which a new address can be entered.

•	Delete
This deletes the selected address from the list

NOTE : This mailing list members are held in a text file called "rcpt.ftg" in the mailbox directory for the mailing list. The file contains one member per line.


List Mailbox Advanced Settings

•	Do not allow members to post messages over ...
This field allows the administrator to limit the size of message that can be sent by list members to the list. This limit does not apply to messages sent by the list owner.

•	Send this message when someone joins the list
This field contains the text that will be sent to anyone who sends a message to the list server with a request to join this list

•	Send this message when someone leaves the list
This field contains the text that will be sent to anyone who sends a message to the list server with a request to leave the list.

•	Append this text to outgoing messages...
Enabling this option will cause any text entered into the text box to be appended to all messages sent from the mailbox.


Auto-responder Properties

The edit Auto-responder dialog allows the user to configure the options for an Auto-responder. An Auto-responder will send a reply to any message it receives. The reply can depend on the subject line of the received message. If the Auto-responder does not recognise the request subject a default message is returned.

General Options

•	Mailbox Name
The mailbox name is the name used for mail delivery. All mail addressed to this name will be placed in this mailbox.

•	Mailbox Location
This is the directory on the mail server machine that contains the files for this mailbox.

•	Real Name
This is the name used in the mail header for outgoing messages from this mailbox, and for display in the comments section of the mailbox manager.

•	Change Password
Pressing this allows the user to change the password for accessing this mailbox.

List Management

•	Maintain Archive of requests
If this option is selected, a copy of all messages received will be maintained in the mailbox directory.

•	Add sender to the following list
This option will cause the sender of any message received by this mailbox to be added to the list selected in the drop down box. This provides a simple way to either manage a mailing list or keep an archive of requests.

•	Remove sender from the following list
This option will cause the sender of any message received by this mailbox to be removed from the list selected in the drop down box. This provides a simple way to manage a mailing list.

Auto Reply Keywords

This section allows the administrator to add keywords to the Auto-Responder.

•	Add
Clicking this button will insert a new keyword into the list and allow the administrator to edit the keywords properties with the Auto-Responder Keyword Edit Dialog.

•	Edit
Clicking this button allows the administrator to edit the selected keyword properties.

•	Delete
Clicking this button allows the administrator to delete a keyword from the list.


Auto-Responder Keyword Edit Dialog

This dialog allows the administrator to edit the properties associated with an Auto-Responder Keyword.

•	Keyword
This is the keyword that will be used to trigger this response.

•	Attached File
This is a file that will be attached as a MIME encoded attachment to the response message.

•	Response Text
This text will be used in the body of the response message.

•	Save
This will save any changes made to this list.


Group Mailbox Properties

Group mailboxes allow local distribution groups and lists to be created without the management problems associated with mailing lists. A group may only contain local mailboxes. Mail sent to the group mailbox will be forwarded on to all group members.

General Options

•	Mailbox Name
The mailbox name is the name used for mail delivery. All mail addressed to this name will be placed in this mailbox.

•	Mailbox Location
This is the directory on the mail server machine that contains the files for this mailbox.

•	Real Name
This is the name used in the mail header for outgoing messages from this mailbox, and for display in the comments section of the mailbox manager.

•	Change Password
Pressing this allows the user to change the password for accessing this mailbox.

Group Members

This lists the current members and available mailboxes for the group.

•	Current Group Members
This is a list of mailboxes which will receive a copy of any message sent to the group. To remove a member from the group select a member and click the "->" button. To add members to the group select a member of the 'Available Mailboxes' list and click the "<-" button.

•	Available mailboxes
This is a list of all the mailboxes on the local system that may be added to the group.


Robot Mailbox Properties

Robot mailboxes enable the mail server functions to be extended. The user can specify a program or batch file to be run when a message is received, together with a set of command line arguments which may include the name of the file.

General Options

•	Mailbox Name
The mailbox name is the name used for mail delivery. All mail addressed to this name will be placed in this mailbox.

•	Mailbox Location
This is the directory on the mail server machine that contains the files for this mailbox.

•	Real Name
This is the name used in the mail header for outgoing messages from this mailbox, and for display in the comments section of the mailbox manager.

•	Change Password
Pressing this allows the user to change the password for accessing this mailbox.

AutoText

This allows the user to specify a text message that will be sent as a reply whenever a message is received. This can be used to send a confirmation message acknowledging the receipt of a message.

•	Send AutoText replies with the following message
This enables the AutoText feature and specifies the message to be sent as the AutoText reply.

Command

This defines the command, to be executed as a separate task, when this mailbox receives a message. The command line must specify the full path and file name of the command, together with any arguments needed. Before executing the command the robot mailbox will substitute any occurrences of %FILE% or %file% with the full path and filename of the received message. The received message will not be deleted by the mailbox and should be deleted by the program or batch file if required.

e.g. If the following command is specified
c:\windows\notepad.exe %FILE% /p
the command executed for a particular message might be
c:\windows\notepad.exe c:\spool\mailbox\m000000a\rob12345.txt /p


Edit/New Alias Dialog

The Edit/New alias dialog allows an alias to be defined for a particular mailbox. Messages addressed to the alias will then be delivered to the selected mailbox.

Select the target mailbox from the drop down list and press OK.


List Processor Properties

There are no properties that can be configured for the List Server.


Command Processor Properties

There are no properties that can be configured for the Command Processor.


Mailing lists

To create a mailing list with the following settings the administrator should follow the steps below.

Name of the domain : mydomain.com
Desired name of the list : friends
Desired email address of the list: friends@mydomain.com
Email address of the list server: listserv@mydomain.com

1.	Open the Properties control and check that in the Domain Properties an entry exists for ‘mydomain.com’

2.	Open the Mailbox Manager and click the Add button

3.	In the Mailbox/Alias Name enter friends

4.	Select the type ‘Mailing List’

5.	Click the Create button
The Mailbox Manager will now display the List Mailbox Properties Page

6.	In the real name type ‘My Friends’

7.	Select the following check boxes:
Set header “Reply-to:” to this list
Allow only members to post messages
Allow SUBSCRIBE
Include Sender in postings

8.	Add the administrators email address to the Recipient list

9.	Now click OK

The mailbox has now been created. To test the list the administrator (who was added to the list) should send a test message to ‘friends@mydomain.com’ and verify that the message is received by the mail server and delivered correctly.

New members can join the list by sending a message to ‘listserv@mydomain.com’ with the first line of the message saying ‘SUBSCRIBE friends’.

To leave a list members send a message to ‘listserv@mydomain.com’ with the first line of the message saying ‘UNSUBSCRIBE friends’.


Command Processor Reference

The command processor allows remote administration of the mail server. In order to administer the mail server, commands are sent to the command mailbox (command@local). These commands will be processed and a message returned showing the success or failure of the commands.

A message to the command processor will consist of a series of commands, each on a separate line.

e.g.

open mailbox j.soap,password

set forward address joe@aol.com

There are two modes of access to the command processor:

•	User access

This mode allows a user to configure a mailbox. The user must know the mailbox name and password, and make the first command they send

open mailbox mailboxname,password

followed by the appropriate commands for the mailbox type.
Administration of user, list and auto-responder mailboxes can be completed in this manner.
e.g.

open mailbox j.soap,password
set password banana

•	Administrator Access

This mode allows a user who knows the administrator password to administer any mailbox without having to know the mailbox password. To enter this mode the first command sent should be

administrator adminpassword

The user can now administer any mailbox by specifying
open mailbox mailboxname
followed by the appropriate commands for the mailbox type.
e.g.

administrator adminpassword
open mailbox j.soap
set password banana

The available commands are grouped as follows.

Administration Control
General Command Options
User mailbox command options
Using list mailbox commands
Using Auto-responder commands

Command processor administration control.

The following commands relate to administrator mode and may only be used by the administrator.

ADMINISTRATOR password

Enter administrator mode by entering the administrator's password.
When in administrator mode mailboxes can be opened without specifying a mailbox password.

GET STATS

Returns a list of the mailbox usage statistics, showing :

•	Name - The name of the mailbox

•	Received - The total number of messages received

•	Sent - The total number of messages sent to a local address

•	External - The total number of messages sent to a non local address

•	Waiting Messages - The total number of messages currently in the mailbox directory

RESET STATS

Resets the mailbox statistics counters to zero.

CREATE MAILBOX name,type

Create the named mailbox.
Valid types are:

•	usermailbox

•	automailbox

•	listmailbox.

DELETE MAILBOX name

Deletes the named mailbox.

LIST MAILBOXES

Returns a list of all mailboxes and aliases

ADD ALIAS newalias,mailbox

Adds a new alias to the mail system, the alias will be 'newalias' and will point to 'mailbox'

DELETE ALIAS alias

Deletes the alias from the mail system

ADD KILL name

Adds the email address or domain to the kill list. To specify an address to kill use the full address, to specify a domain to kill specify the domain with an @ symbol. See Security Properties.

REMOVE KILL name

Removes the email address or domain from the kill list.

General command processor options

These commands are available for all mailboxes

OPEN MAILBOX name,password

Open a mailbox for administration.

SET AUTOTEXT

Set the auto text response for the open mailbox to the lines following the command. To terminate the AutoText entry before the end of the command message, enter a '.' full stop only on a line.

NOTE: In an auto-responder mailbox the AutoText message is the default message.

ENABLE AUTOTEXT

Enables the use of AutoText.

DISABLE AUTOTEXT

Disables the use of AutoText.

SET PASSWORD newpassword

Sets the mailbox password to 'newpassword'.

SET COMMENT newcomment

Sets the mailbox comment to 'new comment'

User mailbox command options.

These commands are only available for a user mailbox.

SET PLAN

Sets the mailbox plan message to the lines following the command.
To terminate the message enter a '.' full stop only on a line.

SET FORWARD ADDRESS

Sets the address to which messages will be forwarded.

ENABLE FORWARDING

Enables the forwarding of messages.

DISABLE FORWARDING

Disables the forwarding of messages

DELETE AFTER FORWARD

Enables the message deletion after forwarding

NO DELETE AFTER FORWARD

Disables the message deletion after forwarding

List mailbox command options

These commands are only available for a list mailbox.

ENABLE SUBSCRIBE

Allow subscribe requests to be accepted.

DISABLE SUBSCRIBE

Reject subscribe messages.

ENABLE CLOSED

Make the mailing list closed.

DISABLE CLOSED

Make the mailing list open.

ENABLE HIDDEN

Hide the mailbox from the list server LIST command.

DISABLE HIDDEN

Show the mailbox from the list server LIST command.

SET OWNER

Set the list owner

ENABLE ARCHIVE

Enable archiving of messages to the list

DISABLE ARCHIVE

Disable archiving of messages to the list

ENABLE MODERATED

Make the list a moderated list.

A moderated list is a list in which only messages sent by the list owner are distributed to the list members. Any message sent by a list member is passed to the list owner for moderation, the list owner should then , if the message is deemed suitable for the list, forward the message to the mailing list.

DISABLE MODERATED

Make the list a free posting list

ENABLE REPLY TO LIST

Sets the "reply-to" field in outgoing messages so that replies to the outgoing message are sent to the mailing list.

DISABLE REPLY TO LIST

Do not adjust the reply-to field in the message headers.

SUBSCRIBE emailaddress

Add 'emailaddress' to the subscribed members list

LIST MEMBERS

List all the members of the list

UNSUBSCRIBE emailaddress

Remove 'emailaddress' from the subscribed members list.


FTGate Application Main Window

Status Indicators

The status indicators allow the operator to determine the current operational status of FTGate.

•	Domain Name
Indicates the primary domain name that the mail server is configured for.

•	Connection
This indicates the current state of FTGate’s connection to remote machines. In a LAN only system it will switch between ‘Online’ and ‘Offline’, while in a dial-up system, it will also indicate the connection status while logging onto the remote system.

•	SMTP Server
Indicates whether FTGate is receiving SMTP mail.

•	SMTP Transmitter
Indicates whether FTGate is sending SMTP mail.

•	POP3 Server
Indicates whether FTGate has a POP3 client connected to it.

•	SmartPop
Indicates whether FTGate is retrieving mail from a remote POP3 host.

•	Finger
Indicates if FTGate has a finger session connected.

•	Waiting Messages
Indicates the number of messages waiting to be sent to the remote SMTP Mailhost(s).

•	Event History

•	The Event History area lists the last 100 events that have occurred. The event history can also be recorded into a disk file - see Logging Options.

Control Buttons

The control buttons are collected into the following three groups.

Connection Group

•	Poll SmartPop
This button will cause FTGate to check any SmartPop mailboxes that are defined. If FTGate is currently Offline a connection will be established. This button is disabled if no SmartPop accounts exist or SmartPop is disabled.

•	Connect
This button causes FTGate to begin a dial-up connection session. When connected FTGate will send any waiting mail and if SmartPop is enabled it will check the SmartPop mailboxes.

•	Disconnect
This button causes an active connection to be closed. This button will only be enabled when a connection has been made.

Operation Group

•	Hide
This button will cause FTGate to minimise down to the tray area. Double clicking on the icon in the tray will cause the mail window to re-appear.

•	About
This will display the FTGate About box.

•	Shutdown
This will cause FTGate to shutdown and exit.

Configuration Group

•	Mailboxes
This button will start the Mailbox Manager, allowing the operator to manage the mailboxes in FTGate.

•	Properties
This will cause the FTGate Properties screen to be displayed allowing the operator to configure the main operational behavior of FTGate.

•	Hide at startup
Checking this option will cause FTGate to start in its minimised state.

Event History

The event history shows the events that have occurred in the mail server. The events shown will be limited by the settings in the Logging Properties.

•	Date/Time
This is the Date and Time of the event

•	ThreadId
This is the ID of the thread that generated the Event. This is useful for tracking events that occurred over a single message transfer when there are large numbers of entries in the log.

•	Details
The details of the event.


SOFTWARE LICENCE AGREEMENT

SUBJECT OF AGREEMENT

FLOOSIETEK hereby grants to the CUSTOMER in consideration of licence fees paid by the CUSTOMER, a non-assignable, non-transferable, non-exclusive licence to use FTGate on a single computer (for the single mailbox version) or on  a single network server accessed by multiple computers (for the multi-user version) on the Terms and Conditions attached. Copyright and other intellectual property rights in FTGate shall at all times remain vested in FLOOSIETEK and the CUSTOMER's rights in FTGate shall be limited to those of a user licensed under the terms of this Agreement, such use to be limited to the CUSTOMER's internal business purposes only.

TERMS AND CONDITIONS

LIMITED WARRENTY

This software and accompanying written materials (including instructions for use) are provided "as is" without warranty of any kind. Further, FLOOSIETEK does not warrant, guarantee, or make any representations regarding the use, or the results of use, of the software or written materials in terms of correctness, accuracy, reliability, currentness, or otherwise. The entire risk as to the results and performance of the software is assumed by the CUSTOMER. If the software or written materials are defective the CUSTOMER, and not FLOOSIETEK or its dealers, distributors, agents, or employees, assumes the entire cost of all necessary servicing, repair, or correction.

The above is the only warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose, that is made by FLOOSIETEK, on this FLOOSIETEK product. No oral or written information or advice given by FLOOSIETEK, its dealers, distributors, agents or employees shall create a warranty or in any way increase the scope of this warranty and the CUSTOMER may not rely on any such information or advice.

Neither FLOOSIETEK nor anyone else who has been involved in the creation, production or delivery of this product shall be liable for any direct, indirect, consequential or incidental damages (including damages for loss of business profits, business interruption, loss of business information, and the like) arising out of the use or inability to use such product even if FLOOSIETEK has been advised of the possibility of such damages.

(2) COPYING OF PROPRIETARY INFORMATION

The CUSTOMER agrees  not to de-compile, reverse-engineer, reproduce, copy or duplicate any part or all of FTGate and to prevent its agents, employees, and representatives from de-compiling, reverse-engineering, copying or duplicating any part of or all of FTGate.

Should any portion of FTGate be de-compiled, reverse-engineered, copied or duplicated , the CUSTOMER shall immediately notify FLOOSIETEK of the

circumstances surrounding such event and shall assist FLOOSIETEK in enforcing its rights against any parties who are in violation of this Agreement.

Permitted exceptions to the above are for normal distribution purposes of the FTGate software, or for normal  back up or archival purposes.

(3) TERMINATION

FLOOSIETEK may terminate this Agreement upon thirty days written notice if the CUSTOMER fails to comply with any of the terms and conditions of this Agreement. In the event of termination, the CUSTOMER shall immediately cease use of FTGate and at its own expense, remove from its computers all copies (including on-line, back-up and archival) of FTGate and destroy them.

(4) NON-TRANSFERABLE LICENCE

The CUSTOMER acknowledges that FTGate is the sole property of FLOOSIETEK and agrees not to assign, sub-licence or otherwise transfer FTGate in any manner without prior written consent of FLOOSIETEK

(5) BINDING AGREEMENT

Upon acceptance of this Agreement by both parties, this Agreement shall constitute the entire Agreement between the parties and shall supersede  all other oral or written agreements or communications between the parties. FLOOSIETEK shall not be bound by additional provisions or provisions at variance herewith that may appear in the CUSTOMER's acknowledgement, purchase order, or in any other communication between the CUSTOMER and FLOOSIETEK.

(6) MODIFICATION/WAIVER

This Agreement may not be modified except by a written addendum signed by duly authorised representatives of both parties. No term or provision shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party claimed to have waived or consented.

(7) ASSIGNMENT

The CUSTOMER shall not assign, sublicense, or otherwise transfer to any other party all or any part of this Agreement, any interest herein or any rights hereunder.

(8) NOTICES

All notices and other communications provided  for or permitted under this Agreement shall be sufficient if contained in writing delivered by hand or registered certified mail or by facsimile addressed to the parties as set forth in this Agreement. Notification of critical errors concerning the FTGate Software should be communicated in writing to FLOOSIETEK by the other party. All such notices or communications shall be deemed received 2 working days after being sent. FLOOSIETEK reserves the right to communicate amendments to this agreement or all notices and other communications provided for or permitted under this Agreement by email to the other party.

(9) SURVIVAL

The CUSTOMER's obligations under paragraph (2) shall survive the termination of this Agreement.

(10) SEVERABILITY

If any provision of this Agreement shall be held void or unenforceable or contrary to English Law, such provision shall be deemed to have been excluded from this Agreement ab initio and shall not affect any other provision of this Agreement, the remainder of which shall be construed as if the excluded provision had never formed part of it.

(11) GOVERNING LAW

This agreement will be governed by and construed in accordance with the laws of England and the parties hereby submit to the exclusive  jurisdiction of the English courts.

ACKNOWLEDGMENT

By using FTGATE you acknowledge that you has read this licence agreement, understand it, and agree to be bound by its' terms and conditions. You also agree that the licence agreement is the complete and exclusive statement of agreement between the parties and supersede all proposals or prior agreements, oral or written, and any other communications between the parties relating to the subject matter of the limited warranty.


Statement of Year 2000 Compliance

FTGate has been designed to avoid any problems that may occur with the change of century. There are no dates stored internally in a manner that might make them susceptible to errors due to the century change. In addition FTGate does not process data from any other source where the date might be misinterpreted. FTGate is Year 2000 Compliant.

Note: This statement does not in anyway guarantee that FTGate will correctly operate across the Year 2000 boundary on any machine who’s BIOS and operating system is not Y2K compliant.


FTGate Version 2.2 Reference Manual

Welcome

Welcome to the FTGate reference manual. In this manual you will find everything you need to setup and use FTGate.

Additional information will also be posted to our web site from time to time,
so you may wish to visit our web site at http://www.floosietek.com for the latest updates.


Introduction

Thank you for choosing the award winning FTGate mail server. We at Floosietek know you will find FTGate to be the perfect solution for your mail server needs. Indeed FTGate was recently described as “The Perfect Mail Server” by  Network World magazine.

FTGate is a quality, feature packed mail server in a cost effective easy to use package running on Windows 95/98 or Windows NT. With a host of advanced features FTGate is suitable for large or small organisations interested in installing a mail server or replacing their current mail server with a solid reliable product.

FTGate can be setup within 10 minutes making it ideal for home networks, schools and charities, while its comprehensive features allows it to be used in large organisations and even by ISPs !

With its simple but comprehensive graphical configuration screens, users with little experience can quickly access the power of FTGate, while advanced users will be able to efficiently configure the sophisticated options that they require.

FTGate allows a network of users to communicate with each other using electronic mail. With its powerful dial-up networking facilities and implementation of standard internet protocols, it also allows each of those users to communicate over the Internet.

Floosietek views customer feedback as a crucial ingredient in the development process. Consequently FTGate is under constant development, reflecting the changing nature of today's communications requirements.


Features and Benefits

FTGate includes many powerful features which include, but not limited to:

•	Eight mailbox types supporting users, mailing lists, auto-responders, robots and more.

•	Optional Windows NT security database support for user validation and simple account creation.

•	An SMTP\ESMTP server for processing email.

•	A POP3 server for handling local mail retrieval.

•	Dial-up modem, Router, Proxy and LAN modes for maximum connection flexibility.

•	Comprehensive scheduling features to reduce the amount of time connected online and thus the costs involved.

•	SmartPop for retrieval of mail from one or more remote POP3 mailboxes.

•	Comprehensive security features to prevent unauthorised mail server use or unauthorised relaying of SPAM messages.

•	Full support for MAPS RBL to prevent bulk email from entering the mail server.

•	Extensive logging facilities to track message processing.

•	Full Year 2000 compliance.

•	Runs as a service under Windows NT and Windows 95/98 allowing unattended operation.

•	Fully multithreaded to give the maximum possible performance

•	Proxy server support through the SOCKS V4 interface making proxy configuration a simple task.

•	Address mapping functions for the dynamic translation of email addresses.

•	Free technical support via email.

•	Free users group, join in discussions about email issues.


SOFTWARE LICENCE AGREEMENT

SUBJECT OF AGREEMENT

FLOOSIETEK hereby grants to the CUSTOMER in consideration of licence fees paid by the CUSTOMER, a non-assignable, non-transferable, non-exclusive licence to use FTGate on a single computer (for the single mailbox version) or on  a single network server accessed by multiple computers (for the multi-user version) on the Terms and Conditions attached. Copyright and other intellectual property rights in FTGate shall at all times remain vested in FLOOSIETEK and the CUSTOMER's rights in FTGate shall be limited to those of a user licensed under the terms of this Agreement, such use to be limited to the CUSTOMER's internal business purposes only.

TERMS AND CONDITIONS

LIMITED WARRENTY

This software and accompanying written materials (including instructions for use) are provided "as is" without warranty of any kind. Further, FLOOSIETEK does not warrant, guarantee, or make any representations regarding the use, or the results of use, of the software or written materials in terms of correctness, accuracy, reliability, currentness, or otherwise. The entire risk as to the results and performance of the software is assumed by the CUSTOMER. If the software or written materials are defective the CUSTOMER, and not FLOOSIETEK or its dealers, distributors, agents, or employees, assumes the entire cost of all necessary servicing, repair, or correction.

The above is the only warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose, that is made by FLOOSIETEK, on this FLOOSIETEK product. No oral or written information or advice given by FLOOSIETEK, its dealers, distributors, agents or employees shall create a warranty or in any way increase the scope of this warranty and the CUSTOMER may not rely on any such information or advice.

Neither FLOOSIETEK nor anyone else who has been involved in the creation, production or delivery of this product shall be liable for any direct, indirect, consequential or incidental damages (including damages for loss of business profits, business interruption, loss of business information, and the like) arising out of the use or inability to use such product even if FLOOSIETEK has been advised of the possibility of such damages.

(2) COPYING OF PROPRIETARY INFORMATION

The CUSTOMER agrees  not to de-compile, reverse-engineer, reproduce, copy or duplicate any part or all of FTGate and to prevent its agents, employees, and representatives from de-compiling, reverse-engineering, copying or duplicating any part of or all of FTGate.

Should any portion of FTGate be de-compiled, reverse-engineered, copied or duplicated , the CUSTOMER shall immediately notify FLOOSIETEK of the

circumstances surrounding such event and shall assist FLOOSIETEK in enforcing its rights against any parties who are in violation of this Agreement.

Permitted exceptions to the above are for normal distribution purposes of the FTGate software, or for normal  back up or archival purposes.

(3) TERMINATION

FLOOSIETEK may terminate this Agreement upon thirty days written notice if the CUSTOMER fails to comply with any of the terms and conditions of this Agreement. In the event of termination, the CUSTOMER shall immediately cease use of FTGate and at its own expense, remove from its computers all copies (including on-line, back-up and archival) of FTGate and destroy them.

(4) NON-TRANSFERABLE LICENCE

The CUSTOMER acknowledges that FTGate is the sole property of FLOOSIETEK and agrees not to assign, sub-licence or otherwise transfer FTGate in any manner without prior written consent of FLOOSIETEK

(5) BINDING AGREEMENT

Upon acceptance of this Agreement by both parties, this Agreement shall constitute the entire Agreement between the parties and shall supersede  all other oral or written agreements or communications between the parties. FLOOSIETEK shall not be bound by additional provisions or provisions at variance herewith that may appear in the CUSTOMER's acknowledgement, purchase order, or in any other communication between the CUSTOMER and FLOOSIETEK.

(6) MODIFICATION/WAIVER

This Agreement may not be modified except by a written addendum signed by duly authorised representatives of both parties. No term or provision shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party claimed to have waived or consented.

(7) ASSIGNMENT

The CUSTOMER shall not assign, sublicense, or otherwise transfer to any other party all or any part of this Agreement, any interest herein or any rights hereunder.

(8) NOTICES

All notices and other communications provided  for or permitted under this Agreement shall be sufficient if contained in writing delivered by hand or registered certified mail or by facsimile addressed to the parties as set forth in this Agreement. Notification of critical errors concerning the FTGate Software should be communicated in writing to FLOOSIETEK by the other party. All such notices or communications shall be deemed received 2 working days after being sent. FLOOSIETEK reserves the right to communicate amendments to this agreement or all notices and other communications provided for or permitted under this Agreement by email to the other party.

(9) SURVIVAL

The CUSTOMER's obligations under paragraph (2) shall survive the termination of this Agreement.

(10) SEVERABILITY

If any provision of this Agreement shall be held void or unenforceable or contrary to English Law, such provision shall be deemed to have been excluded from this Agreement ab initio and shall not affect any other provision of this Agreement, the remainder of which shall be construed as if the excluded provision had never formed part of it.

(11) GOVERNING LAW

This agreement will be governed by and construed in accordance with the laws of England and the parties hereby submit to the exclusive  jurisdiction of the English courts.

ACKNOWLEDGMENT

By using FTGATE you acknowledge that you has read this licence agreement, understand it, and agree to be bound by its' terms and conditions. You also agree that the licence agreement is the complete and exclusive statement of agreement between the parties and supersede all proposals or prior agreements, oral or written, and any other communications between the parties relating to the subject matter of the limited warranty.


Statement of Year 2000 Compliance

FTGate has been designed to avoid any problems that may occur with the change of century. There are no dates stored internally in a manner that might make them susceptible to errors due to the century change. In addition FTGate does not process data from any other source where the date might be misinterpreted. FTGate is Year 2000 Compliant.

Note: This statement does not in anyway guarantee that FTGate will correctly operate across the Year 2000 boundary on any machine who’s BIOS and operating system is not Y2K compliant.


Disclaimer

The information in this document is subject to change without notice and is correct to the best of our knowledge at the time of publication. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose other than as part of the FTGate product, without express written consent of Floosietek Ltd.

You are granted permission to print one copy of this document as part of the FTGate Product licence agreement.


Contacting Floosietek

You can contact us using Fax, Post or email using the addresses shown below.

Electronic mail  Webmaster : webmaster@ftgate.com  Support : support@ftgate.com  Sales : sales@ftgate.com	Mailing lists  FTGate users group:  Send a message to joinftgug@ftgate.com with any subject
Newsgroup  A German newsgroup has been set up for our German speaking users by Adiscon. news://news.adiscon.com/adiscon.products.ftgate	Postal address  Floosietek Ltd  6 & 8 Charlemont Drive  Manea  Cambs  PE15 0GA England
FAX  +44-(0)1354-688426	Telephone  See below
Product Support Policy

Unlike most of our competitors, we do not charge for support. Before asking for support please remember to check this manual to see if your question is answered here. You should also check to see if you have the latest version. When asking for support please supply full details of the problem and if possible a debug log showing the problem. Our support email address is support@ftgate.com.

We do not supply telephone support. There are two reasons for this. First, the international nature of our business means that a large proportion of our customers would not be able to contact us during our office hours and second, when we have given telephone support we find that 95% of the questions are either not about FTGate or are answered in the manual. We actually find that support queries are answered faster and more efficiently by email than by telephone, and we have a superb track record for our support service. In extreme circumstances where we consider it necessary, our support team will phone you, but only after initial contact has been made by email describing the problem and including logs as described above. Please do not email us saying "phone me on xxxxxxx now" (it has happened many times).


FTGate Properties

FTGate comes with a utility that allows the administrator to configure the settings used in FTGate. This utility is the FTGate Properties Panel.

The properties panel can be started in one of two ways:

1.	By selecting the FTGate Properties icon from the FTGate Folder in the Start Programs menu group.

2.	By pressing the Properties button in the FTGate application (this option is not available when using FTGate as a service).

The properties Panel contains 16 pages which allow the administrator to configure the operation of FTGate.

Note: Mailboxes are configured in a separate utility, the Mailbox Manager.

After opening the Properties Panel a tabbed dialog box will be visible. The tabbed dialog box has tabs across the top of the panel. Clicking on a tab will display the appropriate properties page.

The available tab pages are:

•	Information – This shows the version information for different files

•	Startup – This determines how FTGate is started

•	Dialup – Configure the modem dial-up options and connection type.

•	Delivery – Configure the outbound delivery options.

•	MX Delivery – Configure the advanced Delivery settings for MX records and SOCKS V4 support.

•	Domains – Configure the domains that FTGate will use for mail processing.

•	SmartPop – Configure the collection of mail from remote POP3 mailboxes.

•	Security – Configure protection against unsolicited mail or illegal use of the server.

•	Address Mapping – Configure the options for programmed address changes.

•	Administration – Configure the Administration settings and achieving features

•	Registration – Configure and enter the registration details for FTGate.

•	SMTP Server – Configure the properties for the SMTP server

•	Schedule – Configure the timing for connecting via the modem or Proxy/router

•	Logging – Configure the options for logging server activity.

•	Ports – Configure the settings for the server TCP/IP ports.

•	Paths – Configure the disk locations used for data storage.


Information

The information page allows the administrator to see the version information for the various components that make up FTGate.

The above example is running on a Windows NT machine, thus there is information for FTGateNT. This would not be present for Windows 95 or Windows 98.

The modules that are listed are:

•	FTGate
The application version of FTGate. This version runs on all platforms.

•	FTGateNT
The Windows NT service version of FTGate. This version runs as a service on Windows NT and will not run on Windows 95 or 98.

•	Properties Tool
The FTGate Properties tool. Used for configuring the settings in FTGate. This version runs on all platforms.

•	Mailbox Manager
Used for  configuring the mailboxes in FTGate. This version runs on all platforms.

•	Core Library/Platform Library
The core functions of FTGate. This version runs on all platforms.


Startup Properties

The Startup Properties page allows the administrator to control the way in which FTGate starts. There are three possible ways for FTGate to start:

•	As an application
In this mode the administrator must start and stop FTGate manually by selecting the FTGate Server program icon from the Start/Programs/FTGate folder in the task bar. In this mode the administrator can see the FTGate status window and have access to the control functions on the user interface.
Hint: This icon can also be copied into the  Startup menu so that FTGate will run when a user logs on to the computer.

•	As a Windows NT service
This option is only available on a Windows NT system. In this mode FTGate starts as a service when the machine starts. The service version of FTGate (FTGateNT) does not have a user interface. To access the configuration utilities the administrator will need to select them from the Start/Programs/FTGate folder. To monitor the status of FTGate the administrator will need to use their web browser (remotely monitoring status).

•	As a Windows95/98 service
In this mode FTGate will start when the 95/98 machine is stated. However, the administrator will not be able to see the user interface. To access the configuration utilities the administrator will need to select them from the Start/Programs/FTGate folder. To monitor the status of FTGate the administrator will need to use their web browser (remotely monitoring status).

Install and run as a Windows NT service

When the user selects this option the FTGateNT service version will be added to the NT service list and started. When the user deselects this option, the service will be stopped and removed from the NT service list.

Note: The service will not start correctly if the application version of FTGate is already running. The administrator must stop the application version before selecting this option.

Install as a Windows 95/98 service

When this option is selected, Windows 95/98 is instructed to start the FTGate application when the system is started. Deselecting this option will clear the instruction. This option will not take effect until the machine is next rebooted.


Dialup Properties

The Dialup Properties page is where the user configures the way in which FTGate opens a connection to another machine.

There are three possible methods:

•	Connect using LAN ignoring schedule
In this mode the mail server expects to be connected to the Internet or other mail network through a LAN connection. This causes the mail server to send any outgoing mail instantly without using the schedule or waiting for a dial-up session. SmartPop will be checked at the interval specified in the SmartPop properties page. This setting is recommended for systems where the mail server has a permanent connection to the ISP.

•	Connect using a proxy server or dial-up router using defined schedule
In this mode the mail server is not permanently connected to the Internet or remote mail network and the responsibility for opening the connection lies with either another program (proxy server/NAT router) or piece of hardware (dial-up router). Selecting this option causes the mail server to send outgoing mail and check SmartPop mailboxes according to the schedule defined in the Schedule Properties Page. However, the mail server will not monitor any dial-up profile for connection. This option is recommended for systems where the mail server is connected using a proxy server that is on a different machine to the mail server or a dial-up router.
Note: With this setting the mail server will not detect an open connection, and thus outgoing mail will only be sent at scheduled times. In addition, some dial-up routers will not be able to open a connection before some of the tasks in the mail server begin to timeout. In this case the Proxy/Router Kick options should be used.

•	Connect using the following dialup connection using the defined schedule
This mode allows the mail server to monitor a specific Dial-up profile. When the schedule defined in the Schedule Properties requires a connection to be made, the mail server will dial the specified DUN Profile using the options specified. The mail server will also monitor the selected dial up profile and use any open connection on that profile for sending outbound mail. This setting is recommended for systems using a dial-up profile for connection to the Internet with either no proxy server or a proxy server running on the same machine as the mail server.

DUN Profile

This drop down box selects the Dial-up networking profile to use for connecting to the Internet.

Username and Password

These specify any username and password that are required during the logon process.

Number of attempts

This is the number of attempts FTGate will make to connect to the ISP before giving up and setting the connection to a stalled state.

Timeout waiting for logon

This specifies the maximum time from the start of dialing that FTGate will wait to become connected to the ISP before hanging up and retrying.

Inactivity Timeout

This specifies the amount of time to wait after the last data transaction before closing the open connection. For example: If the timeout is set to 30 seconds then the connection will be closed 30 seconds after the last data packet is transferred.

Restart After

This specifies the amount of time to wait before restarting the mail servers dial-up processing after the mail server has stalled.

Execute this command after logging on

This specifies a command, which must include the full path name, that will be executed when the dial up process is complete and the mail server is online.

Note: When the mail server is running as an NT service (see Install and Run as an NT service) any application that is launched will not have access to the user interface. Thus applications that cannot run unattended (e.g. notepad) should not be started using this option.

Proxy/Router Kick

This option can be used to force a Dial-up router to connect. To force a connection the user should specify the address and port of a machine that is not part of the local network, for example, the ISP mailserver port 25. Then when a connection is required the mail server will first attempt to open a connection to the specified machine. When the connection to the specified address and port is made, normal mail transfer will begin. If the connection fails, mail will not be transferred.

•	Address
This is the address of the Machine to which the mail server should to connect, e.g. post.demon.co.uk

•	Port
This is the port to which the mail server should connect, e.g. 25.


Delivery Properties

The Delivery Properties allows the user to configure the basic setting for outgoing mail (SMTP) connections.  The ETRN option is included here because it requires an outgoing SMTP connection to an ISP mailserver to be made before being executed.

ISP mails server settings

•	Mail Server Name
This is the name or IP number of the ISP mail server. A Mail server is required to receive the outgoing messages and route them to their final destinations.

•	Port
This is the port used for connecting to the ISP mail server. This is normally port 25.

SMTP Send Options

•	SMTP Delivery Timeout
This figure sets a time limit used when waiting for a response from a server. If no response is received for a period equal to the timeout then the transmit connection will be closed.

•	Wait for SmartPop to complete before sending messages
This option is used in cases where an ISP mail server will not accept mail until authentication has been received on their POP3 server. When selected, the outgoing mail will be held until ALL the defined SmartPop sessions have been completed

Concurrent SMTP Sessions

•	Maximum number of concurrent send operations
This controls the number of messages that can be sent concurrently. When set to one the messages are delivered one at a time. When set to two, two messages will be delivered at the same time and so on. This allows a better use of the connection and increases the rate at which message are delivered.

ETRN Options

•	Send an ETRN command to the ISP mail server to start remote delivery
When this option is selected the mail server will send an ETRN command to the Mail Server Address. Some ISP mail servers support this method of de-queuing mail.


Schedule Properties

The Schedule properties page allows the user to configure various conditions which will cause FTGate to initiate a connection to the internet via either a DUN Profile or a Router / Proxy server

Connect if a message of high priority is waiting to be sent.

This option causes the mail server to scan the headers of outgoing messages. If a tag indicating high priority is found the mail server will initiate a connection.

Schedule for connecting to Mailhost

This specifies the three simple schedule options.

•	Connect if outgoing message queue has ‘n’ messages waiting
This option will initiate a connection if there are the specified number of messages in the message queue.

•	Connect when the oldest message in the message queue is ‘n’ minutes old
This option will initiate a connection if the oldest message in the message queue is older than the specified time.

•	Connect if no connection has been made for ‘n’ minutes
This option will measure the interval since the last connection closed and will initiate a new connection after the specified time has elapsed.

Note: When using Advanced Delivery options, messages that are held in the queue due to an undeliverable or error status, will not be included in the counts for schedule options A and B.

Advanced Schedule…

Clicking this button will cause the Advanced Scheduling dialog to be displayed.


Advanced Scheduling

The advanced schedule options allow the administrator to select two lists of dedicated times when connections should be made using the dial-up profile specified in the Dialup Options page.

Use advanced schedule

This option enables Advanced Scheduling.

There are two lists Advanced Schedule A and Advanced Schedule B, each containing times and days when a connection should be made.

On these days:

This allows the administrator to select on which days of the week to use the advanced schedule.

Connect at these times:

This is the list of times that will cause a connection to be made.

To add to the list the administrator can enter a time into the time box (in 24hr notation) and click Add Time. The +/- keys will adjust the time in the time box by +15 or -15 minutes on each click.

To remove a time from the list, select a time to remove and click the Delete Time button.


Security Properties

The Security properties page allows the user to configure the mail server to prevent unauthorized relaying of mail and prevent unsolicited email. These options, together with those on the SMTP Server page, allow the user to configure the mail server to offer maximum levels of security.

Kill List

The kill list allows the administrator to prevent unsolicited email messages bothering the system users and can also be used to prevent unauthorized use of the mail server. The list may contain a number of email names or domains with wildcard matching. When a message is received which is from a name or domain that matches an item in the list the message will be deleted.

Entries in the list should be of the form ‘@domain.name’ or ‘user@domain.name’. The first form will block mail from any user at the specified domain while the second form will block only a specific user at a domain.

If mail that matches an entry in the kill list is received via the SMTP server, the server will reject the message. This usually causes the message to bounce back to the sender. If the message was received using SmartPop then the message will be deleted and no reply generated.

In the event of a message being deleted or rejected a notification will be placed in the event log.

A suitable source of names to be pasted directly into the kill file can be found at

http://www.webeasy.com:8080/spam/spam_download_table
http://www.world-net.net/spam/spamdomains.txt

The kill file is located in the FTGate program directory and is called 'kill.lst'.

•	Add Name...
Clicking this button brings up a dialog that allows the user to add a name to the list.

•	Delete Name
Selecting a member of the list and clicking this button will remove the member from the list

Relay Control

Mail relay is the process by which a mail server receives mail from a non local user and passes it to another non local user. An example of this would be a mail server at ftgate.com receiving mail from aol.com and sending it to demon.net. This is the method most often used by unsolicited bulk emails (Spam) to cover their trail. In general this will only be a problem for users with a LAN connection.

•	Permit unlimited relay though this site
This option will cause the server to accept any mail that it receives. This permits a site to send mail though the mail server to another site. It is recommended that this option is not enabled unless other precautions are taken to prevent mail system abuse.

•	Deny relaying to any site not listed below
This option will prevent mail being relayed unless the mail is to or from a mail user in one of the domains listed in the permitted relay domains.

Permitted relay domains

This is the list of permitted relay domains

•	Add ...
Adds a domain to the relay list.

•	Delete
Removes a selected domain from the relay list.


Logging Options

The mail server can generate a variety of messages to indicate the state of message processing. These messages are grouped into classes of message depending on their severity. The administrator can select the level of severity which will generate a message in the event log.

Details to log

This option selects the severity of the event that will be logged either to the status window and/or the event log.

•	Critical Events
These are events that are severe and that the postmaster or administrator should be aware of. It is possible to send a notification message for these events to the postmaster.

•	Warnings
These are events that should be noted.

•	Normal
These are status messages that relate to the normal transfer of messages.

•	Debug
These are additional messages that can be used to determine the cause of problems in configuration.

Log POP3 Access

If the logging level is set to Normal or Debug, the mail server will include in the log details of who accesses the POP3 server.

Send administrative alerts for critical events

When this option is enabled the mail server will send the postmaster a message each time a critical event occurs. This allows the postmaster to be aware of any potential problems without constantly having to check the status monitor or event log. The message generated will contain the last few events that occurred leading to the critical event, e.g. A critical event may be the failure of a dial-up attempt to the ISP.

Confirm that messages are sent.

When this option is selected the mail server will confirm each message that is sent. Each user that sends a message will get a confirmation message when the message is sent successfully. If the message is for more than one recipient and Advanced Delivery is being used the sender will receive a confirmation message for each recipient.

Log file details

This section determines what will be done with the events generated by the mail server

Write log data to disk

If this option is enabled a disk file will be created and each event will be written to the disk. The name of the file is controlled by the following options.

•	Generate a single log file
All events will be written to a file called ftgate.log

•	Generate a new log file each week
All events will be written to a file with the filename yyww.log where yy is the current year and ww is the current week.

•	Generate a new log file each day
All events will be written to a file with the filename yymmdd.log where yy is the current year, mm is the current month and dd is the current day.

Path for log file

This allows the administrator to specify a directory where the log file will be created.


Address Mapping

Address mapping permits the user to dynamically modify the recipient address of incoming messages received by the server.

When a message is received, the recipient address is compared to the entries in the
‘Map From’ list. If a match is found then the address is replaced with the corresponding entry in the ‘Map To’ list.

The Mappings are searched in order from the top down until a match is found. The order can be altered by selecting an entry and using the up and down buttons.

A single wildcard (*) entry is permitted per mapping.

Mapping Examples

Mapping mail for a domain into a single mailbox

Map From = *@inbound.com
Map To = mailbox1

All mail arriving that has a recipient that matches *@inbound. (e.g.  sales@inbound.com) would be mapped to the mailbox mailbox1. This causes all mail for the domain inbound.com to be placed in this mailbox.

Mapping one domain to another.

To change all recipients from one domain to another.

Map From=*@domain1
Map To=*@domain2

All mail arriving that is addressed to a user at domain1 will be changed to be addressed to a user at domain2, e.g. fred@domain1 would become fred@domain2.

Untangling an ISP POP3 mailbox name

Some ISP’s use a convoluted system for marking mail that is delivered to multi-drop mailboxes. Often this takes the form of  ‘mailboxid-user@domain’. To unravel this the following mapping would be used:

Map From= mailboxid-*@domain
Map To= *


Domain Properties

The Domains Properties page allows the user to specify one or more domain names that will be recognised as being for local mailboxes. Messages which are received with a name that matches either the primary or secondary domain names will be delivered to the local mailboxes (subject to further options).

The user can configure the handling of mail that is received for a domain listed but for an unknown mailbox in the Mail for unknown users section.

Settings for Domain

This is the default name of the domain. This option cannot be changed. Mail with this domain "@local" will always be delivered to a local mailbox.

Primary Domain Name

This domain name will be used for identification in all SMTP and POP3 transactions, and in recognising messages for local delivery.

Additional domain names to be used for accepting mail

This specifies additional (secondary) domain names that will be recognised as being for the local mail system.

In outgoing messages replace @local with

This causes the header of outgoing messages to be interpreted and all occurrences of @local replaced with the specified text. This allows mail users of the mail system to set their email return address to user@local. The mail server will then replace the @local with the defined string.

Mail for unknown users

This allows the user to specify what the mail server should do with mail that is addressed to the local mail system but has an unrecognised mailbox name.

•	Reject
Selecting this option would cause the message to be rejected.

•	Send to postmaster
Selecting this option would cause the message to be passed to the postmaster as an attachment for further handling.

•	Forward to the following mailbox
Selecting this option and specifying a mailbox name would cause the message to be sent to the specified mailbox as if the message had originally be addressed to that mailbox.

•	Forward
This would cause the message to be relayed to a further mail server for handling

Note : When receiving mail using SmartPop the above options will be ignored and mail for unrecognised users will be sent to the postmaster. This is to prevent mail loops from forming where the message is sent back to the ISP which places it immediately back into the mailbox for the mail server to download.


SmartPop Options

The SmartPop options page allows the administrator to configure the mail server to retrieve mail from one or more POP3 mailboxes. These messages can then be delivered to either a single defined user or to a local mailbox as specified in the message header (details below).

Enable SmartPop

This option enables the SmartPop account handling

•	UserID
This is the Id used to log into the remote POP3 mailbox

•	Mail server
This is the name or IP number of the POP3 mail server hosting the account

•	Deliver to
This option indicates if the mailserver is sending mail directly to a named mailbox

•	Port
This is the port to which the connection is made.

Add...

This button will create a new SmartPop account and will show the Add/Edit SmartPop dialog.

Edit ...

This button will open the Add/Edit SmartPop dialog for the currently selected SmartPop account.

Delete ...

This will delete the currently selected SmartPop account.

Options

•	Maximum number of accounts to check concurrently
This option permits the user to specify how many SmartPop accounts can be checked for new mail at any one time. For example, the user may define 5 accounts but set the maximum to 2. This would cause the mail server to wait until account 1 or 2 had completed before beginning checking account 3.

•	SmartPop Idle timeout of
In the event of a POP3 server failing to send a response to SmartPop for a period equal to this value, the connection will be closed.

•	When online, check for new messages every
This option specifies the period between successive checks, while the mail server is online, of the SmartPop accounts.
Note: If using a LAN connection (Dialup Options), there will be no scheduled connections and this option will be the only control of interval between SmartPop accesses.


Add/Edit SmartPop

This dialog specifies the account details for a SmartPop account.

Remote POP3 account details

•	POP3 UserId/Mailbox Name
This is the Id used to log into the remote POP3 mailbox.

•	Remote Server name or IP number
This is the name or IP number of the POP3 mail server hosting the account

•	Password
This is the password of the POP3 mailbox that the account is accessing

•	Connect on port
This is the port running the POP£ server on the host machine, normally 110.

•	Leave mail on server for n days
This option sets how long messages will be left on the Remote Server before being deleted. For Example, a setting of 5 would leave the mail on the remote server for five days after it had been retrieved, a setting of 0 will cause the mail to be deleted immediately after it has been retrieved.

Message Delivery

•	Allow FTGate to determine the recipient mailbox from the message header
If this option is selected then SmartPop will scan the message header of each message to be received. If the message contains any details that SmartPop can recognise as a mailbox, SmartPop will deliver the message to that user. Otherwise the message will either be sent to the postmaster as an attachment or forwarded to another user (see Domain Properties)

•	Deliver all mail from this POP3 account to the following mailbox
This allows the administrator to define a mailbox into which the mail will be delivered

SmartPop Header Scanning

SmartPop will scan the header of a message to determine who the local recipient is. There must be a valid address in the header that SmartPop can recognise.

The headers that SmartPop will examine are :

to:
cc:
resent-to:
resent-cc:
bcc:
resent-bcc:
x-listmember:
x-recipient:
envelope-to:
received:
delivered-to:

To permit matching of the addresses the administrator must enter the domain for the email address into the domains section. e.g. if the header contains

x-recipient: j.soap@somedomain.com

and SmartPop should deliver to j.soap, then the domain somedomain.com must be entered in the Domain Properties AND a mailbox j.soap must exist.

If a public mail system (e.g. yahoo.com) is providing the main email address then the administrator should still enter the email domain of the email address but should also enable forwarding of unknown mail in the domains properties section.

SmartPop cannot differentiate users based on comment fields in the headers.

Some ISP’s do not include a delivery address in the headers of messages placed in their POP3 mailboxes. In these cases mail from blind mailing lists may not be delivered correctly. Under these circumstances the  ISP should be contacted and asked to resolve the problem (see SmartPop Delivery Problems)


Ports Properties

The ports properties page allows the administrator to change the configuration of the ports being used by the mail server.

POP3 Server

The POP3 server is used by local mail clients to retrieve their mail.

Enable POP3 server for incoming connection on:

This option allows the administrator to enable or disable the POP3 server port. If the POP3 Server is disabled, users on the local network will not be able to retrieve their mail. When enabled the port will use the following options:

•	POP3 Address
This drop down lists all the available ports to which this server can be bound.

•	POP3 Port
This specifies the port that will be used to detect connections for this server. Specifying a port that is already in use will cause the server to fail to start.

•	POP3 Idle Timeout
If no data transfer occurs on an active connection for a time period equal to this value, the connection will be closed.

HTTP Server

The HTTP server is used to allow a web browser to access the mail server and view the status window.

To access the server use the URL http://mailserver:8080/ where mailserver is the name of the machine running the mail server.

Enable HTTP server for incoming connection on:

This option allows the administrator to enable or disable the HTTP receive port. When enabled the port will use the following options:

•	HTTP Address
This drop down lists all the available ports to which this server can be bound.

•	HTTP Port
This specifies the port that will be used to detect connections for this server. Specifying a port that is already in use will cause the server to fail to start.

•	HTTP Idle Timeout
If no data transfer occurs on an active connection for a time period equal to this value, the connection will be closed.

Finger Server

Enable finger server on port 79

This option allows the administrator to enable or disable the finger server. The finger server can be used by a finger client to view mailbox information. The finger server supports fingering for a specific mailbox or "all".


SMTP Server Properties

The SMTP Server Properties allows the administrator to configure the SMTP server used for receiving mail. The SMTP server is used to receive all mail from the local mail clients and also all SMTP mail from remote systems.

Note: If the SMTP Server is incorrectly configured then it will not be possible to send or receive mail using SMTP.

Enable SMTP server for incoming connection on:

This option allows the administrator to enable or disable the SMTP receive port. When enabled the port will use the following options:

•	Address
This drop down lists all the available ports to which this server can be bound.

•	Port
This specifies the port that will be used to detect connections for this server. Specifying a port that is already in use will cause the server to fail to start.

•	SMTP Idle Timeout
If no data transfer occurs on an active connection for a time period equal to this value, the connection will be closed.

•	Reject messages that have had more than
This option is used to prevent mail from looping endlessly between servers. Each time a message is passed from one server to another is said to have hopped. Normal mail would be delivered after about 5 hops. If the hop count reaches say 15 –20 then there would be a delivery problem and the message would be returned to the sender.

•	Reject messages that are larger than
This option prevents users sending messages that are too large through the system. For example a user might decide to send a 30MB application through the mail system and on a dial-up connection this could take hours to deliver. Hence the administrator can set the limit to a sensible level for their system.

Server Security

This section allows the administrator to configure the security for the SMTP server. The options in this section are based upon IP Numbers and thus offer the highest levels of security available. These options work in addition to those on the Security Properties Page.

Validate incoming servers with MAPS RBL list

This option will cause the mail server to check with the MAPS (Mail Abuse Prevention System) RBL (Real-time Black-hole List) whenever a new connection is made to the server. If the connection is from a server not listed in the MAPS list then mail will be accepted from that site (subject to the additional security options below).

For more details about the MAPS RBL see http://maps.vix.com/rbl/

Permit connections ONLY from the following addresses

Any addresses appearing in this list will be permitted to send mail through this site (subject to the restrictions imposed in the Security Properties page). Thus it would be possible to configure the mail server to only accept mail from a trusted set of mail servers and clients. See Security Issues)

•	Address
This is the dotted IP number of the address or address range required.

•	Subnet Mask
This is the subnet mask of the address range required.

•	Add
Pressing this button will present a dialog in which the address and subnet mask of a new entry can be made.

•	Delete
Pressing this button will delete a selected entry from the list.

Refuse connections from the following addresses

Any addresses appearing in this list will be blocked from using the server. This can be used to prevent known bulk email sites from sending mail. See Security Issues)

•	Address
This is the dotted IP number of the address or address range required. See Addresses and Masks.

•	Subnet Mask
This is the subnet mask of the address range required. See Addresses and Masks.

•	Add
Pressing this button will present a dialog in which the address and subnet mask of a new entry can be made.

•	Delete
Pressing this button will delete a selected entry from the list.


Paths Properties

This page allows the administrator to select the location that is to be used for storing files.

Mailbox Directory for domain 'local'

This specifies a directory that is to be used for storing the local mailboxes. The local mailboxes will be created as directories beneath this directory.

Temporary Directory

This specifies the location that is to be used as a temporary directory for incoming and outgoing messages.

Check for new files and deleted files every ...

This controls the frequency with which the mail server looks for manually created files and checks to see if any files in the output queue have been deleted.


MX Delivery Properties

The advanced delivery page allows advanced users to configure additional options for use when delivering mail to Internet addresses.

Deliver messages using DNS/MX records.

This option causes the mail server to deliver mail directly to the correct server for a particular address. This is done by requesting details of the delivery addresses from a DNS server. These addresses are called MX records.

DNS/MX Record Options

•	Primary DNS Server: and Backup DNS Server:
These are the names or IP addresses of the primary and secondary DNS servers to be used when resolving addresses using MX record resolution. The mail server will use the primary server unless it fails to respond in which case it will use the secondary server.

•	Forward undeliverable mail to ISP mail server for delivery
If a mail server cannot be found for an address or the designated mail servers do not respond, the mail server will attempt to deliver mail to the ISP mail server specified in the Delivery Properties Page.
Note : If the connection to a designated mail server times out, the message will be queued, not sent to the ISP mail server.

•	Hold undeliverable mail in mail queue and try again later
If a mail server cannot be found for an address or the designated mail servers do not respond, the mail server will keep the mail in the Undeliverable mail queue and try to send the mail at a later time.

Undeliverable mail queue options

•	Retry messages after
The mail server will attempt to redeliver any message that has been in the queue longer than the stated interval.

•	Return to sender after
The mail server will return the message to the sender if the message could not be delivered for the specified time.

SOCKS V4 Proxy server details

This section allows the administrator to configure FTGate to operate through a proxy server. When enabled FTGate will negotiate with the proxy server for all outbound connections making configuration with a proxy server a simple task. The proxy server must support SOCKS V4.

Note: This option is unavailable if MX record resolution is in use.

•	Use proxy server for outgoing SMTP and SmartPop connections on:
This option enables the support for proxy servers.

•	Address:
This is the address or IP number of the proxy server machine

•	Port:
The port on the proxy server that is configured for accepting SOCKS V4 connections.


Administration Properties

The administration properties page allows changes to the mail archiving, administrative password and the requirements for an administrator to log on.

Mail Archiving

Mail archiving is achieved by placing a copy of each message received by the SMTP server or processed by the spooler into a directory. After enabling the option the administrator should type in a path for the storage of the files. Each message will be stored in a separate file with the .txt extension.

Administrator Password

The administrator password section controls the use of the administrative password.

Note that this password is also used for administration control of the command processor.

•	Do not use a password to control logon
When this option is selected any user may use the FTGate user interface, Mailbox Manager or the Properties Panel.

•	Use a password to logon
When this option is selected users will be prompted for the password before they can access the FTGate user interface, Mailbox Manager or the Properties Panel.

•	Set Password
This option will display a dialog allowing the administrator to enter a new administrator password.

Forgotten Passwords

A forgotten password may be reset by re-installing FTGate. The password control will then be disabled allowing the administrator to set a new password.


Registration Properties

The Registration Properties Page allows the administrator to enter their licence details here.

For further details on obtaining a licence visit our web site at http://www.floosietek.com.

For the purposes of registration the following count as users/mailboxes:

•	Users Mailboxes

•	Auto-responder Mailboxes

•	List Mailboxes

•	Robot Mailboxes

The following do not count as users/mailboxes:

•	Alias

•	Command Processor

•	List Processor

•	Null Mailbox

•	Group Mailbox

For example a 5 user/mailbox licence would allow 3 User Mailboxes, 1 List and 1 Auto-Responder or 5 users or any other combination.


Security Issues.

To obtain the maximum level of security on your mail server you will need to consider the following aspects:

Will you be receiving mail with SMTP or using SmartPop ?

If  you are using SmartPop then you should configure your SMTP Server to only accept local connection. Do this by entering the appropriate IP address and subnet mask in the SMTP Server Properties page. You may also set the SMTP Server address to a local network address that is not visible to external machines and thus block access.

If you are using SMTP you need to consider enabling the MAPS RBL support and configuring the correct relay controls for your site.

The kill list can also be used to prevent misuse of your mail system. You can enter the email addresses of known spam sources and thus prevent them accessing the system.

Do I want my POP3 mailboxes to be available for access to machines outside my network.

If you want to make your POP3 server secure you should set the POP3 server address to a network address that is not visible to external networks.


What is MAPS RBL?

The MAPS (Mail Abuse Prevention System) RBL (Real-time Black-hole List) is a list of networks which are known to be friendly, or at least neutral, to spammers who use these networks either to originate or relay spam (unsolicited bulk email).

When enabled FTGate will validate any incoming sever connections with the MAPS RBL. If the MAPS system reports that the server is blacklisted then no mail will be accepted from that site.

See the MAPS RBL homepage for more information: http://maps.vix.com/rbl/
and for a full description of MAPS RBL see : http://maps.vix.com/rbl/rationale.html


Backing up FTGate?

Backing up FTGate involves archiving the following:

•	The ‘ftgate.reg’ file
This file is located in the FTGate Program folder and contains the settings for the various mailboxes.

•	The mailbox folders
These contain  the current unread text messages, auto text messages, mailing list members etc. The default location for these are c:\spool\mailbox.

This method can also be used to move FTGate between machines.

If for some reason the ftgate.reg file does not exist, one can be created in the following manner.

1.	Open the registry editor regedit.exe (start\run, type regedit and click OK)

2.	Open the folder HKEY_LOCAL_MACHINE

3.	Open the folder SOFTWARE

4.	Open the folder Floosietek

5.	Click on the folder FTGate

6.	Click the menu Registry\export registry file …

7.	Select a location and set the name to ftgate.reg

8.	Click save

The file can now be backed up.


Send a message from an application?

If you need to automatically send messages from a program you can do this without having to use the SMTP protocol (although this is the best method).

To do this you will need to create the two files in the inbox directory (c:\spool\inbox by default).

The files should be named
FILEXXXXX.TX2 and
FILEXXXXX.WR2
The XXXXX represents a number (say 00001) that is used to make sure that files names do not clash if more than one file is created in the folder.

The .TX2 file is a text file in the format of RFC822. This contains the Body and Header of the message with any attachments in either MIME or UUENCODE format.

e.g.
Date: Tue, 04 May 1999 11:11:18 +0100
Message-Id: f9905041111180001@mydomain.com
From: "Program" <postmaster@mydomain.com>
To: fred@somedomain.com
Subject: An RFC 822 MIME message
ReturnPath: <>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="==_1234567890==_"

This is a MIME-encapsulated message.

--==_1234567890==_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

This is a MIME format text message

--==_1234567890==_--

The .WR2 file is the SMTP envelope. It contains the address of the sender and the recipients each on a separate line

e.g.
postmaster@mydomains.com
fred@somedomain.com

Finally when both these files have been created they should be renamed.  The .TX2 file should be have the extension renamed to .TXT, and the .WR2 renamed to .WRK

The mail server will process the message the next time that it scans the inbox directory.


Creating a Domain or Multi-drop mailbox?

FTGate's Address Mapping features make this a simple task.

e.g. Mapping all the mail for users at somedomain.com to a single mailbox somedomain.

To do this you would create a mailbox called ‘somedomain’ in the Mailbox Manager and then create a mapping in the Mapping Properties Page as follows:

•	Map From : *@somedomain.com

•	Map To: somedomain@local

The task is then complete.


Dynamically forwarding mail?

To dynamically forward mail you should create a mapping (see Mapping Properties Page) from the source address to the target address, e.g.

Map From: sales@ftgatent.com
Map To: sales@ftgate.com

Note that you would need to add ftgate.com to the permitted relay list or the message would be rejected.


Configuring TCP/IP network

Each PC on the local network that will be required to access FTGate will requires that the TCP/IP network protocol is installed. For details on installing TCP/IP please see the information supplied with your PC.

Below is a quick guide to setting up a TCP/IP network.

Network IP Numbers

On a TCP/IP network, each machine is assigned a number called its IP number. You can assign a name to the number by making an entry in a file. This file is named ‘hosts’ (note that it has no file extension). The file is located in the Windows directory on a Windows95 machine and in the system32\drivers\etc directory on a Windows NT machine.

An example of its contents is :

192.168.0.1 Server
192.168.0.1 mailhost
192.168.0.2 ClientA
192.168.0.3 ClientB
192.168.0.4 ClientC
127.0.0.1   localhost

This has six entries for 4 machines. The entries for ‘Server’, ‘ClientA’, ‘ClientB’ and 'ClientC' specify the IP addresses that will be used to access machines with those names. The entry for ‘mailhost’ allows the server to be referred to both as ‘Server’ and ‘mailhost’. The last entry ‘localhost’ is a special entry that allows the machine on which the hosts file is located to refer to itself as ‘localhost’.

Single PC

To access FTGate on a single PC you should add a ‘hosts’ file with the entries

127.0.0.1 mailhost
127.0.0.1 localhost

Network

This is an example of the most common setup in which FTGate is used.

It is recommended that a ‘hosts’ file be created for the local network, and that a copy is placed on each machine on the local network.

A single PC with a modem is used to connect to the Internet using either Windows 95 Dial-up Networking (DUN) or Windows NT Remote Access Services (RAS).

Internet - service provider

•	The Dial-up connection name specified in DUN/RAS :
FTGate Internet Connection

•	The Mail host name where outgoing mail is to be sent :
smtp.isp.com

•	Domain Name for our network:
newdomain.com

•	POP3 Host when SmartPop is to be used (this is where mail is to be retrieved from)
POP3 Mailhost : pop.isp.com
Account Name : newdomain
Password : pword

Server - PC running FTGate with the dial up connection.

IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0

ClientA - Network Machine

IP Address: 192.168.0.2
Subnet Mask: 255.255.255.0

ClientB - Network Machine

IP Address: 192.168.0.3
Subnet Mask: 255.255.255.0

ClientC - Network Machine

IP Address: 192.168.0.4
Subnet Mask: 255.255.255.0

A ‘hosts’ file (shown above) would be placed on each machine.

FTGate settings

In this example FTGate would have the following settings in the properties dialog.

Delivery Properties

Mail Server Name = smtp.isp.com

Dialup Properties

Dun Profile = FTGate Internet Connection

Domains

Primary Domain = newdomain.com

SmartPop

User Id = newdomain
Mail Server = pop.isp.com
Deliver to = blank
Password = pword
port = 110

At this stage the network is ready for the Mail clients to be configured.


Addresses and Masks

IP Number

The Internet uses 4 byte addresses to identify all the computers and devices connected to it. Each device has a unique number and this number is used in all communications with that machine. That number is called the IP Number (Internet Protocol). An example of that number might be 158.152.1.43. When you enter an address into a web browser , FTP Client or mail client, the software executes what is called a DNS lookup. This converts the address into the 4 byte number.

Subnet Mask

Often an organisation will be allocated a range of addresses. For example all the numbers between 158.152.1.128 and 158.152.1.255. This range is described as a subnet. The usual way of describing a subnet is by quoting the first IP number in the range and a SUBNET MASK. The subnet mask is another 4 byte number. This number is used in a binary comparison of the IP number.

An IP Number of 158.152.1.128 and a subnet mask of 255.255.255.128 describes a 128 address subnet.

To determine the range take the IP number and subnet mask and convert them to binary. Then logically AND them together. Any bits passed ignored by the subnet mask are part of the subnet.

When comparing two IP numbers to see if they are in the same subnet, each number has the subnet mask applied to them. If the resulting numbers are equal then they are in the same subnet.

This is the method used by FTGate when comparing addresses with masks.


Moderating a mailing list?

A moderated list is a list in which each message sent to the list is vetted by the list owner before it is distributed.

A message that is sent to a moderated list by a list member will be passed to the list owner. The list owner can then decide if the message is suitable for the list, and if it is, forward the message back to the list. The message would then be sent to all the members of the list.


Moving FTGate to another machine?

This is how to move across machines (NT or 95/98).

1.	Export the Floosietek part of the system registry on the source machine and place it in the FTGate directory on that machine. See Backing up FTGate?

2.	Install FTGate on the new machine.

3.	Copy the FTGate directory, spool directory and any other directories to the new machine, keeping the paths EXACTLY the SAME.

4.	Merge the registry details into the second machine.

5.	Start FTGate.


Managing several domains?

You can manage several domains with unique users by using mappings.

For example:

There are two domains domain1.com and domain2.com. In each domain we require the  mailboxes sales and support.

1.	First create 4 mailboxes:
domain1.sales
domain2.sales
domain1.support
domain2.support

2.	Then add two mappings:
*@domain1.com -> domain1.*
*@domain2.com -> domain2.*

You can now handle two domains with multiple users.


Polling SmartPop in a service?

Launch your web browser and connect to
http://127.0.0.1:8080/
on the server on which FTGate is running or
http://yourserversIPnumber:8080/
from any other machine on your network with access to the server.

Click on the link to the status page. On the status page there is a ‘Poll SmartPop’ button. This will force the connection to the ISP and retrieve any mail in your pop3 mailbox(s). Note that you will need to set your browser’s caching to refresh on every visit to the page or the connection will only be made the first time.


Monitoring the FTGate service?

If you want to monitor the state of the FTGate service, launch your web browser and connect to http://127.0.0.1:8080/
on the machine running FTGate or
http://yourserversIPnumber:8080/
from any other machine on your network with access to the FTGate machine/server.

 If you are unable to connect you will need to ensure that the http server is enabled in FTGate on the Ports properties page.


Registration Codes not working?

You need to enter the registration codes exactly as they appear on the emailed notification of your licence number, with no extra spaces but with the – between the two sets of numbers. Don’t forget to include any punctuation marks as it appears on the emailed notification.

Then shutdown and restart FTGate.

FTGate sends registration warning messages in the last ten days before it expires. These messages are generated and sent automatically by your copy of FTGate. If you have entered your registration codes but you are still receiving expiry messages it would indicate the registration codes are not entered correctly or FTGate was not stopped and restarted after the codes were correctly entered.

You need to ensure that they are entered correctly then shutdown and restart FTGate for the codes to take effect.


Kernel32.dll crash?

You need to download the latest service pack from the Microsoft web site at http://www.microsoft.com (you may need to search around a little).


Rnaapp error.

'Rnaapp' is part of the Microsoft core systems. You could try downloading the latest service pack from the MS web site at www.microsoft.com (you may need to search around a bit).


Relaying Denied Problems?

The relaying denied error message is caused by one or all of the following:

The user name in the mail client of the sender of the message does not match one defined within FTGate. You need to change either the mail client settings or create a mailbox with the users name within FTGate.

The domain name in the mail client of the sender is not set to the same as the Primary domain or one of the additional domains listed in the additional domains for accepting mail field, on the FTGate Domains properties page.

You have not added the domain name to the ‘Permitted relay domains’ on the Spam properties page. This item is most relevant if you are an ISP.


Changing the address to which FTGate forwards my mail to?

This can be done by the administrator in the Mailbox Manager or it can be done remotely using a mail message to the command processor. You would need to send a message to the command processor like this:

TO: command@your.domain.com

Subject: Blank

Message body

Open mailbox [mailbox name] [password] (no [ ] required)

Set forwarding [new address in full] (no [ ] required)


Using a Novell network?

FTGate will communicate with a Novell system and any machine connected through it. Although you will need to run FTGate on a Win 95, Win 98 or Win NT machine connected to the Novell network, you will also need to have TCP/IP installed & working correctly on all machines that require a connection to FTGate.


Using a Mac network?

FTGate will communicate with a Mac system and any machine connected through it. Although you will need to run FTGate on a Win 95, Win 98 or Win NT machine connected to the Mac network, you will also need to have TCP/IP installed & working correctly on all machines that require a connection to FTGate.

A technical article is available on our web site describing one such setup. See http://www.floosietek.com


Retrying failed dial-up connections?

To get FTGate to re-try after a failed dial up attempt, you need to increase the re-try setting on the FTGate>Properties>Dial-up properties page, to say 3 or 5.

You should also set the link stalled setting to 15 or 30 minutes, in order to avoid the connection being ‘down’ for too long.


Dial-up router failures?

This is caused by the router not being set up correctly. It is failing the connection from FTGate before the router is on line. You should contact your router supplier for advice on the settings to change.

Additionally you can use the Route/Proxy Kick options. See Dialup Properties.


Anti-virus software?

The following are four packages that are suitable for use with FTGate.

•	MimeSweeper from Content Technologies.

•	Webshield from Network Solutions (McAfee).

•	Norton AntiVirus for SMTP Gateways from Symantec.

•	InterScan Viruswall from Trend Micro.

Note: This is not an ordered list, there is no implication of suitability for the job and this list is just for your reference. These are amongst the ones we will be testing in the coming months. Instructions to help with the set-up of each will be posted to the technical articles pages, as they are finished.


SMTP Server initialisation failed?

This error is caused by one of two things:

You are trying to run both the service and application versions at the same time on the same machine. You need to stop both versions and re-start one or the other, NOT both.

You could be running another application/service that is capturing the ports, i.e. a proxy server or another mail server. You need to disable the POP & SMTP servers in the Proxy server and re-start FTGate.


How much is a licence upgrade?

We are happy to upgrade your licence to include a larger number of users. You need only pay the difference in price between your current licence and the new one.

To order your upgrade just follow the ordering links to the Upgrade page on our web site at http://www.floosietek.com . You will need the current license details to hand when you enter the details on this page.

You will then receive your new registration details by Email as soon as we have processed your order.


Mail client connection failures?

To access FTGate from a mail client you must first install the TCP/IP protocol on all machines from which you want to be able to access FTGate. These machines should then be given an IP number which will also be entered in the 'hosts' file in your windows directory. c:\windows\hosts

Note: The hosts file has no extension, there is a hosts.sam file located in your windows directory to help with the syntax. You should then be able to access FTGate from the mail clients.

If the mail client still cannot connect to the server, you should try to ping the server. To do this type ‘ping IPAddress’ at the MSDOS prompt.

An example of a successful connection is shown by:

>ping 194.70.211.254
Pinging 194.70.211.254 with 32 bytes of data:
Reply from 194.70.211.254: bytes=32 time<10ms TTL=128
Reply from 194.70.211.254: bytes=32 time<10ms TTL=128
Reply from 194.70.211.254: bytes=32 time<10ms TTL=128
Reply from 194.70.211.254: bytes=32 time<10ms TTL=128

A failure example is:

>ping 158.152.1.129
Pinging 158.152.1.129 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

If the connection fails then you should look at the network settings and wiring to find out why the client cannot ‘see’ the server.

If the connection passes then you should check that you can connect to FTGate. To do this type:
telnet server-IP-number 110
at the command prompt.

If you make a connection then you need to check the settings in the mail client. If not, then you need to make sure that FTGate is running, that the POP3 port number (See Ports Properties Page) is 110 and that the  POP3 Address is ‘Any Unbound Address’.


Connecting to my ISP unattended?

FTGate can connect to an ISP unattended.

•	To do this on an NT machine you will have to configure RAS to have a dialing script - see the RAS documentation for this.

•	On a Windows 95/98 machine, you will need to create, define and configure a Dial-up Networking profile with the correct information to connect to the ISP. i.e. user name and password.

You can then use FTGate's Scheduling options to control when mail is retrieved and/or delivered.


Connecting to Demon Internet?

Demon Internet's mail gateway machine is called post.demon.co.uk. A suitable script for dialing to Demon is:

proc main
waitfor "ogin:"
delay 1
transmit "yourlogin^M"
waitfor "assword:"
delay 1
transmit "yourpassword:^M"
waitfor "otocol:"
delay 1
transmit "PPP^M"
waitfor "ELLO"
endproc


Getting support?

First line support to both customers and resellers is via email only, to support@ftgate.com.

The diagnoses of problems usually involves examining the contents for the FTGate portion of the registry key and a debug log showing the problem. These items are too large to be described over the telephone. Because of this we insist that first line contact is by email.

When contacting us your email should contain the following:

•	The ftgate.reg file from your FTGate Program Folder

•	A debug log showing the problem

•	Your contact telephone number.

•	The country you are in.

When we receive this information we will do one of two things depending on the nature and urgency of the problem. We may either email a response, or phone you.

We also advise that you should join the users group, as this is a valuable source of information.

You can join the users group by emailing joinftgug@ftgate.com with no subject and ‘subscribe’ (no quotes) in the message body. You then post to the group by mailing ftgug@ftgate.com


How do I use an Auto-responder?

An auto responder is a method of maintaining a catalogue of automated responses to messages. An Auto-Responder works by looking at the subject of an incoming message and searching its keyword list for that subject. If a match is found then the Auto-Responder creates a response to the incoming message. The response consists of a block of text and an optional file attachment. These are combined into a single outgoing message which is formatted in the MIME format.

To use an Auto-Responder you must first create an Auto-Responder mailbox. This is done from the Mailbox Manager. In the Mailbox Manager click on the Add button, then type in the name of the new Autoresponder (say newauto) and select the Auto-Responder option.

Then hit the create button.

The  Edit Auto-Responder Dialog will now be displayed.

Type in a suitable Real Name and click on the Add button.

Now change the keyword to the one that you would like (say prices), type in a suitable response text for the message, and if desired enter the name of a file to attach.

Now click SAVE and then OK.

Finally send a message to the auto responder with the subject line set to the keyword.

e.g.
To: newauto
subject: prices

You will then get a response from the Auto-Responder containing the text and any attached file you specified.


Using Mail Clients:

This section details the steps needed to configure various mail clients for use with the mail server.

The examples will use an example network shown below and assumes that the network is operating and there is either a DNS configured or each machine has a local 'hosts' file.

 For details on how to configure a network, DNS and hosts file see the section on “Configuring a TCP-IP network”.

This sample network has 4 machines. Server is the machine on which the mail server is running. ClientA, ClientB and ClientC are machines that will have mail client software running on them.

The examples will show how to configure the mail clients on the machine ClientA for a user "Joe Soap" with an email address of "j.soap@ftgate.com". Configuration of the other machines will be similar.

You may wish to print this page to make following the examples easier.

Examples exist for the following mail clients :

•	Eudora

•	Microsoft Internet Mail (Explorer Mail)

•	Microsoft Messaging Client

•	Netscape Navigator Mail

•	Netscape Communicator

•	Pegasus

•	Outlook Express


Configuring Eudora

Install Eudora (this example uses Eudora Light V3.0.1).

After installation start Eudora. You will be prompted for Options.

Select Getting Started

1.	set POP account to j.soap@server

2.	set Real Name to Joe Soap

3.	set Connection method to "Winsock"

4.	select Personal Info

5.	set Return Address to j.soap@ftgate.com

6.	select Hosts

7.	set SMTP to server

8.	set Finger to server

Click on OK.

Eudora is now configured.


Configuring Microsoft Internet Mail (Explorer Mail)

Start Internet Mail

1.	select Mail then Options

2.	select Server

3.	set Name to Joe Soap

4.	set Email Address to j.soap@ftgate.com

5.	in Servers

6.	set Outgoing Mail (SMTP) to server

7.	set Incoming Mail (POP3) to server

8.	in Logon Settings

9.	select Logon Using:

10.	set Account Name to j.soap

11.	set Password to the account password

Click OK.

Microsoft Internet Mail is now configured.


Configuring Microsoft Messaging Client

If Windows Message is not already on the PC.

Start the control panel and double click on the Add/Remove Programs icon. Then select the Windows Setup Tab and then double click on the Windows Messaging item. Then check the Windows Messaging item, then click on OK. Click on OK to close the Add/Remove Programs window. You may be prompted for a disk or CD at this point. Insert your Windows CD and click on OK. Follow any further instructions required to load the software onto the PC. Finally you will be prompted to restart the computer.

When the computer reboots you will be asked to configure Windows Messaging. Click Cancel and then Yes.

After Installation of Windows Messaging you should do the following to finish configuring the mail client.

First you must add the Internet Mail extensions to the messaging client. These are available from either the Plus CD-ROM or from Microsoft's web site http://www.microsoft.com/windows95/info/inetmail.htm .

1.	After installing the Internet Extensions you will be prompted to restart the PC. Do so.

2.	Start the PC and go to the control panel and start Mail and Fax.

3.	Click on Add...

4.	Make sure that Internet Mail is selected.

5.	Click Next.

6.	Select Network (DO NOT SELECT MODEM)

7.	Click Next.

8.	Enter the name of the profile Internet Mail

9.	Now enter server.

10.	Click Next.

11.	Select Automatic

12.	Click Next.

13.	Enter your email address j.soap@ftgate.com and real name Joe Soap

14.	Click Next.

15.	Enter your mailbox name j.soap and password

16.	Click next

17.	Select an address book

18.	Click next

19.	Select a message store

20.	Click next

21.	Enter any passwords you are asked for.

22.	Click finish.

23.	You should now be back in the profiles dialog. In the drop down box select ‘Internet Mail' as the default profile used 'When starting Microsoft Exchange'.

24.	Click on Close.

25.	Windows Messaging is now configured.


Configuring Netscape Navigator Mail

Install and then run Netscape Navigator.

1.	select Options then Mail and News Preferences.

2.	select Servers

3.	set Outgoing Mail (SMTP) Server to server

4.	set Incoming Mail (POP3) Server to server

5.	set POP3 User Name to j.soap

6.	select Identity

7.	set Your Name to Joe Soap

8.	set Your Email to j.soap@ftgate.com

9.	set Reply-to Address to j.soap@ftgate.com

10.	click on OK.

Netscape Navigator is configured for Email.


Configuring Netscape Communicator.

Install and then run Netscape Messenger.

Select Edit then Preferences

In Mail & Groups select Identity

1.	set Your Name to Joe Soap

2.	set Email address to j.soap@ftgate.com

3.	in Mail & Groups select Mail Server

4.	set Mail Server user name to j.soap

5.	set Outgoing mail (SMTP) server to server

6.	set Incoming mail server to server

7.	set Mail server type to POP3


Configuring Pegasus Mail.

The following steps are required to configure Pegasus Mail.

1.	install Pegasus

2.	start Pegasus and select the single user option.

3.	Pegasus will report that it has found Winsock support. Click Yes.

4.	Pegasus will display a Mail Options window.

5.	under For receiving mail

6.	set POP3 Host: to server

7.	set Username to j.soap

8.	set Password to the correct password

9.	under For sending mail

10.	SMTP Host: server

11.	click Advanced Configuration Options

12.	set From field to j.soap@ftgate.com

13.	click on OK

14.	click on OK

Pegasus Mail is now configured.


Configuring Outlook Express

The setup of Outlook Express is as follows:

1.	If Outlook Express is already installed, start the program and select Tools/Accounts and then click Add->Mail . If you are installing for the first time Outlook Express will begin to prompt for your account details.

2.	Enter the display name for your account. This will be your full name.

3.	Click Next.

4.	Enter your Email address.

5.	Click Next.

6.	Select POP3 as the incoming mail server type.

7.	In the Incoming mail server type the name of the machine running FTGate.

8.	In the Outgoing mail (SMTP) server type the name of the machine running FTGate.

9.	Click Next

10.	Enter the mailbox name (this will be the same as the first part of your email address)

11.	Enter the password for the mailbox.

12.	Click Next

13.	Type FTGate Mail

14.	Click Next

15.	Select "Connect using my local area network (LAN)"

16.	Click Next.

17.	Click Finish.

This correctly configures Outlook express for use with FTGate.


SmartPop mail delivery problems

We are often asked "Why do I get the message 'SmartPop Mail Delivery Failure?". This article will explain why it happens and what can be done about it.

History of SmartPop.

Many ISP's offer multiple mail addresses with their mail accounts, but place all the messages in a single mailbox. So for example you might have the email addresses user1@domain.com, user2@domain.com and user3@domain.com, and all the mail might be placed in a mailbox domain@mail.isp.com. This type of mailbox is commonly known as a domain or multi-drop mailbox.

The problem with a multi-drop mailbox is that the first person to connect to it gets all the mail regardless of who it was sent to. SmartPop solves this problem by retrieving the mail messages and then delivering to the appropriate local mailbox.

To deliver the mail from the example above, the administrator would install FTGate, create three mailboxes (user1, user2 and user3). Enter the domain "domain.com" into the FTGate Domain properties and create a SmartPop account for domain@mail.isp.com. SmartPop would then collect the mail and deliver it to the appropriate user.

What is a message

An Internet mail message consists of two parts, the header and the body. The header contains information such as who the message is from, who it is to, the subject, when it was sent etc. The body is the text of the message.

How is mail transferred around the Internet.

Most mail is transferred from point to point using a protocol called SMTP (Simple Mail Transfer Protocol). This protocol transfers a message by making a connection to a destination computer, sending the Envelope of the message and then sending the message. The Envelope of the message contains the senders email address and one or more recipients addresses.

By the time the message reaches your ISP's machine the envelope will usually consist of the sender and one recipient. It is this recipient address that the ISP uses to determine which mailbox should be used for storing the message. In the above example a message to user1, user2 or user3 would be written to a single mailbox (domain@mail.isp.com).

After the mail is placed in a mailbox it can be retrieved using a protocol called POP3 (Post Office Protocol version 3). This protocol transfers the body of the message. The problem with this protocol is that it was only designed to access mailboxes that had mail for a single user.

What can go wrong to cause delivery failures ?

A message is in the ISP mailbox for an address that doesn't have a local mailbox.
If using the above example a message was in the ISP mailbox addressed to fred@domain.com, SmartPop would not be able to deliver it as there is no mailbox or alias for that name. This can be fixed by creating the mailbox or alias.

The message was sent to the ISP mailbox by a mailing list that doesn't include the recipients address.
Many mailing lists do what is known as blind mailing. This is where the message header has a TO: line to say testlist@listserver.com. Obviously there is no mailbox on the local mail system called that, so this causes an error.

The second problem is harder to fix and will require your ISP's help. I will describe the problem using an analogy with the postal mail system.

A letter is sent inside an envelope (SMTP is the envelope) addressed to Fred Bloggs. The letter inside starts Dear Sir (the message header). The postman (your ISP server) brings the letter to your office but before delivering it takes the letter out of the envelope and puts only the letter through the postbox at the front door (ISP pop3 mailbox). Now when your secretary (FTGate) collects the mail, there is no indication as to who the "Dear Sir" is, so it cannot be delivered.

The Solution

Many ISP's copy the envelope (SMTP) address into the message header, that way the messages recipient address can always be found. There is no standard for the way that they do this and FTGate has been coded with most of the methods in use. This allows SmartPop to read the message header and deliver to the correct mailbox.

If your messages are being delivered as "SmartPop mail delivery failure", you should check the header of the attached message to see if the correct address exists. If it does not, you need to contact your ISP and arrange for them to either add the additional field for the envelope to the message headers or give you an SMTP feed. If they are not prepared to do this then consider changing to another ISP as a multi-drop mailbox will not work correctly without the addition of the extra header information.

An example of a message (sent to user1@domain.com) that has not had the ISP include the additional envelope data might be:

Date: Fri, 26 Jun 1998 08:40:45 -0400
To: ftgug@ftgate.com
From: Fred Bloggs <fred@bloggs.com>
Subject: Version 2.1.0.5 and "Received... for"
Reply-To: ftgug@ftgate.com
x-listserver: ftgug@ftgate.com

and an example that has had the additional information included might be:

X-Recipient: user1@domain.com
Date: Fri, 26 Jun 1998 08:40:45 -0400
To: ftgug@ftgate.com
From: Fred Bloggs <fred@bloggs.com>
Subject: Version 2.1.0.5 and "Received... for"
Reply-To: ftgug@ftgate.com
x-listserver: ftgug@ftgate.com

Note the additional line highlighted line.

We hope that this goes some way towards explaining the problem.