Separate message-ID into it's own column to facilitate identifying emails.

In my scenario I have a webhook that will ping my server when the email failed and this gives me a quick way to find in the emails_log table which email has failed.

Hello, I just stumbled upon this as a way to log emails sent. Upon testing it seems to work perfectly. I would, however, like to see a config file where I could change the table name. In my example I name all tables as a category for easier display in PHPmyAdmin. In this case I would name it Logs__Email This way I can keep all my log tables separated and view uncluttered.

Thank you for your consideration.

Useful Package guys,

I have used it on a few projects but having trouble with sending mails with attachments, like PDF documents since it seems to try insert the PDF into the DB.

Sample error: SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\x9C\x03\x00\x00\x00\x00...' for column 'body' at row 1.

I have tried ->attachData() and ->attach() with no luck. PHP7.0 and Laravel 5.4

I send a few mails with attached pdf documents. Unfortunately they can not get saved and are not sent. The reason is that the MySQL TEXT data type can store only 64kB of data. MEDIUMTEXT can save 16MB and LONGTEXT can store up to 4GB. So I simply changed the datatype of attachments from TEXT to LONGTEXT.

This is the error I get on the command line.

 [ErrorException]
  Declaration of ShvetsGroup\LaravelEmailDatabaseLog\LaravelEmailDatabaseLogServiceProvider::boot(Illuminate\Contracts\E
  vents\Dispatcher $events) should be compatible with Illuminate\Foundation\Support\Providers\EventServiceProvider::boot
  ()

Are you planning to update your package to 5.3?

Thanks!

This package fails when used with Laravel 6.0.1.

Problem 1 - Installation request for shvetsgroup/laravel-email-database-log ^1.2 -> satisfiable by shvetsgroup/laravel-email-database-log[1.2]. - Conclusion: remove laravel/framework v6.0.1 - Conclusion: don't install laravel/framework v6.0.1 - shvetsgroup/laravel-email-database-log 1.2 requires illuminate/support ~5.0 -> satisfiable by laravel/framework[5.8.x-dev], illuminate/support[5.0.x-dev, 5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, 5.8.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.4, v5.8.8, v5.8.9]. - Can only install one of: laravel/framework[5.8.x-dev, v6.0.1]. - don't install illuminate/support 5.5.x-dev|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.6.x-dev|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.7.17|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.7.18|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.7.19|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.7.x-dev|don't install laravel/framework v6.0.1 - don't install illuminate/support 5.8.x-dev|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.0|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.16|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.17|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.2|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.28|don't install laravel/framework v6.0.1 - don't install illuminate/support v5.5.33|don't install laravel/framework v6.0.1

I'm trying to use this package to log emails in Laravel 5.5. I'm queuing my email class like so:

$jobId = Mail::to('[email protected]')->queue(new ApiEmail($data));

However, I'm getting an error:

Argument 1 passed to ShvetsGroup\LaravelEmailDatabaseLog\EmailLogger::getMimeEntityString() must be an instance of Swift_Mime_MimeEntity, instance of Swift_Message given, called in ShvetsGroup/LaravelEmailDatabaseLog/EmailLogger.php on line 23 {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalThrowableError(code: 0): Type error: Argument 1 passed to ShvetsGroup\\LaravelEmailDatabaseLog\\EmailLogger::getMimeEntityString() must be an instance of Swift_Mime_MimeEntity, instance of Swift_Message given, called in /vendor/shvetsgroup/laravel-email-database-log/src/ShvetsGroup/LaravelEmailDatabaseLog/EmailLogger.php on line 23 at /vendor/shvetsgroup/laravel-email-database-log/src/ShvetsGroup/LaravelEmailDatabaseLog/EmailLogger.php:33)

Any idea why this is happening?

When sending an email with an hebrew subject (charset is utf-8), it goes like this on the database: =?utf-8?Q?=D7=A8=D7=A9=D7=99=D7=9E=D7=AA_=D7=94=D7=A6?= =?utf-8?Q?=D7=99=D7=95=D7=93_=D7=9C=D7=9E=D7=A9=D7=97=D7=A7_=D7=A0=D7=92?= =?utf-8?Q?=D7=93_=D7=A8=D7=99=D7=90=D7=9C_=D7=9E=D7=93=D7=A8=D7=99=D7=93?= =?utf-8?Q?_=D7=A4=D7=95=D7=A8=D7=A1=D7=9E=D7=94!?=

[ErrorException] Declaration of ShvetsGroup\LaravelEmailDatabaseLog\LaravelEmailDatabaseLogServiceProvider::boot() should be compatible with Illuminate\Foundation\Support\Providers\E ventServiceProvider::boot(Illuminate\Contracts\Events\Dispatcher $events)

Pull #3 break package in laravel 5.2.

This PR will drop all support for Laravel 8.x and below and only support Laravel 9.x. Because Laravel 9.x only supports PHP 8.x and up we also drop support for any old PHP versions.

Because Laravel switched form SwiftMailer to Symfony Mailer the implementation changed and any logged data could be saved differently, if this is the case please let me know. But i think alle should be the same. (I added some tests to have some better feedback for the future).

Hi,

Just wanted to advise that you should implement long texts for body and headers instead just texts, in fact that a user is using or not html emails could make fail the insert query cause too long.

Thanks,

Since updating to the recent version of this package, emails have stopped being stored as they would be sent with the default Laravel templates. Instead, it is pretty much just raw html. Is this intentional? Is there a config to store with laravel templates?

Is there any way to add login user id or email id to identification that which user sent that mail so we can separate the different user data to display that data to particular user ?

currently, I have to display all email log data to admin because i can't get the particular user data from email log table

please think on it and change accordingly

Laravel 9 Error text: stream_socket_client(): Unable to connect to <host>:587 (Operation timed out) And logged in database

Mail::to('[email protected]')->send(new IcsNotificationShipped($obj));

in the email_log table, some fields (addresses and subject) have type 'string', which means laravel creates them with a default length of 255 characters.

however, in case of many e-mails - e.g. in cc - the total length of a header can exceed this character limit. theoretically, a single e-mail address could be up to 320 characters long

before this patch, the length limit was not checked and e-mails would not be logged. error message:

[previous exception] [object] (PDOException(code: 22001): SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'bcc' at row 1 at /var/www/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:115)
[stacktrace]

this patch truncates fields at 255 characters so the log entry can be created. the untruncated contents are still available in the body column.

test code:

Mail::send([], [], function($message) {
    $message->to('[email protected].' . str_repeat('x', 255))->subject('Test')->setBody('E-Mail'); 
});