Forwarding TB verification codes from Gmail

Total Battle occasionally interrupts a login with a verification-code email. To keep our service running unattended, set up an auto-forward rule on your bot mailbox so those codes land at your clan’s inbound address - the platform reads them from there and submits them on the bot’s behalf.

You only need to do this once. Your clan’s inbound address is shown on your bot-setup page with a copy button.

Note: Using Gmail requires actions from the admin team. Reach out via Discord for them to approve the confirmation code.

1. Add the forwarding address

1. Sign in to the bot Gmail mailbox.
2. Click the gear icon → See all settings.
3. Open the Forwarding and POP/IMAP tab.
4. Click Add a forwarding address. Paste your clan’s inbound address (the one ending in our inbound subdomain) and click Next.
5. Gmail sends a confirmation code to that address. Open the confirmation by following the link Gmail sends back to your bot mailbox.
6. Back in the Forwarding tab, refresh; Gmail now lists the address as confirmed.Leave forwarding itself set to “Disable forwarding” - the filter you set up next does selective forwarding only for TB’s emails, not your entire inbox.

2. Filter TB verification mail to that address

1. Open the Filters and Blocked Addresses tab.
2. Click Create a new filter.
3. In the From field, enter noreply@totalbattle.com. In the Subject field, enter Here’s your verification code!. Click Create filter.
4. Tick Forward it to: and choose the address you confirmed in step 1.
5. Click Create filter.

3. Verify it works

The next time our services encounter a verification prompt, they will wait up to five minutes for the forwarded code to arrive. You can confirm activity in the operator console under the verification-activity panel for your clan; expect to see a received event followed by consumed within seconds of TB sending the email.

If our services repeatedly time out on verification, the forwarding rule probably isn’t firing. To prove the pipe itself works, temporarily widen the filter (or forward one message by hand) so a non-TB email reaches your inbound address - your inbound audit log will show a rejected_sender / sender_not_allowed event, which confirms mail is arriving and being gated. If you see no event at all, nothing is reaching us; check the forwarding address is confirmed and the filter conditions match TB’s emails.

Other mailbox providers

Any mailbox provider with a forwarding rule works - Gmail, Outlook / Microsoft 365, Proton, Yahoo, iCloud, or a self-hosted mailbox with a .forward file. The platform doesn’t parse the forward’s structure or care how your provider rewrites the envelope; it only needs Total Battle’s sender address to appear somewhere in the forwarded message, which every forward style preserves. Forwarding as an attachment, localized mail clients, and HTML-only forwards are all fine. The steps above - forward TB’s notification address to your clan’s inbound address, optionally archive/delete the original - apply identically; only the UI for setting it up differs.

One thing to keep tight: filter on TB’s sender rather than forwarding your whole inbox. Unrelated one-time-code emails are rejected rather than used as codes, but a narrow rule keeps your audit log clean.