6.0.0-git
2019-04-24

[#2086] Angle brackets and semi-colons generates no mail addressees
Summary Angle brackets and semi-colons generates no mail addressees
Queue Horde Framework Packages
Type Bug
State Resolved
Priority 1. Low
Owners
Requester kevin_myer (at) iu13 (dot) org
Created 2005-06-07 (5069 days ago)
Due
Updated 2005-06-24 (5052 days ago)
Assigned
Resolved 2005-06-07 (5069 days ago)
Milestone
Patch No

History
2005-06-24 13:59:27 kevin_myer (at) iu13 (dot) org Comment #10 Reply to this comment
Not sure if this is a result of an incomplete merge or if I missed 
something or if its a bug or what, but we're now seeing the following:



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



Its happening with a normal Expand Names expansion.


2005-06-14 11:29:08 kevin_myer (at) iu13 (dot) org Comment #9 Reply to this comment
http://lists.horde.org/archives/cvs/Week-of-Mon-20050606/thread.html#45895



The six CVS commits starting with the above link are what you want 
(framework/MIME/MIME.php, imp/lib/Compose.php, 
framework/MIME/MIME_Message.php).  You'll only need three of them, 
depending if you're using the HEAD or FRAMEWORK_3 branch.
2005-06-14 07:08:48 it (at) flora38 (dot) ch Comment #8 Reply to this comment
Sorry, I'm not working with cvs, but I also will fix this problem.

I have downloaded Compose.php (1.107.2.13) in  /horde/imp/lib. I can't 
find any file for horde to update (chuck has mentioned to update both 
horde and imp).



With only update Compose.php it doesn't work, but same as before.



Can you give me a hint? (Yes, I'm not a crack, sorry)
2005-06-08 05:07:07 Michael Slusarz Comment #7 Reply to this comment
See also Bug 1352.
2005-06-07 22:20:55 kevin_myer (at) iu13 (dot) org Comment #6 Reply to this comment
Got it.



Any reason not to MFH 1.150 as well, for MIME/MIME.php?  I noticed 
that Expand Names breaks when using group syntax for addressing and I 
think that fixes it.
2005-06-07 22:03:41 Chuck Hagenbuch Comment #5 Reply to this comment
You missed another commit about 30 seconds later. And yes, it'll be in 3.0.5.
2005-06-07 21:55:51 kevin_myer (at) iu13 (dot) org Comment #4 Reply to this comment
Notice: Object to string conversion in /horde/lib/Horde/MIME.php on line 827



Not sure if thats because I only patched the two bits you did and 
there's earlier stuff I haven't merged or not.  But that definitely 
does the trick.  It will hopefully be in Horde 3.0.5?
2005-06-07 18:21:53 Chuck Hagenbuch Comment #3
State ⇒ Resolved
Reply to this comment
Fixed. Unfortunately you'll need updates to both IMP and Horde to 
catch it properly, but it's done in both HEAD and FRAMEWORK_3 for both.
2005-06-07 01:51:03 kevin_myer (at) iu13 (dot) org Comment #2 Reply to this comment
Use this test case to prove:

Kevin Myer <kevin_myer@iu13.org>;dev@lists.horde.org
Generates:

To:
Actually, one slight change.  From a packet capture, this is 
generating a RCPT TO: @localhost, which my MTA was stripping out on 
the bounce.




2005-06-07 01:46:54 kevin_myer (at) iu13 (dot) org Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ Angle brackets and semi-colons generates no mail addressees
Queue ⇒ Horde Framework Packages
Reply to this comment
This is a bit of a bizarre combination but I can reproduce it on two 
different systems, one running HEAD and one running FRAMEWORK_3.



If you address a message to two or more individuals, it appears to be 
possible to separate their addresses with either a comma or a 
semi-colon.  RFC2822 says that addresses should be comma-separated but 
thats not the point of this bug.



If you include an address with angle brackets and a semi-colon, the 
Horde MIME library generates an address of .... nothing :)



Use this test case to prove:



Kevin Myer <kevin_myer@iu13.org>;dev@lists.horde.org

Generates:



To:



Good Example (Works):



kevin_myer@iu13.org;dev@lists.horde.org

Generates:



To:  kevin_myer@iu13.org,dev@lists.horde.org

Saved Queries