How to Share Vacation/Autoreply History Information Between MTAs (Doc ID 1999235.1)

Last updated on JUNE 27, 2024

Applies to:

Goal

In the LMTP delivery scenario,  the autoreply member of the DELIVERY_OPTIONS option is set to perform the autoreply function on the MTA systems.

This is necessary because in the LMTP scenario, the components of the MTA which do the autoreply are not involved on the the message store system.

And, it is desirable because it is more work which can be offloaded from the the backend stores to the MTA systems.

However, it requires the MTA systems be able to share the .vac files which store the autoreply history information for each user.

If those files are not shared between the MTAs, senders may receive multiple automated replies (one per MTA system) even though the recipient, who is on vacation, had configure mailAutoReplyTimeOut (or the time parameters on a sieve vacation script) -- because each MTA would be using its own autoreply history for each user.

Solution

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