Token expiration email not using complete mail config

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SQ 10.3 on docker (Community and Developer edition)


We received lately an email indicating that a token is about to expire. This is fine.

Issue is the email in itself did not used Email prefix configured field, making the email quite generic.
We would expect that any email send from SQ will use the configured email settings.

title: Your token "token_name" will expire.

Your token "token_name" will expire on April 02, 2024.

Token Summary


If this token is still needed, please consider [generating](link to sq here, only way to identify the instance) an equivalent.

Don't forget to update the token in the locations where it is in use. This may include the CI pipeline that analyzes your projects, the IDE settings that connect SonarLint to SonarQube, and any places where you make calls to web services.
1 Like


Thank you for bringing this to us.

Can you also provide us with the following info:

  • Can you share the screenshot of your From name and Email prefix configuration ?
  • Can you confirm the mail you are getting now has the default value i.e. Sonarqube(noreply@nowhere) ?


Hi @revanshu.paliwal

i have edited initial message, turns out only the Email Prefix field is not used properly for token expiration email.

As a working example, email about license expiration is properly using the Email Prefix field, so this is probably just a matter of template…


1 Like