Laravel IMAP client

2.2.0 2020-10-16 14:29 UTC


Latest Version on Packagist Software License Build Status Code quality Total Downloads Hits


Laravel IMAP is an easy way to integrate both the native php-imap module and an extended custom imap protocol into your Laravel app. This enables your app to not only respond to new emails but also allows it to read and parse existing mails and much more.

If you want to use this library outside of Laravel, please head over to webklex/php-imap for a standalone version.

Table of Contents



1.) Install the Laravel IMAP package by running the following command:

composer require webklex/laravel-imap

1.1.) If you are getting errors or having some other issue, please follow step 1. - 1.1 here.

1.2.) If you are having trouble with v2.0.0, please go ahead and create a new issue and perhaps try the latest v1.6.2 version:

composer require webklex/laravel-imap:1.6.2

2.) If you're using Laravel >= 5.5, package discovery will configure the service provider and Client alias out of the box. Otherwise, for Laravel <= 5.4, edit your config/app.php file and:

  • add the following to the providers array:
  • add the following to the aliases array:
'Client' => Webklex\IMAP\Facades\Client::class,

3.) Run the command below to publish the package config file config/imap.php:

php artisan vendor:publish --provider="Webklex\IMAP\Providers\LaravelServiceProvider"


If you are planning to use a single account, you might want to add the following to your .env file.


Please see webklex/php-imap#Configuration and config/imap.php for a detailed list of all available config options.


Basic usage example

This is a basic example, which will echo out all Mails within all imap folders and will move every message into INBOX.read. Please be aware that this should not be tested in real life and is only meant to gives an impression on how things work.

/** @var \Webklex\PHPIMAP\Client $client */
$client = \Webklex\IMAP\Facades\Client::make([
    'host'          => 'somehost.com',
    'port'          => 993,
    'encryption'    => 'ssl',
    'validate_cert' => true,
    'username'      => 'username',
    'password'      => 'password',
    'protocol'      => 'imap'
/* Alternative by using the Facade
$client = Webklex\IMAP\Facades\Client::account('default');

//Connect to the IMAP Server

//Get all Mailboxes
/** @var \Webklex\PHPIMAP\Support\FolderCollection $folders */
$folders = $client->getFolders();

//Loop through every Mailbox
/** @var \Webklex\PHPIMAP\Folder $folder */
foreach($folders as $folder){

    //Get all Messages of the current Mailbox $folder
    /** @var \Webklex\PHPIMAP\Support\MessageCollection $messages */
    $messages = $folder->messages()->all()->get();
    /** @var \Webklex\PHPIMAP\Message $message */
    foreach($messages as $message){
        echo $message->getSubject().'<br />';
        echo 'Attachments: '.$message->getAttachments()->count().'<br />';
        echo $message->getHTMLBody();
        //Move the current Message to 'INBOX.read'
        if($message->moveToFolder('INBOX.read') == true){
            echo 'Message has ben moved';
            echo 'Message could not be moved';

Please see webklex/php-imap#Table of Contents for more detail and further examples.


If you use the Facade \Webklex\IMAP\Facades\Client::class, please start by selecting an in config/imap.php defined account first followed by Client::connect() to establish an authenticated connection:

use Webklex\IMAP\Facades\Client;

/** @var \Webklex\PHPIMAP\Client $client */
$client = Client::account('default');

View examples

You can find a few blade and mask examples under /examples.


Every time a new message is received, the server will notify the client and return the new message.

The callback and Webklex\IMAP\Events\MessageNewEvent($message) event get fired by every new incoming email.

$timeout = 1200;
/** @var \Webklex\PHPIMAP\Folder $folder */
    /** @var \Webklex\PHPIMAP\Message $message */
    dump("new message", $message->subject);
}, $timeout);


Please take a look at the wiki article for gmail / google mail setup.

Basic oAuth example:

/** @var \Webklex\PHPIMAP\Client $client */
$client = \Webklex\IMAP\Facades\Client::make([
    'host'          => 'somehost.com',
    'port'          => 993,
    'encryption'    => 'ssl',
    'validate_cert' => true,
    'username'      => 'example@gmail.com',
    'password'      => 'ACCESS-TOKEN',
    'authentication' => "oauth",
    'protocol'      => 'imap'

//Connect to the IMAP Server


The following events are available:

  • Webklex\IMAP\Events\MessageNewEvent($message) — can get triggered by Folder::idle
  • Webklex\IMAP\Events\MessageDeletedEvent($message) — triggered by Message::delete
  • Webklex\IMAP\Events\MessageRestoredEvent($message) — triggered by Message::restore
  • Webklex\IMAP\Events\MessageMovedEvent($old_message, $new_message) — triggered by Message::move
  • Webklex\IMAP\Events\MessageCopiedEvent($old_message, $new_message) — triggered by Message::copy
  • Webklex\IMAP\Events\FlagNewEvent($flag) — triggered by Message::setFlag
  • Webklex\IMAP\Events\FlagDeletedEvent($flag) — triggered by Message::unsetFlag
  • Webklex\IMAP\Events\FolderNewEvent($folder) — can get triggered by Client::createFolder
  • Webklex\IMAP\Events\FolderDeletedEvent($folder) — triggered by Folder::delete
  • Webklex\IMAP\Events\FolderMovedEvent($old_folder, $new_folder) — triggered by Folder::move

Additional integration information:


Let's assume you want to run the imap idle process in the background of your server to automatically handle new messages. The following examples will show two major ways to archive this:

Event driven

Start by adding the following to your app/Console/Kernel.php file:

 * The Artisan commands provided by your application.
 * @var array
protected $commands = [

Now register an event listener as described by the laravel docs. If you don't use the default account, or if you want to add some of your own magic, you'll need to create a custom command (see next section).

Finally test the command by running:

php artisan imap:idle 

Custom Command

Create a new file like app/Console/Commands/CustomImapIdleCommand.php and add the following:

namespace App\Console\Commands;

use Webklex\IMAP\Commands\ImapIdleCommand;
use Webklex\PHPIMAP\Message;

class CustomImapIdleCommand extends ImapIdleCommand {

     * The name and signature of the console command.
     * @var string
    protected $signature = 'custom_command';

     * Holds the account information
     * @var string|array $account
    protected $account = "default";

     * Callback used for the idle command and triggered for every new received message
     * @param Message $message
    public function onNewMessage(Message $message){
        $this->info("New message received: ".$message->subject);


..and add the following to your app/Console/Kernel.php file:

 * The Artisan commands provided by your application.
 * @var array
protected $commands = [

Finally test the command by running:

php artisan custom_command

Service setup

A basic systemd service can be setup by creating a service file like this:

nano /etc/systemd/system/imap-idle.service

..and adding:




ExecStart=/var/www/my_project/artisan fetch:idle



You can now test the service by running:

systemctl start imap-idle.service
systemctl status imap-idle.service
systemctl stop imap-idle.service
systemctl restart imap-idle.service


If you encounter any problems or if you find a bug, please don't hesitate to create a new issue. However please be aware that it might take some time to get an answer.

Off topic, rude or abusive issues will be deleted without any notice.

If you need immediate or commercial support, feel free to send me a mail at github@webklex.com.

A little notice

If you write source code in your issue, please consider to format it correctly. This makes it so much nicer to read and people are more likely to comment and help :)


echo 'your php code...';


will turn into:

echo 'your php code...';

Features & pull requests

Everyone can contribute to this project. Every pull request will be considered but it can also happen to be declined. To prevent unnecessary work, please consider to create a feature issue first, if you're planning to do bigger changes. Of course you can also create a new feature issue if you're just wishing a feature ;)

Known issues

Error Solution
Kerberos error: No credentials cache file found (try running kinit) (...) Uncomment "DISABLE_AUTHENTICATOR" inside and use the legacy-imap protocol config/imap.php

Change log

Please see CHANGELOG for more information what has changed recently.


If you discover any security related issues, please email github@webklex.com instead of using the issue tracker.



A special thanks to Jetbrains for supporting this project through their open source license program.



The MIT License (MIT). Please see License File for more information.