6.0.0-beta1
7/4/25

[#7061] Turba inserts backslashes (\) before quotes on recipient's name
Summary Turba inserts backslashes (\) before quotes on recipient's name
Queue IMP
Queue Version FRAMEWORK_3
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester lfbm.andamentos (at) gmail (dot) com
Created 07/12/2008 (6201 days ago)
Due
Updated 07/22/2008 (6191 days ago)
Assigned 07/21/2008 (6192 days ago)
Resolved 07/22/2008 (6191 days ago)
Github Issue Link
Github Pull Request
Milestone 4.2.1
Patch No

History
07/22/2008 01:37:20 AM Michael Slusarz State ⇒ Resolved
 
07/22/2008 01:00:13 AM lfbm (dot) andamentos (at) gmail (dot) com Comment #15 Reply to this comment
It should.  Neither Jan or I see this with the latest code.
Yes, it's gone. I can confirm the problem does not happen after update 
horde to 3.2.2-cvs.
07/22/2008 12:17:19 AM Michael Slusarz Comment #14 Reply to this comment
The fix required changes in both Horde 3.2.2 and IMP 4.2.1, so unless
you have both it won't display correctly.
So if I update to the latest horde 3.2.2 does the issue go away? Thanks.
It should.  Neither Jan or I see this with the latest code.
07/21/2008 06:01:28 PM lfbm (dot) andamentos (at) gmail (dot) com Comment #13 Reply to this comment
The fix required changes in both Horde 3.2.2 and IMP 4.2.1, so unless
you have both it won't display correctly.
So if I update to the latest horde 3.2.2 does the issue go away? Thanks.


07/21/2008 05:42:14 PM Michael Slusarz Comment #12 Reply to this comment
The fix required changes in both Horde 3.2.2 and IMP 4.2.1, so unless 
you have both it won't display correctly.


07/21/2008 05:35:55 PM Michael Slusarz Comment #11
Priority ⇒ 1. Low
State ⇒ Feedback
Reply to this comment
These are BC-breaking changes I made to MIME functions in order to fix 
the underlying issue.  But these are one of those BC-breaking changes 
necessary to fix a critical bug (certain messages could not be replied 
to at all without this fix in IMP).  I am more than willing to live 
with a display issue in non-updated installations to fix broken 
behavior.
07/18/2008 05:27:27 PM lfbm (dot) andamentos (at) gmail (dot) com Comment #10 Reply to this comment
And it also happens.
That's not what your screenshots show, and I can't reproduce it with
those versions.
Yes, the screenshots were taken from a fresh testing-only 
installation. They are not my production install.



These are screenshots from my current install:



01 - http://img231.imageshack.us/img231/3636/production00kn0.png

02 - http://img230.imageshack.us/img230/9950/production01vp5.png

03 - http://img228.imageshack.us/img228/8809/production02eh9.png



I wonder if the module horde has anything to do with it?!



Hope it can help finding out what´s wrong.



Thanks
07/18/2008 02:05:43 PM Jan Schneider Comment #9 Reply to this comment

[Show Quoted Text - 9 lines]
That's not what your screenshots show, and I can't reproduce it with 
those versions.
07/18/2008 01:58:47 PM lfbm (dot) andamentos (at) gmail (dot) com Comment #8 Reply to this comment
Got it. This only happens if you use the release version of Turba
(2.2.1), and FW_3 from IMP.
My production installation is:



(truba) H3 (2.2.2-cvs)

(imp)  H3 (4.2.1-cvs)



And it also happens.
07/18/2008 11:11:16 AM Jan Schneider Assigned to Michael Slusarz
Priority ⇒ 2. Medium
State ⇒ Assigned
Milestone ⇒ 4.2.1
 
07/18/2008 11:10:59 AM Jan Schneider Comment #7
Version ⇒ FRAMEWORK_3
Queue ⇒ IMP
Reply to this comment
Got it. This only happens if you use the release version of Turba 
(2.2.1), and FW_3 from IMP.
07/18/2008 12:51:38 AM lfbm (dot) andamentos (at) gmail (dot) com Comment #6 Reply to this comment
Maybe the screenshots below can help.



When using stable IMP, I get the following when hovering the mouse 
over turba's link:



javascript:popup_imp('/imp/compose.php',700,650,'to=\"Luis Felipe 
Marzagao\" <duli@dulinux.com>');



01 - http://img253.imageshack.us/img253/1919/001zz3.png

02 - http://img139.imageshack.us/img139/2745/002zn9.png

03 - http://img253.imageshack.us/img253/6728/003oi3.png





When using latest FRAMEWORK_3 IMP (20080717), I get the following when 
hovering the mouse over turba's link:



javascript:popup_imp('/imp/compose.php',700,650,'to=\\\"Luis Felipe 
Marzagao\\\" <duli@dulinux.com>');



01 - http://img253.imageshack.us/img253/6305/004lj3.png

02 - http://img367.imageshack.us/img367/2939/005kc8.png

03 - http://img125.imageshack.us/img125/9691/006lq9.png



Hope this can help.
07/17/2008 11:03:05 PM Jan Schneider Comment #5 Reply to this comment
I don't even have any quotes when composing from Turba's links.
07/17/2008 11:02:28 PM Jan Schneider Comment #4 Reply to this comment
I still don't see this with up-to-date FRAMEWORK_3 checkout of both 
IMP and Turba.
07/14/2008 12:28:59 AM lfbm (dot) andamentos (at) gmail (dot) com Comment #3 Reply to this comment
And I still can't reproduce it.
It's not a turba issue. It's IMP H3 (4.2.1-cvs).



I just did a complete clean installation of Webmail Groupware 1.1.1 
and tested it. It was just fine. Then I copied the latest snapshot of 
IMP framework_3 over imp directory, and then the problem happens. If I 
go back to IMP 4.2 (May 25 2008), it stops happening.
07/13/2008 07:50:26 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
And I still can't reproduce it.
07/12/2008 07:13:23 PM lfbm (dot) andamentos (at) gmail (dot) com Comment #1
Milestone ⇒
State ⇒ Unconfirmed
Patch ⇒ No
Queue ⇒ Turba
Summary ⇒ Turba inserts backslashes (\) before quotes on recipient's name
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
Browse "my contacts" and then click on any email address, the "new

message" window appears and the clicked email address automatically

shows up in the "to:" field, but it gets like this:



\"John Doe\" <johndoe@example.com>



And, after being sent, it stays like this in the sent folder:



\\\"John Doe\\\ <johndoe@example.com>



The email arrives just fine (altought in the recepient's inbox it shows:

To: "\\\"John Does\\\"" <johndoe@example.com>



If you first click on the contact, then go to the "Communications" tab 
and then click on the contact's e-mail, then the New Message opens 
with just johndoe@example.com in the "To:" field.



So different behaviours exist for the same functionality.



The backslashes make users confused.



Truba version: H3 (2.2.2-cvs)



Thanks a lot

Luis Felipe (duli)


Saved Queries