[imp] IMAP Alert command (was Performance after upgrade)

[Chuck Hagenbuch]

Quoting "Stephen A. Cochran Lists" <stephen.a.cochran.lists at cahir.net>:

> I've found the source of the problem, although I'm not sure of a  
> solution yet. The problem is that our IMAP server issues an alert at  
> login as show below, which seems to throw IMP for a loop, literally:
>
> 11/02/2006 10:22:51 [166400648] C: 00000000 CAPABILITY
> 11/02/2006 10:22:51 [166400648] S: 00000000 OK CAPABILITY completed
> 11/02/2006 10:22:51 [166400648] C: LOGIN Test1
> 11/02/2006 10:22:51 IMAPS Logged on: Test1 23868; currently: 1;  
> peak: 10 from 129.170.208.37
> 11/02/2006 10:22:51 [166400648] S: * OK [ALERT] This account is  
> scheduled to be deactivated on 5-Nov-2006. Contact the Postmaster  
> for more information.
> 11/02/2006 10:22:51 [166400648] S: 00000001 OK Login completed
> 11/02/2006 10:22:51 [166400648] C: 00000002 CAPABILITY
> 11/02/2006 10:22:51 [166400648] S: 00000002 OK CAPABILITY completed
>
> Note that the alert comes between the client command and the server  
> response. I can't be exactly sure why, but this sends imp/apache  
> into some kind of infinite loop, with each process hit by this  
> trying to take 100% of the CPU. The execution stops in Session.php  
> at line 298:

I'd suggest experimenting with different PHP/c-client versions. The  
loop appears to be outside of IMP's scope here. You could try removing  
the imap_alerts() calls from IMP.php and IMAP.php (in imp/lib/), but  
that won't affect whether or not the server sends them.

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris