• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Question suspicious email address automatically created in plesk panel

skrdknd

New Pleskian
Server operating system version
CentOS 7
Plesk version and microupdate number
18.0.55
I have Plesk installed on my dedicated server and a couple of client accounts. Five suspect email addresses were recently generated automatically in one of the customers. [email protected] is the email address.

Why was this email produced, and how can it be avoided?

Can somebody give me some tips on how to avoid it?
 
They could have been created by a script through API. They could have also been created by an extension, although I am not aware of extensions that do this. It is also possible that - if a subscription allows root access - a script in the subscription itself runs a Plesk command on the server to create the mailboxes. Finally, it is thinkable that a hacker gained access to the account by stealing username and password and simply created the mailboxes manually. That can be avoided by using the Google Authenticator 2FA extension to protect account access.
 
If you install the Action Log extension, you can monitor who or what creates a mail account (amongst others):
 
Back
Top