My Oracle Support Banner

How to Remove Messages from the MTA Queue (Doc ID 1001803.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Messaging Server - Version 5.2.0 and later
All Platforms
Checked for relevance on 23-JUN-2017.

Purpose

A Message Transfer Agent (MTA) bounces a message back to the sender when the MTA cannot deliver the message to the recipient because of a permanent failure -- or a temporary failure that is not corrected within a specified amount of time. The bounced message is addressed to the sender of the original message. The From: address of the bounced message cannot contain the recipient's address because the recipient's address cannot be reached. Therefore, according to RFC 821, the bounced message contains a From: address of "<>" (that is, a null address), which signifies that an MTA, rather than the recipient, sent back the message.

Normally, because these messages are bounced back immediately, they do not appear in the queue. However, in mail-bombs and spamming, the sender's address of the original message is rarely valid, so the bounce messages can end up in the MTA queue being retried for some time.

Questions and Answers

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
Purpose
Questions and Answers
 How to remove messages with null from address?
 How to remove messages from the queue in a single operation?
 Why .HELD messages remain in the message queue ?
 What if I want to delete .HELD messages?
 What if there are thousands of messages to be deleted?
 Using find | xargs
 Moving the queue out of the way
 Make sure the moves only change the name and not copy to different file system
 Find and fix the root cause
References

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