MTA Ignores Failure Due To UTF8 Not Being Supported
(Doc ID 2661662.1)
Last updated on MAY 10, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
On : Oracle Communications Messaging Server 220.127.116.11.20200312 64bit (built Mar 12 2020), Message Store
MTA ignores failure due to UTF8 not being supported
During an attempt to test EAI (Email Address Internationalization) Support, consider performing following steps:
(1) Set utf8negotiate keyword on SMTP source channels - 'tcp_local' and 'tcp_intranet' on an ingress MTA, but not on the next-hop MTA.
(2) Send an mail with user part in UTF8 to a normal non-EAI internal recipient address.
The ingress MTA accepts the mail, successfully processes any internal (process_milters) channel defined and then enqueues to tcp_intranet -- all good, no surprise
However, as the MTA on the ingress system tries to relay the mail to the next-hop MTA, which does not have EAI enabled, following errors / messages are seen in master channel_debug log:
The above log extract indicates a wait time of 10 minutes before the next-hop MTA timed out waiting for a command and closing of connection.
Shouldn't the MTA react to the '555 5.5.4' response when 'MAIL FROM' failed?
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