When clicking on mailto-link in Firefox, Evolution ignores BCC in settings

Bug #92036 reported by Fredrik
6
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Hardy
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I have configurated Evolution to always do a BCC to myself.
It works fine when i select "Compose" inside Evolution but when I click on a mailto-link in Firefox, Evolution ignores my BCC (leaves it blank).

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

Thank you for your bug. That's known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=274052

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

I think this should be Importance = medium. Atleast for me, this is a big issue.

Is it patched in Gutsy?

Revision history for this message
C de-Avillez (hggdh2) wrote :

@Fredrik Sjögren:

No. It has not been patched upstream, and nobody has (so far) written & proposed a patch for it. Changing the importance here will not give us anything, since we depend on someone being available and willing to look at this bug upstream, and code the fix.

Revision history for this message
Fredrik (fredrk) wrote :

Any news on this one? It's important...

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

why do you consider that important? you have a sent folder which has the mails you sent already

Changed in evolution:
status: Confirmed → Triaged
Revision history for this message
Fredrik (fredrk) wrote :

I do not use the sent folder as it breaks the threads. I want all mails in the thread to be in the same folder. I know MANY people like me.

Why shouldn't Evolution honor my BCC-settings just because it is started from a mailto-link? What's the problem with that?

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

It's important to me because if I BCC a mail to myself, I have a greater degree of certainty that the got out and into the world and a copy stored on my mail server. Sure, as a workaround, I can fiddle Evo's sent folder setting to be a folder on the imap server, but that just copies the message to a mailbox, it doesn't route through SMTP.

In any event, Evo should work properly with any legitimate configuration of the settings it provides. As bug #198167 shows, there is probably a deeper bug here.

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

nobody discuss it being a bug, we just need to know what the usecase are to prioritize correctly the importance of the issue

Revision history for this message
Stefan (fasten) wrote :

I have the very same problem with evolution-2.22.0-0ubuntu2 but not only through "mailto:" links in firefox or other software.

Evolution just *never* does use my "bcc" setting (neither does he use my cc: setting), may I create a new email or reply to an existing one.

This bug is very similar, so is it the same bug or should I open a new one ?

Revision history for this message
Glen (nzwrx) wrote :

I would like to add my voice to this as well. Ever since I upgraded from Gutsy to Hardy a few weeks ago Evolution no longer includes the address in the "Always blind carbon-copy (bcc) to:," regardless of where the composer window originates. As I do work from home, I always bcc myself so that I have a copy of all emails sent from home on my work computer. If I do not remember to add my address manually, I lose emails, which is a Bad Thing. Not life-threatening in terms of importance, but very annoying. Other than that, using Hardy is great!

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

the new upstream version 2.22.1.1 fixes this issue and will be uploaded as an hardy update

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

the update doesn't fix this issue

Changed in evolution:
status: Triaged → Invalid
Changed in evolution:
importance: Unknown → Medium
Changed in evolution:
status: Confirmed → Fix Released
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

change status to invalid (see gnome-bugs)

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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