Documentation
Set up RubySig
RubySig stamps email signatures in transit — nothing is installed on user devices and no mailbox delegation is required. Connecting your mail platform takes one administrator and about twenty minutes.
Microsoft 365Microsoft 365 / Exchange OnlineTwo connectors and one transport rule in the Exchange admin center, then a DNS record. Every screen, in order.Start Google WorkspaceGoogle WorkspaceA mail route, a content compliance rule and the SMTP relay service in the Google Admin console, then a DNS record.Start
Getting started
Setup
- Microsoft 365 / Exchange OnlineTwo connectors and one transport rule in the Exchange admin center, then a DNS record. Every screen, in order.
- Google WorkspaceA mail route, a content compliance rule and the SMTP relay service in the Google Admin console, then a DNS record.
- Generic SMTP relayAny mail platform that can route outbound mail through a smart host over TLS, exempt mail by header, and accept it back. Postfix shown in full.
DNS & deliverability
- DKIMRubySig signs mail as your domain. One TXT record publishes the key that lets the world verify it.
- SPF & DMARC alignmentYour platform still delivers, so your SPF still passes. One optional addition covers the return leg.
- Verifying your setupSend one message, read its headers, and know in a minute whether everything works.
Signatures
- Designing a templateStart from a gallery design, set your brand, preview against real directory data, and go live.
- Assigning signatures to usersUsers come from your directory; the live template applies to all of them. What each mailbox gets, and what happens to the ones with no profile.
- Banner campaignsA time-boxed image under every signature — an event, a launch, a notice — designed in the portal and taken down on a date.
- SalesforcePull titles, phone numbers and departments from Salesforce into signatures, and report banner clicks back into Salesforce as campaigns.
Accounts & billing
- Users and seatsA billable mailbox is one that sends through RubySig. How the count is arrived at, where to see it, and how changes are handled.
- Consolidated billingOne invoice for several organizations — for agencies, MSPs and groups — while each keeps its own tenant, directory and templates.
- Staff rolesWho in your organization can sign in to the portal, what they can change, and how that differs from RubySig's own staff.
- Single sign-onLet your staff open the RubySig portal with your own identity provider — Okta, Microsoft Entra ID, Google — instead of a separate password.
Troubleshooting
- Mail deferred or refusedWhat each RubySig SMTP response means, and which ones mean a message is waiting rather than lost.
- DKIM not publishedThe portal says Not published, or received mail shows dkim=none for your domain.
- Mail loopsA message arrives many times, or bounces with "too many hops". The loop guard is missing.