** Changed in: evolution
Importance: Unknown = Medium
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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
ugh, on the step 2 not 1.
** Tags added: verification-done
** Tags removed: verification-needed
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Copied to hardy-updates.
** Changed in: evolution (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs,
hardy-proposed copied to intrepid.
** Changed in: evolution (Ubuntu)
Status: Fix Committed = Fix Released
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Accepted into -proposed, please test and give feedback here
** Changed in: evolution (Ubuntu Hardy)
Status: Triaged = Fix Committed
** Tags added: verification-needed
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You
Fixed, thank you (2.22.1.1-0ubuntu2 amd64).
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
the issue you describe seems to be bug #92036
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received
I can confirm that the 2.22.1.1 update fixes the issue
** Description changed:
- Binary package hint: evolution
+ configuring a default bcc in the account properties has no effect, the
+ value set there should be used for the new mails
- I set Evolution to bcc myself on all messages. Under
Just performed last Evolution updates on Hardy (8.10), but BCC field is
still empty.
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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.
** Changed in: evolution
Status: In Progress = Fix Released
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
the bug has been fixed upstream and the change will be backported to
hardy
** Changed in: evolution (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: evolution (Ubuntu Hardy)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
** Summary changed:
- [hardy] account default for always bcc doesn't set the field for new message
+ account default for always bcc doesn't set the field for new message
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received
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
The sister bug:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/92036
has been present for very long time (at least Gutsy).
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are
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
I get your point but I really am loosing data as I always forget to
manually add the BCC.
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
the mails you send are stored in the sent folder though no?
--
account default for always bcc doesn't set the field for new message
https://bugs.launchpad.net/bugs/198167
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
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.
--
account default for always bcc doesn't set
22 matches
Mail list logo
