friendsoftypo3/tt-address

Store mail recipients

friendsoftypo3/jumpurl

Used for click tracking

typo3/cms-redirects

Used for redirects of shorted links in plain text mails

scssphp/scssphp

This package transpiles scss files to css, which makes it possible to use the scss files of foundation mail and change there values (colors, dimensions) using typoscript constants. I had to modify the original scss from foundation a little, because the scssphp package could currently not handle sass modules like math, which were used on some places. See https://github.com/scssphp/scssphp/issues/421 for more information. Basically, I just replaced all math.div() with /.

pelago/emogrifier

This package is needed to convert all css to inline styles, which is unfortunately necessary for outlook and co.

league/html-to-markdown

This package is used to convert an html mail to a plain text (markdown) version using a middleware, just by adding ?plain=1 to the url. It has the ability to add own converters, which is used by this extension to handle the mail boundaries, which wrapped around every content element.

masterminds/html5

This package is used on several places to extract specific parts of a mail (e.g. links, images, special data attributes).

ddeboer/imap

This package is used by the AnalyzeBounceMailCommand to read the mail account of returned mails.

Patreon

Support me on patreon.com

PayPal

Support me on paypal.com.

It's just one click away!

Rate it

In any case, please rate my extension here: https://extensions.typo3.org/extension/mail

and if you are using composer to install it, here as well: https://packagist.org/packages/mediaessenz/mail

To do so, you have to login first in the corresponding system.

Thank you!

Update the database scheme

After the first install, depending of the way (composer or other), it could be necessary to update the database, to get ready for go.

Open your TYPO3 backend with t3start:system-maintainer permissions.

In the module menu to the left navigate to Admin Tools > Maintenance, then click on Analyze database and create all.

Clear all caches

Clearing all caches after installing a new extension is always a good thing.

In the same module like before, you can also conveniently do this by clicking the button Flush cache.

Further reading

• Global extension configuration
• Site configuration (Recipient sources and mail transport settings)
• TypoScript configuration
• Page TSconfig configuration

MAIL comes with a lot of possibilities:

• From pages

  • Compare to EXT:direct_mail, MAIL is not limited to fe_groups, fe_users, tt_address and one custom table
  • It is possible to add as many tables you like, as long they have the needed fields or an extbase model which implements at least the RecipientInterface, defined in Classes/Domain/Model/RecipientInterface.php
  • To make it even more flexible it is possible to define query restrictions (for tables) or use the RecipientsRestrictionEvent (for extbase) to filter recipients list. Checkout https://gitlab.com/mediaessenz/additional-mail-recipients how to do it.
  • Beside the recipient source (table) it is also possible to set a starting point where the records should be taken from
  • Categories can also be set to filter the list of recipients to only those who have at least one of them assigned as well

• Plain list

  • A comma separated list of recipients (just mails or names and mails separated by a comma or semicolon)
  • Compare to EXT:direct_mail, within MAIL you also can choose whether the recipients should get html or plain mails.
  • Categories are also assignable

• CSV (Plain/File)

  • Configurable CSV input format (different separators, enclosures and check if first line contain field names)
  • If the first line doesn't contain the fieldnames, the order of the data must be "name", "email" and (optionally) "salutation"
  • Data can be plain pasted into the data field or from a selected csv file (must be utf-8 encoded!)
  • Compare to EXT:direct_mail, within MAIL you also can choose whether the recipients should get html or plain mails.
  • Categories are also assignable

• Static list

  • Single records of all defined sources can be added – also fe_groups which will add all fe_users who have this groups assigned.

• From other recipient lists

  • To make things even more flexible, it is also possible to create a compilation of different other recipient groups.

Some EXT:direct_mail power users may miss the possibility to define queries as sending groups. This feature is currently not available, and will maybe come with a future release. Sponsoring is highly welcome.

Importing CSV data (plain/file) as tt_address records

This module, which needs tt_address to be installed, gives you the option to import a csv (comma-separates list) of addresses as tt_address records, which could be added as "From pages" or "Static list" recipient group afterwards.

To make it easier to import csv records, there is a wizard, which guide you through the process.

In the first step you can choose to upload a csv file or paste the records into a text field. You can use comma (;), semicolon (;), or colon (:) as field delimiter. This can be configured in the second step.

By clicking the NEXT button, the csv file or csv records are uploaded and the second step is shown. In this step you can specify the detail information of the csv data, such as field delimiter, field encapsulation, and field name in the first line. You can also specify the sys-folder, where the records should be imported to, the uniqueness of the records, rename or update the records if a similar record is found, or to empty the sys-folder before importing.

After specifying the configuration you can start mapping the fields. There are 3 columns in the mapping step. The description column shows the first row of the csv records (if you set in the configuration that the first row is the field names) or shows only field_xx (where xx is continuous number).

The mapping column shows only the list of field, which are part of tt_address table. You must at least map the field “Name” and “Email”.

The value column shows the first up to three rows from the csv records. They should help you to map the field.

You can also set the HTML flag or categories to all records you are importing.

In the select box, which contains the field names of tt_address, there is also an entry “categories”. This entry can be mapped to a comma-separated list of sys_category IDs. This value will overwrite whatever categories you selected in the “Additional options” section.

After mapping the fields you are ready to start the import process by pressing the IMPORT button. If finished a list of new imported, invalid email, updated and doublet records will be shown.

This process generates tt_address records in the choosen folder. To create a recipient group from this records, you must add a new recipient group of the type “From pages” and select “Addresses” as Recipient source. Then choose the folder where you imported the records under "Startingpoint" and finally press Save.

Wrong Entry Point

This extension needs an entry point with a protokoll and domain to proper fetch internal pages.

An entry point with just a slash ("/") will not work!

This value can be set here "Sites Module" > "Edit site" > "General" > "Entry Point".

If you e.g. use the introduction package, this value is set to "/" by default!

Self Signed Certificates

If you use a self signed certificate, you should also check, that "HTTP" > "verify" is set to "0".

This can be done under "Admin Tools" > "Settings" > "Configure Installation Wide Options" > Filter by "verify" > enter "0" > Press "Write configuration"

Jumpurl Error Messages

The current version of jumpurl found in ter (8.0.3) has some php 8 issues:

• https://github.com/FriendsOfTYPO3/jumpurl/issues/33
• https://github.com/FriendsOfTYPO3/jumpurl/issues/36
• https://github.com/FriendsOfTYPO3/jumpurl/issues/37

There is already a pending pull request, which unfortunately stuck in that state since a while:

• https://github.com/FriendsOfTYPO3/jumpurl/pull/35

To help your self out, you could download the zip of the pull request repo, which contains the necessary fixes under this url:

• https://github.com/woodyc79/jumpurl_t3v11/archive/refs/heads/master.zip

After downloading, rename the master.zip to jumpurl_8.0.3.zip and upload it within the extension manager.

Mail

Feature

Direct Mail Migration

Transport.yaml

This configuration should only be used as a copy base for your own mail transport settings. The supported parameters are the same as definable in $GLOBALS['TYPO3_CONF_VARS']['Mail'].

Adding one or more of this setting inside your site configuration is only necessary if you like to override the mail transport setting for a specific site. If a property is not set via site config, there corresponding system setting is used, defined in $GLOBALS['TYPO3_CONF_VARS']['Mail']. The overrides do only affect the transport settings used by EXT:mail or its MEDIAESSENZ\Mail\Mail\(Mailer|MailMessage) classes.

RecipientSources.yaml

To add all recipient sources come with MAIL (fe_groups, fe_users, tt_address) you has nothing to do.

MAIL imports the settings stored in this file:

imports:
   - { resource: "EXT:mail/Configuration/Site/RecipientSources.yaml" }

If you would like to add your own recipient sources, just add it to your site configuration under the key mail.recipientSources.

Here is an example of how to add a table which has all necessary fields (at least uid, email, name, salutation, mail_html, mail_active):

mail:
   recipientSources:
      tx_extension_domain_model_address: #<- Table name
         title: 'LLL:EXT:extension/Resources/Private/Language/locallang.xlf:tx_extension_domain_model_address.title' #<- title of the recipient source
         icon: 'tcarecords-tx_extension_domain_model_address-default' #<- icon identifier

To simplify things a bit, it is also possible to ignore the mail_html and mail_active fields (they not need to exist at all). To do this, just add forceHtmlMail: true or/and ignoreMailActive: true to your recipientSource configuration.

It is also possible to use a table more than once to create recipient sources with a subset of e.g. tt_address records.

mail:
   recipientSources:
      female_tt_address:
         table: 'tt_address'
         title: 'Female filtered tt_address records using table'
         icon: 'tcarecords-tt_address-default'
         queryRestrictions:
           - 'MEDIAESSENZ\AdditionalMailRecipients\Database\Query\Restriction\FemaleRestriction'
         csvExportFields: [uid,gender,name,first_name,middle_name,last_name,title,email,phone,www,address,company,city,zip,country,fax,categories,mail_salutation,mail_html,tstamp]

In this case the table name has to be defined as table property. To create a subset of tt_address records, one or more QueryRestrictions can be defined.

Such a QueryRestrictions could look like this:

<?php
namespace MEDIAESSENZ\AdditionalMailRecipients\Database\Query\Restriction;

use TYPO3\CMS\Core\Database\Query\Expression\CompositeExpression;
use TYPO3\CMS\Core\Database\Query\Expression\ExpressionBuilder;
use TYPO3\CMS\Core\Database\Query\Restriction\QueryRestrictionInterface;

class FemaleRestriction implements QueryRestrictionInterface
{
    public function buildExpression(array $queriedTables, ExpressionBuilder $expressionBuilder): CompositeExpression
    {
        $constraints = [];
        foreach ($queriedTables as $tableAlias => $tableName) {
            if ($tableName === 'tt_address') {
                // attention: since gender is a string in tt_address the value has to be set in double quotes!
                // normally this should be done with help of the $queryBuilder->createNamedParameter('f', Connection::PARAM_STR)), but here we do not have the query builder :-(
                $constraints[] = $expressionBuilder->eq(
                    $tableAlias . '.' . 'gender',
                    '"f"'
                );
            }
        }
        return $expressionBuilder->and(...$constraints);
    }
}

If a table doesn't contain the upper mentioned fields, or the fields have different names, it is also possible to use an extbase model to map fields to the need. A site configuration doing this could look like this:

mail:
   recipientSources:
      tx_extension_domain_model_address: #<- Table name
         title: 'LLL:EXT:extension/Resources/Private/Language/locallang.xlf:tx_extension_domain_model_address.title' #<- title of the recipient source
         icon: 'tcarecords-tx_extension_domain_model_address-default' #<- icon identifier
         model: Vendor\Extension\Domain\Model\MailAddress #<- the extbase model

Beside of the site configuration a model definition and a mapping configuration is needed as well. Check the included model EXT:mail/Classes/Domain/Model/Address.php and EXT:mail/Configuration/Extbase/Persistence/Classes.php for how this can look like.

The model needs to implement at least the included RecipientInterface. If you like to use categories, to send specific parts of a mail only to a specific group of recipients, the included CategoryInterface has to be implemented as well.

Since this extension can handle simple tables and extbase models as well, and in the end its data only used to replace a simple placeholder like ###USER_name###, I decided to use simple arrays for transporting.

Because of this, every model needs to have a getEnhancedData method, which must return an array of all fields, which should serve as placeholder later on. Btw.: The same method will be used by the csv-export inside the recipient group module.

It is also possible to create a subset of record from a domain model source.

Since MAIL doesn't use the "normal" repository classes of a model, this restriction has to be added as an event listener (RecipientsRestrictionEvent).

An example how this could look like, can be found here: https://gitlab.com/mediaessenz/additional-mail-recipients

The responsible files in the example extension are

• Configuration/Services.yaml (line 16-19)
• Configuration/Site/RecipientSources.yaml (line 12-19)
• Classes/EventListener/AddressModelRestriction.php.

Page View Settings

All page view settings need to be prefixed with plugin.mail.view.page.

Content View Settings

All content view settings need to be prefixed with plugin.mail.view.content.

Header Settings

All header settings need to be prefixed with plugin.mail.settings.header.

SCSS Settings

All scss settings need to be prefixed with plugin.mail.settings.scss.

Content Objects

This extension brings two new content object EMOGRIFIER and SCSS

EMOGRIFIER is used to transform all given css files to inline styles.

SCSS is used to transform given scss files to css.

See EXT:mail/Configuration/TypoScript/ContentElements/setup.typoscript for how to use.

Frontend related (mail content)

This extension come with three static Page TSconfig files, which all can be found here:

EXT:mail/Configuration/TsConfig/Page

• ContentElement/All.tsconfig removes all not supported fluid_styled_content elements from the newContentElement wizard of TYPO3.
• BackendLayouts/Mail.tsconfig adds a very simple one-column backend layout for mail content to the system.
• TCADefaults.tsconfig contain some default pages settings which does not (for me) make sense in context of mails.

Backend related (modules)

All this MAIL configuration properties must be set in the Page TSconfig field of the MAIL sys-folder under the key mod.web_modules.mail.

Most of these properties may conveniently be set using the MAIL configuration module.

The following properties set default values for corresponding properties of mails and can (mostly) changed in the settings step of the mail wizard.

Restrict categories example

Here is an Page TSconfig example of how to restrict a list of categories to a specific parent category (has uid 1 in this example):

TCEFORM.tt_content.categories.config.treeConfig.startingPoints = 1
TCEFORM.tt_content.categories.config.treeConfig.appearance.nonSelectableLevels = 0
TCEFORM.tt_address.categories.config.treeConfig.startingPoints = 1
TCEFORM.tt_address.categories.config.treeConfig.appearance.nonSelectableLevels = 0
TCEFORM.fe_users.categories.config.treeConfig.startingPoints = 1
TCEFORM.fe_users.categories.config.treeConfig.appearance.nonSelectableLevels = 0
TCEFORM.tx_mail_domain_model_group.categories.config.treeConfig.startingPoints = 1
TCEFORM.tx_mail_domain_model_group.categories.config.treeConfig.appearance.nonSelectableLevels = 0

This config placed in the Page TSconfig field of the MAIL sys-folder page, will reduce all categories shown in tt_content, tt_address, fe_users and for simple list recipient groups living inside the MAIL sys-folder to the parent category with the uid 1.

Beside of this, the nonSelectableLevels = 0 lines prevent the parent category itself to be selectable.

AdditionalMailHeadersEvent

Adds possibility to modify mail headers

DeactivateRecipientsEvent

To deactivate returned mail recipients within the report module (beside tt_address and fe_users), it is necessary to register corresponding event listeners.

See MEDIAESSENZ\Mail\EventListener\DeactivateAddresses and DeactivateFeUsers for example.

VENDOR\ExtensionKey\EventListener\DeactivateMyAddresses:
  tags:
    - name: 'event.listener'
      identifier: 'vendor/extensionkey/deactivate-my-addresses'

ManipulateCsvImportDataEvent

Adds possibility to modify csv data during import them to tt_address records. This needs tt_address to be installed.

ManipulateMailRecipientsEvent

Adds possibility to manipulate the recipients list of a mailing right after finishing the mail wizard.

ManipulateMarkersEvent

See MEDIAESSENZ\Mail\EventListener\AddUpperCaseMarkers for example.

MEDIAESSENZ\Mail\EventListener\AddUpperCaseMarkers:
  tags:
    - name: 'event.listener'
      identifier: ''mediaessenz/mail/add-upper-case-markers'

ManipulateRecipientEvent

See MEDIAESSENZ\Mail\EventListener\ManipulateAddressRecipient and MEDIAESSENZ\Mail\EventListener\ManipulateFrontendUserRecipient for example.

RecipientsRestrictionEvent

Adds possibility to restrict recipients from extbase model sources

ScheduledSendBegunEvent

Adds possibility to do something after scheduled sending begun

ScheduledSendFinishedEvent

Adds possibility to do something after scheduled sending finished

MassMailingCommand

This command is responsible for adding scheduled mailings to the sending queue. There are two mandatory parameters:

• site-identifier
• send-per-cycle

The first one (site-identifier) is the identifier of the site configuration where MAIL can find its recipient sources configuration. You can find it inside the TYPO3 sites module under the "General" tab.

The second (send-per-cycle) determine how many mails should be sent per cycle.

The time between a cycle can be defined in the "Frequency" field of a task. e.g. * * * * * will run the task every minute, if you put 50 into the send-per-cycle field, 50 Mails per minute will be sent.

AnalyzeBounceMailCommand

This command fetches returned mails from the mail account defined in the return-path field of the MAIL configuration module. Depends on special headers, the reason of the return will be added to the report of the corresponding mail.

SpoolSendCommand

This command controller can be used to send mail in a queue. It's basically the same coming with TYPO3, but it uses a site specific mail transport configuration. See site configuration Transport.yaml under Integration up in this manuel. To make this command controller work, it is also necessary to set transport_spool_type to file or memory. if the type was set to file, the transport_spool_type has to be set as well, e.g. to upload/tx_mailspool/. This command controller is not really needed by this extension, since the sending is already queued by the MassMailingCommand. But if a developer wants to use the extended Mail-Classes MEDIAESSENZ\Mail\Mail\(Mailer|MailMessage) inside their own extension, it can be usefully.

ClearScssParserCacheCommand

This command controller clears the scss parser cache files located in typo3temp/assets/mail/css. This cache is also cleared after a mail report is deleted.

PreviewLinksViewHelper

<f:variable name="previewLinks" value="{mail:previewLinks(uid:uid,pageId:pageId)}"/>

GetBodyContentViewHelper

Extract the body tag content of the mail html content. Used to embed the mail html content.

{mail.htmlContent -> mail:getBodyContent()}

RemoveMailBoundariesViewHelper

Remove the mail boundaries from the mail plain content. Used to embed the mail plain text content.

{mail.plainContent -> mail:removeMailBoundaries()}

ConstantViewHelper

   <f:variable name="contentSelectionBoundary" value="{mail:constant(name:'CONTENT_SECTION_BOUNDARY')}"/>
<!--{contentSelectionBoundary}_-->Content for all<!--{contentSelectionBoundary}_END-->
<!--{contentSelectionBoundary}_1-->content for category 1<!--{contentSelectionBoundary}_END-->
<!--{contentSelectionBoundary}_1,2,3-->content for category 1, 2 and 3<!--{contentSelectionBoundary}_END-->

TYPO3 13 compatibility + Recipient group refactoring

• Add more possibilities to manipulate recipient groups using query restrictions on tables or extbase model based recipient sources
• Enhanced csv based recipient groups
• Add feature to reduce the list of recipients of a mailing by choosing one or more other recipient groups
• Improved bounce mails handing (needs IMAP account now!)

New features

• Add RecipientsRestrictionEvent to manipulate querys of extbase model recipient sources. This way it is now possible to e.g. filter recipient lists coming from extbase.

  See here how to use:

  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Site/RecipientSources.yaml (recipientSources:male_tt_address)
  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Classes/EventListener/AddressModelRestriction.php
  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Services.yaml

• Add possibility to define one or more query restrictions to manipulate table recipient sources. This way it is now possible to e.g. filter recipient lists coming from tables.

  See here how to use:

  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Site/RecipientSources.yaml (recipientSources:female_tt_address)
  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Classes/Database/Query/Restriction/FemaleRestriction.php
• To make it possible to use a table more than once, a new recipient source confiiguration property table was added. If not set, the identifier is used as table name instead.
• The mail queue is now pausable. This opens the possibility to pause a running delivery to e.g. give another delivery priority.

• A new recipient group type "CSV" was added with additional configuration settings:

  • Type "Plain CSV" and "CSV from file"
  • Field separator
  • Field enclosure
  • First line contains field names, which makes it possible to use every field defined in the extension settings "defaultRecipientFields" or "additionalRecipientFields" as marker
  • CSV file as source (file must be UTF-8 encoded!)
• The bounce mail handling was enhanced to handle recipients from csv and plain lists as well. After deactivate bounced recipients inside the report module, the affected emails will be changed inside there source (recipient group record or csv file) like so: invalid-email@domain.com -> !invalid!--invalid-email[at]domain.com. In this way, any other data for this user is retained. However, it will no longer be used as a recipient due to the invalid email.
• The last step of the Mail Wizard has been expanded to include a new “Exclude recipient groups” selection, which allows to define one or more recipient groups that are to be excluded from a mailing. This makes it possible, for example, to exclude a few people from a larger list in order to prevent them from receiving a specific mailing. This list could be a plain list with just email addresses.

Breaking changes

• Recipient Source Configurations now uses the DTO MEDIAESSENZ\Domain\Model\Dto\RecipientSourceConfigurationDTO.

  Previously the getRecipientSourceConfiguration method of the following events returns an array:

  • ManipulateMarkersEvent
  • ManipulateRecipientEvent
  • DeactivateRecipientEvent

  Please adjust your event listeners to use e.g. $recipientsSourceConfiguration->table instead of $recipientsSourceConfiguration['table']. There is also a custom property available to transfer custom yaml config into event listeners.

  mail:
    recipientSources:
      myCustomDataSource:
        custom:
          foo: bar

  Copied!

  This will be available as $recipientsSourceConfiguration->custom['foo'] in an event listener.

• Plain Lists and CSV recipient groups are now different recipient group types. A migration wizard to convert from the old to new format comes with this version. Attention: Before using the migration wizard please do a database compare, but do not rename or remove the field "csv" in the first step! After the new fields "csv_type", "csv_data", "csv_separator" and "csv_file" have been generated, goto admin tools > upgrade and click on upgrade wizard. Here start the wizard with the title: "EXT:mail: Migrate mail group type plain to plain or new group csv, depending on csv type.". After this, you can safely delete the field "csv" from the tx_mail_domain_model_group database table.

• Mail records now have a status field, which can hold (currently) 5 different states:

  • 0 = DRAFT
  • 1 = SCHEDULED
  • 2 = SENDING
  • 3 = PAUSED
  • 4 = ABORTED
  • 5 = SENT

  There is an update wizard to convert existing mail records. Please do not delete the mail database field "sent" or rename it to "zzz_deleted_sent" before running it once!

  As a side effect, the backend module of the queue now only shows scheduled mails that have not yet been sent.

• For a better bounce mail handling MAIL now uses ddeboer/imap instead of tedivm/fetch. Since ddeboer/imap only can handle IMAP accounts, the possibility to use a POP3 account for collecting bounce mails is dropped. As the mail server type parameter in the bounce mail command is therefore obsolete, it is also deleted. The parameter "count", to set the number of bounce mail to be processed per run, was dropped as well, since it should not be a critical thing, to handle all found bounce mail in one run. Due to this changes, all scheduler task using this command may be corrupt after updating to MAIL 3.0. In dought just recreate them.

New features

• Add ManipulateMailRecipientsEvent to manipulate the array of recipients of a mail after pressing the finish button in the mail wizard.

  This event can be helpful to remove duplicate email recipients comming from multiple selected recipient lists.

  Please note that recipients with the same email may have subscribed to different email categories. If this is the case and a mailing also uses the category function, caution is advised!

New features

• The included NormalizeRecipientData Event Listener now normalizes the name of recipients. If the name field is empty, it now searches for the fields first_name, middle_name and last_name and uses them (combined) as replacements in case they are not empty as well.

• Add an example of how to prevent duplicate sendings using the new ManipulateMailRecipientsEvent introduced with version 3.1.0

  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Classes/EventListener/FilterDuplicateRecipients.php
  • https://gitlab.com/mediaessenz/additional-mail-recipients/-/blob/main/Configuration/Services.yaml

• Enhance the ManipulateFrontendUserRecipients to also normalize the phone field (from telephone) if the source is table

Bug Fixes

• CSV sendings now do not stop after the first sending period anymore
• Recipient data containing null or 0 are now also have this value in there corresponding markers
• The getRecipientsDataByUidListAndModelName, responsible for getting the data of recipients from a model source, now make use of the getEnhancedData method

Bug Fixes & Changes

• Creating and sending mails in other languages then default (0) had some issues which needs to change several files:

  • Templates/Backend/Mail/Index.html (preview modals link changed)
  • ViewHelpers/PreviewLinksViewHelper.php (change way how to get links to translated pages and add page title to return array)
  • Configuration/TCA/tx_mail_domain_model_mail.php (remove 'languageField' => 'sys_language_uid', from the ctrl section, since this field is only used to fetch the right language from a given internal page, not from the mail record it self)
• Make all included viewhelpers future proof by changing them from renderStatic to render

Bug Fixes & Changes

• Improved migration logic by adding checks for record validity and content structure within DirectMailMigration.
• Enhanced documentation with notes on excluding links from tracking.
• Performed bug fixes in UpperCaseMarkers handling.
• Updated dependencies in composer.lock of phar package for TER releases to newer versions for PHP-CSS-Parser and Symfony Polyfills.
• Fix permalinks in documentation guides.xml.
• Refactor ViewHelpers and improve multilingual support.
• Update URL counter logic in ReportService.php

Bug Fixes & Changes

• Add missing link to change log of manual. List of changes can be found under 3.4.0 - 5th June. 2025

Sending Priority Feature

• Add sending priority to the last step of the mail wizard. Mails set to "high" will be send before other mails. At the end of an already running sending cycle, triggered by the scheduler task, a currently running delivery will be paused, until the mail with the higher priority was sent out.
• New page and user TsConfig parameters (defaultSendingPriority, showSendingPriority) are available to set the default priority and show/hide the priority selector. The sending priority selector is set to hidden by default!
• hideExcludeRecipientGroups is now also available as pageTsConfig parameter (mod.web_modules.mail.hideExcludeRecipientGroups)