Why Buzzy Email Stops Reaching Inboxes
Buzzy relies on outbound transactional mail for the things users actually notice: account verification links, password resets, notification digests, and admin alerts. When those messages silently vanish, the application itself usually appears healthy, so the problem is easy to misdiagnose as a bug. On a managed shared platform running LiteSpeed over CloudLinux, the real cause is almost always the mail transport layer and how the sending domain authenticates, not the PHP code inside Buzzy.
The first common failure is the default transport. If Buzzy is configured to use PHP's built-in mail() function, messages are handed to the local MTA with a generic envelope sender and no authentication. Modern receivers at Gmail, Outlook, and Yahoo treat unauthenticated mail from shared IP ranges with heavy suspicion. Even when the message is accepted, it frequently lands in spam or is rejected outright with a 550 policy error. This is why switching Buzzy to authenticated SMTP is the single most effective change you can make.
The second failure pattern is a mismatch between the envelope sender, the visible From header, and the domains that actually publish SPF and DKIM records. If Buzzy sends as no-reply@yourdomain.com but your DNS has no SPF entry authorizing the mail server, or the DKIM signature does not match, receivers downgrade or discard the message. On shared hosting you cannot touch the server MTA configuration, but you can and should control the DNS records for your own domain and the sender settings inside Buzzy's admin area.
The third pattern is queue backlog. Buzzy batches larger sends, such as notification fan-out, through a queue that is drained by a scheduled task. If that cron job never runs, or runs as the wrong user, queued mail accumulates and nothing is delivered until the backlog is cleared manually. Understanding which of these three layers is failing tells you exactly where to apply the fix, and all three are solvable with unprivileged account tools.
Configuring Authenticated SMTP in Buzzy
Start by creating a dedicated mailbox for the application rather than reusing a personal address. In cPanel open Email Accounts and add something like no-reply@yourdomain.com with a strong password. In DirectAdmin the equivalent path is E-Mail Manager → E-Mail Accounts → Create Account. A dedicated mailbox keeps the application's sending reputation isolated and makes it trivial to rotate the password without disrupting human users.
Next, point Buzzy at that mailbox over SMTP. Log in to the Buzzy admin dashboard and open Settings → Email (or System Settings → Mail Configuration, depending on your build). Change the mail driver from mail or sendmail to smtp and enter the local server values. Because the mailbox lives on the same account, use the server's own hostname and the authenticated submission port:
Mail Driver: smtp
SMTP Host: mail.yourdomain.com
SMTP Port: 465
Encryption: SSL
SMTP Username: no-reply@yourdomain.com
SMTP Password: (the mailbox password)
From Address: no-reply@yourdomain.com
From Name: BuzzyIf port 465 with SSL is blocked or refused, fall back to port 587 with TLS/STARTTLS, which is the standard submission port on LiteSpeed-based hosts. Keep the username and the From Address identical; a sender that authenticates as one address but presents a different From header is a reliable way to trigger spam filtering. After saving, use the built-in Send Test Email button if your Buzzy version exposes one, and confirm the message arrives with correct headers.
Some Buzzy distributions store mail settings in a configuration file rather than the database. If the admin panel does not expose SMTP fields, open File Manager in cPanel, navigate to the Buzzy root (commonly /home/username/public_html or a subfolder), and edit the .env file. Set the matching keys and save:
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="Buzzy"After editing .env, clear any cached configuration. If Buzzy ships an admin cache-clear button, use it; otherwise deleting the files under bootstrap/cache/ through File Manager forces the new values to load on the next request. Watch the application's own log at storage/logs/laravel.log or the per-folder error_log for authentication failures, which usually indicate a wrong password or a blocked port rather than a DNS problem.
SPF, DKIM, and DMARC for the Sending Domain
Authenticated SMTP gets the message out of Buzzy cleanly, but receivers still check whether your domain authorizes that server to send on its behalf. These checks live in DNS, which you manage through the Zone Editor in cPanel or DNS Management in DirectAdmin. Most managed hosts publish a correct SPF and DKIM record automatically when a domain is added, but migrated or externally-hosted DNS frequently loses them.
Verify an SPF TXT record exists on the root domain. A minimal correct record authorizes the host's mail servers and nothing else:
Type: TXT
Host: @
Value: v=spf1 +a +mx include:_spf.yourhost.com -allUse the exact include value your hosting panel recommends rather than guessing, and never publish more than one SPF record on the same domain, which invalidates both. For DKIM, cPanel's Email Deliverability page shows the current signing key and flags any record that is missing or mismatched; click Repair to have the panel install the correct public key into the zone. In DirectAdmin, DKIM is managed under E-Mail Manager → DKIM.
Add a conservative DMARC record once SPF and DKIM pass, so receivers know how to treat failures and where to send reports:
Type: TXT
Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.comStart with p=none to monitor without risking legitimate mail, then tighten to quarantine once reports confirm alignment. The Email Deliverability panel in cPanel Jupiter consolidates all three checks on one screen, making it the fastest place to confirm the sending domain is fully aligned before you troubleshoot anything else. The same authentication principles apply to other PHP applications; our companion article on LaraClassified email and SMTP delivery covers the equivalent setup for a Laravel-based classifieds platform.
Queue Handling and the Scheduled Drain
Buzzy queues high-volume mail so a single page request does not stall while dozens of notifications are sent. That queue only moves when a worker processes it on a schedule, and on shared hosting you drive that schedule with a cron job rather than a long-running daemon. In cPanel open Cron Jobs, or in DirectAdmin go to Advanced Features → Cron Jobs, and add an entry that runs the application scheduler every minute:
* * * * * /usr/local/bin/php /home/username/public_html/artisan schedule:run >/dev/null 2>&1Confirm the PHP binary path matches the version selected in the MultiPHP Manager or PHP Selector for that domain; a mismatched interpreter silently fails. If Buzzy uses a persistent queue connection such as database or Redis, add a bounded worker that exits cleanly instead of running forever, which shared hosting process limits will otherwise kill:
* * * * * /usr/local/bin/php /home/username/public_html/artisan queue:work --stop-when-empty --max-time=55 >/dev/null 2>&1The --stop-when-empty and --max-time flags keep the worker within the CloudLinux resource envelope and let the next cron tick pick up new jobs. When mail appears stuck, inspect storage/logs/laravel.log and the failed_jobs table in phpMyAdmin; a growing failed-jobs count points at SMTP credentials or port issues, while an empty queue table with no delivery points back to DNS alignment. Working methodically from transport, to authentication, to the queue drain resolves nearly every Buzzy delivery problem without needing any server-level access.