Imsconnutil: Unable To Kill IMAP Sessions (Doc ID 2866994.1)

Last updated on AUGUST 04, 2023

Applies to:

Symptoms

Strange behavior was observed when using the imsconnutil command. When a user logged into their imap session, *two* entries were observed for this user in the "imsconnutil -c" output, e.g.:

This behavior was observed for other users, as well.

Note that the FROM "IP:<port>" numbers are the same for both lines, but the PIDs are different. How can that be?

What was actually much worse was within 10 to 90 seconds (that was the range that was measured from trying a few times), *both entries would completely disappear* from the imsconnutil output despite the sessions still being active.

This is a potentially a huge security issue, as imsconnutil is then unable to find the user session in order to kill them (with "-k") when the need to terminate user access arises.

The imsconnutil command output should handle the session information correctly so that user sessions can be terminated using the -k option.

Changes

Cause