Configuring From and Reply-To Addresses in Laravel Mail

When Laravel sends email, the From address identifies who the message appears to come from, while Reply-To tells email programs where to direct a recipient’s reply. Laravel lets you set both as shared defaults or choose them for individual messages. The From address also affects email authentication: receiving providers check whether the domain in that address matches the domain authenticated by the sending service.

A display name is the readable label shown alongside an email address, such as “Example Support.” It helps recipients recognize the sender, but it does not authenticate the message. The visible From and Reply-To addresses are message headers, or fields that describe the email. They are separate from the sending service’s technical handling of delivery and bounces.

Set shared defaults in Laravel

Put the From and Reply-To defaults in config/mail.php when most messages use the same sender identity and reply destination. Laravel’s mail configuration supports an address and display name for each:

// config/mail.php

'from' => [
    'address' => env('MAIL_FROM_ADDRESS', 'notifications@example.com'),
    'name' => env('MAIL_FROM_NAME', 'Example Support'),
],

'reply_to' => [
    'address' => env('MAIL_REPLY_TO_ADDRESS', 'support@example.com'),
    'name' => 'Example Support',
],

The From default applies when a mailable does not specify its own From address. Laravel configuration lets you set different addresses for each environment instead of hard-coding them into every message. Choose an address on a domain your organization controls and has prepared for sending mail.

Choose addresses for an individual message

A Laravel mailable, a class that defines an email message, can set its own From and Reply-To addresses in the envelope() method. Use this when a message needs a different sender or reply destination, such as a billing address for invoices:

use Illuminate\Mail\Mailables\Address;
use Illuminate\Mail\Mailables\Envelope;

public function envelope(): Envelope
{
    return new Envelope(
        from: new Address('notifications@example.com', 'Example Support'),
        replyTo: [
            new Address('support@example.com', 'Example Support'),
        ],
        subject: 'Your order has shipped',
    );
}

Laravel’s mailable documentation explains these Envelope fields. When Laravel sends a notification by email, the notification can also set a From address for that message. Laravel describes this option in its notification mail settings.

Understand what each sender field controls

The From header identifies the message’s author. The Reply-To header gives the recipient’s email program a suggested destination for replies. Under RFC 5322, replies normally go to From when Reply-To is absent. When Reply-To is present, email programs generally use that address for replies, though some reply-command behavior depends on the program. Laravel sets the address in the message; it does not route incoming replies or guarantee how every email program handles them.

Two other sender fields serve different purposes. The Sender header identifies the person or service transmitting a message when that sender differs from the author. The SMTP envelope sender is an address used during mail delivery and commonly handles bounce messages, which report delivery failures. Laravel’s standard From setting does not set either value consistently across all mail transports and providers. Check your provider’s documentation or inspect a delivered message and provider logs when those values matter.

Align the From domain with email authentication

A Laravel From setting controls a message header. It does not configure domain authentication. SPF lets receiving providers check whether a sending service is authorized for a domain. DKIM adds a signature that receiving providers can verify. DMARC checks whether the domain in the visible From address aligns with a domain authenticated through SPF or DKIM.

Google’s sender guidelines require senders who send mail to Gmail to use SPF or DKIM authentication. Bulk senders must use SPF, DKIM, and DMARC. Configure your sending provider and the domain’s records to authenticate mail for the domain used in From. A Reply-To address directs replies; it does not replace authentication or align the From domain with a domain authenticated through SPF or DKIM.

Authentication helps with delivery, but Laravel’s From or Reply-To settings alone do not guarantee that a message reaches the inbox instead of spam. Receiving providers make delivery decisions based on authentication and other sending signals. A display name can help recipients recognize an email, but it does not prove that the sender controls the displayed domain.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com