Okay, should really be handled now. Let me know if you run into 
anything else - thanks!



(this is the change to HEAD for reference - exact same diff on FW_3:) 
http://cvs.horde.org/diff.php/framework/Notification/Notification/Listener.php?r1=1.23&r2=1.24&ty=u

Actually, make that:



             if ($userinfo) {

                 if (is_array($userinfo) &&

                     !array_walk($userinfo,

                                 create_function('$a,$b,$c', 'return 
is_a($a,$c);'),

                                'PEAR_Error')) {

                     $userinfo = @implode(', ', $userinfo);

                 }

                 $ob->_message = $ob->getMessage() . ' : ' . $userinfo;

             }



so that the array_walk() comes after the is_array().

If the commit to Listener.php (line 102) was the only commit related 
to this, it doesn't fix it.  $userinfo is an array of 1 PEAR_Error, so 
the is_a() fails.  This works for me, so far:



             if ($userinfo &&

                 !array_walk($userinfo,

                             create_function('$a,$b,$c', 'return 
is_a($a,$c);'),

                             'PEAR_Error')) {

This was a bug, of sorts, in the Horde Notification package. I've 
fixed it in HEAD and FW_3; it'll be in the next stable Horde release.

And, the reason that the implode is failing is because $userinfo is an 
array of one PEAR_Error object, not an array of strings.



PHP is 5.2.0, PEAR is 1.4.11.

After adding a lot more logging, I've tracked it to 
Horde/Notification/Listener.php:getEvent()



This isn't completing:



             if ($userinfo) {

                 if (is_array($userinfo)) {

                     $userinfo = @implode(', ', $userinfo);

                 }

                 $ob->_message = $ob->getMessage() . ' : ' . $userinfo;



The @implode is failing.  If I comment that out, I get back to the 
compose screen with one "Please resolve ambiguous or invalid 
addresses." message in a yellow warning box for every time that I 
reloaded / clicked "Expand Names".

horde is set to



$conf['debug_level'] = E_ALL;



php is set to log E_ALL



There is nothing unusual in the horde error log - the last line logged 
is writing the session data.  There is nothing in the apache error 
log.  It does not look like php is segfaulting.

Is PHP segfaulting? Anything in your apache logs? What about PHP error 
reporting - is it turned on and at the highest level?

This is with IMP 4.1.3 and Horde 3.1.3



If I click Net Message, type in an address that is not in my address 
book (any keyboard mashing will do), then click Expand Addresses, the 
page posts, starts to reload, and then stops.



I traced it to the call to IMP::status() on line 56 of 
templates/compose/compose.inc



in lib/IMP.php, if I modify status() so that the last three lines are:



         if (class_exists('Notification_Listener_audio')) {

             $notification->notify(array('listeners' => 'audio'));

         }



instead of



         if (class_exists('Notification_Listener_audio')) {

             $notification->notify(array('listeners' => 
array('status', 'audio')));

         }



the page loads normally.



If I change the notifiy call to



             $notification->notify(array('listeners' => 'status'));



the page fails to not load.