The issue is private, because it contains logs and other information from a user that can't be shared.
The problem only affects the verify button though, so if you configure your email and don't hit verify it will work. Here's a workaround you can use to verify this:
- Log in as an administrator.
- Go to Email.
- Re-enter the credentials carefully, make sure Enabled is checked, and click Save. Don't click Verify.
- Now go to Tasks.
- Create Task.
- Select Execute script.
- Enter:
- a name
- set notification email to an account you can check
- groovy for the language
- For script source, enter just 'throw new IllegalStateException("foo")' (no single quotes)
- Select Manual for task Frequency
- Save, then run your new task.
You should get an email successfully. If true, that means repository manager can successfully send through your SES account; the Verify control on the Email view just doesn't use the correct credentials.