Skip to Content
Browse documentation

Account Unsuspension Hooks

Handle Eenos unsuspendacct UPDATE hooks and understand already-active accounts, loaded payloads and post-hook failure semantics.

PropertyValue
Function/directoryunsuspendacct
Pre scripts/var/eenos/hooks/unsuspendacct/pre/
Post scripts/var/eenos/hooks/unsuspendacct/post/
Delivered actionsUPDATE
Panel labelwap

The shared unsuspension routine emits unsuspendacct hooks with panel=wap and action=UPDATE. Use the event directory to distinguish it from suspension; action is not UNSUSPEND.

Payload and timing

data is the hosting-user mapping loaded before unsuspension. The pre-hook runs when a suspension marker exists, before account unlock, home permission restoration, marker removal and vhost rebuild. The post-hook follows the try/except block and can run after an exception; no result flag is passed.

If the account is already unsuspended and has no suspension marker, this routine reports that state without emitting these hook calls. Do not use repeated unsuspend requests as a reliable way to trigger custom scripts.

Verify resulting state

Check that the underlying operation actually restored the intended account state before propagating an external activation. Hooks have no rollback/veto contract. Handle repeated events idempotently, keep work bounded and avoid recursively invoking unsuspension from its own hook.

Script contract

Each script receives command-line key=value arguments: base64-encoded JSON data, uppercase action, lowercase panel and optional domain/user. Use the argument decoder examples and installation guide. Scripts run in lexicographic filename order within each phase. There is no automatic retry, hook-specific timeout or parent-operation veto from a nonzero exit code.