Marc Balmer wrote:
It will be one of your users. Looking at the logfiles you will quickly identify him.
You came into the thread later ... it is me. :)
I suggest that you take your concern upstream, i.e. to the courier developers. Here, we more or less only package what they provide us with.
I know. Going in circles. I started upstream, with a few posts, but got one single answer: courier-imap does not fork. I showed my 100 processes, all trying to search an item, and all evolved from a single search of a single user. No answer was forthcoming. Only then did I start the thread in here. And in here, Alf pointed to the culprit: re-requesting searches after a specific time. I posted this upstream, but not a single answer. So what it made from this, was that there was no interest, sort of 'works for me'. But 'works for me' still is no security means. If I can DoS a 1.7 GHz/256MB box through dial-up, involuntarily, who would want to argue that larger iron could not. A new term is born: "Security through processing power" ;),
Uwe
