<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Relayly Changelog</title>
    <link>https://relayly.io/changelog</link>
    <description>What's new at Relayly — every notable shipping moment.</description>
    <language>en-us</language>
    <atom:link href="https://relayly.io/changelog.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Fri, 08 May 2026 10:00:00 +0000</lastBuildDate>

    <item>
      <title>Email verification banner + forgot password flow</title>
      <link>https://relayly.io/changelog#2026-05-08</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-08-verify-banner</guid>
      <pubDate>Fri, 08 May 2026 10:00:00 +0000</pubDate>
      <description>Customer dashboard now shows a yellow verification banner above every page until you've clicked the verification link. Forgot-password and self-serve reset flow ship at the same time, plus 2FA enrollment in Settings → Security.</description>
    </item>

    <item>
      <title>Per-container memory limits + watchdog v2</title>
      <link>https://relayly.io/changelog#2026-05-07</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-07-resilience</guid>
      <pubDate>Thu, 07 May 2026 10:00:00 +0000</pubDate>
      <description>Every production service now has mem_limit, healthcheck, and restart=unless-stopped. A per-minute watchdog cron tails Docker for unhealthy/exited/restarting states and auto-recovers. Compose images pinned to specific minor versions.</description>
    </item>

    <item>
      <title>32 MB inbound message size limit</title>
      <link>https://relayly.io/changelog#2026-05-07</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-07-32mb</guid>
      <pubDate>Thu, 07 May 2026 09:00:00 +0000</pubDate>
      <description>Cloudflare Email Worker → /v1/inbound was rejecting messages above 8 MB. Real Gmail forwards routinely exceed that. Bumped to 32 MB after CF Analytics confirmed all errors were size-related.</description>
    </item>

    <item>
      <title>Klaviyo migration toolkit</title>
      <link>https://relayly.io/changelog#2026-05-06</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-06-klaviyo</guid>
      <pubDate>Wed, 06 May 2026 10:00:00 +0000</pubDate>
      <description>One script, end-to-end. Reads Klaviyo's REST API and writes ready-to-import CSVs + SQL for lists, profiles, list memberships, segments (predicate-translated), templates, and campaigns.</description>
    </item>

    <item>
      <title>Multi-provider import (Mailchimp, SendGrid, Klaviyo, Constant Contact, ActiveCampaign, HubSpot)</title>
      <link>https://relayly.io/changelog#2026-05-05</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-05-multi-import</guid>
      <pubDate>Tue, 05 May 2026 10:00:00 +0000</pubDate>
      <description>Auto-detects competitor CSV shapes and normalizes into Relayly's schema. Idempotent — re-runs deduplicate via (account_id, email).</description>
    </item>

    <item>
      <title>RFC 8058 one-click List-Unsubscribe — on every send</title>
      <link>https://relayly.io/changelog#2026-05-04</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-04-rfc8058</guid>
      <pubDate>Mon, 04 May 2026 10:00:00 +0000</pubDate>
      <description>Gmail and Yahoo's bulk-sender requirements (5,000+ emails/day) now mandate one-click unsubscribe. Every Relayly send now carries List-Unsubscribe-Post by default.</description>
    </item>

    <item>
      <title>Custom Return-Path + tracking domains per customer</title>
      <link>https://relayly.io/changelog#2026-05-02</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-02-return-path</guid>
      <pubDate>Sat, 02 May 2026 10:00:00 +0000</pubDate>
      <description>Stronger DMARC alignment by routing bounces through your own subdomain. Set up via Domains → DNS → Advanced with a single CNAME.</description>
    </item>

    <item>
      <title>Dedicated IP marketplace + OVH rDNS automation</title>
      <link>https://relayly.io/changelog#2026-05-01</link>
      <guid isPermaLink="false">relayly-changelog-2026-05-01-ip-marketplace</guid>
      <pubDate>Fri, 01 May 2026 10:00:00 +0000</pubDate>
      <description>Order a dedicated IP from the Scale dashboard. We provision the IP, set rDNS, add it to your warmup pool, and start the 14-day curve. Median time from click to first send: 4 minutes.</description>
    </item>

    <item>
      <title>SAML 2.0 + OIDC SSO + SCIM 2.0</title>
      <link>https://relayly.io/changelog#2026-04-28</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-28-sso</guid>
      <pubDate>Tue, 28 Apr 2026 10:00:00 +0000</pubDate>
      <description>Enterprise-tier identity. SAML XML-DSig signature verification, OIDC JWKS-based id_token verification, SCIM 2.0 user provisioning. Tested against Okta, Azure AD, and Google Workspace.</description>
    </item>

    <item>
      <title>Drag-drop email designer (MJML-based)</title>
      <link>https://relayly.io/changelog#2026-04-25</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-25-designer</guid>
      <pubDate>Sat, 25 Apr 2026 10:00:00 +0000</pubDate>
      <description>The block editor everyone expected. Output is MJML, which compiles to email-safe HTML at send time.</description>
    </item>

    <item>
      <title>Send-time optimisation — per-recipient best hour</title>
      <link>https://relayly.io/changelog#2026-04-22</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-22-sto</guid>
      <pubDate>Wed, 22 Apr 2026 10:00:00 +0000</pubDate>
      <description>Marketing campaigns now learn each recipient's best engagement window.</description>
    </item>

    <item>
      <title>Predicate-based segments</title>
      <link>https://relayly.io/changelog#2026-04-19</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-19-segments</guid>
      <pubDate>Sun, 19 Apr 2026 10:00:00 +0000</pubDate>
      <description>JSON-DSL segments. Saved segments evaluate live against your contact base; campaigns target the live count, not a frozen snapshot.</description>
    </item>

    <item>
      <title>FBL ingest — Yahoo CFL, Microsoft JMRP, Google Postmaster</title>
      <link>https://relayly.io/changelog#2026-04-15</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-15-fbl</guid>
      <pubDate>Wed, 15 Apr 2026 10:00:00 +0000</pubDate>
      <description>Spam complaints from major providers now flow into the suppression list within minutes.</description>
    </item>

    <item>
      <title>MTA-STS + TLS-RPT publishing</title>
      <link>https://relayly.io/changelog#2026-04-12</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-12-mtasts</guid>
      <pubDate>Sun, 12 Apr 2026 10:00:00 +0000</pubDate>
      <description>Auto-publishes mta-sts.relayly.io policy and _smtp._tls TLS-RPT records — zero customer action required.</description>
    </item>

    <item>
      <title>Provider-aware routing GA</title>
      <link>https://relayly.io/changelog#2026-04-08</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-08-provider-routing</guid>
      <pubDate>Wed, 08 Apr 2026 10:00:00 +0000</pubDate>
      <description>The deliverability brain. Mailbox-provider classifier + per-(IP × domain × provider) reputation tracking + auto-routing around throttled IPs.</description>
    </item>

    <item>
      <title>BHS Canada region online</title>
      <link>https://relayly.io/changelog#2026-04-01</link>
      <guid isPermaLink="false">relayly-changelog-2026-04-01-bhs</guid>
      <pubDate>Wed, 01 Apr 2026 10:00:00 +0000</pubDate>
      <description>Second region: OVH BHS, Quebec. Per-send region pinning available from today.</description>
    </item>

    <item>
      <title>v1 launch</title>
      <link>https://relayly.io/changelog#2026-03-15</link>
      <guid isPermaLink="false">relayly-changelog-2026-03-15-v1</guid>
      <pubDate>Sun, 15 Mar 2026 10:00:00 +0000</pubDate>
      <description>The first send. POST /v1/email/send, smtp.relayly.io:587, customer dashboard, webhooks, free tier, four pricing tiers.</description>
    </item>

  </channel>
</rss>
