My Oracle Support Banner

How To Adjust Front End Server To Retry Defered Email Every 30 Minutes (Doc ID 3081753.1)

Last updated on APRIL 14, 2025

Applies to:

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

Goal

On: Oracle Communications Messaging Server 8.1.0.21.20230112 64bit (built Jan 12 2023)

In a particular deployment, a Barracuda device was moved from being on-prem to the cloud. Since doing this, the Messaging Server front-end queues started growing slowly every day. It was suspected that this was due to the rate control on the Barracuda which is 150eml/user/30 mins and 250eml/domain/30 mins.
Barracuda's recommendation on this was:

 "We recommend configuring your mail server to retry deferred mail once every 30 minutes. This will prevent retries from occurring every minute (as many mail servers are set to do by default), which can create a heavy load on the server and potentially result in the mail being stuck in a constant rate control state."

The reason for setting this rate limit is to prevent spammers or hackers who might compromise a customer’s network or mail server from sending large-scale mass mailings.

Questions regarding this implementation:

1) What are the current settings for retrying deferred emails?
2) If it is by default, how can it be set up to only retry every 30 mins?

Solution

To view full details, 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 a vibrant support community of peers and Oracle experts.