Tickets :: [#5393] Turba generates syntactically wrong adresses for IMP

6.0.0-beta1

11/6/25

Summary	Turba generates syntactically wrong adresses for IMP
Queue	Turba
Queue Version	2.1.3
Type	Bug
State	Resolved
Priority	2. Medium
Owners
Requester	Otto.Stolz (at) uni-konstanz (dot) de
Created	05/23/2007 (6742 days ago)
Due
Updated	06/14/2007 (6720 days ago)
Assigned	05/25/2007 (6740 days ago)
Resolved	06/14/2007 (6720 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/14/2007 01:39:13 AM	Chuck Hagenbuch	Comment #8 State ⇒ Resolved	Reply to this comment
I can't reproduce this with HEAD, either.

06/13/2007 11:59:58 AM	Jan Schneider	Comment #7	Reply to this comment
So, did you try the latest code?

05/27/2007 10:01:50 AM	Jan Schneider	Comment #6	Reply to this comment
This is relevant because not being able to reproduce it could mean that is has been fixed already. And you are not even using the latest stable versions.

05/26/2007 07:14:46 PM	otto (dot) stolz (at) uni-konstanz (dot) de	Comment #5	Reply to this comment
You have indicated your Turba version as being 2.1.3 My current versions are indeed: Horde 3.1.3, Imp H3 (4.1.3) und Turba H3 (2.1.3). However, I have retrofitted one or two CVS patches to it, as discussed in tickets ~~#3392~~, perhaps ~~#5327~~ (I am not in my office to check the latter, until June 9th). I do not think that that is relevant for this new bug, though.

05/26/2007 06:32:15 PM	Michael Rubinsky	Comment #4	Reply to this comment
What is FW_3 code? FW_3 = Framework_3 - the CVS branch for the latest stable releases. (You have indicated your Turba version as being 2.1.3) CVS HEAD is the latest development code.

05/26/2007 06:07:02 PM	otto (dot) stolz (at) uni-konstanz (dot) de	Comment #3	Reply to this comment
I see this in CVS HEAD, but not with the FW_3 code. You are asking for feedback, but, sorry, I do not understand your remark. What is FW_3 code? And what question am I supposed to answer?

05/25/2007 05:29:49 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I see this in CVS HEAD, but not with the FW_3 code.

05/23/2007 11:51:06 AM	Otto (dot) Stolz (at) uni-konstanz (dot) de	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Queue ⇒ Turba Summary ⇒ Turba generates syntactically wrong adresses for IMP Type ⇒ Bug	Reply to this comment
One way to start message composition (IMP) is to click on the E-Mail field of some entry, in the adressbook listing (Turba). Now, when the pertinent Name field contains a comma, IMP will get the To field wrong. Example: - Adressbook entry: · Name: Stolz, Otto · Alias: Kommatest · E-Mail: otto.stolz@uni-konstanz.de - To field: · as displayed in the Compose form: \"Stolz, Otto\" <otto.stolz@uni-konstanz.de> · as sent in the message: "\"Stolz"@uni-konstanz.de, "Otto\"" <otto.stolz@uni-konstanz.de> - Message will be sent to: <Stolz>, <@uni-konstanz.de>, <otto.stolz@uni-konstanz.de> - Entry added to the addressbook: · Name: "\"Stolz" · Alias: · E-Mail: "\"Stolz"@uni-konstanz.de In contrast, if the address is fetched via IMP's search, or expand, function (Address Book, or Expand Names options, respectively, in the Compose Message form), then the address will be alright. Example: - Adressbook entry: as above - To field: · as displayed in the Compose form: "Stolz, Otto" <otto.stolz@uni-konstanz.de> · as sent in the message: "Stolz, Otto" <otto.stolz@uni-konstanz.de> - Message will be sent to: <otto.stolz@uni-konstanz.de> - No entry added to the addressbook.