.. include:: /Includes.rst.txt

.. _extension-configuration:

=======================
Extension Configuration
=======================

Some general settings can be configured in the Extension Configuration.

#. Go to :guilabel:`Admin Tools > Settings > Extension Configuration`
#. Choose :guilabel:`mail`

The settings are divided into several tabs and described here in detail:

.. only:: html

   .. contents:: Properties
        :local:
        :depth: 2

Mail
====

.. _extension-configuration-default-recipient-fields:

Default recipient fields `defaultRecipientFields`
-------------------------------------------------

.. confval:: defaultRecipientFields

   :type: string
   :Default: uid, salutation, name, title, email, phone, www, address, company, city, zip, country, fax, firstname, first_name, last_name

   Default (comma separated) fields will be available by markers in a mail message. e.g. name as ###USER_name### or ###USER_NAME### filled with (uppercase) value of the user.

.. _extension-configuration-additional-recipient-fields:

Additional DB fields of the recipient `additionalRecipientFields`
-----------------------------------------------------------------

.. confval:: additionalRecipientFields

   :type: string
   :Default:

   Additional (comma separated) fields that may be substituted in the mail messages.

.. _extension-configuration-mail-page-type-number:

MAIL page type number `mailPageTypeNumber`
------------------------------------------

.. confval:: mailPageTypeNumber

   :type: int
   :Default: 24

   Change this number only if another extension use the same.

.. _extension-configuration-mail-module-position:

MAIL modules position in the side navigation `mailModulePosition`
-----------------------------------------------------------------

.. confval:: mailModulePosition

   :type: string
   :Default: after:web

   If set to empty, the module will move to the end of all other modules

.. _extension-configuration-mail-module-page-id:

MAIL module page id `mailModulePageId`
-----------------------------------------------------------------

.. confval:: mailModulePageId

   :type: int
   :Default:

   If set, page tree navigation will be hidden in MAIL module. Here you can add the uid of the MAIL sys-folder if you only have one.

Feature
=======

.. _extension-configuration-delete-unused-markers:

Delete unused markers in personalized mails `deleteUnusedMarkers`
-----------------------------------------------------------------

.. confval:: deleteUnusedMarkers

   :type: bool
   :Default: 1

   All markers/placeholder without corresponding recipient data will remove from personalized mails.

.. _extension-configuration-notification-job:

Enable notification mail `notificationJob`
-----------------------------------------

.. confval:: notificationJob

   :type: bool
   :Default: 1

   Allow MAIL to send notification about start and end of a mailing job.

.. _extension-configuration-deactivate-categories:

Deactivate categories `deactivateCategories`
--------------------------------------------

.. confval:: deactivateCategories

   :type: bool
   :Default: 0

   Attention: If set, ALL category fields inside tt_content,fe_users,tt_address,tx_mail_domain_model_group will be disabled!

.. _extension-configuration-use-http-to-fetch:

Use http connection for fetching Newsletter-Content `useHttpToFetch`
--------------------------------------------------------------------

.. confval:: useHttpToFetch

   :type: bool
   :Default: 0

   Even if your TYPO3 Backend is in SSL-Mode, the URL for fetching the newsletter contents will be http

Direct Mail Migration
=====================

.. _extension-configuration-direct-mail-category-sys-category-mapping:

Mapping sys_dmail_category -> sys_category `directMailCategorySysCategoryMapping`
---------------------------------------------------------------------------------

.. confval:: directMailCategorySysCategoryMapping

   :type: string
   :Default:

   Used by update wizard to migrate Direct Mail records to MAIL records.
   Format: 1:2,2:3,3:4 maps Direct mail category 1 to sys_category 2 and Direct mail category 2 to sys_category 3 and so on. If categories not found or set, new categories will be added.

.. _extension-configuration-direct-mail-category-sys-category-parent-category:

Parent sys_category used by sys_dmail_category -> sys_category migration `directMailCategorySysCategoryParentCategory`
----------------------------------------------------------------------------------------------------------------------

.. confval:: directMailCategorySysCategoryParentCategory

   :type: int
   :Default:

   If the migrated categories should be attached to a parent sys_category.