account default for "always bcc" doesn't set the field for new message

Bug #198167 reported by Michael R. Head
38
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Hardy
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

configuring a default bcc in the account properties has no effect, the value set there should be used for the new mails

TESTCASE

1) Launch evolution
2) edit the default account and set (in the account editor) a value for BCC the "always blind carbon copy to" and tick the checkbox.
3) close out of the account editor and preferences window.
4) create a new email (File/New/Mail Message)
5) note that the BCC field is empty.

I've noticed that this doesn't happen for all my accounts, just my default, main account.
It only seems to occur for the first account in the list of accounts when that account is the default account. Hopefully that will help with reproduction.

Related branches

Revision history for this message
Christophe Sauthier (christophe.sauthier) wrote :

I have the same behaviour here.

Changed in evolution:
status: New → Confirmed
Changed in evolution:
assignee: nobody → ubuntu-desktop
assignee: ubuntu-desktop → desktop-bugs
Changed in evolution:
status: Unknown → New
Changed in evolution:
importance: Undecided → Low
status: Confirmed → Triaged
Changed in evolution:
status: New → Confirmed
Revision history for this message
Fredrik (fredrk) wrote :

Sam here. VERY annoying. Make me loose mails all the time.

Revision history for this message
Michael R. Head (burner) wrote :

Wait, is this really a dupe of bug 92036? This is a NEW regression in hardy. bug 92036 was something different, since it was triggered by clicking a mailto: link from outside evolution. This bug is about the fact that the first account's BCC settings are ignored even when creating a new message from inside evolution!

Similar effect, but different cause. It may have the same solution, but I'm not sure this should be considered a dupe until that's determined.

Revision history for this message
nic (nic-suzor) wrote :

Agreed - upstream bug report is in direct conflict with new behaviour reported here.

Upstream (http://bugzilla.gnome.org/show_bug.cgi?id=274052) says:
1. Compose new mail starting from evolution menus
- BCC: present
- signature: present

While this behaviour is:
1. Compose new mail starting from evolution menus
- BCC: not present
- signature: present

Revision history for this message
David Medberry (med) wrote :

The missing BCC: follows the default around. If you change default mail accounts, only that one will be missing the BCC. This is clearly DISTINCT AND NOT A DUPLICATE of 92036. I'd say they aren't even close cousins as the mechanism for creating emails in each case are distinct.

What is the upstream gnome defect for this?

Evolution: 2.22.1
evolution version 2.22.1-0ubuntu2
evolution-common version 2.22.1-0ubuntu2

Changed in evolution:
status: Confirmed → In Progress
Revision history for this message
David Medberry (med) wrote :

I'm trying to understand how this bug got triaged as a Low Importance. Can someone explain that to me--it's one of the few bugs in Hardy that prohibits me from recommending folks upgrade. (There are certainly other bugs in Hardy but this one effects me every day with each email I write.)

Is Evolution not "core"?

Revision history for this message
Fredrik (fredrk) wrote :

The "sister bug":

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/92036

has been present for very long time (at least Gutsy).

Revision history for this message
Sebastien Bacher (seb128) wrote :

how it has been triaged as low? there is some thousand evolution bugs open, this one is not a crasher, it's not loosing any user datas, and it's concerning a feature that is enable automatically. the number of comments and duplicates seems to indicate it's not a priority for lot of users which means it's a low importance issue. now we don't deny that some people have a workflow adapt to this feature and that it would be nice to get that fixed but the team has limited ressources and has to prioritize the work, we will fix it in hardy-updates and 8.04.1 if possible though

Revision history for this message
Fredrik (fredrk) wrote :

I get your point but I really am loosing data as I always forget to manually add the BCC.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the mails you send are stored in the sent folder though no?

Revision history for this message
Fredrik (fredrk) wrote :

They could. But I use no sent folder as it breaks up the threading and make it harder to follow.

So sure, it's my workflow that is extra sensitive to this bug - but it's still a big issue according to me.

I'm happy if I don't need to wait to 8.10.

Changed in evolution:
status: In Progress → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream and the change will be backported to hardy

Changed in evolution:
status: Triaged → Fix Committed
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

I can confirm that the 2.22.1.1 update fixes the issue

description: updated
Revision history for this message
robsyd (robsydemail) wrote :

Just performed last Evolution updates on Hardy (8.10), but BCC field is still empty.

Revision history for this message
robsyd (robsydemail) wrote :

excuse me for two consecutive messages.
I tried with two different accounts.
When I open the new message window (with default account) Bcc is still empty.
If, in the same window, I switch to the second account and than to the default one, the Bcc field is correctly filled with programmed address.

Revision history for this message
Michael R. Head (burner) wrote :

This is still not completely fixed (though it is mostly fixed). Most cases appear to now work but there is at least one that doesn't:

1) select an existing message
2) right click on an email address in the header of the message
3) select Send New Message To...
4) Note that the BCC field is not filled in.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue you describe seems to be bug #92036

Revision history for this message
Michael R. Head (burner) wrote :

bug #92036 is different. It's about when the user clicked a mailto: link in an external link. What I described is, IIRC, part of the regression specific to the 2.22 series.

Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Changed in evolution:
status: Triaged → Fix Committed
Revision history for this message
nic (nic-suzor) wrote :

Fixed, thank you (2.22.1.1-0ubuntu2 amd64).

Revision history for this message
Martin Pitt (pitti) wrote :

hardy-proposed copied to intrepid.

Changed in evolution:
status: Fix Committed → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

verification done:

- test with evolution from hardy (2.22.1-0ubuntu3.1), followed the test case and after create a new message the BCC field is empty.
- test with evolution from proposed (2.22.1.1-0ubuntu3), followed the test case, click on create new message the BCC field contains the email address i've set on the step 1, bug is fixed, thanks.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

ugh, on the step 2 not 1.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in evolution:
status: Fix Committed → Fix Released
Changed in evolution:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.