Configure outgoing mail
In Email & templates, save the intended SMTP profile, send its verification message and enter the code received at the intended mailbox. Configure verified routes for general, billing, support and security mail, including each brand's explicit choices.
Check actual inbox receipt as well as the application's delivery status. Provider acceptance does not guarantee inbox placement. A message without its verified configured route can remain pending; another brand's sender must not be borrowed to make it send.
Incoming email-to-ticket piping is not part of the fresh-install core. A support address configured for routing is not evidence that replies by email create tickets.
Add one scheduler
Use the same PHP 8.4 CLI and the private application directory as the installed release. The normal Laravel scheduler entry point is:
php artisan schedule:run
Configure the hosting account's cron facility to invoke that command once per minute from emaila-cloud-app/, using the host's absolute PHP path. Run one scheduler, not duplicate renewal jobs. Its schedule includes licence checks, the application tick and configured queue/service work; the release's worker mode must match your deployment.
Confirm actual work
Review scheduler heartbeat, due-task states, queue backlog and delivery records. A fresh heartbeat alone does not prove every task succeeded. After interruption or an uncertain send, use delivery troubleshooting rather than manually replaying jobs.