zintara.io

Campaign operations · Practical guide

Plain-text campaign preview: distinguish simple formatting from the MIME format

A message that looks like plain text is not necessarily sent as text/plain. Zintara's current mailer sends the campaign body as HTML, so verify the delivered message rather than inferring format from the editor.

Reviewed · Examples are illustrative

Who this helps: Operators reviewing campaign retirement, rendering, threading and responsibility changes.

Define the decision

Simple formatting can help a message remain readable, but the underlying content type is a separate technical property. In the current implementation, the ordinary body uses text/html; attachments use a multipart message with an HTML body part. This guide does not claim that a plain-text alternative is automatically generated.

Work through the procedure

  1. Prepare a simple message with short paragraphs and the required identity and stop information.
  2. Preview realistic and missing variable values.
  3. Send a controlled test to an authorized mailbox and inspect both rendering and message source.
  4. Check line breaks, links, signature and content type before describing the message format to others.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Editor appearance: short unstyled paragraphs
Delivered source in the current implementation: Content-Type: text/html; charset=UTF-8
Correct description: a simply formatted HTML message
Unverified claim to avoid: a multipart plain-text alternative exists
If text/plain is a requirement, verify support before choosing this sending path.

Read the result

The distinction prevents a styling preference from becoming a false technical claim. A readable test also does not prove that every client will render the message identically. Review the clients relevant to the actual workflow and preserve any observed defect for repair.

Check before moving on

  1. Inspect the final signature and automatic additions.
  2. Do not assume line breaks in source text render as intended in HTML.
  3. Keep content-format claims separate from deliverability promises.

Limits and next action

This guide describes current mailer behavior, not a guarantee that HTML or plain text will perform better. Zintara does not presently promise automatic plain-text MIME alternatives through this workflow. Recheck the implementation after format-related updates.

Source: Zintara product context; procedures and examples are editorial guidance

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.

Related guides

Explore the Zintara workflow