DEFAULT_PRIVACY
(integer, -1, 0 - 255) Whether or not to set the privacy flag in an SMS message, and what value to use is controlled with the DEFAULT_PRIVACY and USE_HEADER_SENSITIVITY options. By default, a value of -1 is used for DEFAULT_PRIVACY. Table C–12 that follows shows the result of setting the DEFAULT_PRIVACY and USE_HEADER_SENSITIVITY options to various values.
Table C–12 Result of Values for DEFAULT_PRIVACY and USE_HEADER_SENSITIVITY|
DEFAULT_PRIVACY |
USE_HEADER_SENSITIVITY |
Result |
|---|---|---|
|
-1 |
0 |
The SMS privacy flag is never set in SMS messages. |
|
n >= 0 |
0 |
The SMS privacy flag is always set to the value n. RFC 822 Sensitivity: header lines are always ignored. |
|
-1 (default) |
1 (default) |
The SMS message’s privacy flag is only set when the originating email message has an RFC 822 Sensitivity: header line. In that case, the SMS privacy flag is set to correspond to the Sensitivity: header line’s value. This is the default. |
|
n >= 0 |
1 |
The SMS message’s privacy flag is set to correspond to the originating email message’s RFC 822 Sensitivity: header line. If the email message does not have a Sensitivity: header line, then the value of the SMS privacy flag is set to n. |
The SMS interpretation of privacy values is shown in Table C–13 that follows:
Table C–13 SMS Interpretation of Privacy Values|
Value |
Description |
|---|---|
|
0 |
Unrestricted |
|
1 |
Restricted |
|
2 |
Confidential |
|
3 |
Secret |
|
>= 4 |
Undefined |
The mapping used to translate RFC 822 Sensitivity: header line values to SMS privacy values is shown in Table C–14 that follows:
Table C–14 Mapping Translation of Sensitivity Headers to SMS Privacy Values|
RFC 822 Sensitivity: value |
SMS privacy value |
|---|---|
|
Personal |
1 (Restricted) |
|
Private |
2 (Confidential) |
|
Company confidential |
3 (Secret) |
- © 2010, Oracle Corporation and/or its affiliates