6.0.0-alpha12
6/6/25

[#9334] Sending message is ignoring Cc and Bcc fields
Summary Sending message is ignoring Cc and Bcc fields
Queue IMP
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester goncalo.queiros (at) portugalmail (dot) net
Created 10/22/2010 (5341 days ago)
Due
Updated 10/29/2010 (5334 days ago)
Assigned
Resolved 10/22/2010 (5341 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
10/27/2010 07:18:42 AM goncalo (dot) queiros (at) portugalmail (dot) net Comment #6 Reply to this comment
So if i lock this pref (so the users can't change its value through
options page), and still want the Cc and Bcc fields to not show by
default, i can't do it, since locking it and setting it's value to 0
will not give me the option to show the Cc and Bcc is that it?
Yes.
Ok, it seems a bit strange, and its also not working btw. Locking the 
pref will not remove the 2 checkboxes to add the Cc and Bcc
10/26/2010 11:13:45 PM Michael Slusarz Comment #5 Reply to this comment
So if i lock this pref (so the users can't change its value through 
options page), and still want the Cc and Bcc fields to not show by 
default, i can't do it, since locking it and setting it's value to 0 
will not give me the option to show the Cc and Bcc is that it?
Yes.

10/25/2010 04:51:14 PM goncalo (dot) queiros (at) portugalmail (dot) net Comment #4 Reply to this comment
But you are also partially incorrect - since if compose_[b]cc is 
locked, we don't want to allow a user to add those values even by 
form manipulation.  So I added a locked check in dimp.
So if i lock this pref (so the users can't change its value through 
options page), and still want the Cc and Bcc fields to not show by 
default, i can't do it, since locking it and setting it's value to 0 
will not give me the option to show the Cc and Bcc is that it?

10/22/2010 05:19:14 PM Michael Slusarz Comment #3
Assigned to Michael Slusarz
State ⇒ Resolved
Reply to this comment
When sending a message with Cc and Bcc fields, these addresses are 
being ignored, because we are looking at the value of compose_cc and 
compose_bcc prefs to decide if we should include those values in the 
header of the message.
For dimp you are partially correct - since we allow Showing Cc/Bcc 
after the page is loaded.  But you are also partially incorrect - 
since if compose_[b]cc is locked, we don't want to allow a user to add 
those values even by form manipulation.  So I added a locked check in 
dimp.

However, in imp, there is no way to show Cc/Bcc if it is disabled in 
prefs.  So we need to ignore any cc/bcc data passed in the form.

The rest of the patch, slightly modified and cleaned up, was applied as-is.
10/22/2010 03:41:23 PM goncalo (dot) queiros (at) portugalmail (dot) net Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Sending message is ignoring Cc and Bcc fields
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ Yes
New Attachment: 0001-Don-t-use-compose_cc-and-compose_bcc-prefs-to-decide.patch Download
State ⇒ Unconfirmed
Reply to this comment
When sending a message with Cc and Bcc fields, these addresses are 
being ignored, because we are looking at the value of compose_cc and 
compose_bcc prefs to decide if we should include those values in the 
header of the message.

Correcting this issue i also found out that Horde is not showing the 
Bcc field on the headers of the message. The problem is that on 
drafts, there may exist value on the Bcc field, so the patch also 
corrects this.

Also, when resuming a draft, Horde should show the Cc and Bcc if they 
have any value (regardless of their pref)

Patch corrects all this issues

Saved Queries