How to build an automatic email newsletter for your MU Online server

A MU Online server portal that relies only on Discord to communicate with players loses reach: not everyone is always online on the server's Discord, and messages in text channels disappear quickly in the flow of conversation. An automatic email newsletter solves this by creating a direct channel that you own — unlike Discord, you don't depend on an algorithm or third-party notifications to reach the player. This tutorial teaches you how to build that newsletter from scratch: collecting emails on the site, choosing a tool, automating sends, and reading metrics to continuously improve engagement.

Why invest in email when Discord already exists

Discord is great for an active real-time community, but has structural limitations for long-term communication: messages disappear in the scroll, players who leave the server's Discord (or mute notifications) simply stop seeing anything, and there's no way to measure open rate or real engagement. Email complements this with an asynchronous channel that the player checks at their own pace, generating measurable data (who opened, who clicked, who never interacted again) — valuable information for deciding where to invest retention effort.

Choosing the sending tool

The choice of tool depends on contact volume and the site's tech stack. A practical comparison:

For portals built with Next.js (common among MU server sites), Resend has the advantage of letting you write email templates as React components, reusing the site's design system.

Setting up the sign-up form on the site

The first step is collecting emails clearly and with explicit consent. Place the form in strategic spots across the portal:

• Site footer, visible on every page.
• A light, non-intrusive pop-up after a few seconds of browsing, offering something of value (e.g., "get notified about new events and resets").
• A dedicated sign-up page, linked in the main menu and on Discord.

An example of a simple form integrated via the Resend API in a Next.js server route:

// app/api/newsletter/route.js
import { Resend } from 'resend';

const resend = new Resend(process.env.RESEND_API_KEY);

export async function POST(request) {
  const { email } = await request.json();

  if (!email || !email.includes('@')) {
    return Response.json({ error: 'E-mail inválido' }, { status: 400 });
  }

  await resend.contacts.create({
    email,
    audienceId: process.env.RESEND_AUDIENCE_ID,
  });

  return Response.json({ success: true });
}

Always include an explicit consent checkbox next to the email field, making clear what the player is agreeing to receive.

Domain authentication: SPF, DKIM, and DMARC

Before sending any email at volume, set up domain authentication — without it, most emails land straight in spam or get rejected. The three essential DNS records:

Most email marketing tools (Resend, Brevo, Mailchimp) provide the exact values for these records in the domain configuration panel — just add them to your domain's DNS.

Structuring the newsletter content

A MU Online server newsletter engages better when it follows a predictable structure that the player learns to expect:

1. Highlight of the week: special event, new reset, or the most impactful update.
2. Patch notes summary: balance changes, new items, bug fixes.
3. Weekly event calendar: Castle Siege, Invasion, and special event times.
4. Community spotlight: rankings, featured guild, a clip or screenshot sent by a player.
5. Call to action: invite to Discord, the shop, or a specific event.

Keeping this fixed structure reduces production time for each edition and builds familiarity with readers.

Automating the send

The goal is to not depend on manual sending every week. Two practical approaches:

• Fixed-schedule automation: set up a workflow in the email marketing tool to send every Friday at 6 PM, pulling content from a draft prepared during the week.
• Content-trigger automation (webhook): connect the site's CMS (e.g., when a new "patch notes" post is published) to a webhook that automatically sends a summary email to the list, without waiting for the weekly cycle.

An example webhook flow: the CMS publishes the post → sends a request to a site API route → that route calls the email marketing tool's API → the email is sent to the segmented "patch alerts" list.

Segmenting the contact list

Not every player wants every type of content. Segmenting the list boosts relevance and reduces unsubscribes:

This segmentation can be done via tags applied at sign-up (a simple question in the form) or by behavior (previous clicks on certain link types).

Metrics that actually matter

Tracking just the number of subscribers isn't enough — the metrics that indicate the real health of the newsletter are:

If the open rate drops consistently, review the email subject lines and sending frequency before assuming the content itself is the problem.

Common errors and fixes

Automatic newsletter checklist

• Email marketing tool chosen and account configured.
• Sign-up form with explicit consent on the site.
• SPF, DKIM, and DMARC records configured on the domain.
• Fixed content structure defined for each edition.
• Send automation configured (fixed schedule or webhook).
• Basic list segmentation implemented.
• Open, click, and unsubscribe metrics being tracked.

With the automated newsletter running, the natural next step is to expand the server's retention channels by combining email with real-time notifications — it's worth checking out the MU Online server setup tutorial to review the overall portal structure this communication relies on.

Frequently asked questions