Quelltext der Seite CSNCurrent en:Using Subject Line Tags for Auto Processed Messages

  

-----

= About Tags in Subject Lines for Auto-Processed Messages =
To trigger the rule-based processing of messages, you have the option to add a text tag into the subject line of a message before sending. This tag has to be made known to the CS4N Application and will be removed again from the subject line automatically during processing, so the recipient receives the original subject text set by the sender. The tag can either be added manually to the subject line by the sender or it can be added automatically using a control element added to the HCL Notes Mail Template.

As of version 2.15, the forwarding of notifications to internal recipients can be set up in such a way that they are delivered directly to the respective recipients without the diversions via the Cryptshare server. For this, however, the marking of such notifications must also be taken into account in the rule-based forwarding. The keyword for marking such notifications is defined in the configuration in the section '''Rules > Messaging type to internal recipients > Flag for internal e-mail forwarding'''. This keyword must then also be taken into account in the server-based rules so that such notifications are delivered directly.

{{NoteBox|title=Using Journal.NSF for e-mail archiving|content=<br />
If there is a Domino Server rule for redirecting Cryptshare for Notes emails …<br /><b>and</b> another Domino Server rule exists for archiving to Journal.NSF …<br /><b>and</b> the relevant Journal.NSF <b>is not</b> on the same server as the Cryptshare application …<br />then the existing Domino server rule for archiving <b>must</b> be extended in order to avoid duplication of emails.<br />
<b>Additional condition: The Cryptshare for Notes placeholder (e.g. [CS4N]) must not be included in the subject of the email.</b>}}

= Option 1 - No integration into personal mail file =
The sender can enter the tag into the subject line. If a Domino server-side rule exists that checks for the tag in the subject line, the e-mail will be forwarded to Cryptshare.nsf if the tag is found in the subject.
However, you should consider the settings concerning how Cryptshare should deal with attachments. If the setting is set to only send messages with attachments, messages containing the tag but no attachments will still be delivered as standard e-mails. The sender cannot be made aware of this in advance.
If all messages (with and without attachments) should be delivered via CS4N, the Domino Server rule only needs to check for the subject line. In this case you need to configure CS4N so that messages that are processed based on rules are sent as complete encrypted messages ([[{{NAMESPACE}}:6489420|Send complete message as EML file]]).
{{TipBox|title=|content=If messages without attachments should also be sent as encrypted EML files, the outbound messages have to contain the text field '''CSEMLBodyOptions''' and the field value has to be "'''0'''". Also the option "Send complete message as EML file" has to be selected in the field '''E-Mail handling in case of rule based processing''' on the [[{{NAMESPACE}}:6489420{{!}}Sub-Tab "Rule-based processing"]].
}}

[[File:21823870.png]]
= Option 2 - Integration into the Memo Form of the personal mail file =
If the sender sends the message from his personal mail file (see [[{{NAMESPACE}}:Integration_into_personal_mail_files|Integration into personal mail files]]) using the option "As Cryptshare messge" (text label configurable), the defined tag will automatically be added to the subject line of the outbound message. The Domino Server rule checks the subject line for the tag and forwards the message into Cryptshare.nsf if applicable.

When sending from the personal mail file, the system checks which configuration settings in CS4N apply for sending rule-based e-mail messages.

Depending on the configuration of CS4N, the Domino server rules may have to be adapted. 


'''Example:'''

[[File:21823869.png]]
{{NoteBox|title=|content=The Domino router server task should be restarted after each change.
}}

-----