Metermaid Appears to be Counting Invalid Recipient Addresses Multiple Times
Last updated on MAY 23, 2017
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
Using metermaid to impose a quota/limit of how many messages a user can send and how many individual recipients. This is done using callouts in FROM_ACCESS (message quota) and SEND_ACCESS (recipient quota). See Triggering Effects From Transaction Logging: The LOG_ACTION Mapping Table.
A problem has been seen in the way the MTA counts invalid recipients. It appears that, in some cases, the MTA will count an invalid recipient as many as 6 times. This penalizes users who accidentally enter invalid recipient addresses, especially when using clients that automatically retry sending.
In the log entries from the MTA and Metermaid for one user, you can see that they tried to send to three invalid recipients, but their recipient count was incremented by 20. This happened to this user repeatedly, which resulted in them being incorrectly blocked from sending.
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 hundreds of Community platforms