How a reply gets from an inbox to the community
Jetonomy sends a notification email when someone replies to a member’s topic or reply. That email carries a reply-to address that is unique to the member and the topic. The member replies to it the way they reply to any email.
The message reaches Jetonomy through your inbound webhook or the mailbox it polls. Jetonomy parses it, strips the quoted history and signature, keeps the new text, and creates a community reply attributed to that member. From the member’s side there was one action: type and Send. No browser, no login, no hunting for the thread.
Parsing that keeps the reply clean
Raw email is messy, so Jetonomy is strict about what it keeps. It reads only the plain text part of the message and removes lines that begin with the standard quote marker. Paragraph breaks are preserved, so the reply keeps the structure the member typed.
A signature that follows the standard ”— ” separator line is cut off, and each member can post a limited number of email replies in a short window, so a mail loop cannot flood a thread. Whatever survives parsing goes through the same sanitization every other reply passes, so email is not a way around your content rules.
Safe by design
Open inbound email is an obvious target, so the address itself is the security boundary. Every reply-to address contains a signed token tied to one WordPress user and one topic. Jetonomy checks that token before it writes anything, so an attacker who sees or guesses an address still cannot post as another member, because the token is bound to the real user ID. Tokens expire after 7 days, so an old notification cannot be replied to indefinitely.
Setup is a one-time job: enter your reply domain, then either copy the inbound webhook URL from settings into SendGrid or Mailgun, or enter the IMAP details of the mailbox that receives replies.
