GNOME Bugzilla – Bug 274052
Auto-BCC ignored when starting from command line
Last modified: 2012-06-20 12:34:57 UTC
Depending on how you start composing new mail BCC and signature from (default?) account setup may or may not be included by default. The preferences should be taken into account in all cases. 1. Compose new mail starting from evolution menus - BCC: present - signature: present 2. Compose new mail by running 'evolution-2.2 mailto:' - BCC: missing - signature: present 3. Compose new mail by running 'evolution-2.2 mailto:?body=foo' - BCC: missing - signature: missing In all cases the signature selector in the composer window indicates the default signature regardless of whether it's actually present or not.
*** This bug has been marked as a duplicate of 272555 ***
This is not about shell meta characters. This is about evolution ignoring certain preferences.
uhhm...damn! sorry, i misunderstood you (i should read it more carefully). :-(
this is just a bug, not a wishlist
This is still present in 2.9.6. A simple way to trigger it is to use "Send Link" from firefox, which I do regularly... Is it hard to fix?
Ubuntu bug https://launchpad.net/bugs/92036
Any progress on this one? I always bcc myself so this bug is making me thinking about to switch to an other mail reader.
evolution mailto:?cc=cc@example.com\&bcc=bcc@example.com\&body=foo works for me - it adds "bcc@example.com" to the BCC list, so i don't see a big issue here (except of the differing behaviours)
A ordniary mailto-link (whithout BCC) should use the BCC-settings from evolution. Like it is now is a BUG.
*** Bug 537404 has been marked as a duplicate of this bug. ***
Fixed the signature issues as part of bug #323142. Adjusting summary.
Cannot reproduce in 3.2.3. evolution mailto:foo@xyz.aa?cc=cc@example.com\&body=body\&subject=subject uses the default BCC for the account defined under "Edit > Preferences > Mail Accounts > Edit > Defaults > Composing Messages > Always blind carbon-copy to". Closing As FIXED.