Red Hat Bugzilla – Bug 162028
Evolution connector (MS Exchange) accounts don't keep signature
Last modified: 2018-04-11 12:20:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
Evolution doesn't remember the signature assigned to a connector-based account after restarting Evolution. It remembers other signatures fine. The signature exists and can be selected manually.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up an evolution-connector (MS Exchange) account
2. Create a signature
3. Choose Edit --> Preferences --> Mail Accounts --> <exchange account>
4. Set the created signature as the default
5. Exit Evolution
6. Start Evolution
7. Compose a message
Actual Results: Message has no signature
Expected Results: Message should default to the signature set up in Preferences
Just a "me too" with the latest Evo builds:
Also worth mentioning here that generally setting any kind of preferences in Evo
may affect autocompletition and contacts through GAL. The entries (Global
Address Book and Contact) simply go away.
Bottom line, latest builds of Evo related stuff unfortunately work and feel
exactly the same as the previous ones - all the bugs appear to be there.
And I'll add a me too as well.
If I create a new Signature with the "Add New Signature..." in the connector
preferences (instead of Composer preferences), select that signature and then
restart evolution the signature does appear in my 'New Messages' but is not
selected in my connector preferences. If I restart evolution again, then the
signature no longer appears in my messages, regardless of whether I've been into
the connector preferences the previous reboot.
The new packages that have just been uploaded (2.2.3 for evolution, 1.2.3 for
evolution-data-server) have fixed this for me.
Ok - I spoke too soon. The new packages haven't fixed it. Worked for one
reboot and has now stopped again. Signature problem is now exactly as before.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report. If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
Closing as INSUFFICIENT_DATA.