SMTP Time-Out After BDAT LAST Command
(Doc ID 1308682.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Communications Messaging Server - Version 6.0.0 and laterInformation in this document applies to any platform.
Affected software:
Oracle Messaging Exchange Server 6.3
Affected Component:
MTA SMTP_SERVER
Symptoms
An SMTP submitting messages using BDAT command to chunk MIME parts receives an error after the "BDAT 0 LAST" command.
After enabling slave_debug on the associated channel, in the tcp_<channel>_slave.log file, we see:
17:29:15.40: smtpc_enqueue returning a status of 137 (Timeout)
17:29:15.40: SMTP routine failure from SMTPC_ENQUEUE
17:29:15.40: pmt_close: [19] status 0
17:29:15.40: SMTP routine failure from SMTPC_ENQUEUE
17:29:15.40: pmt_close: [19] status 0
The message is not accepted after the error occurs.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |