Jon Clayton

My feedback

  1. 1,348 votes
    Vote
    Sign in Sign in with GFI
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    60 comments  ·  Kerio Connect  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Clayton supported this idea  · 
  2. 317 votes
    Vote
    Sign in Sign in with GFI
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Kerio Connect  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Heather P responded

    Please see our Kerio Connect 9.1 beta for Remote Archiving per domain.

    Jon Clayton supported this idea  · 
  3. 3 votes
    Vote
    Sign in Sign in with GFI
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Kerio Control  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Clayton shared this idea  · 
  4. 134 votes
    Vote
    Sign in Sign in with GFI
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Kerio Connect  ·  Flag idea as inappropriate…  ·  Admin →
    Jon Clayton commented  · 

    I run into this issue all the time. There will be a particular client who is unable to log in because their account is locked while it's being indexed. Then they build up dozens of connections to their account slowing everything down. These sessions only drop off after they time out. Many times I have had to restart Kerio Connect to drop the excessive sessions. If we could kill a connection, like we are able to do within Kerio Control, then perhaps we can more easily control this issue. As an alternative, perhaps we can select a user and "kill all sessions" from that one single user. This would be huge.

    Jon Clayton commented  · 

    Please allow us to force quit or end a user session without having to restart the entire service.

    Jon Clayton supported this idea  · 

Feedback and Knowledge Base