This error (no session) is randomly popping up on some installations for incoming messages. I was unable to track the causes of it. Most likely I would assume it may be somehow triggered by a session loss (or reinitialized). It may be due to the fact that Siskin is not used frequently enough and old messages are dropped due to the MAM retention policy.