Run Jooosi Mail commands with WP-CLI from the WordPress installation directory. Start with read-only status commands, then use worker, retry, or test commands when you are ready to trigger delivery.
Inspect profiles and connections#
wp jooosi-mail connection:profiles
wp jooosi-mail connection:list
wp jooosi-mail connection:status --all
Use the profile catalog to check supported schemes and required fields. Connection status shows which routes are available. See Provider profiles and transports.
Send a test and inspect attempts#
wp jooosi-mail mail:test [email protected]
wp jooosi-mail mail:test [email protected] --connection-id=3
wp jooosi-mail mail:attempts --limit=20
Replace the example address and connection ID. A test sends a real email to the address you specify.
Check and process the queue#
wp jooosi-mail queue:status
wp jooosi-mail queue:work --limit=25 --time-limit=20
wp jooosi-mail queue:processing --limit=20
wp jooosi-mail queue:release-stale --older-than=300
wp jooosi-mail queue:failed --limit=20
wp jooosi-mail queue:retry --id=42
Replace 42 with the failed queue message ID. The worker can deliver messages; retry schedules another
attempt. Read Queue
operations and retries before working failed or stale messages.
Check webhooks#
wp jooosi-mail webhook:status --all=true
wp jooosi-mail webhook:events --limit=20
wp jooosi-mail webhook:events --connection-id=3
Replace the example connection ID with the connection to inspect. See Provider webhooks for callback setup and verification.
Check runtime state#
wp jooosi-mail container:status
wp jooosi-mail migration:status
These commands report the service container cache and database migration state. For product settings and operational flows, return to the Jooosi Mail documentation overview.