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.

Description of problem:
While configuring a account in Evolution, at the "Sending Mail" Tab, you need to specify a username, if you enabled encryption once.

Version-Release number of selected component (if applicable):
evolution-3.8.5-21.el7.x86_64

How reproducible:


Steps to Reproduce:
1. Create a new account in evolution
2. Under "Sending Email" enable "Server requires authentication"
3. Set "Encrypting method" to: STARTTLS after connecting
4. Click on "Check for supported Types"

Actual results:
The Continue button stays grey, even if you set the "Encrypting method" back to "No encryption" or disable "Server requires authentication". unless you enter a character into the Username field. Than you can disable Server authentication,can click on continue. 

Expected results:
As soon as you disable the Server authentication, the Continue button should be available again.

Thanks for a bug report. I fixed this upstream as [1] for 3.13.4+ and also for 3.12.4+.

[1] https://git.gnome.org/browse/evolution/commit/?id=e837eb2

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.

https://rhn.redhat.com/errata/RHBA-2015-0305.html