• Hello,

    Thank you for your reply.

    I understand that this requires confirmation from the technical support team.

    Could you please check specifically how MailPoet handles custom SMTP headers when using an external SMTP provider?

    My setup is:

    MailPoet → Custom SMTP → Mailjet

    I need MailPoet to send these two headers on transactional emails:

    X-Mailjet-TrackOpen: 0
    X-Mailjet-TrackClick: 0

    Mailjet has confirmed that these headers are the supported way to disable open and click tracking on individual SMTP emails.

    Could your technical team please confirm the following:

    1. Does MailPoet preserve custom headers added to WordPress transactional emails when those emails are routed through MailPoet’s configured SMTP method?
    2. Does MailPoet remove or rebuild the email headers before passing the message to the SMTP provider?
    3. Is there an existing MailPoet filter or hook that allows adding custom SMTP headers specifically to transactional/site emails?
    4. If MailPoet does not support this, is it possible to configure MailPoet so that:
      • MailPoet newsletters continue to use Mailjet SMTP
      • WordPress transactional emails bypass MailPoet and are sent through a separate SMTP configuration?

    The goal is simply:

    • Marketing emails: Mailjet tracking enabled
    • Transactional emails: Mailjet tracking disabled

    Mailjet support has confirmed that this separation can be achieved through the X-Mailjet headers, provided the SMTP application passes them correctly.

    Thank you for checking this with the technical team.

Viewing 1 replies (of 1 total)
  • Plugin Author Bruna a11n

    (@bruberries)

    Hi @fly_in_the_sky,

    I believe your plan works, and it’s the right way to get per-message Mailjet tracking control. MailPoet keeps two sending settings that operate independently, so you can split the two email streams exactly as you described:

    Newsletters stay on Mailjet through MailPoet. This is controlled under MailPoet > Settings > Send With…, and nothing below changes it.

    Under MailPoet > Settings > Advanced > Send all site’s emails with…, choose The default WordPress sending method. In this mode MailPoet steps out of your site’s transactional email entirely and hands it back to WordPress’s built-in wp_mail() function.

    Because transactional emails now flow through wp_mail(), a separate SMTP plugin can take them over and apply its own SMTP connection and headers, including the Mailjet X-Mailjet-TrackOpen and X-Mailjet-TrackClick headers.

    Two things to keep an eye on:
    1. Make sure only one plugin is handling the transactional (wp_mail) side. With “The default WordPress sending method” selected, MailPoet is no longer intercepting those emails, so your chosen SMTP plugin should be the only thing hooking wp_mail(). Otherwise the headers may not apply predictably.
    2. Adding the tracking headers is a function of that second SMTP plugin, not of MailPoet. So configure the Mailjet header rules there. Since that plugin is developed by a third party, we’re not able to help with its specific setup, but the plugin’s own developer can assist with where to add those headers.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.