Search
Contribute
Navigation
- ACL
- administration
- AJAX
- authentication
- Best Practice
- calendaring & scheduling
- certificate
- certificate authority
- Citrix
- Client deployment
- Client setup configfile
- composite apps
- compression
- concepts
- database
- database properties
- Deployment issues
- diagnostics
- directory
- Domino Server Install
- Eclipse
- encryption
- FIPS
- full text indexing
- groups
- id
- ID file
- images
- install
- Java
- Javascript
- journal
- language pack
- learning
- live text
- logging
- mail file
- mail router
- mail rules
- mail.box
- memory
- messaging
- MIME
- mobility
- Monitoring
- My Widgets
- network
- notes.ini
- NSF performance
- obsolete notes.inis
- ODS
- Partitioned server install
- performance
- plug-ins
- Policies
- replication
- resources
- Resources database
- search
- security
- SMTP
- s/mime
- templates
- TNEF
- transaction logging
- tutorials
- update
- upgrade
- views
- web
- @ formulas
Go elsewhere
Subscribe to RSS
TNEFBreakSMIME, notes.ini option related to RTF conversion of incoming MS Exchange mail
Article information
| Domino messaging
, Server Notes.inis
s/mime , TNEF |
Harry Peebles 05/13/2008 |
Amy Smith 06/11/2008 |
|
|
Explanation:
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.
Default:
When this option is absent or set to 0 this behavior is disabled.0: do not process TNEF objects in S/MIME signed messages
Recommendation:
If TNEF conversion is enabled, enable conversion of S/MIME signed messages with TNEFBreakSMIME=1
Restrictions:
This Domino feature became available in versions 6.5.6 and 7.02.
Related Settings:
TNEFConverter_Log_Level, TNEFAttachRTF, TNEFKeepAttachment, TNEFEnableConversion
References:
Technote 1093342
Attachments to messages received from the Internet are named as winmail.dat
http://www.ibm.com/support/docview.wss?uid=swg21093342
Domino 7.0.2 Release Notes
http://www.lotus.com/ldd/doc/domino_notes/7.0.2/rn702.nsf/db69c81afd0e71cf852561b700752f5e/9cf4aeb9883ea711852572450060cd47
Domino Configuration Tuner:
This setting is included in the DCT catalog of best practices as of Domino 8.5
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.
Default:
When this option is absent or set to 0 this behavior is disabled.0: do not process TNEF objects in S/MIME signed messages
Recommendation:
If TNEF conversion is enabled, enable conversion of S/MIME signed messages with TNEFBreakSMIME=1
Restrictions:
This Domino feature became available in versions 6.5.6 and 7.02.
Related Settings:
TNEFConverter_Log_Level, TNEFAttachRTF, TNEFKeepAttachment, TNEFEnableConversion
References:
Technote 1093342
Attachments to messages received from the Internet are named as winmail.dat
http://www.ibm.com/support/docview.wss?uid=swg21093342
Domino 7.0.2 Release Notes
http://www.lotus.com/ldd/doc/domino_notes/7.0.2/rn702.nsf/db69c81afd0e71cf852561b700752f5e/9cf4aeb9883ea711852572450060cd47
Domino Configuration Tuner:
This setting is included in the DCT catalog of best practices as of Domino 8.5
Comments
Add a comment