This may be the intended function, but it appears to be ripe for abuse and would seem to need to be corrected.
If a server has a reseller user - reseller1 - that has an account - account1 - that is suspended by root, then reseller1 can log into account1's cPanel using their reseller1 password (reseller overwrite ... Tweak Setting -> account_login_access -> owner_root) and change the password to an email account therefore overwriting the email account's suspension.
That email account can then be checked for new mail, and used in SMTP authentication to send out mail. Mostly defeating the point of the account suspension.
Is this the intended behavior?
To duplicate this:
Insure that the tweak setting account_login_access is set to owner_root, which I believe is the default cPanel setting.
Create a new cPanel account on the server - reseller1.
Give that newly created cPanel account (reseller1) reseller privileges.
Log into the WHM using this newly created reseller account (reseller1).
Create a cPanel account on a server (cpuser1).
Log into that cPanel account and create a random test email account ([email protected]).
Note that you can log into that email account and use SMTP authentication with that email account's ([email protected]) username and password.
Log into root's WHM (root)
Suspend the cPanel account (cpuser1)
Note that the email account's username and password ([email protected]) no longer works for POP3/IMAP and SMTP authentication.
Note that the user's cPanel login (cpuser1) is rejected when using the cPanel's username and corresponding password.
Note that logging into the cPanel account (cpuser1) using the reseller's password (reseller1) of the server is successful.
While logged into the cPanel account using the reseller's password, navigate to Email Accounts, choose the random test email account and select Password and Authentication.
Change the password to the email account ([email protected]) to something new.
Note that you can now log into the email account ([email protected]) using POP3/IMAP and use the email account's username and password for SMTP Authentication to send out mail.
This behavior would seem to circumvent the ability of root (the server administrator) from suspending a reseller's resold account (cpuser1) with the intent of preventing that account from being able to send out mail through their email accounts ([email protected]). Perhaps this is the intended behavior - but it seems to be a bad design to me.
If a server has a reseller user - reseller1 - that has an account - account1 - that is suspended by root, then reseller1 can log into account1's cPanel using their reseller1 password (reseller overwrite ... Tweak Setting -> account_login_access -> owner_root) and change the password to an email account therefore overwriting the email account's suspension.
That email account can then be checked for new mail, and used in SMTP authentication to send out mail. Mostly defeating the point of the account suspension.
Is this the intended behavior?
To duplicate this:
Insure that the tweak setting account_login_access is set to owner_root, which I believe is the default cPanel setting.
Create a new cPanel account on the server - reseller1.
Give that newly created cPanel account (reseller1) reseller privileges.
Log into the WHM using this newly created reseller account (reseller1).
Create a cPanel account on a server (cpuser1).
Log into that cPanel account and create a random test email account ([email protected]).
Note that you can log into that email account and use SMTP authentication with that email account's ([email protected]) username and password.
Log into root's WHM (root)
Suspend the cPanel account (cpuser1)
Note that the email account's username and password ([email protected]) no longer works for POP3/IMAP and SMTP authentication.
Note that the user's cPanel login (cpuser1) is rejected when using the cPanel's username and corresponding password.
Note that logging into the cPanel account (cpuser1) using the reseller's password (reseller1) of the server is successful.
While logged into the cPanel account using the reseller's password, navigate to Email Accounts, choose the random test email account and select Password and Authentication.
Change the password to the email account ([email protected]) to something new.
Note that you can now log into the email account ([email protected]) using POP3/IMAP and use the email account's username and password for SMTP Authentication to send out mail.
This behavior would seem to circumvent the ability of root (the server administrator) from suspending a reseller's resold account (cpuser1) with the intent of preventing that account from being able to send out mail through their email accounts ([email protected]). Perhaps this is the intended behavior - but it seems to be a bad design to me.