PHPackages ressourcenmangel/rsmbouncemailprocessor - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Mail & Notifications](/categories/mail) 4. / 5. ressourcenmangel/rsmbouncemailprocessor ActiveTypo3-cms-extension[Mail & Notifications](/categories/mail) ressourcenmangel/rsmbouncemailprocessor ======================================= A TYPO3 extension that handles bounce mails in combination with cute\_mailing. 2.2.1(2y ago)12[1 issues](https://github.com/ressourcenmangel/rsmbouncemailprocessor/issues)GPL-2.0+PHPPHP ^8.1 Since Nov 22Pushed 1y ago6 watchersCompare [ Source](https://github.com/ressourcenmangel/rsmbouncemailprocessor)[ Packagist](https://packagist.org/packages/ressourcenmangel/rsmbouncemailprocessor)[ Docs](https://www.ressourcenmangel.de/)[ RSS](/packages/ressourcenmangel-rsmbouncemailprocessor/feed)WikiDiscussions main Synced 1mo ago READMEChangelogDependencies (4)Versions (8)Used By (0) EXT:rsmbouncemailprocessor ========================== [](#extrsmbouncemailprocessor) A TYPO3 Extension for newsletter bounce handling Introduction ============ [](#introduction) Why did we create the "rsmbouncemailprocessor" extension? --------------------------------------------------------- [](#why-did-we-create-the-rsmbouncemailprocessor-extension) - When sending newsletters for many years, the number of bounces will increase. The more bounces you send, the worse the sender's ranking with email providers like Gmail, Yahoo, T-Online and so on. - The idea behind the extension is to achieve automatic bounce handling for newsletters and thus minimize the rate of bounces. - Furthermore the extension supports list unsubscribe header handling via e-mail Requires -------- [](#requires) - This extension was developed for use with [cute\_mailing](https://extensions.typo3.org/extension/cute_mailing/) by undkonsorten - cute\_mailing should be used with [tt\_address](https://extensions.typo3.org/extension/tt_address/) to allow automatic cleaning of email addresses - When sending the newsletters, an e-mail address must be defined as the sender to which bounce e-mails are delivered. This e-mail address must be a POP3 / IMAP account Features -------- [](#features) - Automatic reading of e-mails received in the bounce mailbox via POP3 or IMAP. - Analyze the emails based on the headers set by cute\_mailing (X-TYPO3RCPT and X-TYPO3NLUID) - Reading the original recipient (aka E-Mail) from the header field X-TYPO3RCPT (fallback x-failed-recipients) and the newsletter from the header field (TYPO3NLUID as the cute\_mailing sendout) - Analyzes the reason for the bounce mail using a rule set extensible via TS - Analyzes the mails generated by mail apps with the "list unsubscribe header" and removes those addresses - Generates statistics per newsletter with the reason of bounces - Generates statistics per recipient with the reason of bounces - Deletes recipients from tt\_address when one or more bounde reasons have exceeded their limit - Logging the deletion of recipients by bounce handling - Logging the deletion of recipients by "list unsubscribe header" handling - Offers some Cleaner-tasks to clean taskqueue, recipient-reports, receiver-report, delete-logs entries Setup ===== [](#setup) Installation ------------ [](#installation) Install this extension from the [TYPO3 Extension Repository](https://extensions.typo3.org/extension/rsmbouncemailprocessor/) and activate the extension in the Extension Manager of your TYPO3 installation. Once installed, configure cute\_mailing and then this extension configure your POP3 / IMAP email bounce account ----------------------------------------------- [](#configure-your-pop3--imap-email-bounce-account) - Create a POP3/IMAP enabled E-Mail account, for example . configure cute\_mailing ----------------------- [](#configure-cute_mailing) The configuration is made by cute\_mailing [page-TS](https://docs.typo3.org/p/undkonsorten/typo3-cute-mailing/3.1/en-us/Configuration/Index.html#page-ts-config) These following settings are important for us: Set the bounce email address from as the sender / reply to address ``` reply_to = bounce@myfancydomain.de return_path = bounce@myfancydomain.de ``` enable the "list unsubscribe header" ``` listunsubscribe_enable = 1 listunsubscribe_email = bounce@myfancydomain.de ``` configure this extension by TS ------------------------------ [](#configure-this-extension-by-ts) The configuration is made by Typoscript-Setup! You'll find an example in the default configuration in Configuration/TypoScript/setup.typoscript. All the parameters are explained in the file. Just copy that file, edit it for your user and include it. #### settings.reasontext [](#settingsreasontext) You should not change settings.reasontext unless you know what you are doing. #### settings.deletelog [](#settingsdeletelog) You should enable the delete log via settings.deletelog.enabled and the settings.deletelog.pid. #### settings.deletelimits [](#settingsdeletelimits) Check out the settings.deletelimits! The delete limits specify how often (per emal / address) a bounce-reason must occur so that the recipient is deleted from the tt\_address table. Without changing these values, no addresses will be deleted! ### settings.deletetables [](#settingsdeletetables) Check out settings.deletetables if you want the tables mentioned there to be cleaned automatically. This is an optional feature. configure the taskplaner tasks ------------------------------ [](#configure-the-taskplaner-tasks) There are several TYPO3 tasks which are partly otpional. ### RSM analyze bounce mail (rsmbouncemailprocessor) [](#rsm-analyze-bounce-mail-rsmbouncemailprocessor) This is the primary task that reads and analyzes the bounce-mails and created the statistics. So, yes, this task is required. Let's say you've 40.000 recipients and you're sending 2.000 mails every 15 minutes. Your recipient ist quite old and you expect 10% bounces. Your POP3 is small and can store 800 mails. Your POP3 account would be full after one hour. So it would make sense to retrieve the POP3 mails every 30 minutes. This task should thus be started every 30 minutes - or more often. The **server** options are the data that apply to your POP3 / IMAP account. ``` Server URL/IP: The IP or URL of your mail server (e.g.: pop3.yourmailserver.com) Port number: The port number of your mail server (e.g.: 995) Username: The username / login for the mail account (e.g.: horstmueller) Password: The password / login for the mail account (e.g.: geheim0815) Type of mailserver: Either POP3 or IMAP. POP3 should be a goog option. ``` [![alt text](Documentation/Images/screen_taskplaner_analyze.png "Logo Title Text 1")](Documentation/Images/screen_taskplaner_analyze.png) For **other** options here a few hints: ``` Number of bounce mail to be processed: 250 ``` We use the PHP IMAP class to read the mails. With a lot of mails this class becomes very slow, so the value should not be too high. We have had good experiences with a value of 250. ``` Delete every mail ``` Normally your POP3 account has a maximum size and no human has the time to read bounce mails. If you set this option to true, what we're recommending, you make sure that the POP3 account will never overflow. ### RSM process bounce mail (rsmbouncemailprocessor) [](#rsm-process-bounce-mail-rsmbouncemailprocessor) This is the second task entry that scans the recipient-report table for addresses to be deleted. This requires that the settings.deleteimits have been set in the TS-Setup! You can run this task once a day e.g. in the early morning or whenever you prefer. ### RSM clean task queue (rsmbouncemailprocessor) [](#rsm-clean-task-queue-rsmbouncemailprocessor) This is the third task and it is used for data cleaning. It is optional! You can run this task once a day e.g. in the early morning or whenever you prefer. This task is again set up by the TS-setup options. See settings.deletetables! ### The Backend Module [](#the-backend-module) The extension comes with it's own BE module for displaying bounce reports and recipient reports **bounce report** [![bounce report](Documentation/Images/screen_be_bounce_report.png "bounce report")](Documentation/Images/screen_be_bounce_report.png) **recipient report** [![alt recipient report](Documentation/Images/screen_be_bounce_recipients.png "recipient report")](Documentation/Images/screen_be_bounce_recipients.png) ### The TYPO3 List [](#the-typo3-list) If you have set up the deletelog, you'll will find some lig entries in the TYPO3 BE list. See deletelog-pid. **Delete Log** [![Delete Log](Documentation/Images/deletelog_recipients.png "Delete Log")](Documentation/Images/deletelog_recipients.png) **List Unsubscribe Log** [![Delete Log](Documentation/Images/deletelog_listunsubscribe.png "Delete Log")](Documentation/Images/deletelog_listunsubscribe.png) TODOs ----- [](#todos) - none at the moment Credits ------- [](#credits) This extension was created by Ralph Brugger for [ressourcenmangel](https://www.ressourcenmangel.de/). Many thanks to Eike Starkmann from [undkonsorten](https://www.undkonsorten.com/) for developing and extending cute\_mailing! ### Health Score 22 — LowBetter than 22% of packages Maintenance8 Infrequent updates — may be unmaintained Popularity4 Limited adoption so far Community10 Small or concentrated contributor base Maturity56 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~21 days Recently: every ~26 days Total 6 Last Release 795d ago Major Versions v1.0.0 → v2.0.02023-11-24 ### Community Maintainers ![](https://www.gravatar.com/avatar/2b9818b4fbec510c5963e5edfc30ce52bee267147d75747a6f78f64e0f1cd781?d=identicon)[m-kappenberg](/maintainers/m-kappenberg) ![](https://www.gravatar.com/avatar/f5820e4f8eaea9707d3403281ddc757235d4db63d445595b6ef232e9f211dcc3?d=identicon)[linkpool](/maintainers/linkpool) --- Top Contributors [![LinkPool2](https://avatars.githubusercontent.com/u/117345721?v=4)](https://github.com/LinkPool2 "LinkPool2 (1 commits)") --- Tags emailtypo3newslettercute\_mailing ### Embed Badge ![Health badge](/badges/ressourcenmangel-rsmbouncemailprocessor/health.svg) ``` [![Health](https://phpackages.com/badges/ressourcenmangel-rsmbouncemailprocessor/health.svg)](https://phpackages.com/packages/ressourcenmangel-rsmbouncemailprocessor) ``` ### Alternatives [aimeos/aimeos-typo3 Professional, full-featured and high performance TYPO3 e-commerce extension for online shops and complex B2B projects 1.5k91.2k4](/packages/aimeos-aimeos-typo3)[typo3/testing-framework The TYPO3 testing framework provides base classes for unit, functional and acceptance testing. 675.0M775](/packages/typo3-testing-framework)[directmailteam/direct-mail Advanced Direct Mail/Newsletter mailer system with sophisticated options for personalization of emails including response statistics. 39209.3k2](/packages/directmailteam-direct-mail)[pagemachine/typo3-formlog Form log for TYPO3 23225.3k6](/packages/pagemachine-typo3-formlog)[leuchtfeuer/secure-downloads "Secure Download": Apply TYPO3 access rights to ALL file assets (PDFs, TGZs or JPGs etc. - configurable) - protect them from direct access. 22234.7k1](/packages/leuchtfeuer-secure-downloads)[in2code/luxletter Free newsletter extension for TYPO3 for an individual email marketing. A lot of analytics and modern concepts. Works with and without EXT:lux. 2572.3k2](/packages/in2code-luxletter) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)