# Email notification configuration error

**URL:** <https://community.sonarsource.com/t/email-notification-configuration-error/136811>\
**Category:** SonarQube Server / Community Build\
**Created:** [March 14, 2025, 2:30pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811 "2025-03-14T14:30:06Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 14, 2025, 2:30pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/1 "2025-03-14T14:30:06Z")

</div>

Hi, I am using SonarQube Community v25.3.0.104237

Server is deployed to Kubernets with my own helm chart.

I am having problems to configure Email Notification by using my standard AWS SES account that I use for other services.

When I click save, I get `The request cannot be processed. Try again later`

In the console log, I get `401` for the POST request `/api/v2/system/email-configurations`

How can I see more details on what is wrong? I was increasing log levels but did not have any luck.

Attached are the screenshots of my configuration.

 ![Screenshot 2025-03-14 at 15.18.47](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/b/9/b9d0781a6768b315c691a0647eab3c2f760227e5.png)  
 ![Screenshot 2025-03-14 at 15.20.11](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/7/f/7ff6cfef62cea31f02f17bea4c4dcf113b75e391.png)

Thanks,

Ivica.

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 17, 2025, 10:18am UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/2 "2025-03-17T10:18:12Z")

</div>

Hey there.

I suggest you start by finding out **what** exactly is returning a 401 error. SonarQube itself, or something sitting in front of the SonarQube Server (like a load balancer).

Concretely this means looking at your [`access.log`](https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/troubleshooting/server-logs/) to see if a 401 error is being reported upon hitting the `/api/v2/system/email-configurations` endpoint. Can you check that?

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 17, 2025, 1:56pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/3 "2025-03-17T13:56:30Z")

</div>

Thanks for the reply,

Based on nginx logs, I am getting error from the backend service:  
`IP ADDRESS - - [17/Mar/2025:13:48:49 +0000] "POST /api/v2/system/email-configurations HTTP/2.0" 401 0 "https://sonarqube.my.host/admin/settings?category=email_notification" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36" 359 0.008 [sonarqube-sonarqube-9000] [] 10.42.0.68:9000 0 0.004 401 408dacdb2a241a76449f645a66250991`

It is maybe worth mentioning that the GET method to the same endpoint succeeds `/api/v2/system/email-configurations`

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 17, 2025, 1:58pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/4 "2025-03-17T13:58:34Z")

</div>

But is the request actually making it to the SonarQube server? That’s what you’ll find out in the `access.log` file (which I assume is not what you’re showing me, since you mentioned nginx)

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 17, 2025, 2:04pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/5 "2025-03-17T14:04:47Z")

</div>

Yes sorry,

This is the entry from SonarQube’s `/opt/sonarqube/logs/access.log`

`10.42.0.2 - - [17/Mar/2025:14:03:08 +0000] "POST /api/v2/system/email-configurations HTTP/1.1" 401 - "https://sonarqube.my.host/admin/settings?category=email_notification" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36" "73e3bbf7-0a39-4959-9def-cce80cdeda59" 3`

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 17, 2025, 2:10pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/6 "2025-03-17T14:10:17Z")

</div>

No worries, I just wanted to clarify!

Have you tried configuring anything else on your server? I’d like to understand if it’s a problem with just SMTP settings, or if you also face the issue say, updating an exclusion or creating a new user (the former uses Web API v1, the latter Web API v2)

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/0/f/0fb01ed0131692891e2d99b83c1efbd08f985a69.jpeg)  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/6/5/6526c93a8690baa58ec6863b643903462351f648.jpeg)

I’ve seen issues in the past where for some reason (bad cookies, bad loadblancer configuration) only `POST` requests are rejected, but they’re rejected across the board.

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 17, 2025, 2:21pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/7 "2025-03-17T14:21:33Z")

</div>

Oh, I am also getting 401 for creating user.  
 ![Screenshot 2025-03-17 at 15.19.33](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/2/9/297d0c00ce5e17189ea4213f7f04defa9b0d403d.png)

I am using the default `admin` account.

And I can configure the `Global Source File Exclusions` successfully.

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 17, 2025, 2:33pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/8 "2025-03-17T14:33:36Z")

</div>

Maybe will this TRACE logs from `web.log` help

```auto
2025.03.17 13:58:21 TRACE web[7f543d4b-2d54-408a-96df-f5aac2e6be54][o.s.s.p.w.UserSessionFilter] Thread[http-nio-0.0.0.0-9000-exec-35,5,main] serves /api/v2/system/email-configurations
2025.03.17 13:58:21 TRACE web[7f543d4b-2d54-408a-96df-f5aac2e6be54][sql] time=0ms | sql=select st.uuid as uuid, st.user_uuid as "userUuid", st.expiration_date as "expirationDate", st.created_at as "createdAt", st.updated_at as "updatedAt" from session_tokens st where st.uuid=? | params=51a559ed-7eee-4234-b3a4-42de3503dd2d
2025.03.17 13:58:21 TRACE web[7f543d4b-2d54-408a-96df-f5aac2e6be54][sql] time=1ms | sql=SELECT sa.scm_account as "scm_account", u.uuid as uuid, u.login as login, u.name as name, u.email as email, u.active as "active", u.salt as "salt", u.crypted_password as "cryptedPassword", u.hash_method as "hashMethod", u.external_id as "externalId", u.external_login as "externalLogin", u.external_identity_provider as "externalIdentityProvider", u.user_local as "local", u.reset_password as "resetPassword", u.homepage_type as "homepageType", u.homepage_parameter as "homepageParameter", u.last_connection_date as "lastConnectionDate", u.last_sonarlint_connection as "lastSonarlintConnectionDate", u.created_at as "createdAt", u.updated_at as "updatedAt" FROM users u left outer join scm_accounts sa on sa.user_uuid = u.uuid WHERE u.uuid=? | params=9ae10a61-cef1-40bf-806f-b67c8ae03dde
2025.03.17 13:58:21 TRACE web[7f543d4b-2d54-408a-96df-f5aac2e6be54][sql] time=0ms | sql=select gr.role from group_roles gr inner join groups_users gu on gr.group_uuid=gu.group_uuid where gr.entity_uuid is null and gu.user_uuid=? union select gr.role from group_roles gr where gr.group_uuid is null and gr.entity_uuid is null union select ur.role from user_roles ur where ur.user_uuid=? and ur.entity_uuid is null | params=9ae10a61-cef1-40bf-806f-b67c8ae03dde, 9ae10a61-cef1-40bf-806f-b67c8ae03dde
2025.03.17 13:58:21 TRACE web[7f543d4b-2d54-408a-96df-f5aac2e6be54][sql] time=1ms | sql=select kee as "key", is_empty as empty, text_value as value, created_at as createdAt from internal_properties where kee in ( ? ) | params=email.smtp_host.secured

```

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [March 25, 2025, 11:59am UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/9 "2025-03-25T11:59:25Z")

</div>

Hi Colin ,

Do you maybe have an idea why is this happening?

Thanks

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 26, 2025, 4:47pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/10 "2025-03-26T16:47:55Z")

</div>

Hey @Ivica_Vojinovic

I owe you a response and I’m sorry to be late on this one. I’ll try to come back to you tomorrow!

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [March 28, 2025, 4:20pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/11 "2025-03-28T16:20:40Z")

</div>

Hey @Ivica_Vojinovic!

I have two suggestions that might help us narrow down what’s going on:

- To remove any possibility that it’s a client-side issue (your browser), try hitting one of the api/v2 endpoints from the command line. Using `curl`, this would look like:

```auto
curl -i \
    -H "Content-Type: application/json" \
    -u TOKEN: \
    -X POST \
    -d '{"email":"test@test.com","name":"test","local":true,"login":"testAccount","password":"testTest123123!"}' \
    'SONARQUBE_URL/api/v2/users-management/users'

```

Replacing `TOKEN` and `SONARQUBE_URL` with appropriate values.

If that still doesn’t work, I reccomend using the deprecated `POST api/users/create` to create a second account and granting _that_ user admin powers. See if this other account also faces the same issues.

`curl -X POST -u TOKEN: 'SONARQUBE_URL/api/users/create?login=test&name=test&password=TestTest123123!'`

And if **that** fails, please share your Kubernetes helm chart values.

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [April 1, 2025, 11:32am UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/12 "2025-04-01T11:32:33Z")

</div>

Hi Colin,

I’ve managed to create a test user via v2 API…

I also gave admin privileges to that user and tried to perform POST actions with it (like creating another user) but I am again getting 401 error…

Do you have any more ideas where could I look at for the issue?

Thanks,

Ivica

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [April 2, 2025, 3:50pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/13 "2025-04-02T15:50:31Z")

</div>

Hey there.

Hm. It’s sounding more like a client-side issue or something _else_ in the middle (load balancer, reverse proxy). I expect that you could even use [**POST/api/v2/system/email-configurations**](https://next.sonarqube.com/sonarqube/web_api_v2#/system/email-configurations--post) to configure your SMTP settings.

This is going to sound very basic – but does the issue persist in different browsers, and/or after a cache/cookie clear?

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [April 4, 2025, 12:27pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/14 "2025-04-04T12:27:37Z")

</div>

Hi Collin,

So clearing browser cache helped. Now I can execute POST actions and create email configuration.

Unfortunately, I do not manage to set it up correctly. I am using AWS SES configuration that I am using for other services we host and they are working correctly but SonarQube is saying that something is wrong with my configuration.

And I’ve also tried to use Gmail’s smtp with App Password and still no luck.

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/5/c/5c873be1d0fb379f55ab1555ec3072ec6f28a5a7.png)

I’ve also increased log level to trace but could not find anything helpful there.

Let me know if you have any idea…

Thanks,

Ivica.

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [April 9, 2025, 4:19pm UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/15 "2025-04-09T16:19:17Z")

</div>

Hey @Ivica_Vojinovic

In the _web.log_ file at `DEBUG` level you should be able to get a clear(ish) error message.

```auto
2025.04.09 18:18:35 DEBUG web[40d64c12-518b-40b3-92e3-90ce64755ec1][o.s.s.n.e.EmailNotificationChannel] Fail to send test email to test@test.com: {}
org.apache.commons.mail2.core.EmailException: Sending the email to the following server failed : smtp.com:587
	at org.apache.commons.mail2.jakarta.Email.sendMimeMessage(Email.java:1085)
	at org.apache.commons.mail2.jakarta.Email.send(Email.java:1069)
	at org.sonar.server.notification.email.EmailNotificationChannel.send(EmailNotificationChannel.java:238)
	at org.sonar.server.notification.email.EmailNotificationChannel.sendTestEmail(EmailNotificationChannel.java:358)
	at org.sonar.server.email.ws.SendAction.handle(SendAction.java:71)
	at org.sonar.server.ws.WebServiceEngine.execute(WebServiceEngine.java:114)
	at org.sonar.server.platform.web.WebServiceFilter.doFilter(WebServiceFilter.java:84)
	at org.sonar.server.platform.web.MasterServletFilter$JavaxFilterAdapter.doFilter(MasterServletFilter.java:194)
	at org.sonar.server.platform.web.MasterServletFilter$GodFilterChain.doFilter(MasterServletFilter.java:165)
	at org.sonar.server.platform.web.MasterServletFilter$HttpFilterChainAdapter.doFilter(MasterServletFilter.java:208)
	at org.sonar.server.platform.web.SonarQubeIdeConnectionFilter.doFilter(SonarQubeIdeConnectionFilter.java:62)
	at org.sonar.server.platform.web.MasterServletFilter$JavaxFilterAdapter.doFilter(MasterServletFilter.java:194)
	at org.sonar.server.platform.web.MasterServletFilter$GodFilterChain.doFilter(MasterServletFilter.java:165)
	at org.sonar.server.platform.web.MasterServletFilter.doFilter(MasterServletFilter.java:126)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.UserSessionFilter.doFilter(UserSessionFilter.java:83)
	at org.sonar.server.platform.web.UserSessionFilter.doFilter(UserSessionFilter.java:70)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.CspFilter.doFilter(CspFilter.java:67)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.CacheControlFilter.doFilter(CacheControlFilter.java:76)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.SecurityServletFilter.doHttpFilter(SecurityServletFilter.java:60)
	at org.sonar.server.platform.web.SecurityServletFilter.doFilter(SecurityServletFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.RedirectFilter.doFilter(RedirectFilter.java:56)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.EndpointPathFilter.doFilter(EndpointPathFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.RequestIdFilter.doFilter(RequestIdFilter.java:66)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.sonar.server.platform.web.RootFilter.doFilter(RootFilter.java:65)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:115)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:164)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:140)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:483)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:115)
	at ch.qos.logback.access.tomcat.LogbackValve.invoke(LogbackValve.java:268)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:397)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:905)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: jakarta.mail.AuthenticationFailedException: 535 5.7.8 Sorry.

	at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:947)
	at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:858)
	at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:762)
	at jakarta.mail.Service.connect(Service.java:364)
	at jakarta.mail.Service.connect(Service.java:222)
	at jakarta.mail.Service.connect(Service.java:171)
	at jakarta.mail.Transport.send0(Transport.java:230)
	at jakarta.mail.Transport.send(Transport.java:100)
	at org.apache.commons.mail2.jakarta.Email.sendMimeMessage(Email.java:1082)
	... 61 common frames omitted

```

---

<div class="post-metadata">

**Author:** ![Ivica\_Vojinovic](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivica_vojinovic/32/61583_2.png) [@Ivica\_Vojinovic](https://community.sonarsource.com/u/Ivica_Vojinovic)\
**Post date:** [April 10, 2025, 11:02am UTC](https://community.sonarsource.com/t/email-notification-configuration-error/136811/16 "2025-04-10T11:02:02Z")

</div>

Hi Colin,

It turned out that the second issue is with our infrastructure and smtp connectivity.

It is working now when I deployed SonarQube to another machine.

Thanks for you help!

Ivica
