Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Messaging Server - Version 5.2.0 and later
Information in this document applies to any platform.
Occasionally you need to enable IMAP telemetry to try to capture information about a problem for a specific user, but you do not know exactly when the problem will happen, or exactly what IMAP commands are involved.
Enabling IMAP telemetry for the user is easy. Leaving it run that way can accumulate a lot of data. Be careful not to let it fill the file system where telemetry is stored.
The telemetry feature captures all the data received from and sent to the client. There is a separate file for each session. The file name is the Unix date/time when the session started. If multiple sessions start in the same second, a .n is appended to the file name to keep them unique.
But once you have all that data, if you do not know exactly when the problem happened or what IMAP command is involved, how do you sort through all that data?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms