My Oracle Support Banner

How To Disable Sieve Processing? (Doc ID 2801747.1)

Last updated on AUGUST 24, 2021

Applies to:

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

Goal


How to disable sieve processing?

There is a need to disable users' sieve (mailSieveRuleSource) on a per-system level.

In more detail, there will be a switch to LMTP to be able to use Cassandra. Currently, there are hundreds of thousands of users, across tens of backends.  An all-at-once switch to LMTP is out of the question.

The MTA layer currently relays to the backends using SMTP. Per-user sieve is run on the backends, as part of enqueue to the ims-ms channel.

A scheme for determining LMTP vs SMTP on the MTAs, is working. But, it also engages any recipient sieve on the MTA system. That is fine/expected for LMTP. But for the users on backends still using SMTP, that means it will happen twice: once on the MTA and again on the backend.

The goal is to disable users' sieve processing on the MTAs for users who are still on SMTP backends.
Disabling it on the backends is not a good solution, because either of the following can exist:


- a window where sieve is not happening at all for some users
- a window where sieve is happening twice for some users

If it is disabled on the backends, the following would have to happen:


* stop dispatcher on all the MTAs
* wait for queues to clear
* make the change to disable per-user sieve on the backends
* make this change to enable per-user sieve on the MTAs
* start everything up again

It is the same all-at-once risk as if LMTP were enabled on all the existing backends.
 
How can this be done successfully?
 

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.