freento / emailslog
Catches all emails sent from a Magento store and additionally logs them to the database.
Emails Log extension for Magento 2
The Emails Log extension for Magento 2 / Adobe Commerce is a powerful debugging tool that allows you to analyze sent emails. Administrators and owners of online stores can use it to see the sending status, content of emails and other necessary and important information.
The report appears in a separate grid and contains the following data for all the emails sent from your Magento 2 store:
- recipient
- Bcc
- subject of the email
- status of the email
- created at and view - active link
You can also export the report for further analysis.
Key features include:
- Comprehensive report
- Clickable column actions
- Built-in export to CSV or Excel XML
- Option to clear records older than (N days)
All columns of the report can be sorted, and almost all can be filtered. Moreover, the report can be exported for further import and analysis. You can export the report to CSV or Excel XML. You can also set up an automatic cleanup of log entries after the number of days you specify.
Refer to the extension page for the full description and user guide: https://freento.com/emails-log.html
Installation
You can install the Emails Log extension with Composer:
composer require freento/emailslog
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 1
| Package | Constraint |
|---|---|
| php | >=8.1 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
No license declared
This package's composer.json doesn't declare a license, homepage, or authors. Check the source repository for terms of use.
More from Freento
View vendorMCP Audit Tools for Magento 2
MCP (Model Context Protocol) server for Magento 2 - All-in-one module
Dimensional Shipping module with REST API integration
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.