LaraClassified sends a steady stream of transactional email: account verification links, password resets, listing approval notices, payment confirmations, and the contact-seller messages that make a classifieds site function. When any of those fail silently, registrations stall and sellers never hear from buyers. On a Managed Cloud Shared Hosting account you do not control the server MTA or root configuration, so every fix lives inside the application, your hosting control panel, and your domain's DNS zone. The good news is that LaraClassified is a Laravel application, which means its mail behavior is fully configurable from files and panels you already have access to.

The most common failure is that the application tries to send through PHP's default mail() transport. On a shared LiteSpeed server that mail often lands in spam or is rejected outright because it lacks proper authentication and a matching envelope sender. Switching to authenticated SMTP against a mailbox on your own domain fixes the majority of delivery problems before you touch anything else.

Why LaraClassified mail fails on shared hosting

Laravel reads its mail settings from the .env file in the application root and from config/mail.php. When LaraClassified is installed, the installer writes an initial MAIL_* block, but it frequently defaults to the sendmail or mail driver with a placeholder MAIL_FROM_ADDRESS like noreply@example.com. Three things then go wrong at once: the sending domain does not match your real domain, there is no SMTP authentication, and the receiving server cannot verify that your server is allowed to send for that domain.

Receiving providers such as Gmail, Outlook, and Yahoo evaluate three signals before trusting a message: an SPF record authorizing the sending host, a DKIM signature matching the From domain, and an envelope sender that aligns with the visible From address. The PHP mail() path on a shared box usually fails alignment because the envelope sender becomes the Unix account user rather than your domain mailbox. Authenticated SMTP to a mailbox you created in cPanel or DirectAdmin solves this, because the message is then handled by the server's own mail system with the correct identity and local DKIM signing already in place.

Before changing anything, confirm what the application currently believes. In cPanel open File Manager and navigate to the LaraClassified root (commonly /home/USERNAME/public_html or a subdirectory). Enable Show Hidden Files (dotfiles) from Settings, then open .env. In DirectAdmin the equivalent is File Manager under the domain's public_html. Read the existing MAIL_MAILER, MAIL_HOST, and MAIL_FROM_ADDRESS values so you know your starting point. Keep the local error log open too: Laravel writes mail exceptions to storage/logs/laravel.log, and that file is usually the fastest way to see a rejected login or a connection timeout.

Create a mailbox and configure SMTP

First create a dedicated sending mailbox so authentication uses a real account. In cPanel go to Email Accounts > Create and make something like no-reply@yourdomain.com with a strong password. In DirectAdmin use E-Mail Accounts > Create Account. After creating it, open the account's Connect Devices (cPanel) or mail client settings to confirm the exact SMTP hostname. On most Hostiso accounts the secure hostname is your server's mail host or mail.yourdomain.com on port 465 with SSL, or port 587 with STARTTLS.

Now edit .env through File Manager. LaraClassified uses the standard Laravel keys, so set them to point at the mailbox you just created:

MAIL_MAILER=smtp
MAIL_HOST=mail.yourdomain.com
MAIL_PORT=465
MAIL_USERNAME=no-reply@yourdomain.com
MAIL_PASSWORD=your-mailbox-password
MAIL_ENCRYPTION=ssl
MAIL_FROM_ADDRESS=no-reply@yourdomain.com
MAIL_FROM_NAME="Your Site Name"

If you prefer STARTTLS, use MAIL_PORT=587 and MAIL_ENCRYPTION=tls instead. Keep MAIL_FROM_ADDRESS identical to MAIL_USERNAME so the envelope and header senders align. Because LaraClassified also exposes mail fields inside the admin panel, log in to the back office at /admin and open Settings > Mail. Values entered there are written back to the application configuration, so set the same host, port, username, encryption, and from-address to avoid a mismatch where the database overrides your file. After saving, Laravel caches configuration; if the panel does not clear it automatically, delete the cached config file at bootstrap/cache/config.php through File Manager so new values are read on the next request.

Test immediately. Trigger a password-reset email to an inbox you control, then watch storage/logs/laravel.log. A Connection could not be established error means the host or port is wrong or outbound SMTP is being blocked, in which case try the alternate port. A 535 Authentication failed message means the username or password is incorrect, or the username needs the full user@domain form rather than just the local part.

Align SPF, DKIM, and DMARC for deliverability

Authenticated SMTP gets the message out; DNS determines whether it reaches the inbox. In cPanel open Email Deliverability (Jupiter theme) to see SPF and DKIM status for your domain. The panel will show whether records are valid and offer the exact values to publish if they are missing. In DirectAdmin the same controls live under E-Mail Accounts > DNS or the SPF/DKIM management section. Resolve any warnings there first, because the panel generates records that match your server automatically.

A working SPF record authorizes your hosting server to send for the domain and typically looks like v=spf1 +a +mx +ip4:SERVER_IP ~all, though the exact value is what Email Deliverability presents. Never publish two SPF records on one domain; combine them into a single line. DKIM signing is handled by the mail server once enabled, and the public key is published as a TXT record that the panel inserts for you. Add a conservative DMARC record as a TXT entry on _dmarc.yourdomain.com such as v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.com so you receive aggregate reports while you confirm alignment, then tighten the policy later. Allow DNS changes time to propagate, and verify by sending a message to a Gmail account, opening it, and using Show original to confirm SPF, DKIM, and DMARC all read PASS.

Queue handling and sending volume

LaraClassified can send mail synchronously during the web request or push it onto a queue. Synchronous sending is fine for low volume, but a slow SMTP handshake makes registration and checkout pages feel sluggish, and a hiccup can throw a visible error. Queued mail writes jobs to the jobs database table and sends them in the background, which keeps the user-facing pages fast. Set QUEUE_CONNECTION=database in .env to enable it, and make sure the queue tables exist from the original installation.

Because you cannot run a persistent queue:work daemon without SSH on shared hosting, drive the queue with a scheduled cron job instead. In cPanel open Cron Jobs, or in DirectAdmin open Cron Jobs under Advanced Features, and add an entry that processes a short burst of jobs every minute. Use the PHP binary matching the version you selected in MultiPHP Manager or PHP Selector, and reference the full path to artisan:

* * * * * /usr/local/bin/php /home/USERNAME/public_html/artisan queue:work --stop-when-empty --tries=3 >/dev/null 2>&1

The --stop-when-empty flag lets the process exit once the queue drains so it never runs forever, and --tries=3 retries transient SMTP failures before marking a job failed. If LaraClassified also relies on a scheduler for digests or cleanup, add the standard artisan schedule:run cron on the same minute cadence. Watch your outbound volume: shared hosting enforces an hourly email limit per domain, so bulk notifications can hit that cap and queue up as deferred. Keep transactional mail lean, avoid sending large batches from the same mailbox, and if your site grows into heavy marketing sends, move that traffic to a dedicated mail service rather than the hosting mailbox. Any mail that cannot be delivered after its retries lands in the failed_jobs table, which you can inspect through phpMyAdmin to diagnose recurring recipients or authentication drift.