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

Last updated on NOVEMBER 15, 2022

Applies to:

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.

• Channel Definitions - http://docs.oracle.com/cd/E63708_01/doc.801/e63711/msadm_mta_concepts.htm#MSVAG543

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.