Set up DMARC and see who's sending email using your brand's domain.
x

How to send transactional emails with Laravel PHP framework

In this post, we’ll go over two ways you can send Laravel emails via Postmark: 

But first, let’s walk through signing up for a free Postmark developer account. If you already have a Postmark account, you can skip this step and go straight to the Laravel setup section

Create a Postmark account and sender signature #

If you don’t have an account, head to the homepage and click “Start Free Trial” in the top right corner. Fill out your account details then click “Let’s get started.”

Postmark account creation page.
Postmark account creation page.

Once you’ve entered your account information, you’ll be taken straight to the Postmark dashboard:

Postmark server dashboard
Postmark server dashboard

Note: Postmark developer accounts are limited to 100 emails per month. Before you can send more than that, you’ll need to go through the account approval process by clicking on the "Request approval" button. To maintain high deliverability rates, Postmark is selective about the types of emails that can be sent.

Set up the Postmark adapter for Laravel #

In the following code examples, we’ll assume that you have a fresh new Laravel project using at least Laravel 5.7 and that you’re using a Mac. Let’s set up the Laravel Postmark adapter.

1. Open terminal and cd to your new Laravel project directory

Terminal window showing Laravel project directory

2. Now run composer require coconutcraig/laravel-postmark:

Installing Postmark adapter for Laravel.

3. Open up your config/services.php and add:

return [
        // ...
        'postmark' => [
            'token' => env('POSTMARK_TOKEN'),    
        ],
    ];

Note: leave POSTMARK_TOKEN, you’ll add the actual secret to your ENV file next.

4. Open your .env file. 

Change MAIL_MAILER from smtp to postmark

Add POSTMARK_TOKEN=<YOUR-SERVER-API-TOKEN-HERE> to the bottom of the file and be sure to replace <YOUR-SERVER-API-TOKEN-HERE> with your Server API token, which you can find in your Postmark dashboard in the API Token section.

Image of the Postmark Credentials page
Server API tokens are found on the Postmark API Tokens page.

That’s it! 

Now whenever you send email through your Laravel app, it will be sent via your Postmark account.

Note: If you’re running a version of Laravel older than 5.7, you can check out and use an older branch of this adapter:

Laravel branch adapter

If you're running older versions, you can check the changelog in GitHub to figure out version compatibility.

Send email via SMTP #

Now let’s look at what it takes to send email via SMTP through Postmark instead of through the Postmark API.

1. Log into your Postmark dashboard, and head to the SMTP tab within the “Setup Instructions” section:

Image of the SMTP section within the Postmark dashboard.
SMTP section within the Postmark dashboard.

2. Next, open up config/mail.php in your favorite text editor.

Change the MAIL_HOST to smtp.postmarkapp.com.

Change the global from name and address to match the sender signature you set up during the Postmark account creation process above. If you have an existing Postmark account and skipped the account creation step above, you can find your sender signature by clicking “Sender Signatures” from your Postmark dashboard.

Finally, change the MAIL_USERNAME and MAIL_PASSWORD to match the username and password listed in your setup instructions:

A couple of notes:

  • Yes, the username and password are intentionally the same. 😉 
  • You can ignore the sendmail driver path as this sends through SMTP, not sendmail.
  • Additional ports and authentication protocols are listed in your setup instructions (in the black box above), but if you don’t know what you’re doing, it’s best to leave them defaulted to port 587, and tls for the protocol.

Big props to Craig Paul for open sourcing his Postmark adapter for Laravel.

Postmark team

Postmark team

Hi, we’re the humans behind Postmark! When you see this signature, you’ll know the piece was written collaboratively by our remote-first team distributed across the globe.