The use of subject line keywords (see Table 1), which can be individually adapted if required, guarantees the independence from the used email client when controlling the appliance.

Similarly, (X) headers (also in Table 1) can be evaluated for controlling actions which are to be implemented on the SEPPmail Secure E-Mail Gateway. By default, these X headers are used by the SEPPmail Microsoft Outlook Add-In but can also be set in other email clients, such as IBM Notes, by means of adapted email templates (please also refer to IBM Notes: Creating An Encrypted Send Button) or Novell Groupwise via templates.

Subject lines

Keyword

(X) header/Value

[plain]

x-smplain / yes

Suppress any cryptographic action.

[confidential]

sensitivity / companyconfidential

x-smenc / yes

Trigger encryption (Encryption Hierarchy).

[priv]

sensitivity / private

x-smwebmail / yes

Triggering encryption by means of the GINA technology (keyword: read confirmation)

empty

Note:

If, in addition to enforcing the GINA technology, a read confirmation (disposition-notification to header) is requested in the email client, a read confirmation is requested via this technology. This means that the recipient cannot suppress the triggering of this read confirmation – in contrast to MS Outlook, for example.
The SEPPmail Microsoft Outlook Add-In automatically requests a read confirmation to the GINA technology (disposition-notification-to header).

[emptypw]

Suppressing the necessity of entering an initial password for GINA emails (causing security concerns)

[sms:<inter-national prefix><mobile phone number>]

Optional entry of the mobile phone number for the transmission of the initial password of an GINA email by SMS.

Format:

[sms:0041791234567]

[sms:+41791234567]

[zip]

Sending the encrypted email part of a GINA email in ZIP format instead of HTML format.

For instance, this is required if the recipient uses Outlook Web Access (OWA) 2003 since GINA emails in the HTML format from OWA 2003 cannot be decrypted.

[noenc]

x-smnoenc / yes

Suppressing the encryption of the email if "Encrypt" has been defined as the default in the ruleset

[sign]

x-smsign / yes

Triggering the signing of the email.

[nosign]

x-smnosign / yes

Suppressing the signing of the email, provided that "Sign" has been defined as the default in the ruleset

[lfm]

x-smlfm / yes

Activating the Large File Transfer (LFT), regardless of the email size*

[nolfm]

Suppressing the Large File Transfer (LFT), even if the set threshold value is exceeded
((Size (in KB) above which outgoing messages are treated as large files).).

Table 1

empty

Note:

The simultaneous use of contradictory keywords and (X)-headers as triggers within an email can end in a non-defined state and is therefore to be absolutely avoided!

Please enable JavaScript to view this site.

Note:

Note:

Keyboard Navigation