So here’s a gnarly little snag popping up in the Mautic community lately: how do you stop emails with past dates from blasting out to folks who join your campaign late? If you’re on Mautic 4, you might fondly remember the simple savior called “unpublish date.” Set it, and your email wouldn’t send beyond that date—problem solved.
Flash forward to Mautic 5 and 6 — that nifty unpublish date feature has vanished into thin air. No more easy toggle to keep outdated emails from firing off to new contacts. This is a head-scratcher if you’re running automated campaigns spanning weeks or months, where timing matters big time.
Digging into the chatter, it’s clear this change caught a few people off guard. The absence of an explicit “unpublish” option means no built-in safety net. The community hasn’t found a silver bullet in the newer versions or a plug-and-play workaround yet. A quick peek at GitHub didn’t show any official fix or workaround in the pipeline, either — so you’re mostly on your own for now.
What can you do? One practical takeaway is to rethink how you design drip campaigns. Instead of relying on the date baked into an email, use campaign decisions or stages that check the contact’s join time. Basically, add logic in your campaign that branches or skips sending emails to people who enter “too late.” It’s less convenient but gets the job done until Mautic brings back something like the unpublish date feature.
Also, keep your eye on forum threads where users brainstorm ideas—sometimes someone crafts a nifty approach using date conditions or custom fields to simulate the old unpublish function.
Bottom line? If your campaign depends heavily on tight control over email timing, you’ll need to build in extra checks or consider manual intervention for now. It’s a small workflow annoyance but manageable with some clever campaign design.
Curious how others are handling it or want to drop your own tips? Swing by the original forum post here and join the conversation.
