RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 772652 - Evolution picks default account address when it does not make sense
Summary: Evolution picks default account address when it does not make sense
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 6.4
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 883010
Blocks: 1025695
TreeView+ depends on / blocked
 
Reported: 2012-01-09 14:35 UTC by David Jaša
Modified: 2014-01-02 09:08 UTC (History)
5 users (show)

Fixed In Version: evolution-2.32.3-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1025695 (view as bug list)
Environment:
Last Closed: 2013-11-21 05:04:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
evo patch for the "Send New Message To..." (1.05 KB, patch)
2012-01-10 12:32 UTC, Milan Crha 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1540 0 normal SHIPPED_LIVE Low: evolution security, bug fix, and enhancement update 2013-11-21 00:40:51 UTC

Description David Jaša 2012-01-09 14:35:09 UTC 
Description of problem:
I have two accounts in Evolution: personal (default) and corporate (non-default). When addressing emails to corporate suffix or when writing a message to an address in corporate account, I expect my corporate account to be used. Evolution however picks up default address which causes frequent Message Delivery Failures or weird mail usage.

Version-Release number of selected component (if applicable):
evolution-2.28.3-24.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. go to some folder in non-default account, select a message
2. right-click any address in message header, click "Send a new message To..."

OR

1. look some mail in non-default account, write a new message

OR

1. start writing some email to @company.com address
  
Actual results:
New message window pops up with default address

Expected results:
non-default account should be pre-chosen in all three cases

Additional info:
Comment 1 David Jaša 2012-01-09 15:08:34 UTC 
Based on discussion with developer, I'd add three more points:

* reply / reply to all works as expected

* both accounts are IMAP

* third case can be questionable but still can make sense (like if some "this is corporate account" checkbox that would be account properties would be ticked)
Comment 2 David Jaša 2012-01-09 16:47:37 UTC 
(In reply to comment #0)
... 
> 1. look some mail in non-default account, write a new message
> 

A little clarification to this: the bug occurs when a sub-folder is active, when I choose a folder that is direct "child" of account in tree view, the actual account is chosen rightly.
Comment 3 Milan Crha 2012-01-10 12:13:13 UTC 
(In reply to comment #0)
> 1. go to some folder in non-default account, select a message
> 2. right-click any address in message header, click "Send a new message To..."

I can reproduce this one.

> 1. look some mail in non-default account, write a new message
(In reply to comment #2)
> A little clarification to this: the bug occurs when a sub-folder is active,
> when I choose a folder that is direct "child" of account in tree view, the
> actual account is chosen rightly.

I cannot reproduce this one. Whenever I do File->New->Mail Message, or click the "New" button on the tool bar, or just press Ctrl+N, I get preselected From in the composer based on the account the folder I stay in belongs to. The only exception is all under On This Computer and Search Folders, where is preselected the default account, because these has no association with real accounts.

> 1. start writing some email to @company.com address
(In reply to comment #1)
> * third case can be questionable but still can make sense (like if some "this
> is corporate account" checkbox that would be account properties would be
> ticked)

I would not do this one. There would be a complication with multiple recipients being filled, for example, and I do not think it being a useful option. The other two issues should cover this one already.
Comment 4 Milan Crha 2012-01-10 12:28:40 UTC 
I forgot to mention, I do this all from the main Mail view, with the preview panel being on (I do not use extra message window, like when user double-clicks the message in the message list).
Comment 5 Milan Crha 2012-01-10 12:32:32 UTC 
Created attachment 551825 [details]
evo patch for the "Send New Message To..."

for evolution;

This lets the "Send New Message To..." preselect From based on the account folder the message is show in.
Comment 7 Suzanne Logcher 2012-02-14 23:27:31 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8 RHEL Program Management 2012-07-10 06:35:42 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 9 RHEL Program Management 2012-07-10 23:09:00 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 10 RHEL Program Management 2012-12-14 07:08:17 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 22 errata-xmlrpc 2013-11-21 05:04:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html
Note You need to log in before you can comment on or make changes to this bug.