How Does tcp_smtp_server Know to Invalidate Cache During Rehostuser?
(Doc ID 2518757.1)
Last updated on MAY 11, 2021
Applies to:Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.
Contemplating MTA - LDAP cache tuning on a setup having alias_entry_cache_timeout and base.authcachettl both set to 0.
Thinking of setting alias_entry_cache_timeout to 1200.
This would only be on the core-routing MTAs, not the back-ends (which are still using SMTP, not LMTP), nor the MTA component on the MMP or webmail systems.
But cannot recall how the rehostuser design is supposed to force such caches to be invalidated.
The message would be enqueued to ims-ms where it would not be delivered because the folder is locked by rehostuser. Is there something about that scenario that is supposed to cause the message to get reprocessed instead of just retried by ims_master?
Is there some way the tcp_smtp_server should learn to invalidate the cache in this scenario?
Or does it depend on the default alias_entry_cache_timeout being shorter than the expected duration of a rehostuser?
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