Hi All,
I am trying to change a user's MX routing options via API with the "MX Entry" feature disabled for the user.
After a long search, it appears that this should be done via the WHMAPI1 command 'modifyacct', specifying the MXCHECK-<domain>=string option.
In testing via the command line however, this does not appear to be the case.
I have a test account 'example.com' for user mrzt63d9 on the server. I have made the following attempts, however it always returns MXCHECK-example.com=remote
I've also attempted with integer values (0, 1, 2) with the same result.
How can I alter this option via API without enabling "MX Entry" in the user's feature list and backdooring UAPI/API2?
I am trying to change a user's MX routing options via API with the "MX Entry" feature disabled for the user.
After a long search, it appears that this should be done via the WHMAPI1 command 'modifyacct', specifying the MXCHECK-<domain>=string option.
In testing via the command line however, this does not appear to be the case.
I have a test account 'example.com' for user mrzt63d9 on the server. I have made the following attempts, however it always returns MXCHECK-example.com=remote
- whmapi1 modifyacct user=mrzt63d9 MXCHECK-example.com=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK-example%2Ecom=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK%2Dexample%2Ecom=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK-example.COM=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK-example%2ECOM=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK%2Dexample%2ECOM=local
- whmapi1 modifyacct user=mrzt63d9 MXCHECK=local
I've also attempted with integer values (0, 1, 2) with the same result.
How can I alter this option via API without enabling "MX Entry" in the user's feature list and backdooring UAPI/API2?
Last edited by a moderator: