<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Warnings when using expand names in IMP</title> 
  <pubDate>Fri, 10 Apr 2026 12:25:55 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/2334</link> 
  <atom:link rel="self" type="application/rss+xml" title="Warnings when using expand names in IMP" href="https://bugs.horde.org/ticket/2334/rss" /> 
  <description>Warnings when using expand names in IMP</description> 
 
   
   
  <item> 
   <title>In IMP, I have defined an LDAP server to search for email ad</title> 
   <description>In IMP, I have defined an LDAP server to search for email adresses. When I use the &quot;Expand Names&quot; button in the compose window of IMP (4.0.3) to search for a name that returns more than one choice, I get the following warnings at the top of the compose window:



Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 609

Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 610

Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 614

Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 620

Warning: strpos(): Empty delimiter. in /usr/share/pear/Mail/RFC822.php on line 620

Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 620

Notice: Object to string conversion in /usr/share/pear/Mail/RFC822.php on line 627



These warning messages appeared with Horde 3.0.5-RC2 and were not there when using Horde 3.0.4.



Luc.</description> 
   <pubDate>Mon, 25 Jul 2005 14:20:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10007</link> 
  </item> 
   
  <item> 
   <title>I used to receive this also using HEAD, but it went away (I </title> 
   <description>I used to receive this also using HEAD, but it went away (I think) once I upgraded the PEAR Mail package to the latest/greatest.  Either that or it was the MIME encodeAddress stuff that was fixed in Horde, but needs a new version of IMP to be compatible (this was the BC breaking conversation I had with Chuck on the dev@ list a few weeks back).  The only answer to this might be to upgrade IMP to CVS (or wait for 4.0.4 to come out).</description> 
   <pubDate>Tue, 26 Jul 2005 16:26:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10045</link> 
  </item> 
   
  <item> 
   <title>&gt; I used to receive this also using HEAD, but it went away (</title> 
   <description>&gt; I used to receive this also using HEAD, but it went away (I think) 

&gt; once I upgraded the PEAR Mail package to the latest/greatest.  



I updated PEAR Mail package from 1.1.4 to 1.1.6 (the latest) but the problem is still there.



&gt; The only answer to this might be to upgrade IMP to CVS (or 

&gt; wait for 4.0.4 to come out).



OK, I&#039;ll try IMP 4.0.4 as soon as it is available. Thanks.

</description> 
   <pubDate>Wed, 27 Jul 2005 13:46:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10073</link> 
  </item> 
   
  <item> 
   <title>

I&#039;ve also seen this bug with lates horde+imp+turba as of 1</title> 
   <description>

I&#039;ve also seen this bug with lates horde+imp+turba as of 16&#039;th of August 2005.

The problem appears if you expand a string like &quot;lars duelund&quot;, but expanding

&quot;duelund&quot; [both cases without &quot; of course] will NOT produce the warning from

RFC822.php. Spaces in a string seems to cause the problem, when the query 

is &quot;shipped&quot; to ldap.



Thanx,



Claus.



P.S.   	



Address Book (turba) H3 (2.0.3) 

Calendar (kronolith) H3 (2.0.3) 

Filters (ingo) H3 (1.0.1) 

Horde (horde) 3.0.5

Mail (imp) H3 (4.0.3)

</description> 
   <pubDate>Tue, 16 Aug 2005 15:28:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10598</link> 
  </item> 
   
  <item> 
   <title>I installed horde 3.0.5 and IMP 4.0.4-cvs today, and I still</title> 
   <description>I installed horde 3.0.5 and IMP 4.0.4-cvs today, and I still see the same warnings. 



As pointed out by jeppesen, the warnings shows only if the searched string has a space in it, and it happens weather the search string match one or more names.</description> 
   <pubDate>Thu, 18 Aug 2005 14:11:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10648</link> 
  </item> 
   
  <item> 
   <title>I can verify that this error does *not* occur with Horde 3.0</title> 
   <description>I can verify that this error does *not* occur with Horde 3.0.5, IMP 4.0.4-cvs, and the Mail package 1.1.6 or greater.</description> 
   <pubDate>Thu, 25 Aug 2005 00:13:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10778</link> 
  </item> 
   
  <item> 
   <title>I&#039;m pretty sure that I have seen this here with that combina</title> 
   <description>I&#039;m pretty sure that I have seen this here with that combination, I&#039;ll have to try later.</description> 
   <pubDate>Thu, 25 Aug 2005 07:36:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10787</link> 
  </item> 
   
  <item> 
   <title>Will be fixed with IMP 4.0.4.</title> 
   <description>Will be fixed with IMP 4.0.4.</description> 
   <pubDate>Thu, 01 Sep 2005 07:40:51 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/2334#t10916</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
