Configuration and Administration
glog.mail Properties
To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.
Property |
New in Version |
Definition |
---|---|---|
|
For emails from Oracle Transportation Management, this sets the outgoing charset and should match the recipient browser assumptions. |
|
glog.mail.diagnoseQuota.group.<display interval name>.count= <display interval count> |
20C |
For the MAIL QUOTA performance collector. The number of display intervals for this group. Note that in-memory counts will only display intervals for which they have data. |
glog.mail.diagnoseQuota.group.<display interval name>.interval= <display interval length> |
20C |
For the MAIL QUOTA performance collector. The duration of the display interval in this group. This should be a multiple of the track quota interval. |
|
The value of glog.mail.from should match: <email address>[=<first name> <last name>] OR <email address>[=<first name> <last name> at <company name>] The string in the square brackets is optional. If a value for <first name>, <last name> or <company name> has spaces, enclose the value in double quotes. E.g. glog.mail.from=donotrespond@mycompany.com="John Jay" "Smith Jr." at "Yellow and Blue, Inc." The default is: glog.workflow.notify.advisor.mail. This property does not display in the properties servlet by default. It must be added manually. In the cloud, glog.workflow.notify.advisor.email, glog.properties.log.email.from, glog.procurement.fromAddress, glog.mail.from, and glog.odi.email.from.address should all be set to the same address. |
|
|
Image file for the embedded HTML image. |
|
|
Pixel height for the embedded HTML image. Used to insert a logo above mail content. |
|
22C |
Controls placement of the logo within the email message. It supports the
|
|
|
Pixel width for the embedded HTML image. Used to insert a logo above mail content. |
|
|
Text of mail content link when the content exceeds the maximum content size. |
|
|
Text notifying the recipient that the content or attachments exceeded the maximum size, when the mail is HTML. |
|
|
Text notifying the recipient that the content or attachments exceeded the maximum size, when the mail is plain text. |
|
|
This is set to the string value of: <html><body>Mail file {0} is invalid. It can not be retrieved.</body></html> This property controls the untranslated HTML result that will be returned from the glog.webserver.mail.MailFileServlet in the case the Mail File that is attempted to be received is not valid. |
|
|
Text notifying the recipient that a mail link (created because maximum size was exceeded) is no longer available on the server. |
|
20C |
A comma delimited list of email addresses. When the overall email quota is exceeded, these emails will be notified. If no emails are defined in this property, then no notifications are sent. |
|
20C |
Controls how frequently notifications about blocked emails are sent. The notification frequency represents how often the quota blockage email resent. E.g., a frequency of 10 would send out an email on the first quota blockage and every ten blocked emails after that. |
|
|
The maximum number of emails any single recipient can receive a day. |
|
|
This property controls email redirection. The format of the property is: glog.mail.redirect.<old address>=<to address> It redirects any outbound Oracle Transportation Management email sent to <old address>. The email is rerouted to <to address>. Address is not case sensitive. This is especially helpful when copying a production database to a test system. It will prevent emails from being sent to carriers during testing. This property also reassigns any "from" or "cc" email addresses. For example, tender emails from <old address> will now be sent from <new address>. This again is helpful in a test environment. It will prevent email replies from going to the wrong place. Note: This property does not display in the properties servlet by default. It must be added manually. |
|
20B |
Sets the system default reply to email address. Note that this property can contain a list of comma-delimited addresses to support multiple reply to parties. If this property is blank, a reply to is not used on an outbound email. |
|
glog.mail.smtp.connectTimeout= <# of milliseconds for an SMTP connection operation before timeout> |
6.3.6 |
These properties to control SMTP timeouts. Note that the property is blank or missing, we revert to default behavior: i.e., an infinite timeout. These are set to blank in glog.common.properties for backward compatibility. These properties may be changed in the application-tier property servlet. When changed, all cached mail sessions are dropped to use the new timeouts. The Java mail API does not allow for host-specific timeouts. These timeouts will impact any SMTP host used by the application tier. |
22A |
These properties provide the ability to route email to a corporate email server. In addition to configuring the host/port and credentials for the SMTP server, it is necessary for Cloud Operations to assist in configuring IP address whitelisting to ensure a secure connection. Contact Oracle Support if you would like to use this feature. |
|
glog.mail.smtp.external.sessionLife= <# of messages between refreshes> |
22C |
SMTP sessions can be automatically refreshed every N mail messages. For OCI mail, automatic refresh is disabled. For external servers, this property controls the session refresh. It defaults to the value for OCI (Oracle Cloud Infrastructure) mail (i.e. 0, no refreshing). |
<# of milliseconds for an SMTP read operation before timeout> <# of milliseconds for an SMTP write operation before timeout> |
6.3.6 |
See glog.mail.smtp.connectTimeout above. |
|
Interprets the incoming character set from the database. ALWAYS needs to be set to UTF-8, regardless of what the database character set is. |
|
21C |
When false, mail exceptions are logged as they were in 21A. When true, exceptions are suppressed and errors are redirected to the MailError log ID. The default is true. |
|
21C |
If true, blocks due to unregistered mail senders are written as warnings to MailError logging rather than exceptions to the EXCEPTION log. Default: true. |
|
21C |
If true, blocks due to Sender Policy Framework (SPF) failures are written as warnings to MailError logging rather than exceptions to the EXCEPTION log. Default: true. |
|
21C |
If true, OTM mail blockages due to SPF exceptions and unregistered OCI Mail Senders are accumulated in the mail failure counts on the Mail Failures screen and the Mail Suppression metrics. Default: true. |
|
23A |
Allows From mail addresses to be automatically mapped to Reply-To addresses. This mapping is to avoid having dynamic From addresses require registration in Oracle Mail. This impacts rules and displays in various mailbox providers. The all case supersedes any others if true and maps all non-standard from addresses to the reply-to. This feature only applies to business-driven From addresses (e.g. Contacts, Domain Settings, and integration). Property-driven ones (the standard) are not affected.
|