Knowledge base

render-enabled verifiedimportantWritten by the Hub

Email preview module

in the configuration this is a linerender-enabled: …

Whether the console may display fully rendered messages taken from the live stream.

Values

Values
true · false
applying
restart required
where it can be set
in the config file · with a startup flag · as an environment variable

In detail

The module shows real customer mail, rendered, in the operator's browser. That is genuinely useful for finding out why a campaign looks wrong — and it carries two costs that are easy to miss. The browser loads the images in the message, and in bulk mail those images are tracking pixels: opening a message here registers as the recipient opening it, and the customer's open rate is quietly wrong. And the module exposes message content — including personal data of the customer's recipients — to anyone with console access. The console has a message for the case where this is switched off ("disabled by the MailerQ configuration"), so the ability to turn it off is real and visible in the interface.

What happens if you get it wrong

Left enabled on a node sending tracked campaigns.Every message opened in the panel counts as an open in the customer's statistics, from the operator's address rather than the recipient's.from the documentation · inference
Left enabled where console access is broad.Recipient names, addresses and message contents are readable by everyone who can log in.inference · inference