Manually overwrite the list-unsubscribe header

As mentioned previously, the information in the list-unsubscribe header set by default by Inxmail Professional refers to the correct execution of unsubscriptions in Inxmail Professional.

If you are using a third-party system and leave the list-unsubscribe header that is set as standard, then unsubscriptions via the list-unsubscribe header will be processed in Inxmail Professional but not in your third-party system. It is therefore possible that unsubscriptions via the unsubscribe link integrated in your newsletter are processed (correctly) in your CRM system, but that the unsubscriptions via the list-unsubscribe header are not recognised by your CRM system. In the worst case, this can lead to you sending mailings again to recipients who have used the list-unsubscribe header to unsubscribe.

No action required for Salesforce and Microsoft CRM

The Inxmail Professional Email Marketing for Salesforce and Inxmail Professional for Microsoft Dynamics integrations automatically read out the unsubscriptions received in Inxmail Professional and synchronise them.

Action required for third-party systems without automatic synchronisation

If you are using a third-party system that does not perform an automatic synchronisation of unsubscriptions with Inxmail Professional, you must ensure that the information in the list-unsubscribe header triggers an unsubscription in your third-party system. (Just like the unsubscribe link included in the newsletter triggers an unsubscription in your third-party system.) You must therefore manually enter a list-unsubscribe header that replaces and overwrites the list-unsubscribe header set as standard by Inxmail Professional.

The following describes how to enter a list-unsubscribe header manually in Inxmail Professional.

Note: The following contains more detailed information on creating the lists-unsubscribe headers. Your third party system may also require more specific details or parameters. It is also possible that your unsubscription links require special syntax.  In these cases, it may be necessary to contact the manufacturer of your third-party system or the associated service provider.