PHPackages cylancer/cy\_mail\_to\_news - 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. [Utility & Helpers](/categories/utility) 4. / 5. cylancer/cy\_mail\_to\_news ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) cylancer/cy\_mail\_to\_news =========================== Creates news from emails 1.0.1(3mo ago)20GPL-2.0-or-laterPHP Since Jul 19Pushed 3mo agoCompare [ Source](https://github.com/docmcfly/cyMailToNews)[ Packagist](https://packagist.org/packages/cylancer/cy_mail_to_news)[ RSS](/packages/cylancer-cy-mail-to-news/feed)WikiDiscussions main Synced today READMEChangelog (3)Dependencies (4)Versions (5)Used By (0) Typo3 extension cyMailToNews ============================ [](#typo3-extension-cymailtonews) Change log ---------- [](#change-log) - 1.0.1 : FIX : Fix the depends version syntax. - 1.0.0 : UPD : Release news extension in version 14. - 0.9.12 : FIX : Category parser has a small bug. - 0.9.11 : FIX : Compose requirment: "georgringer/news" : ">=12.3.0" - 0.9.10 : FIX : Remove warning in the get data metod. - 0.9.9 : FIX : Default media is displayed only in the list view. - 0.9.8 : FIX : Fix the mail seen flag handling. - 0.9.7 : FIX : Fix the attachment folder validation. - 0.9.6 : FIX : Checkbox in the scheduler configuration works as expected. - 0.9.5 : CHG : Change the extension icon. - 0.9.4 : FIX : Manipulation rules for the news content rendering. - 0.9.3 : FIX : htmlspecialchars encoding / decoding - 0.9.2 : FIX : Fix the mail part analyse (mail in mail problem) - 0.9.1 : UPD : Alpha version - 0.9.0 : INI : Initial Templates --------- [](#templates) You can descript the form of your news title or news body. ### A very simple example [](#a-very-simple-example) Title: ``` Automatic news ``` => the title is always "Automatic news" ### A simple example [](#a-simple-example) Title: ``` {Subject} ``` => Your title is replaced with the subject. ### Combination of very simple and simple example [](#combination-of-very-simple-and-simple-example) Title: ``` Automatic news: {Subject} ``` => Your title is a combination of the static text: "Automatic news: " and the dynamic subject part. ### A simple example with a special tag [](#a-simple-example-with-a-special-tag) Body: ``` {body} ``` => Your body is replaced with the mail text body. You have three body options: - `"bodyHtml"` returns the HTML text of the email (if available) - `"bodyPlain"` returns the plain text of the email (if available) - `"body"` returns the HTML text of the email, if available; otherwise, the plain text. ### A stronger example with replacement [](#a-stronger-example-with-replacement) You can manipulate the content of the replacement. Title: ``` {Subject pattern="^\[spam] (.*)$" replacement="$1"} ``` => Example set the title with the mail subject without the start word "\[spam\]". **HINT:** The replacement rule will ignore if the pattern does not matched. In this example: When your mail subject has not a spam marker, the news title has the original subject. Filter rules ------------ [](#filter-rules) The filter rules are defined in a JSON format. When the regex rule (set) matches, the task creates a news from the mail and mark this mails as "readed". ``` { "Subject": "[regex]", "body": "[regex]" } ``` `[regex]` is a placeholder for a regular expression. The keys are mail header keys or one of these special keys: - `"bodyHtml"` returns the HTML text of the email (if available) - `"bodyPlain"` returns the plain text of the email (if available) - `"body"` returns the HTML text of the email, if available; otherwise, the plain text. Category rules -------------- [](#category-rules) The category rules are defined in a JSON format. When a regex rule (set) matches, the news is added with the specified category. ``` { "[categoryUid]": { "Subject": "[regex]", "body": "[regex]" } } ``` `[categoryUid]` is a placeholder for an integer and the category identifier. `[regex]` is a placeholder for a regular expression. The keys are mail header keys or one of these special keys: - `"bodyHtml"` returns the HTML text of the email (if available) - `"bodyPlain"` returns the plain text of the email (if available) - `"body"` returns the HTML text of the email, if available; otherwise, the plain text. ### Health Score 34 — LowBetter than 75% of packages Maintenance82 Actively maintained with recent releases Popularity2 Limited adoption so far Community6 Small or concentrated contributor base Maturity40 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 ~126 days Total 3 Last Release 96d ago Major Versions 0.9.12 → 1.0.12026-03-29 ### Community Maintainers ![](https://www.gravatar.com/avatar/e80d990786107e860444861a172251e6e67ac84d1c9717179755018a912df534?d=identicon)[docmcfly](/maintainers/docmcfly) --- Top Contributors [![docmcfly](https://avatars.githubusercontent.com/u/7195547?v=4)](https://github.com/docmcfly "docmcfly (9 commits)") ### Embed Badge ![Health badge](/badges/cylancer-cy-mail-to-news/health.svg) ``` [![Health](https://phpackages.com/badges/cylancer-cy-mail-to-news/health.svg)](https://phpackages.com/packages/cylancer-cy-mail-to-news) ``` ### Alternatives [friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 103519.9k53](/packages/friendsoftypo3-content-blocks)[wazum/sluggi TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects 40529.5k](/packages/wazum-sluggi)[typo3/cms-lowlevel TYPO3 CMS Lowlevel - Technical analysis of the system. This includes raw database search, checking relations, counting pages and records etc. 178.2M316](/packages/typo3-cms-lowlevel)[typo3/cms-redirects TYPO3 CMS Redirects - Create manual redirects, list existing redirects and automatically createredirects on slug changes. 167.4M80](/packages/typo3-cms-redirects)[typo3/cms-form TYPO3 CMS Form - Flexible TYPO3 frontend form framework that comes with a backend editor interface. 147.6M265](/packages/typo3-cms-form)[derhansen/sf_event_mgt Event management and registration - Configurable event management and registration extension based on ExtBase and Fluid 66338.4k10](/packages/derhansen-sf-event-mgt) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)