MTA Tries to Connect to Wrong IP Address for Remote MTA Instead of Using MX Records (Doc ID 1485559.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

Oracle Communications Messaging Server - Version 6.3 and later
Information in this document applies to any platform.

Symptoms

Attempts to relay mail from local users to users on remote, public mail service fail -- stay in queue until maximum notices period and then are returned to sender.

The mail.log_current log file shows "Q" status messages about the failed attempts and the message is put back in the queue for later retry.

Enabling LOG_CONNECTION=3 provides more information showing the names and IP addresses it tries to connect to each time before logging the Q status.

Changes

At some time in the past, the environment was configured to relay all outbound mail through a specific system. To accomplish that, the nomx and daemon keywords were added to the tcp_local channel definition in the imta.cnf config file. Recently that was changed to allow connections directly from the MTA out to the internet and the daemon option was removed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms