The TNEF Converter can process TNEF objects in an S/MIME signed message,
but doing so invalidates the signature. By default, the TNEF Converter
does not process S/MIME signed messages. You can use TNEFBreakSMIME=1 in
NOTES.INI to force the TNEF Converter to process S/MIME signed messages
at the server.
0: do not process TNEF objects in S/MIME signed messages
1: process TNEF objects in S/MIME signed objects, invalidating the S/MIME
signature if necessary
The TNEF Converter can not process objects in an S/MIME encrypted message
because it can not decrypt the message on the server. The TNEF converter
can only handle clear signed messages. S/MIME clear signed messages are
sent as a multiple part signed message. The first part of the multiple
part signed message is the original message, which may in turn be multiple
part. The second part of the multiple part signed message is the signature.
Unlike an opaque signed message, the clear signed message's data is in
the clear. The TNEF Converter can find and open the TNEF stream, extracting
any attachments contained within the TNEF stream.
The TNEF Converter is built into the SMTP task. TNEFEnableConversion=1
must exist in order for TNEFBreakSMIME=1 to take effect.
When this option is absent or set to 0 this behavior is disabled.0: do
not process TNEF objects in S/MIME signed messages
If TNEF conversion is enabled, consider enabling conversion of S/MIME signed
messages with TNEFBreakSMIME=1
This Domino feature became available in versions 6.5.6 and 7.02.
TNEFConverter_Log_Level, TNEFAttachRTF, TNEFKeepAttachment, TNEFEnableConversion
to messages received from the Internet are named as winmail.dat
7.0.2 Release Notes
Domino Configuration Tuner:
This setting is included in the DCT
catalog of best practices.