Re: SSL Setup

Hi Bill.Hewitt,

Es war einmal 23.04.2002 16:39:27  mit dieser Mail:

> Would someone please be so kind as to post the full setup instructions
> in order to enable SMTP over SSL to MyRealBox for v1.3.23.150.

Here is a version of a FAQ which isn't best et all.
I didn't have the time to implement the helps of other folks, so don't harm if
anything isn't well.
---
         ______________________________________________
           Hamster-Update  <1.3.23.130 to 1.3.23.140>
         ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

Since Hamster Classic 1.3.23.140 the SSL-functionality is integrated 
in Hamster itself. Because of this there were changes in the commands 
HamFetchMail and HamSendMail(Auth). 
These changes harms many Hamster-Users so this document was written.



What to do?
##########

1. *All* Users:
     This part is also important for users who doesn't use SSL yet.


Every script with "HamFetchMail" or "HamSendMail(Auth)" have to be proofed of
having parameters _after_ "<LeaveOnServer>" or "<from-select>".
Those have to be corrected/updated.


The new Syntax of these commands are:
------------------------------------

HamFetchMail   ( <server>, <port>, <user>, <pass>, <destuser>, <filter>,
                 <LeaveOnServer>, <SSLMode>, <SSLVerify>, <SSLCaFile> )

HamSendMail    ( <server>, <port>, <from-select>, <to-select>, <SSLMode>,
                 <SSLVerify>, <SSLCaFile> )

HamSendMailAuth( <server>, <port>, <user>, <pass>, <from-select>, 
                 <to-select>, <SSLMode>, <SSLVerify>, <SSLCaFile> )


Important: Not only the count of parameter has changed but also the format!
¯¯¯¯¯¯¯¯¯

    SSLMode:   Integer [0..3]
    SSLVerify: Integer [0..3]
    SSLCaFile: String

That means the full given paramters without using SSL looks like this:

HamFetchMail   ( "pop3-server", "110", "user", "pass", "admin", "", 0, 0, 0, "" )
HamSendMail    ( "smtp-server", "25", ".*", ".*", 0, 0, ""  )
HamSendMailAuth( "smtp-server", "25", "", "", ".*", ".*", 0, 0, "" )



2. For users who had used Stunnel or now wants to use SSL:
   -------------------------------------------------------

Most useful to read is the SSL-FAQ (not yet translated) by Phillip Wendler 
and Martin German:
http://sites.inka.de/ximera/hamster-ssl-faq.txt

It's also included in the German helpfile of Joern Weber:
http://home.t-online.de/home/joern_weber/HAMSTER_HLP_DE_BETA.ZIP


Some important notes:
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

For using SSL you have to download two additional dll-files. 
Those couldn't be given with Hamster because of cryptographic (import-)
limitations in some states.

1. libssl32.dll
2. libeay32.dll

They have to be newer as version openssl-0-9-6b

Download (for example):
  http://sites.inka.de/ximera/openssl_dlls.zip


These DLLs have to be copied into main Hamster-Directory or one of 
the pathes included in the windows-%PATH%-Variable.
On its start Hamster does find those libaries automatical.

After this the main configuration can be found in 
Configuration|General Settings|SSL.


There are two possibilities to save the certificates:
You can use both in addition.

1. In "Path to certifivates for verification" you can give a Path 
   where all certificates are saved as single files. The names of 
   these files are in the format (as said in SSL-FAQ.):
     "<Hash_of_certificate>.0"
2. In "File with certificates for verification" you can give a 
   PEM-file where you can include all certificates. (according to SSL-FAQ!)


You should have in brain that *all* SSL-actions (and their verifications) of
Hamster according to the certifications given. 
You can use other configurations for single servers given in the single 
server-configuration or given by the parameters of the scriptcommands.



Purging the old SSL-Entrys
##########################

If you know that the old method of using Stunnel will *never* be 
used anymore, you can delete those entrys:


server.ini: (all)
| UseSSL
| SSL-Port
| sTunnelOption


hamster.ini
| SSLWrapperNotClose
| SSLProg
| SSLStartTimeout
| SSLlocalStartTimeout
| SSLKeyFile
| STunnelOption




Version of document
###################

German:                Mathias Berle <[email protected]>
  22.3.2002
English (Translation): Heiko Studt <[email protected]>
  22.3.2002


-- 
Heiko Studt <[email protected]>
Last Update: 22.3.2002
---


MFG

-- 
[email protected]