My email broadcast went to Junk/Spam
Why a test or a real email broadcast can land in the reader's Junk/Spam folder, and the two fixes: send from your own mailbox instead of the shared server, and keep the message itself looking like mail a person wants.
What you see
A test email ("Send test email to yourself") or a real Email broadcast arrives in the reader's Junk/Spam folder instead of their inbox, or does not visibly arrive at all.
Why it happens
Every broadcast that goes out from OmniBrand's shared mail server (the default, when you have not connected your own mailbox under Send from) is sent as no-reply@omnibrand.app, not as your own domain. OmniBrand's own domain has SPF, DKIM and DMARC set up correctly, so the message itself is technically valid mail - but a mail provider still weighs:
- Brand/domain mismatch: the message talks about your business but comes from a domain (
omnibrand.app) the reader has never seen and does not recognise. - New sender reputation: a shared server sending on behalf of many different tenants has a mixed, constantly-changing reputation with mail providers, unlike a mailbox you have used for years.
- Promotional content: coupon codes, "click here" buttons and marketing language are exactly what spam filters are tuned to catch, whatever the sending domain.
- Redirect links: OmniBrand's own click-tracking redirect (
api.omnibrand.app/email/c/…) is a link-shortener pattern some filters distrust; you can turn Count link clicks off in the composer's Tracking section to send links as written instead.
The fix: send from your own mailbox
Under Send from in the composer, pick a connected Microsoft 365 or IMAP/SMTP mailbox instead of the platform's shared server (see Microsoft 365 mailboxes and Any mailbox (IMAP/SMTP) to connect one, then Email broadcasts to pick it). Sent this way:
- The From address is your own mailbox's address, on a domain the reader may already know and trust - the single biggest lever over inbox placement.
- The message carries your mailbox's own sending reputation, built from years of one-to-one mail, not a shared server's.
- Microsoft 365 sends at about 30 messages a minute and 10,000 a day per mailbox; most IMAP/SMTP mailboxes (Gmail, Google Workspace, your host) are more limited - the composer shows the mailbox's own daily limit and how much is left today next to Send from.
- The one-click List-Unsubscribe header Gmail and Yahoo require of bulk senders is kept either way.
If you must keep the shared server
When no mailbox is connected yet, OmniBrand's fallback already does what it can: the From name reads "<your sender name> via OmniBrand" (so the reader sees your name, not just the shared domain), every message carries a proper Message-ID and Date, and a plain-text alternative is always included alongside the HTML - three things spam filters check for on every bulk sender. The composer shows a note under Send from explaining this and suggesting you connect a mailbox.
Beyond the sending domain
- Keep the subject and preview text plain and specific; avoid all-caps, excessive punctuation ("!!!") and words like "free" or "winner" stacked together.
- A Design (block editor) email with real content, images and one clear call to action reads less like a template blast than a wall of promotional text.
- Ask a few known readers to mark the first message Not spam / add your address to contacts - this is the single fastest way a new sender builds trust with a provider.
- A message that keeps landing in Junk despite a connected mailbox may mean that mailbox itself is new or has sent very little mail before; reputation builds over the first few weeks of real use. When the reader's mail server refuses a message outright as spam, the recipient shows Failed in the broadcast's Recipients list with the server's words (for example 550 5.7.1 … rejected as spam). That is about the message or the sender, not the address: the address is not marked bounced and can get your next, improved broadcast.