Generally, the button "Large File Transfer" can be used in the add-in to enforce the use of this technology.
For the Delivering/Sending Files Via Standard Email Client variant, this means that an email is sent as an LFT message irrespective of the set threshold value (please also refer to Size (in KB) above which outgoing messages are treated as large files (set to 0 to treat all outgoing messages as large files)). For this, during the installation process it is only necessary to activate the button "Large File Transfer".
With Delivery/Sending via SEPPmail Microsoft Outlook Add-In there is an option of uploading large attachments directly to the SEPPmail Secure E-Mail Gateway, thereby bypassing the email server in order not to put any unnecessary load on it and, if applicable, bypass email size restrictions.
For this function, the URL for the upload must be provided to the add-in. This is done during the installation process, and/or via the Registry value "LFTSEPPmailHostname", and generally corresponds to the Hostname of the GINA name [default].
Alternatively, a hostname or an IP address can be entered here via which the SEPPmail Secure E-Mail Gateway can be reached in the internal network.
This is of particular importance for Frontend/Backend Clusters since the delivery to a frontend system is impossible with this option. This means that in this case, the FQDN/IP addresses entered under "LFTSEPPmailHostname" would have to be used to reach the backend system via which the LFT transfer is then implemented. The LFT download by the recipient is then possible at the frontend system again.
Note:To use this method, it is strongly recommended to activate the External authentication per LDAP by activating the options Authenticate GINA users from this domain to external LDAP server and Automatically create GINA account if user exists on external LDAP server. |