Forwarding TB verification codes from Gmail

Total Battle occasionally interrupts a bot login with a verification-code email. To keep the harvester 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 the harvester encounters a verification prompt, it 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 the harvester repeatedly times out on verification, the forwarding rule probably isn’t firing. Send a test email manually from a different account to your bot mailbox with subject “verification 123456” — your inbound audit log will show a rejected_sender / inner_from_mismatch event, which proves the forward rule is wired up. If you see no event at all, the filter conditions don’t match the test email; tighten them.

Other mailbox providers

v1 supports Gmail explicitly. Other providers (Outlook, Proton, Yahoo) all expose forwarding rules; the platform doesn’t care which one you use as long as the envelope-from of forwarded mail equals the bot email you registered. If you’d like to use a provider we don’t yet have screenshots for, the steps above — forward TB’s notification address, optionally archive/delete the original — apply identically; only the UI for setting it up differs.