Skip to content
Reward Loyalty
Get it · $349
Reward Loyalty
Get it · $349 Sign in
Documentation
Back to Home Buy Reward Loyalty

Email sender and templates.

Set up email sending for notifications and verification.

Jul 21, 2026

Reward Loyalty sends emails for registration, password resets, and notifications. Configure your email provider and sender settings.

Sender settings (admin dashboard)

You can configure the sender name and address via the Admin Dashboard:

  1. Navigate to Settings in the admin sidebar
  2. Click the Email Settings tab
  3. Configure the following:
Setting Description
Mail From Name The name that appears as the sender of outgoing emails
Mail From Address The email address used as the sender for outgoing emails
  1. Click Save Changes

The Email Preview section shows how your emails will appear to recipients.

Note: Dashboard settings override environment file values for these fields.

What these settings affect

Your sender name and address appear on all system-generated emails:

  • Welcome emails for new members
  • Email verification and OTP codes
  • Point balance notifications
  • Reward redemption confirmations
  • Staff notifications
  • Partner account emails
  • Contact form messages, sent to the system owner: the admin email captured during installation, or APP_ADMIN_EMAIL if you set that override. The submitter's address becomes the reply-to, so you can reply to them. The recipient is never MAIL_FROM_ADDRESS; until a real owner address is available, the app writes messages to storage/logs/laravel.log instead of an unmonitored placeholder.

Partner-level overrides (business settings)

For emails related to a partner's loyalty programs (points, stamps, vouchers, tiers, campaigns) and store integrations (the order welcome, points, and coupon emails from WooCommerce), the sender name and reply-to are determined by the partner's Business settings:

Setting Where to Configure Used For
Business Name Business settings > Branding Sender "From" name on partner emails
Email Address Business settings > Branding Reply-to address on partner emails
Show email on public card Business settings > Branding Controls whether the email appears as a contact button on the public business card

If these are not set, the partner's account name and email act as fallbacks. System-level settings apply only when no partner-level settings exist.

Important: The Email Address field serves two independent purposes:

  1. Reply-to: Always used as the reply-to address on all partner emails, regardless of any toggle.
  2. Public display: Only shown on the member-facing business card when Show email on public card is enabled. This toggle defaults to off, so existing partners do not expose their email after upgrading.

Note: The "From" email address (e.g., [email protected]) always uses the system-level setting for SPF/DKIM compliance. Only the display name and reply-to are customizable per partner.

See Business settings for full details.

Email provider configuration (.env)

SMTP and email provider settings must be configured in your .env file. These cannot be changed via the Admin Dashboard.

Basic SMTP configuration

MAIL_MAILER=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=587
MAIL_USERNAME=your_username
MAIL_PASSWORD=your_password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS="[email protected]"
MAIL_FROM_NAME="${APP_NAME}"

Provider-specific setup

The exact .env values differ per provider (Gmail, Mailgun, Postmark, Amazon SES, Resend, and others). The email configuration guide owns provider setup: it walks through each provider's settings step by step and shows how to send a test email.

What can be configured where

Setting Admin Dashboard .env File
Mail From Name ✅ Yes ✅ Yes
Mail From Address ✅ Yes ✅ Yes
SMTP Host/Port ❌ No ✅ Yes
SMTP Username/Password ❌ No ✅ Yes
Email Provider (mailer) ❌ No ✅ Yes
API Keys (Mailgun, etc.) ❌ No ✅ Yes

Customizing email templates

The mail views live in resources/views/vendor/mail. The folder holds the HTML and plain-text components behind every message (layout, header, footer, button, panel), and a customized theme ships in html/themes/platform.css for the branded emails.

You can edit these files to change how outgoing email looks. Updates replace them unless you add the folder to PROTECTED_PATHS in your .env file:

PROTECTED_PATHS="resources/views/vendor/mail/"

Important: Without this entry, the next update overwrites your template edits. See Updating for how preserved paths work.

Spam prevention

If registration emails land in spam:

  1. Configure SPF and DKIM records on your domain
  2. Use a reputable email provider (Mailgun, Postmark, SES)
  3. Avoid spam trigger words in email content
  4. Use a dedicated sending domain separate from your marketing emails

Long URLs in registration emails may trigger spam filters. If you have deliverability issues:

APP_REGISTRATION_EMAIL_LINK=false

This disables the automatic login link in registration emails.

Testing

After configuring, test email sending:

  1. Register a new test account
  2. Check if the verification email arrives
  3. Verify it doesn't land in spam
  4. Check the sender name and address are correct

Troubleshooting

Emails not sending:

  • Verify credentials are correct
  • Check your provider's sending limits
  • Review storage/logs/laravel.log for errors
  • Ensure firewall allows outbound SMTP connections

Emails in spam:

  • Configure SPF/DKIM records for your domain
  • Use a dedicated sending domain
  • Consider a transactional email service (Mailgun, Postmark)

Wrong sender name/address:

  • Check Admin Dashboard settings (they override .env)
  • Clear config cache: php artisan config:clear

Cookies on this site.

Google Analytics runs only if you allow it. Cookie policy