"Made for the Mac and Helix™ Only"

HeliMailServer 3 Setup
 


Double click the Application icon

Select the Preferences menu in the “Tools” menu. These preferences concern standard mail activities..

Please note that although the fields contain data by default (for the sdk) you must enter the correct data for your collection.

 

Helix Application : Select the application running the Collection. (You can ignore “Remote” as it is not implemented in this version.)   Collection Name : The name of the collection User Name : the name of the user that you would log in as. Please note HeliMailServer 3 will log in as this user so ALL views accessed by HeliMailServer 3 MUST be in the chosen User menus, AND those views HAVE to be compiled. The User name therefore is NOT the user name required for E-mail (POP) access.

Password : requires the password for the collection user. Don’t forget, the password is case sensitive.

E-Mail account info is stored in :
Relation Name : The “Custom” name of the relation that contains the user mail information.
Form Name : the “custom” name of the view that supplies this info. (list or entry form). Note that HeliMailServer 3 can handle multiple mail accounts.

E-Mail InBox (Entry view) is in :
Relation Name : The relation containing the AE entry view
Form name : The name of the AE entry view for incoming mails.

E-Mail OutBox (List View) is in :
Relation Name : The relation containing the AE mail out list
Form name : The name of the AE out list containing the queued mails to be sent.

E-Mail Checkout (Entry view) is in :
Relation Name : The relation containing the AE Checkout entry form
Form name : the name of the AE entry view that marks mails as sent
Once all the fields entered
Click on “Save”.

This should now have created the HeliMail Prefs in the preferences folder.

Registration.

HeliMailServer 3 requires a valid registration in order to function. It will run in demo version mode if no registration is found in the collection
The registration is to be held in the Registration Relation of the collection. The registration file MUST BE LOADED into the Registration view. No records must be deleted in this relation. Loading a registration must enter the initial record OR overwrite the existing record. Any other method of entering data is not acceptable!!!!! Do not delete the record in this relation…..

Entering the Email account info in Helix.

Open the user preferences in the Helix collection

 

This is where you enter your email account info.

POP (incoming) : Enter the pop address
SMTP (Outgoing) : Enter the smtp address
User: Enter the username of the account
Warning : User Name is NOT your User Name for accessing the collection. It is your user name for your email account as provided by your ISP
Password : Enter the account password for mail reception (if reception enabled)
Delete on server : This field defines whether or not an email is to be deleted from the POP server once it has been downloaded.
Attachments folder (In) : This designates the folder where all incoming attachments for the account must go.
Email Address : Enter the account email address

Send only : this field defines whether an account can send only or send and receive mails.


Now there’s just one last thing to do.
Set the send and retrieve frequency
Go back to HeliMailServer 3
Click on the “Batch Timer” list item and enter the number of minutes between each batch.


Quit HeliMailServer 3 and restart.

 You are now set for sending and retrieving Email.

To stop the Batch cycle
Click on the Stop Batch Cycle button

Clicking on Start Batch Cycle will launch a cycle 10 seconds later.



Global Settings

 

HeliMailServer 3 has a predefined set of settings that define the relations and views to be used for retrieving and entering data under various situations. A number of these situations are related to collection syncronisation via mail and are not available in this version. Whether or not an option is valid for this version is indicated . See below
 
The relation and view columns can be edited by clicking the cell and typing in a new value


 
The following parameters can be set in this version 
Helix Batch Info
This is a view in the collection that receives the next batch info so that users of the collection can see when the next collect is to occur.
HTMLCounter
Used for storing an incremented number in Helix. Retrieved by HeliMail on launch to increment the Html files  recovered in mails. When an incoming mail has a html part  this part is written to disk and the filename “HtmlFile x.html” is indicated as an attachment  in the record. See the sample collection for how this operates.
Error indications
Error messages received can be sent back to the collection, For example a client could control these messages and undertake the necessary remedial action.

The Save Global Settings saves all the global settings that can be defined from HeliMailServer 3. 

Attachment Option
Using the new load attachment functionality.

This version enables you to load attachment documents into your collection either :
- on the machine serving your collection
or
- on a Helix Client machine on the network

Setting up

- Stop the batch cycle if active
- select the "Attachment option" list item
- click Load Attachments

Setting a "Local" import.

There are 2 possibilities for loading documents locally. You are either using a  Helix Rade/Engine or  a Helix Server.
If you are using a Helix Rade or Engine
- check the Local Application checkbox
If you are running a Helix Server
- you will have to run a Helix Client on the same machine and check the "Client" Checkbox

Setting a remote import

-check the "Remote" checkbox
the "Use Port" field appears
- Enter 9090 - this is the port to be used to communicate with the Doc Loader application on the client machine. The "helper' only works on port 9090 for the moment.



More Info

Clicking the “More info” arrow enlarges the window to display the following :

 

The window now displays the following info
Batch Info: The times of the next Mail out and Mail In operations
 Note the “Get next mail in” time  is sent to the collection. If your collection does not have valid relation and view to receive this info then a “relation does not exist” message will appear in the Logfile.
Logging off : if this is checked then the log field is not updated. If it is not checked then the last “log” operation is displayed. To see the complete log file click on the “Read Log File “ button.

This opens the HMLog files and displays the content as per the time opened.

 
 

These files  are useful to return information should a bug/problem be encountered.
The Tools menu


 

Preferences just opens the initial parameter setting form for the basic appleevents.
MailTimer reopens the MailTimer window.