If you have lost your SMTP password or want to change it for security reasons, you need to reset it from your Cyberimpact account. This article explains how to proceed and what you need to do afterward.
What it's used for
Resetting your SMTP password allows you to:
- Regain access to your service if you have lost your password
- Secure your access if you believe your credentials have been compromised
- Update your connection settings in your applications
Before you begin
- Administrator access on your Cyberimpact account — only administrators can manage SMTP users
- Once the reset is confirmed, the old password stops working immediately. Make sure you have time to update the configuration in all your applications.
Step by step
- Log in to your Cyberimpact account and access the SMTP section via the main navigation menu.
- Click the Domains tab and open the page of the domain associated with the relevant SMTP user.
- Locate the SMTP user in the Users section and click ⋯ to the right of their name.
- Select Modify from the action menu.
- Click Reset in the Modify SMTP user window.
- Copy the new password.
- Click Save — a Password change confirmation window appears with the newly generated password. If you did not copy it in the previous step, copy the new password now.
- Click Save and close to confirm.
- Update the SMTP configuration in all applications that use this user with the new password.
Tips and tricks
Why can't the old password be recovered?
For security reasons, SMTP passwords are never stored in plain text. It is therefore impossible to display them after creation. The only option is to reset them.
Multiple applications using the same SMTP user?
If several of your applications use the same SMTP user, you will need to update the password in each one after the reset. This is a good reason to create a separate SMTP user per application — that way, a reset only affects one tool at a time.
Not sure which applications are affected?
Check the Last connection field in the user list — it shows the last time the user successfully authenticated. This can help you identify which applications are using this access.
See also: