Elysia Tools
Navigation
Workflow Playbook
Validate recipients, inspect domain and DNS signals, encode MIME-safe content, add tracking parameters, and package a pre-send handoff artifact.
Hubs
Pull the actual addresses and outgoing URLs from the draft source instead of relying on a copied summary. Validate individual addresses or run a batch pass, then isolate malformed entries before the message package is assembled. This keeps the pre-send package tied to the real list that will move downstream.
Extract the sender and landing domains, inspect DNS answers, and record visible ownership context. If a domain uses internationalized labels, convert it to punycode for transport-safe handling and keep the decoded form for reviewers. These checks help document whether the campaign references technically coherent domains, but they do not prove that mailbox providers will accept or place the email.
Build a reviewable RFC 2822 style representation, apply quoted-printable where the content needs a MIME-safe textual encoding, and identify the types of attached or referenced assets. Standardize tracking parameters across outgoing links or audit the existing ones for drift. When the sending team needs a portable review artifact, render the HTML draft to PDF and hand off the package with explicit limits: this workflow prepares a send and documents it, but it does not execute the send or certify deliverability.
Workflow playbook
Pull addresses and referenced URLs from the provided draft, spreadsheet export, or copied source, then validate the recipient set before any MIME work begins.
Extract sender and landing domains, review DNS answers and registration context, and normalize any internationalized domains for transport-safe handling.
Convert headers or body fragments into RFC 2822 compatible structure, apply quoted-printable where needed, and identify the MIME types of files or assets included in the handoff.
Standardize campaign parameters on outgoing URLs or extract existing parameters to confirm naming, values, and duplication before release.
Render an HTML email draft to PDF when a shareable review artifact is required, then package the validated recipients, DNS notes, MIME decisions, tracking map, and explicit pre-send limitations for the sending team.
Use email-validator for one address or a small sample. Use batch-email-validator after extracting addresses from a larger source and de-duplicating the working list.
If the sender domain or linked host contains non-ASCII labels, convert with punycode-encoder for transport-safe use and keep punycode-decoder available for human review.
Use url-parameter-builder when campaign parameters are missing or inconsistent. Use bulk-url-extractor and url-parameter-extractor when links already exist and must be checked before handoff.